HTML Prerender and Navigation Privacy Considerations

A small piece of HTML can change what a visitor sees or how the browser understands a page. In this lesson, you will explore prerender and navigation privacy considerations using a short example that you can inspect and change.

The Idea in Plain English

Speculation rules allow compatible browsers to prepare likely future navigations, but prerendering can have privacy, server-load and side-effect implications. Not every browser honors the rules.

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.

<script type="speculationrules">
{
    "prefetch": [{
        "urls": ["/lesson-2.html"]
    }]
}
</script>

What Each Part Does

The script element can load code or hold data; the type attribute tells the browser how to treat its contents.
type chooses the relevant kind of script, input, media or embedded object.

A browser may preload or prerender a likely next page, but normal navigation must still work without the hint.

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: demonstrate a safe and an unsafe snippet and validate behavior focused on HTML Prerender and Navigation Privacy Considerations, including a working example and an incorrect example to correct. Then inspect the page and explain what changed.

Common Beginner Mistakes

Prerendering pages that trigger state changes or contain sensitive content.
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

Speculation rules allow compatible browsers to prepare likely future navigations, but prerendering can have privacy, server-load and side-effect implications. Not every browser honors the rules.
A browser may preload or prerender a likely next page, but normal navigation must still work without the hint.
Test the markup in a browser, and check accessibility and real-world behavior where relevant.