Website Speed Test
Test a public webpage on mobile or desktop for Lighthouse performance, accessibility, best-practices, and SEO scores.
Enter a public URL and run a mobile or desktop audit. WhateverTools securely requests a Google PageSpeed Insights report through its server, retries short-lived provider throttling automatically, and turns the Lighthouse results into a compact scorecard, lab metrics, real-user data when available, and a prioritized fix list.
LIGHTHOUSE SCORECARD
A controlled Lighthouse run from Google. These numbers are useful for debugging one test run and can vary between runs.
Chrome UX Report data reflects actual Chrome visits collected over time when Google has enough data for the tested page or origin.
Failed or weak Lighthouse audits are sorted with measurable performance savings first, followed by lower-scoring accessibility, best-practice, and SEO checks.
EXTERNAL TEST NOTE: This tool sends only the public URL you enter and the selected mobile/desktop strategy to WhateverTools, which forwards that request to Google PageSpeed Insights. Recent identical reports may be reused briefly to avoid hammering Google's test quota, and a recent successful report may be shown if Google is temporarily throttling new tests. WhateverTools does not need your site login, source files, or analytics account. Only test pages that are intentionally public.
What the four scores mean.
Performance summarizes Lighthouse loading and responsiveness checks. Accessibility checks machine-testable accessibility rules. Best Practices looks for common web-platform and security problems. SEO checks technical discoverability basics. A score of 90–100 is generally considered good, 50–89 needs improvement, and below 50 is poor.
One test run and real-user history answer different questions.
Lab data is generated during this test under controlled Lighthouse conditions, so it is ideal for reproducing performance problems and testing changes. Field data, when available, comes from the Chrome User Experience Report and represents real Chrome users over time. A site can have good lab results and weaker field results—or the reverse—because devices, networks, geography, cache state, and user behavior differ.