SUBMIT A GUEST POST
TOP POSTS
Navratri Diet Plan: How to Stay Energetic During 9 Days of FastingNavratri Special Sabudana and Kuttu Recipes for Fasting DaysNavratri Wishes and Messages: 100 Greetings for WhatsApp and Instagram
Add as preferred source
FREE TOOL

PageSpeed Checker: Free Web Page Speed Test

A PageSpeed checker tests how quickly a web page loads and how it responds, then scores it and lists what to fix. The WritoryBuzz tool runs your URL through Google's own PageSpeed Insights API, on mobile or desktop, and returns a performance score, Core Web Vitals and ranked improvement opportunities. It is a free web page speed test with no signup.

Paste a URL, pick Mobile or Desktop, click Analyze and read the results below. This page explains what every result means, what to fix first and where a single test can mislead you.

Run your PageSpeed test above
Quick start
1Enter the full URL
2Choose Mobile or Desktop
3Click Analyze
4Read field data first
Try: web.devwordpress.org

Results

Fetching Google PageSpeed Insights data. This takes 10 to 30 seconds.
Enter a URL above to test it.
Key Takeaway:: The three Core Web Vitals:
LCP (loading), INP (responsiveness) and CLS (visual stability). Good thresholds: LCP at or under 2.5 seconds, INP at or under 200 milliseconds, CLS at or under 0.1. INP replaced FID as a Core Web Vital in March 2024, according to Google's web.dev. Field data decides ranking signals. Lab scores help you debug but are not what Google uses.

How to Use the PageSpeed Checker

  1. 1
    STEP 1 Enter the full URL of the page you want to test, for example https://example.com/pricing. Test individual pages, not only the homepage.
  2. 2
    STEP 2 Choose Mobile or Desktop. Start with Mobile.
  3. 3
    STEP 3 Click Analyze. The test can take up to a minute because the tool runs a real Lighthouse analysis.
  4. 4
    STEP 4 Read field data first if it appears, then the lab metrics.
  5. 5
    STEP 5 Work down the opportunities list from the biggest estimated saving.
  6. 6
    STEP 6 Fix, deploy, re-test. Run the same URL on the same device mode so the comparison is fair.
Run your PageSpeed test above

Core Web Vitals Explained

Core Web Vitals are Google's set of user-experience metrics. Each one measures a different moment in the visit, and each has published thresholds for good, needs improvement and poor.

MetricWhat it measuresGoodPoorType
LCP, Largest Contentful PaintHow long the largest visible element, often a hero image or headline, takes to appear2.5 s or lessOver 4 sCore Web Vital
INP, Interaction to Next PaintHow quickly the page responds visually after taps, clicks and key presses200 ms or lessOver 500 msCore Web Vital
CLS, Cumulative Layout ShiftHow much visible content jumps around while loading0.1 or lessOver 0.25Core Web Vital
FCP, First Contentful PaintWhen the first text or image appears1.8 s or lessOver 3 sLab diagnostic
TBT, Total Blocking TimeHow long the main thread is blocked during load200 ms or lessOver 600 msLab diagnostic

Google judges a page against the 75th percentile of real visits, so at least three in four visits should meet the "good" threshold. These thresholds are documented on web.dev.

INP replaced FID

First Input Delay (FID) measured only the delay before the browser began handling the first interaction. Interaction to Next Paint (INP) looks at the responsiveness of interactions across the whole visit. According to Google's web.dev, INP replaced FID as a Core Web Vital in March 2024. If an older guide still lists FID, it is out of date.

Citable definition

Core Web Vitals are three Google metrics for real-world page experience: Largest Contentful Paint (loading), Interaction to Next Paint (responsiveness) and Cumulative Layout Shift (visual stability).

Lab Data vs Field Data

This is the most misunderstood part of any PageSpeed test, and it explains most "my score changed" complaints.

Field dataLab data
SourceChrome User Experience Report (CrUX), real Chrome usersLighthouse running one simulated load
Time windowAggregated over the previous 28 daysA single test, right now
Best forKnowing how real visitors experience the pageDebugging and checking a fix immediately
Used by Google for Core Web VitalsYesNo
AvailabilityOnly when the page or origin has enough Chrome trafficAlways

If a small or new page shows lab data only, that is normal. It does not mean something is broken. It means Google does not yet have enough real-user samples for it.

How to Read Your Results

  • Performance score (0 to 100). A weighted blend of lab metrics. Google's own colour bands treat 90 and above as good. Use it as a trend line, not a target to hit exactly.
  • Core Web Vitals assessment. Based on field data. Passing means all three vitals meet the good threshold at the 75th percentile.
  • Opportunities. Specific fixes with estimated time savings, such as properly sized images or reducing unused JavaScript.
  • Diagnostics. Extra detail, such as main-thread work or large layout shifts, that explains why a metric is poor.

Why Mobile Scores Are Usually Lower

Mobile and desktop tests use different conditions. Lighthouse simulates a mid-range phone on a slower, throttled network for mobile, while desktop assumes a faster connection and a more powerful processor. The same page can therefore score far lower on mobile without any bug. Google also uses the mobile version of a site for indexing, so prioritise Mobile if you only test one mode. For many Indian audiences on mid-range phones and variable mobile networks, the mobile test is the more realistic picture.

Common Causes of a Slow Page and Their Fixes

