Website Speed Checker

Analyze page speed and Core Web Vitals in seconds. 100% private, no tracking.

How It Works

Enter URL

Type in the URL you want to analyze and select Desktop or Mobile strategy.

API Diagnosis

We query Google PageSpeed Insights in real-time without proxy caching.

Get Audits

Review Core Web Vitals, speed ratings, and custom compression suggestions.

Frequently Asked Questions

What is a good performance score?

A score of 90 or above is considered good. Scores between 50 and 89 indicate that the page needs improvement, and scores below 50 are considered poor.

How often should I check my site speed?

We recommend testing after every major update, new feature deployment, or content change. Regular monitoring helps ensure a consistent user experience.

Does UtilVox offer automated monitoring?

Yes, our Pro plan includes automated weekly speed audits and historical performance tracking for up to 50 URLs.

What Your Connection Numbers Actually Mean

The three numbers, translated

A speed test reports three figures — each gates different activities:

Metric	Gates	Comfortable values
Download (Mbps)	Streaming, browsing, updates	HD: 5+; 4K: 25+; household: 50+
Upload (Mbps)	Video calls, file sending, streaming out	Calls: 3+; creators: 10+
Ping/latency (ms)	Gaming, call smoothness	Gaming: under 50; calls: under 100
Jitter	Call/game stability	Low and steady beats fast and spiky

Testing so the numbers mean something

One test is an anecdote. Test wired (or next to the router) to measure the connection, then at your desk to measure the WiFi — the gap between them is a router-placement problem, not an ISP problem. Test at different hours: evening collapse with fine mornings is neighborhood congestion, a common story on shared connections. Keep screenshots with timestamps; a pattern of paying for 100 and receiving 30 is a complaint with evidence.

When speed is fine but a site is slow

A fast connection plus a slow website points at the site, not you: check whether it's even responding with the HTTP status checker and whether its name resolves via the DNS lookup. If you run the slow site yourself, your asset weight is the usual culprit — start with the image compressor and JS minifier.