Page Speed CheckerTest Speed and Core Web Vitals

A page that loads in two seconds and a page that loads in six can carry the same content, yet visitors treat them very differently. The Kwebby Page Speed Checker runs any URL through the Google PageSpeed Insights API and returns a performance score, lab metrics, real-user Core Web Vitals when Google has them, and key audits for mobile and desktop.

Use this guide to read the results, decide what to fix first and confirm that your changes worked.

Key Takeaways

• Kwebby's Page Speed Checker uses the Google PageSpeed Insights API (v5) to score a URL from 0 to 100 and report Core Web Vitals for mobile and desktop.
• Google colors scores in three bands: 90 to 100 is good, 50 to 89 needs improvement and 0 to 49 is poor.
• The three Core Web Vitals are LCP (good at 2.5 seconds or less), INP (200 milliseconds or less) and CLS (0.1 or less), measured at the 75th percentile.
• The performance score is lab data from Lighthouse, while real-user field data comes from the Chrome User Experience Report.
• Compressing images, enabling server compression, minifying code and using a CDN fix most speed problems.
• Each browser gets 1 free check per day, and each check covers mobile and desktop, so batch your fixes before you test again.

What Is the Kwebby Page Speed Checker?

Kwebby's Page Speed Checker is a web tool that tests how fast a page loads using Google PageSpeed Insights. You enter a URL and press Analyze. The tool runs a mobile and a desktop test in parallel and returns, for each, a performance score from 0 to 100, real-user Core Web Vitals when Google has them, and a list of lab metrics and audits. An Ask AI button on each audit row returns a short plain-English explanation and fix ideas.

PageSpeed Insights, or PSI, is Google's free service for assessing page performance. Kwebby's checker sends your URL to that service and shows you the result.

Key Features and How It Works

The checker does one job: it turns a URL into a prioritized speed report. These are the parts of the report.

Performance Score

The score runs from 0 to 100. According to Google's PageSpeed Insights documentation, 90 to 100 is green (good), 50 to 89 is amber (needs improvement) and 0 to 49 is red (poor). Use the score to compare one page before and after a change, not as a goal on its own.

Core Web Vitals

Core Web Vitals are three metrics Google uses to describe real page experience. The web.dev guide lists them:

• LCP (Largest Contentful Paint) measures loading. Good is 2.5 seconds or less.
• INP (Interaction to Next Paint) measures responsiveness. Good is 200 milliseconds or less. INP replaced First Input Delay in 2024.
• CLS (Cumulative Layout Shift) measures visual stability. Good is 0.1 or less.

A page passes the assessment when the 75th percentile of all three metrics is good. The tool shows these three values from the Chrome UX Report for the URL, or for the whole origin when the URL has too little traffic. When Google has no field data, the tool says so and you rely on the lab metrics.

Lab Metrics and Audits

Below the scores, the tool lists lab metrics such as First Contentful Paint, Largest Contentful Paint, Speed Index, Total Blocking Time and Cumulative Layout Shift, plus audits such as render-blocking resources, unused CSS and JavaScript, text compression, cache lifetimes and server response time when Lighthouse reports them. Each row has an Ask AI button that sends the audit to Kwebby's AI service and shows an explanation with one or two fixes.

Mobile and Desktop Results

Results cover mobile and desktop, with a tab for each. Mobile tests simulate a mid-tier phone on a mobile network, so mobile scores are usually lower. Start with the mobile report, since improvements such as lighter images usually help both.

Lab Data and Field Data

PageSpeed Insights reports two kinds of data. Lab data comes from Lighthouse, which loads your page in a simulated environment. Field data comes from the Chrome User Experience Report (CrUX) and reflects real visits over the previous 28 days. Lab data suits debugging because you can repeat it; field data shows what visitors actually experienced.

Why Page Speed Matters

Page speed matters because slow pages lose visitors before they read a word, and Google's ranking systems use Core Web Vitals. Google's page experience documentation states that Core Web Vitals are used by its ranking systems. It also says there is no single signal, and that Search still shows the most relevant content even when page experience is weak.

Treat speed as one signal among many and as a conversion factor, not a replacement for good content. A fast page with weak content will not outrank a relevant page, but a slow page makes a good page work harder for every visit.

How to Use the Page Speed Checker

Follow these steps to test one URL.

1. Enter the URL. Type the full page address, such as https://yourwebsite.com, in the URL box.
2. Press Analyze. The tool sends the page to PageSpeed Insights and shows the report when it is ready.
3. Read the performance score. Compare it with the bands: 90 to 100 good, 50 to 89 needs improvement, 0 to 49 poor.
4. Check the Core Web Vitals. Compare the real-user LCP, INP and CLS with the good values above, if Google has field data for the page.
5. Review the lab metrics and audits. Note the three largest issues and who owns each (design, development or hosting). Click Ask AI on a row for an explanation.
6. Compare mobile and desktop. If mobile is far lower, start there.
7. Fix, then test again. Each browser gets 1 free check per day, so apply several fixes before you re-run the same URL.

Best Practices for Improving Page Speed

Most speed gains come from sending fewer bytes and blocking the page less. These practices match the fixes the report usually suggests.

Compress and Resize Images

Images are often the heaviest files on a page. Use modern formats such as WebP, resize each image to its display size, compress before upload and lazy-load images below the first screen. Common mistake: uploading a 4,000 pixel photo for a 600 pixel slot.

Turn On Server Compression

Gzip or Brotli compression shrinks HTML, CSS and JavaScript during transfer. Verify that it works with the Gzip Compression Checker.

Minify CSS and JavaScript

Minifying removes whitespace and comments without changing behavior. Use the CSS Minifier and the JavaScript Minifier for files you edit by hand, and a build step for larger projects.

Cache Static Files

Set cache headers so returning visitors reuse files instead of downloading them again.

Use a CDN

A content delivery network serves static files from locations close to each visitor, which reduces latency for people far from your server.

Defer Blocking Scripts

Scripts and stylesheets in the head can block rendering. Defer non-critical JavaScript and load only the CSS the first screen needs.

Watch Total Page Weight

Measure the HTML size and count of files with the Page Size Checker. A page that downloads dozens of scripts rarely scores well, however well each one is compressed.

Common Use Cases

• Before and after a release. Test the same URL before and after a deploy to see whether a change helped.
• Client audits. Agencies include the score and Core Web Vitals in a technical SEO report.
• Hosting decisions. A slow response on a simple page can point to the host rather than the theme.
• Competitor benchmarks. Test a rival's page to see where your numbers stand.
• Template checks. Test one page per template (home, article, product) because templates share most problems.

Related Kwebby Tools

Speed testing sits inside the wider SEO Tools toolkit. These tools cover the next steps.

• Mobile Friendly Test focuses on the mobile result from the same engine.
• Page Size Checker reports HTML size and the number of CSS, JavaScript and image files.
• Check Gzip Compression confirms that your server compresses text files.
• SSL Checker verifies your HTTPS certificate, another part of a technical audit.
• Website Reviewer reviews a site beyond speed.

Final Thoughts

A fast page starts with a baseline. Test your most important URL now, write down the score and the three Core Web Vitals, and fix the largest opportunity first.

Then work through compression, caching and script loading, and test again after the changes. If the fixes need development help, Kwebby's web development services can take them on.