Website Performance Check

Measure real document timings, inspect delivery overhead, and pull PageSpeed snapshots when a Google API key is configured. AI web research can add public-market context, but direct measurements still win if the two disagree.

What this website performance report actually answers

People usually arrive here with one of four questions: how fast does this website load, what is slowing it down, what does Google PageSpeed think, and what can I learn about the site’s traffic or competitors from the public web.

Start with the measured timings. They tell you how fast the document responded from this server on this run, which is useful for catching slow redirects, weak caching, and heavy HTML responses. Then compare that against the PageSpeed snapshot when it is available. After that, use the research block for keyword, competitor, and market context that comes from public evidence rather than guesswork.

Website speed test

Use the measured timings when you want a quick answer to “how fast does this page respond from the outside?”

Core Web Vitals check

Use the PageSpeed and field-data sections when you need a rough Lighthouse-style view of loading and interaction quality.

Traffic and competitor research

Use the AI research block when you want public-web clues about keywords, alternatives, and market positioning, with blanks left blank if the evidence is thin.

International performance notes

Website speed is not one number for the whole planet. A page can feel fast in London, Frankfurt, Singapore, or São Paulo for different reasons depending on the CDN footprint, origin region, network quality, and how much JavaScript the browser still has to execute after the first response.

Treat this page as an external checkpoint, not a final verdict. For a genuinely global product, compare this report with your own analytics, real-user monitoring, and country-level search data before you decide what to optimise first.

Performance FAQ

What if PageSpeed is blank?

That usually means the Google API key is missing or the quota is exhausted. The synthetic timing section is still valid and continues to run.

Where do traffic estimates come from?

From public-web research when enough signal exists. If the public evidence is weak, the section stays blank instead of inventing numbers.

What should I read next?

Use the Core Web Vitals guide for optimization priorities and Domain Lookup when the delivery path or DNS layer looks suspicious.

Can I use this for competitor research?

Yes, in a limited way. The public-web research layer can surface likely competitors and keyword themes, but it is still weaker than first-party market data.

What is website performance?What is website uptime?Core Web Vitals guideWhat is TTFB?Lab vs field dataEstimate website trafficWebsite down or slow?Speed test vs PageSpeedDomain lookupCDN vs origin guideImage resizer

Keep exploring

Jump straight to our most-used IP intelligence tools.