Vahan Petrosyan
Language · English

Site Speed Audit

A site speed audit examines how quickly the main content appears, how promptly the page responds and whether the layout moves while someone reads. Core Web Vitals describe these experiences through LCP, INP and CLS. Field data identifies affected visitors where available. Browser traces help explain what the page was doing at the time.

What you get

  • A mobile and desktop baseline for representative page types.
  • Browser traces identifying the image, script or layout change behind a delay.
  • Prioritized fixes with a repeatable test and a plan for checking field results.

Who it's for

  • Visitors wait for a hero image or a navigation control to respond.
  • A lab score improved but real-user performance remains poor.

How it works

  1. Select the sample

    Group URLs by template and identify where real-user data is available.

  2. Record the delay

    Capture loading and interaction traces under controlled conditions.

  3. Measure the change

    Repeat the lab test and follow field metrics as new visits enter the reporting window.

Related articles

All articles

Contact

Frequently asked questions

Why do Lighthouse and real-user results differ?

A lab run uses one device profile and set of conditions. Field data includes actual devices, networks and interactions over time. Each answers a different question.

What if a page has too little field data?

The report labels any origin-level data and uses repeatable lab measurements for the page. Origin data is never presented as a measurement of that specific URL.

Which Core Web Vital should we fix first?

Start with the failing metric on a template that matters to users. Its trace helps distinguish an image-loading delay from a slow interaction or a shifting element.