- Home
- Calculators
- CWV Checker
Website Speed Test
Check your website speed in seconds — no login needed. See exactly what slows your site down and get a clear action plan to fix it.
Why test your website speed?
- See what Google sees — real field data, not lab estimates
- Spot the #1 issue slowing your site in under 10 seconds
- Prioritize fixes that actually move the needle on rankings
Fetching Core Web Vitals data…
Recommendations
How Core Web Vitals Work
Core Web Vitals are three key metrics that Google uses to evaluate real-world user experience on your website.
Largest Contentful Paint (LCP)
Measures loading performance. LCP should occur within 2.5 seconds of when the page first starts loading.
Interaction to Next Paint (INP)
Measures interactivity. INP should be 200 milliseconds or less for a good user experience.
Cumulative Layout Shift (CLS)
Measures visual stability. CLS should be 0.1 or less for a good user experience.
Get Your Website Speed Report
Detailed breakdown of all Core Web Vitals metrics with prioritized fix recommendations.
Includes competitive benchmarks and ROI estimates for each fix
How Core Web Vitals Work
Enter your URL
Paste any page URL to analyse its Core Web Vitals performance using real-world Chrome data.
Review your scores
See LCP, INP, and CLS scores with pass/fail indicators and comparison against Google's thresholds.
Get recommendations
Receive prioritised, actionable fixes to improve each metric and boost your search ranking.
Frequently asked questions about Core Web Vitals
What are Core Web Vitals?
Core Web Vitals are three metrics Google uses to measure real-world user experience: LCP (Largest Contentful Paint) measures loading speed, INP (Interaction to Next Paint) measures interactivity, and CLS (Cumulative Layout Shift) measures visual stability. They are a confirmed Google ranking factor since 2021.
What replaced FID as a Core Web Vital?
INP (Interaction to Next Paint) replaced FID (First Input Delay) in March 2024. While FID only measured the delay of the first interaction, INP measures the responsiveness of all interactions throughout the page lifecycle, making it a more comprehensive interactivity metric.
How do I check my Core Web Vitals?
Use Google PageSpeed Insights for per-URL analysis with both lab and field data. Google Search Console shows CWV status across your entire site. Chrome DevTools Lighthouse provides lab-only metrics. For real-user monitoring (RUM), use the web-vitals JavaScript library or tools like SpeedCurve.
What is a good LCP score?
Good: ≤ 2.5 seconds. Needs improvement: 2.5-4.0 seconds. Poor: > 4.0 seconds. LCP measures when the largest content element (image, video, or text block) becomes visible. Common causes of poor LCP: unoptimised images, render-blocking resources, slow server response time, and client-side rendering.
How do I fix a high CLS score?
Top fixes for CLS: (1) Always set width and height attributes on images and videos, (2) Reserve space for ads and embeds with CSS aspect-ratio or min-height, (3) Avoid inserting content above existing content dynamically, (4) Use CSS contain for layout containment, (5) Preload web fonts and use font-display: swap to prevent layout shifts from font loading.
Do Core Web Vitals affect mobile and desktop differently?
Yes. Google uses mobile CWV data for mobile search rankings and desktop data for desktop rankings. Mobile scores are typically worse due to slower processors, network latency, and smaller viewports. Only ~33% of sites pass all CWV on mobile vs ~55% on desktop. Optimise for mobile first.
How long does it take for CWV improvements to affect SEO?
CWV changes typically take 28-30 days to reflect in Google Search Console after deployment, because Google uses a rolling 28-day average of field data from the Chrome User Experience Report. Ranking impact may take an additional 2-4 weeks after data updates. Plan for 6-8 weeks total from fix to visible SEO effect.
Is the Core Web Vitals Checker free?
Yes, the tool is completely free and requires no signup. It uses the Google PageSpeed Insights API to fetch both lab and field data for any URL. Your data is not stored — each check is a live query to Google's API.