Compare website speed
Put your page next to up to four competitors. Same device, same test, one table, with the winner of each metric marked.
How to read a speed comparison
A single lab run can swing by 5–10 Lighthouse points, so don’t declare a winner on a two-point gap. Look for differences that hold up: an LCP that is a full second slower, a CLS that is in a different band, or a Total Blocking Time several times higher than your competitors’.
Real-user rows come from the Chrome UX Report and reflect each site’s actual audience. A competitor with fast field data but a mediocre lab score often has a quick CDN and returning visitors with warm caches, which is a strategy you can copy.
Found a gap? The guides on LCP, INP and CLS show what moves each number.
Questions people ask
How many sites can I compare?
Up to five: your own page plus four competitors. Each site is tested on the device you choose, through Google’s PageSpeed Insights API.
Should I compare home pages or specific pages?
Compare like with like: home page vs home page, product page vs product page. Templates differ a lot in weight, so a fair comparison uses the same page type on each site.
Which numbers decide who is fastest?
For search, the real-user field data (LCP, INP, CLS at the 75th percentile) matters most. The Lighthouse score is a lab estimate that’s useful for spotting technical differences but moves between runs.
Why is a competitor missing field data?
The Chrome UX Report only publishes data for sites with enough Chrome traffic. If a site has none, compare its lab metrics only.