Core Web Vitals Checker
Check your page against the Core Web Vitals items from our Website Standards: LCP image handling, layout stability, script weight, field-data readiness, with evidence for every finding
Enter the page address, with or without https://
What This Tool Checks
Touch targets at least 24px min, 44-48 primary, ~8px gaps
Loading skeletons pixel-matched to final layout
Reserved space for ads/embeds/iframes/consent UI
Hero/LCP image never lazy; fetchpriority/preload
Accurate sizes on responsive/fill images
Third-party scripts non-blocking (afterInteractive/lazyOnload class)
First-load JS ~<200KB gz/route; no dep >50KB unaudited
Bfcache-eligible pages
Preconnect only 1-3 critical origins
Judge on field data: CrUX p75 28-day, mobile first
RUM wired (web-vitals to analytics)
Staging/preview never indexable (Coolify needs explicit header)
WhatsApp/chat widget: lazy-loaded, staffed
Redirects from all old URLs after relaunch
Every result quotes the evidence we found. Anything we cannot measure from outside is listed plainly instead of guessed.
Frequently Asked Questions
Common questions about this tool and how to use it effectively
Google's three field metrics for page experience: LCP (Largest Contentful Paint, loading), INP (Interaction to Next Paint, responsiveness), and CLS (Cumulative Layout Shift, visual stability). They are measured from real Chrome users and feed into search rankings.
It runs the Core Web Vitals items from our published Website Standards: whether your hero image loads with priority instead of lazily, whether space is reserved for ads, embeds and consent banners (the layout-shift killers), script weight and third-party loading strategy, image sizing, preconnect discipline, and whether real-user measurement is wired up. Each finding quotes the evidence we collected.
Lab tests measure one synthetic load from one machine; Google ranks on what real visitors experience (the CrUX p75 over 28 days, mobile first). A lab score can look great while real users on mid-range phones struggle. That is why this tool never shows a single performance number, it shows what is structurally right or wrong.
Lazy-loading the hero image. Lazy loading is great below the fold, but applied to the largest visible image it delays the very thing LCP measures. Our standard: the hero image is never lazy, and gets fetchpriority or a preload hint.
Anything that appears late and pushes content: images without dimensions, ads and embeds without reserved space, consent banners injected at the top, and fonts swapping size. Reserve explicit space for every late-loading element and never insert content above what is already rendered.
Our standard: roughly under 200KB gzipped of first-load JavaScript per route, with no single dependency over 50KB added unaudited. Past that, mid-range phones spend seconds parsing script before the page becomes usable, which shows up directly in responsiveness metrics.
Still have questions?
Contact our team for helpRelated Tools You Might Like
Continue optimizing your website with these complementary tools
Page Speed Analyzer
Analyze loading performance and get actionable recommendations
Website Analyzer
Evidence-backed checks across search, speed, security, accessibility, and conversion basics
HTML/CSS/JS Minifier
Minify code to reduce file size and improve page speed