First-view performance

Above The Fold Asset Checklist

List the CSS, fonts, images, and scripts in the first view, then score blocking, lazy heroes, font loading, and third-party risk before publish.

Waiting0/100

Assets0

Blocking0

Third party0

Open critical0

Page details

Describe the page you are reviewing so the export is usable in handoff.

Page namePage typePrimary viewport

Notes

Details, HTML, and the asset list stay in this browser.

HTML snapshot

Optional. Paste the document head and first-view markup, then extract assets.

First-view resource list

Edit extracted rows or add assets by hand. Size is optional and used for image budget checks.

Extract HTML or add an asset to start the inventory.

Inventory risks

Heuristic signals from the resource list. They are not a lab Lighthouse run.

Add assets to score first-view risks.

Manual first-view checks

Confirm what HTML cannot prove: fetchpriority, font-display, inlined CSS, and delayed widgets.

The LCP hero is identifiedCriticalYou know which image or text block is the LCP element on mobile and desktop.The hero is not lazy-loadedCriticalThe LCP image uses eager loading and is not behind a carousel or client-only mount.The hero meets a size budgetCriticalThe displayed hero is compressed and sized close to CSS × DPR, usually well under 150–200 KB.Fonts use font-displayCriticalFirst-view fonts set font-display to swap or optional so text stays visible.Critical fonts are preloadedRecommendedOnly the first-view font files are preloaded, with matching type and crossorigin.First-view CSS is limitedCriticalCritical CSS is small or inlined; unused framework CSS is not all render-blocking.Non-critical JS is deferredCriticalApp, analytics, and A/B scripts use defer, async, or load after first paint.Chat and tags are delayedRecommendedChat widgets, heatmaps, and extra pixels do not load on the first view.