Security alerts WordPress 7.1.4 · no-login code execution in the updater 117 critical WordPress plugin CVEs · in October, most need no login

Website speed test

Why is my site slow?

See where the time goes — your server, redirects, blocking scripts, heavy images — and get the exact files and settings to fix, biggest win first.

tinyexample.com leanwikipedia.org typicalgithub.com heavycnn.com

What you get

Plain answers, and the exact files to fix

sample result

What we check

What the speed test looks at

Server response time
How long your server takes to start sending the page, split into DNS, connection, TLS and the time your server spends building it.
Redirects
Every hop between the address you typed and the real page, and what each one costs.
Render-blocking scripts
Scripts in your <head> that stop the page from showing, with the exact tags to change.
Compression
Whether your HTML, CSS and JavaScript are sent gzip, brotli or zstd compressed, and the config for your server if not.
Browser caching
Which of your files tell browsers to keep a copy, and which make returning visitors download them again.
Images
Oversized images, old formats, a lazy-loaded hero image, and images without dimensions that make the layout jump.
Page weight and files
Everything the HTML pulls in, biggest first, with size, compression, cache lifetime and time for each file.
Third parties
Every other domain your page loads from, and how much each one adds.

Questions

Why don’t you show Core Web Vitals?+

LCP, CLS and INP have to be measured in a real browser that renders the page. We load your page from our server without running it, so instead of guessing, we show only what we actually measured: server time, redirects, file sizes, compression, caching and what blocks rendering. For browser-measured Core Web Vitals, use Google PageSpeed Insights; the fixes here are usually what moves those numbers.

Why is my result different from PageSpeed Insights or GTmetrix?+

They render the page in a simulated phone or desktop browser from their own locations, run your JavaScript, and throttle the connection. We measure the network side from our server. Both are useful: a slow server or a 4 MB page shows up in every tool.

What is a good server response time (TTFB)?+

Under 200 ms is excellent and under 600 ms is fine. Over a second usually means the page is rebuilt from scratch for every visitor; full-page caching or a CDN that caches HTML is the usual fix.

What does render-blocking mean?+

When the browser reaches a normal <script> tag in the <head>, it stops building the page until that script has downloaded and run. Adding defer lets it download in the background and run once the page is parsed, so visitors see content sooner.

Does the test see files loaded by JavaScript?+

No. We count everything referenced in the HTML (stylesheets, scripts, images, preloads), the way a browser sees the page before scripts run. Single-page apps and tag managers often load more afterwards, so the real total can be higher.

Can you watch my site’s speed for me?+

Yes. Add it as a free monitor and we check it every 10 seconds from six locations, record the response time of every check, and alert you when it goes down.

Free plan

Get told before it breaks.

Monitoring checks your site every 10 seconds from six locations, records its response time, and emails you the moment it slows down or goes offline.

$0 / month, forever

No credit card.

Monitor it free Compare plans

  • 1 monitor, checked every 10 seconds

    From six locations, confirmed before we alert, so no false alarms.

  • Certificate expiry alerts

    Email 30, 14 and 7 days before it runs out.

  • Security scans and change alerts

    Certificate, chain, headers, DNS and email security, with an email when anything changes.

  • Cloudflare offline page

    Visitors see a status page instead of an error while you fix it.

  • 12 months of history

    Every check, change and incident, kept for a year.

  • Slack, JIRA, Linear and Teams

    Send alerts where your team already works.