Hosting Checker
The hosting checker shows which host a website runs on, whether a CDN sits in front, which country the server is in and which CMS it uses. It then places the site's real-user server response among other sites at the same host in the same market.
From the Solo plan
Prove whether a host migration worked
After a move, a plan keeps measuring your pages every day and stores field and lab data in the history. Add a note on migration day and you can see whether the new host responds faster.
How the hosting checker finds the host
The checker reads the response headers that some hosts set, then the hostname behind the server's IP address, and finally the network the IP belongs to. Name servers are not used, because they often only show where the domain was registered. When a CDN such as Cloudflare answers in front of the site, the real host stays hidden and the checker says so instead of guessing.
Server response compared with other sites at the same host
The checker takes the site's Time to First Byte from the Chrome UX Report: how long real Chrome visitors on phones waited for the first byte over the last 28 days. It then places that value among other sites at the same host that target the same market. If most of them respond faster, the cause is more likely the site's own setup, such as a missing page cache, than the host.
When the host itself is slow
The web hosting comparison shows for each market the median of a host's sites next to the median of all sites without CDN. If both the site and its host are above it, both are possible causes. The TTFB test then shows whether all pages respond slowly or only some, and the website speed test measures server response in the lab.
How quickly sites respond on each host is shown in the web hosting comparison.
FAQ
How do you find out who hosts a website?
Through response headers, the hostname of the server IP (reverse DNS) and the network of the IP (ASN). The hosting checker checks all three automatically.
Why does the checker not show the host behind Cloudflare?
Because the IP address then belongs to the CDN. In that case TTFB measures the CDN, not the host's server.
What is a good server response time?
According to web.dev, a TTFB up to 800 ms at the 75th percentile is good, up to 1,800 ms needs improvement.
Is my host the reason my site is slow?
The checker compares the site with other sites at the same host. If those respond much faster, the cause is more likely the setup.
More free tools
- TTFB Test: Shows how long real visitors wait for the first byte of a URL and of the whole origin, from Chrome UX Report data.
- Website Speed Test: Tests several pages of a site on mobile and desktop and shows real-user data, lab findings and competitors in one report.
- Image Compressor: Compresses and converts JPG, PNG, WebP and AVIF in bulk, with responsive sizes and srcset code. Images never leave your device.
- Core Web Vitals Test: Checks LCP, INP and CLS of real visitors against Google's thresholds and shows which pages fail and why.
- Mobile Website Speed Test: Measures how fast a site loads on phones, with real-user data from mobile Chrome and a throttled lab test.
- Performance Budget Calculator: Turns medians of comparable sites into limits for page weight, scripts and Core Web Vitals, with ready-to-use Lighthouse CI files.
A free account saves your tests and shows how your values change from one test to the next. Daily monitoring with field data and alerts starts with the Solo plan.