Page Speed & Core Web Vitals Checker
Analyze Lighthouse scores and Core Web Vitals (LCP, CLS, TTFB) via Google PageSpeed Insights. Mobile and desktop scores side by side with improvement priorities.
This public tool does not use a MillionsCode server API key. Your key is not stored on our server and is sent directly from this browser to Google PageSpeed Insights. Clear it after use on a shared computer.
To get a key, enable the PageSpeed Insights API in Google Cloud Console and create an API key. Any quota or billing belongs to your own Google account.
How to use
- Enter a web page URL. https:// is added automatically.
- Enter your own Google PageSpeed API key. It is not stored on the server.
- Performance score from Google PageSpeed Insights (0-100).
- Compare mobile and desktop scores with Core Web Vitals detail.
- Generate tailored improvement suggestions from the score.
- Save the 3 most recent results for quick retesting.
This is an affiliate link. We may earn a commission at no extra cost to you.
How to read the Page Speed & Core Web Vitals Checker result
Page Speed & Core Web Vitals Checker is most useful when it is treated as a quick decision aid, not as a standalone answer. Enter clean inputs, compare the result with a related tool, and keep the final decision tied to the real context behind the numbers or text.
Check the input first
A small typo, wrong unit, or missing condition can change the Page Speed & Core Web Vitals Checker output. Recheck the input before copying, saving, or sharing the result.
Compare one related signal
Use another MillionsCode tool or hub to confirm the same decision from a different angle. This reduces mistakes when the result affects money, health, publishing, or planning.
Keep the result reusable
If the result is something you will revisit, copy it into your notes with the date and the assumption you used. A saved result without its assumption is easy to misread later.
Use guides for edge cases
When the result feels close to a limit, read the related guide before acting. Calculators and browser tools are fast, but rules, fees, policies, and personal conditions can change the final answer.
Before you act on the result
Use this short checklist before treating the Page Speed & Core Web Vitals Checker result as final. It helps separate a quick browser calculation from a real decision that may affect money, publishing, travel, health, study, or work.
Is the result sensitive to one input?
If one value can change the answer heavily, run the tool twice with a conservative and an optimistic assumption. The difference between those two results is often more useful than a single exact number.
Does the result need a date?
Many decisions depend on the date of the calculation. Exchange rates, search demand, platform rules, fees, and personal conditions move over time, so save the date with the result when you plan to reuse it.
Can another tool confirm it?
When the result leads to a real action, open one related tool or guide and check whether the same direction still makes sense. This is especially important for finance, SEO, crypto, tax, health, and publishing decisions.
Is there a policy or local rule behind it?
A browser tool cannot know every local rule, bank condition, platform limit, or personal exception. If the result is close to a threshold, read the related guide before making the final call.
A practical next step
After using Page Speed & Core Web Vitals Checker, write down the input, the output, and the action you are considering. If the action still looks useful after a second check, move to the related hub or guide and compare the broader context before you commit.
Frequently Asked Questions
Q. What is PageSpeed Insights (PSI)?
Google's PageSpeed Insights tool measures Core Web Vitals — LCP, INP, CLS, FCP, TTFB — for both mobile and desktop. Scores above 90 are "Good"; 50–89 are "Needs Improvement"; below 50 are "Poor".
Q. What are Core Web Vitals and how do they affect SEO?
Core Web Vitals (LCP, INP, CLS) are a set of real-world performance metrics that Google uses as a ranking factor since 2021. LCP measures loading speed, INP measures interactivity, and CLS measures visual stability.
Q. What is a good LCP score?
LCP (Largest Contentful Paint) should be 2.5 seconds or less for a "Good" rating. Above 4 seconds is "Poor." The most common culprit is a large hero image or font loading delay.
Q. What causes Cumulative Layout Shift (CLS)?
CLS (Cumulative Layout Shift) is caused by images without fixed dimensions, dynamically injected ads, and late-loading fonts that cause content to shift. Always specify width/height on img elements and reserve space for ads.
Q. How do I improve my PageSpeed score quickly?
Quick wins: (1) Convert images to WebP and lazy-load below-fold images; (2) Enable browser caching and CDN; (3) Remove render-blocking JavaScript; (4) Use next/image in Next.js for automatic optimization.
Q. Is mobile PageSpeed more important than desktop?
Yes. Google uses mobile-first indexing, so your mobile PageSpeed score directly impacts search rankings. Desktop scores matter for user experience but carry less SEO weight.
How to Use
Type the full URL of the page you want to analyze (e.g., https://millionscode.com).
Choose Mobile or Desktop analysis (or run both for a complete picture).
See your Performance, Accessibility, Best Practices, and SEO scores plus Core Web Vitals (LCP, INP, CLS).
Review the Opportunities section and prioritize fixes by estimated impact on load time.
Expert Knowledge: Page Speed & Core Web Vitals Checker
Core Web Vitals became official Google ranking factors in June 2021 with the Page Experience update. The three metrics — LCP (Largest Contentful Paint), INP (Interaction to Next Paint, replacing FID since March 2024), and CLS (Cumulative Layout Shift) — collectively measure loading, interactivity, and visual stability. Passing all three thresholds qualifies a page for the "Good page experience" signal.
The most impactful improvements for Korean blogs and e-commerce sites are typically image-related. Hero images and product photos are the primary LCP elements. Switching to WebP format, implementing lazy loading (loading="lazy"), and using responsive srcset attributes can cut LCP by 40–60% on image-heavy pages. Cloudflare's image resizing feature automatically serves appropriately-sized images for each device.
For Next.js sites like those deployed on Cloudflare Pages, the built-in next/image component handles most image optimization automatically: WebP conversion, lazy loading, proper sizing, and preloading of critical above-fold images. The remaining CWV improvements typically involve reducing third-party script impact (tag managers, chat widgets), eliminating render-blocking CSS/JS, and optimizing web font loading with font-display: swap.
Related Tools
Convert JPG/PNG images to WebP in your browser in 1 second. 100% client-side processing — no file upload. Reduces file size by ~26% to improve LCP scores.
Extract and audit meta tags including title, description, OG tags, canonical, hreflang, and Schema.org from any URL. Get actionable SEO improvement tips.
Look up A, AAAA, MX, TXT, NS, and CNAME DNS records via Google DNS (8.8.8.8). Diagnose domain setup issues and mail delivery errors instantly.