Performance score
Connection timings
Core Web Vitals
Lighthouse categories
Security headers
Delivery & TLS
Real-user Core Web Vitals (CrUX)
Mobile screenshot
Desktop screenshot
Detailed analytics
Request chain
Page details
Mobile diagnostics
Desktop diagnostics
Resource breakdown (mobile)
Third-party code (mobile)
Opportunities
History for
Total load time (ms)
Performance score
Previous runs
Pages tested on
Latest result for each tested page on this site only.
Performance score
Total load time (ms)
How it works
One URL in, a full performance picture out. Every run takes about 2–3 minutes.
-
1
Enter your URL
Paste any public page. We validate it, queue the run and show live progress while it works.
-
2
We test it from Australia
Real connection phase timings (DNS, connect, TLS, TTFB, download) plus two full Lighthouse passes: throttled mobile and desktop.
-
3
Get scores you can act on
Performance scores, Core Web Vitals, screenshots and prioritised improvement opportunities, with a link you can share.
What you get in every test
Mobile vs desktop scores
Two separate Lighthouse runs show how your page really feels on a throttled phone versus a desktop connection.
Core Web Vitals
LCP, CLS and total blocking time: the metrics Google uses to judge page experience, measured in a real Chromium browser.
Connection timings
Phase-by-phase curl timings reveal whether the delay is DNS, TLS, a slow server response or a heavy download.
History & trends
Every run is saved, so you can chart load time and score over time and prove an optimisation actually worked.
Site-wide comparison
Tested more than one page on your site? Compare their latest scores and load times side by side.
Shareable results
Each result has a permanent link with a preview card, ready to drop into a ticket, chat or client email.
Frequently asked questions
What does WebTest actually measure?
Each run measures connection phase timings (DNS lookup, TCP connect, TLS handshake, time to first byte and download) with curl, then loads your page twice in a real Chromium browser using Google Lighthouse: once with mobile emulation and network throttling, once as desktop. You get performance scores, Core Web Vitals, screenshots, a resource breakdown and improvement opportunities.
What is a good Lighthouse performance score?
Lighthouse scores run 0–100. 90 or above is considered good, 50–89 needs improvement, and below 50 is poor. Mobile scores are usually lower than desktop because the test simulates a mid-range phone on a throttled connection.
Why are my mobile and desktop scores so different?
The mobile pass emulates a slower device and network, so JavaScript-heavy pages are hit much harder. If desktop scores well but mobile does not, the usual culprits are large scripts, unoptimised images and third-party code.
Where are the tests run from?
All tests run from Australian infrastructure, so the timings reflect what visitors in Australia actually experience: especially relevant if your site is hosted overseas.
How often can I test, and are results saved?
You can run up to 10 tests per hour. Every result is saved with a permanent shareable link, and repeat tests of the same page build a history so you can track trends over time.
How do I improve my score?
Start with the opportunities listed in your result: they are ordered by estimated saving. Common wins are compressing and resizing images, reducing JavaScript, enabling caching and compression, and moving to faster hosting closer to your visitors.