Page Speed Checker
Check if a website is online and measure response time.
📊 Status:
Not checked yetResponse time is measured inside your browser, so it reflects your device, your connection and your route to the site at this moment — not a global average. The score is a simple banding of that single number (under 200 ms = 100, under 500 ms = 90, under 1 s = 80, under 2 s = 60, under 3 s = 40, under 4 s = 20). A cross-origin request returns an opaque response, so "Reachable" means the connection completed: the HTTP status code, page weight, request count and Core Web Vitals cannot be read this way. For lab metrics on a real URL, use Google PageSpeed Insights; for field data on your own property, use Search Console Core Web Vitals.
How to Use Page Speed Checker
Follow these simple steps to get the best results.
Enter website URL
Paste any page URL (the https:// prefix is added automatically if you leave it out).
Timed from your browser
A single cache-bypassing request is made and the round-trip is measured with performance.now(), so the number reflects your own network and route.
Read the honest result
See reachability, response time and the banded response score, plus exactly which lab metrics a browser check cannot read.
Frequently Asked Questions
Everything you need to know about Page Speed Checker.
About the Page Speed Checker Tool
The ToolFlic Page Speed Checker answers the one question a browser can resolve on its own: how long does a URL take to respond from where you are sitting right now? It makes a single cache-bypassing request, times the round trip, reports whether the connection completed and bands the result into a response score. It does not pretend to be Lighthouse. A cross-origin request returns an opaque response, so the HTTP status code, page weight, request count and Core Web Vitals (LCP, INP, CLS) cannot be read this way, and the page says so instead of inventing them.
Core Advantages
Use it as a fast reachability and origin-speed probe: confirm a host is answering after a DNS change, notice a server that has started taking seconds to respond, or compare the same URL over Wi-Fi and mobile data. Knowing which signals are real measurements and which need dedicated tooling keeps optimisation work honest - and points you at PageSpeed Insights for lab data or Search Console for field data when a number actually matters.
Architecture & Security
The check issues one fetch request with mode "no-cors" and cache "no-cache", bracketed by performance.now() timestamps, so timing resolution is sub-millisecond and no cached response is reused. A resolved promise means bytes arrived; a rejected one means DNS, TLS, timeout or a blocked request. The score maps elapsed milliseconds onto six bands (200, 500, 1000, 2000, 3000 and 4000 ms). Nothing is uploaded, and no synthetic or stored score is ever displayed before you run a test.
Under the Hood: the Page Speed Checker explained properly
No marketing filler — just the mechanics, the trade-offs and the real limits, explained clearly.
How it actually works
It makes one cache-bypassing request to the page from your own browser and measures the round trip with performance.now(), reporting whether the site was reachable and how long the connection took.
What that means for your results
The number is real for your network and route at that moment. Because the request is opaque, the page cannot read the response body, so it reports timing and reachability honestly and says plainly that the status code was not readable, rather than showing a made-up score.
Where it falls short — honestly
It measures only round-trip time from one device on one connection. It cannot report page size, request count, Largest Contentful Paint or any Core Web Vitals, and it runs no mobile or desktop emulation. A lab-style full audit needs field data from tools such as Lighthouse or PageSpeed Insights.
A real end-to-end workflow
Paste any URL and read the response time as a quick reachability check from your side, remembering the result moves with network and location. When the timing looks slow, hand the deeper diagnosis to a real lab tool, and use HTTP Status Checker to confirm the page returns the status you expect and Broken Link Checker to catch links that fail on the page.
In-Depth Guides Using This Tool
Tested workflows, exact sizes and limits — written step by step by the ToolFlic team.
Browse more Seo Tools
View All Seo →Your Privacy is Our Core Mission
We've built this utility specifically to protect your digital footprint. Every byte of data is processed locally within your browser — it never touches our servers. That is our absolute guarantee.
Designed for productivity, optimized for security. We know how critical 📈 are, and we're here to make them seamless and safe.
