An experiment implementing the PRPL pattern with HTML files.
Visit the deployed site to get a feel for how the mechanism works.
Typically this pattern is used to prefetch things like JavaScript bundles or JSON required to construct the DOM for the next page. I thought it might be interesting to boil it down further and prefetch the actual html of the next page.
- Initial html file is loaded by the browser
- After the page is loaded, we grab an achor tag that points to another html file and fetch it
- After that page is fetched, we save the html string in local storage
- Still on the initial html file, we add an event listener to listen for clicks on that anchor tag
- When a user clicks on that anchor tag, we tell the browser not to load it normally. Then, we take the
hrefattribute and get the item we fetched earlier in local storage. - Now that we have the html string for the file we want to navigate to, we use the DOMParser interface to parse it into a document
- Finally, we replace the current document body with the target document body
- Using local storage needs further consideration:
- Storage item size
- Number of storage items
- Read/write speed
- Sites or users that disable local storage
- Should use a smarter technique to determine which links to prefetch and when to do it
- Should do the prefetch in a worker to offload work to another thread