Website speed test.

What this test measures

This is a test from our server. It shows how fast your server responds and what your page asks visitors to download. It doesn't run the page in a browser, so it can't measure Core Web Vitals such as LCP, INP and CLS, which depend on the visitor's device and connection. Your server may also be nearer to or further from our server than your customers are, so use the timings to compare and track, not as an exact figure.

Reading the timings

• Connect and SSL: opening a secure connection to the server.
• Server response (TTFB): the wait until the first byte arrives. Google suggests 800 ms or less as a good target.
• Full HTML: when the page's HTML has fully downloaded, before images and scripts.

What usually makes the biggest difference

• Slow server response: add page caching, upgrade from overloaded shared hosting, or put a CDN in front.
• Heavy pages: compress images with the image compressor and resize them with the image resizer.
• Too many scripts: remove unused plugins and tracking tags, and defer the rest.
• No compression: turn on gzip or Brotli. The page size checker shows the effect on each file.

Does speed affect rankings?

Yes, but modestly. Core Web Vitals are one of many signals, and good content on a slower page can still outrank a thin, fast one. The bigger payoff is often in conversions, because people abandon slow pages, particularly on mobile data. If you want it handled for you, our speed optimization service covers all of this.