Symptom in reportLikely causeTypical fix
Poor LCPLarge unoptimised hero image, slow server response, render-blocking CSSCompress and resize images, use WebP or AVIF, preload the LCP image, reduce server response time
Poor INPHeavy JavaScript, long tasks, third-party scriptsSplit or defer scripts, remove unused plugins, cut third-party tags
Poor CLSImages without dimensions, late-loading ads or fontsSet width and height, reserve space for ads, preload key fonts
High TTFBSlow hosting, no caching, heavy database queriesUse caching, a CDN and better hosting
Large page weightUncompressed images, bloated themes or pluginsEnable compression, lazy-load below-the-fold images

Time to First Byte (TTFB), the delay before the first byte of a response arrives, is easy to overlook. If the server is slow, front-end fixes can only do so much. Server-side caching and a content delivery network (CDN) often give the biggest early gains on CMS sites such as WordPress.

Who Uses a Page Speed Test

Site owners and bloggers

Who want a plain-English list of what slows their pages.

Developers

Who need a quick check after a deployment.

SEO professionals

Auditing Core Web Vitals before a technical review.

Ecommerce teams

Testing product and checkout pages, where delays cost sales.

Agencies

Sharing a before and after comparison with a client.

Common Mistakes When Testing Page Speed

  • Chasing a perfect 100. Beyond a good score, extra points rarely change real user experience. Fix real bottlenecks instead.
  • Testing only the homepage. Templates differ. Test a post, a product and a category page.
  • Comparing one run to another. Scores vary between runs. Test a few times and compare ranges.
  • Mixing mobile and desktop results. Compare like with like.
  • Ignoring field data. A great lab score does not help if real users on slower devices have a poor experience.
  • Installing many optimisation plugins. Stacking plugins can add the very JavaScript you are trying to remove.

Does Page Speed Affect SEO and Revenue?

Core Web Vitals are part of Google's page experience signals, but Google says relevance remains more important, so a fast page with poor content will not outrank a slower page that answers the query better. Speed matters more for people. Google's 2017 mobile research, "The Need for Mobile Speed", found that the probability of a bounce increases 32 percent as page load time goes from 1 second to 3 seconds. Faster pages keep visitors, which tends to protect conversions.

Honest Limits of This Tool

  • It reports what the PageSpeed Insights API returns. It is not a different measurement engine.
  • A single lab test is a snapshot. Results change with server load, network conditions and third-party scripts.
  • It can test only publicly reachable URLs. Pages behind a login or firewall will not work.
  • Field data appears only when Google has enough real-user data for the URL or origin.
  • The score does not capture everything about quality. Content, accessibility and usability matter too.

Privacy

The tool sends the URL you enter to Google's PageSpeed Insights API for analysis. Do not test pages containing private or unpublished information.

Open the tool

Frequently Asked Questions

What is a PageSpeed checker?

A PageSpeed checker tests how fast and stable a web page is, then reports a score, Core Web Vitals and fixes. This tool uses Google's PageSpeed Insights API for mobile or desktop.

What is a good PageSpeed score?

Google treats 90 to 100 as good, 50 to 89 as needs improvement and below 50 as poor. The Core Web Vitals pass or fail result from field data matters more than the headline number.

What are the Core Web Vitals thresholds?

Good is LCP at or under 2.5 seconds, INP at or under 200 milliseconds and CLS at or under 0.1. Poor starts above 4 seconds, 500 milliseconds and 0.25.

What replaced FID in Core Web Vitals?

Interaction to Next Paint (INP) replaced First Input Delay in March 2024, according to Google's web.dev. INP measures responsiveness across the whole visit.

What is the difference between lab data and field data?

Field data comes from real Chrome users over the previous 28 days through CrUX. Lab data is one simulated Lighthouse test. Google uses field data for Core Web Vitals.

Why is my mobile score lower than desktop?

Mobile tests simulate a slower phone and network, so scores are harsher. A large gap is common and not necessarily a bug.

Why does my score change every time I test?

Lab tests are affected by server load, network variation and third-party scripts. Run the test several times and compare ranges rather than single numbers.

Does page speed affect Google rankings?

Core Web Vitals are part of Google's page experience signals, but relevance and content quality matter more. Speed mainly helps users and conversions.

Is this PageSpeed checker free?

Yes. It is free, needs no signup and uses Google's public PageSpeed Insights API. Test your page speed now and fix the top opportunity first.

Ready to try the PageSpeed Checker?

Free to use. Open the tool and get your result in seconds.

Run your PageSpeed test above
For contributors
Got something worth sharing? Write for us.

Original, well researched guides are always welcome here.

  1. 1Read the guidelines
  2. 2Send us your pitch
  3. 3Our editors review it
BECOME A CONTRIBUTOR Read the editorial policy
WritoryBuzz

A guest posting platform where analysts, founders and specialists publish original, well researched guides.

connect@writorybuzz.com
Top categories
SEOBusinessArtificial IntelligenceTechnologyDigital Marketing All categories →
Free tools
Page Speed CheckerKeyword Density CheckerMeta Tag GeneratorSchema Markup GeneratorWord Counter All free tools →
For contributors
Write For UsEditorial PolicyContributor loginContact the editor
Company
About UsContactSitemap PostoryCafe Preferred source on Google
Fresh this week Navratri Diet Plan: How to Stay Energetic During 9 Days of FastingNavratri Special Sabudana and Kuttu Recipes for Fasting DaysNavratri Wishes and Messages: 100 Greetings for WhatsApp and Instagram
© 2026 WritoryBuzz. All rights reserved. Privacy PolicyTerms and Conditions