Skip to content
Somia Digital

Free, no sign-up

Test your website’s hosting

We measure three times how long your server takes to respond and look at how it’s set up: HTTP/2 and HTTP/3, compression, file caching and CDN. It’s the first thing that decides how fast a website loads.

We take three measurements in a row from our server and see how it responds. It takes a few seconds.

Want everything in one report? Run the full website audit

What makes hosting fast

Before the browser can draw anything, the server has to respond and send the files. These four things decide how long that takes.

  • TTFB

    Time to first byte

    It’s the time from requesting the page until the server’s first response arrives: connecting, encrypting the connection and waiting for the server to build the page. Google considers it good up to 0.8 seconds.

  • HTTP/2 · HTTP/3

    Many files over one connection

    With HTTP/2, the browser requests all the files at once over the same connection. HTTP/3 does the same over QUIC and copes better with unstable mobile networks. Both depend on your hosting or CDN.

  • Brotli · gzip

    Compress before sending

    The server can compress the HTML, styles and scripts before sending them, and the browser unpacks them in no time. Brotli and Zstandard compress more than gzip, but any of them is far better than none.

  • Cache · CDN

    Don’t send the same thing twice

    With good caching, the browser keeps files that don’t change and doesn’t request them again. A CDN keeps copies on servers around the world, closer to each visitor.

Domains & hosting

Want hosting that’s fast?

We host your website on fast servers, with compression, caching and a CDN set up properly, and we make sure it stays that way.

Questions about hosting

What is server response time (TTFB)?

It’s the time from when the browser requests the page until it receives the first byte. It includes connecting to the server, encrypting the connection and waiting for the server to build the page. Google considers it good up to 0.8 seconds and slow from 1.8.

Why is my time different from PageSpeed?

Because it’s measured from somewhere else. We measure from our server, three times, with a fresh connection each time; PageSpeed and your visitors measure from their own devices and networks. For real visitors, the benchmark is Google’s speed data in the full audit.

How do I know if my website has HTTP/2, HTTP/3 and a CDN?

With this test: we connect to your website and check which protocol the server negotiates (HTTP/2), whether it advertises HTTP/3 and whether the headers come from a known CDN such as Cloudflare, Netlify, Vercel, Fastly, CloudFront or Akamai.

If it looks bad, do I need to change hosting?

Not always. Often it’s enough to turn on compression, set up proper caching or put a CDN in front of the same hosting. If the server takes a long time to build each page, then it’s worth looking at a faster one.