Page Speed Test

Core Web Vitals are the three metrics Google uses to measure real-world page experience: Largest Contentful Paint (LCP, how fast the main content appears), Interaction to Next Paint (INP, how responsive the page feels to taps and clicks), and Cumulative Layout Shift (CLS, how much the layout jumps around while loading). They are a confirmed ranking signal, so a page that fails them can be held back even when its content is good. This tool shows both the lab result from a fresh Lighthouse run and the real-user field data Google collects from actual Chrome visitors.

Lab data is a single controlled test we run right now on a simulated device and network — it is reproducible and great for debugging, but it is one sample. Field data (from Google's CrUX dataset) is what real Chrome users actually experienced on your page over the last 28 days. Field data is the truth about your users; lab data is the microscope for fixing it. New or low-traffic pages have no field data yet, so we fall back to the origin-level numbers for your whole site.

The waterfall lists every request the page made — HTML, CSS, JavaScript, fonts, images — in the order the browser started them, with a bar showing when each one started and how long it took. Long bars early in the load, or many bars stacked at the same moment, are what delays your content from appearing. Render-blocking CSS and JavaScript are flagged: those are the files the browser must finish before it can paint anything, so they are usually the highest-leverage things to defer or shrink.

Speed is a real ranking factor through Core Web Vitals, but it is a tie-breaker, not a magic lever — a fast page with weak content still won't outrank a slow page that better answers the query. The honest way to use this: fix failing Core Web Vitals so speed stops holding a deserving page back, then invest in the content and relevance that actually win the ranking. We won't promise that shaving a second buys you positions; it removes an obstacle.