Docs Speed

Server response time

Measures how long your homepage takes to start answering scorebadge's request. Under 800 ms passes. Shown for information; not part of the score.

SpeedWeight 0 (shown, not scored)In reports as server-response

What it checks

We time one request to https://yourdomain/, from sending it to receiving the response headers. Redirects on the way are included. The request comes from scorebadge's servers, so the result depends partly on where those are compared with yours.

Why it matters

Nothing on the page can start loading until the server answers. A slow first answer delays every other step, and it is often the cause behind a slow Largest Contentful Paint.

How to fix it

Cache the homepage so the server does not build it from scratch for every visitor, serve it from a CDN close to your visitors, and look for slow database queries, plugins or a server that sleeps between visits. A long redirect chain adds time too.

Platform notes

WordPress

A page caching plugin or your host's built-in cache usually makes the biggest difference. Cheap shared hosting is often slow to answer.

Cloudflare

By default Cloudflare does not cache HTML. A cache rule for your pages can serve them from the edge.

Next.js, Vercel and Netlify

Pages rendered on every request are slower to answer than static or cached ones. Use static rendering or caching where the content allows it, and watch for cold starts on serverless functions.

Your report shows what this check found on your site. Pro shows the exact fix for your site. See pricing.

See what this check finds on your site

Free, about 30 seconds, with every other check included.