Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when reviewing templates, rendered HTML, or shared components related to Add resource hints (preload, prefetch, dns-prefetch). Validate the final browser-facing markup, not just the source framework abstraction.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | -13% | 0% |
| case-03 | ✓→✓ | = Same ✓ | 41% | 0% |
| case-04 | ✓→✓ | = Same ✓ | -12% | 0% |
| case-05 | ✓→✓ | = Same ✓ | -3% | 0% |
| case-06 | ✓→✓ | = Same ✓ | 24% | 0% |
The browser's HTML parser discovers resources sequentially — a font referenced in a CSS file won't be fetched until the CSS is parsed. Resource hints break this dependency chain, allowing the browser to start fetching critical resources in parallel with parsing. A single preload directive for a critical font can eliminate a 100–300ms Flash of Invisible Text.
Look at this HTML file for late-discovered critical resources — fonts referenced in CSS, hero images, and key scripts. Identify where preload or preconnect hints would help.
Add appropriate preload hints for critical fonts, images, and scripts. Add preconnect for third-party domains used early in the page.
Explain each resource hint type (preload, prefetch, preconnect, dns-prefetch), when to use each, and the consequences of misusing them.
Review templates, server-rendered HTML, and shared components that output markup related to Add resource hints (preload, prefetch, dns-prefetch). Flag exact elements, attributes, and routes where the rendered HTML violates the rule.
For full implementation details, code examples, and framework-specific guidance, see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/html/html-resource-hints
Other measured skills in the registry, with their headline benchmark lift.