Free tool
Paste your URL. We'll run a real Lighthouse audit against Google's own PageSpeed Insights server, then hand back a colour-coded scorecard for performance, SEO, accessibility & best-practices — plus the top opportunities to fix, sorted by impact.
What to do next
Related tool
Run the free SEO audit
Meta tags, OG cards, headings, schema, alt text — everything the speed test doesn't look at.
Try it
Get a hand-checked audit
Free 24-hour audit
A strategist reviews your live site + report and sends a prioritised written action plan within 24 hours.
Request audit
Fix it for me
Website design & development
A rebuild that ships with LCP ≤ 2.5s baked in — plus SEO structure, CMS, forms and analytics.
Explore
FAQ
Yes. Behind the scenes we call Google's official PageSpeed Insights API — the same engine that generates the reports at pagespeed.web.dev. That means the scores you see here match the ones Google's own tooling would show.
Lighthouse simulates a real device on a throttled connection, and network conditions vary by run. Google recommends running the test 3 times and taking the median. Small deltas (±5 points) are normal and don't reflect a real change in your site's performance.
Mobile, because Google's search index and Core Web Vitals ranking signals are mobile-first. If a page ranks well on mobile, desktop usually follows. We'll add a desktop toggle in a later iteration.
The three Core Web Vitals. LCP (Largest Contentful Paint) is how fast the main content becomes visible — target under 2.5s. INP (Interaction to Next Paint) is how snappy the site feels when you tap or type — target under 200ms. CLS (Cumulative Layout Shift) is how much the page jumps around while loading — target under 0.1.
Ship the top 1-2 opportunities listed on the report first — they're sorted by estimated load-time savings. If you'd rather have someone do it, book a free 24-hour hand-written audit at /audit or send a project brief at /start-a-project.
No. We proxy the request to Google, return the report and forget it. Nothing is stored on our side and no analytics event is emitted with the URL.