TontonTools

Page Speed Checker

Test any page's loading speed — response time and size, instantly.

100% Free No signup Privacy-friendly SEO Tools
Updated Sep 2026

Share X / Twitter Facebook LinkedIn WhatsApp

How to use Page Speed Checker

  1. Enter the page URL and click “Test Speed”.
  2. Read the two numbers: server response time (server health) and page size (content weight).
  3. Diagnose by pattern: slow response = hosting/caching problem; big page = images/scripts problem.
  4. Fix and re-test — compress images, enable caching, then measure the improvement.

What is Page Speed Checker?

A page speed checker measures how quickly a web page responds and how heavy it is — the server's response time (how long until the first byte arrives) and the page's size (how much must download before it renders). Together they answer the first diagnostic question of web performance: is this page slow, and is the server or the page itself to blame?

Speed is money and rankings both: Google uses page experience signals in ranking, and the classic industry findings hold — a page taking 3+ seconds loses roughly half its mobile visitors before it loads, and every extra second measurably cuts conversions.

About the Page Speed Checker

Enter a URL, click Test Speed, and get the core numbers: server response time and page weight, with context on what's good (server response under ~200 ms is strong, under 600 ms acceptable; total page weight under ~1–2 MB is healthy for content pages).

Reading the result: a slow response with a small page points at the server — cheap hosting, no caching, slow database queries — fixable with caching plugins, a CDN, or better hosting. A fast response with a huge page points at the content — uncompressed images are the usual culprit (fix with our Image Compressor), followed by too much JavaScript. Test both your homepage and your money pages, and test competitors for context: beating the sites you compete with matters more than absolute perfection.

For the full lab treatment — Core Web Vitals, filmstrips, per-resource waterfalls — pair this quick check with our Core Web Vitals Checker and Google's PageSpeed Insights.

Frequently Asked Questions

Under 2 seconds to interactive is the practical target; under 1 second feels instant. Server response (TTFB) specifically: under 200 ms is excellent, 200–600 acceptable, beyond that the server itself is the bottleneck.
Yes — speed has been a ranking signal since 2010 on desktop and 2018 on mobile, now folded into the page experience signals with Core Web Vitals. It's a tiebreaker more than a dominator: content still wins, but slow loses ties.
Your connection isn't the variable — the server's response time and the page's weight are. A 5 MB page on a 400 ms server is slow on any connection, and most of your visitors have slower devices and networks than you.
Images, overwhelmingly — a single unoptimized photo can outweigh all the code combined. Then JavaScript bundles, web fonts and third-party scripts (chat widgets, trackers). Compressing images is the highest-impact five minutes in web performance.
Under 200 ms is strong; Google's guidance flags over 600 ms as poor. High TTFB on shared hosting typically means no page caching — a caching layer or plugin often cuts it by 5–10×.

Learn more

How to Test and Improve Your Website Speed

Slow sites lose visitors and rankings. Here is how to measure your page speed and the highest-impact fixes.

Read the guide

We use cookies for analytics and to keep the tools free via ads. See our Privacy Policy.