A small piece of HTML can change what a visitor sees or how the browser understands a page. In this lesson, you will explore link prefetch and speculative navigation using a short example that you can inspect and change.
The Idea in Plain English
Prefetch offers a low-priority hint to fetch something that might help with a future navigation. Browsers may ignore it depending on bandwidth, privacy settings and their own priorities.
You can test this using a small local HTML file. Change one part at a time and check the result in the browser before adding more code.
A Working Example
Read the sample once before copying it. Notice the element names and attribute values, then compare them with the explanation below.
<head>
<link rel="prefetch" href="/next-lesson.html" as="document">
</head>What Each Part Does
- The link element declares a relationship such as a stylesheet or alternate language.
- The head holds page metadata, not the visible lesson content.
- rel describes the relationship between the current page and a linked resource.
- href is the URL or fragment destination of a link.
The current page does not change. On some visits, a future page or asset may load faster.
Keep the example small while learning. Once it behaves as expected, try it inside a larger page and make sure the URLs, files and surrounding HTML are correct.
Try It Yourself
Try this next: create one complete head or structured content example focused on Link Prefetch and Speculative Navigation, including a working example and an incorrect example to correct. Then inspect the page and explain what changed.
Common Beginner Mistakes
- Using prefetch for a resource required to render the current page; preload is the more appropriate hint there.
- Changing several parts of the example at once, making it difficult to see which part caused a different result.
- Choosing a tag only because its default appearance looks right, without checking whether it describes the content correctly.
Key Takeaways
- Prefetch offers a low-priority hint to fetch something that might help with a future navigation. Browsers may ignore it depending on bandwidth, privacy settings and their own priorities.
- The current page does not change. On some visits, a future page or asset may load faster.
- Test the markup in a browser, and check accessibility and real-world behavior where relevant.