Lighthouse score, live.
Enter a URL. Get a Lighthouse score across Performance, SEO, Accessibility, Best Practices. Mobile + desktop strategy toggle. Top audit findings ranked by impact. Runs on Google PageSpeed Insights; no signup, no email gate.
Single-purpose Lighthouse scorer. The form below sends your URL to Google's public PageSpeed Insights v5 API, parses the four category scores (Performance, SEO, Accessibility, Best Practices), and returns the top audit findings ranked by impact. No signup. No email. Mobile + desktop toggle. Typical run: 25 to 50 seconds.
Privacy: the URL is sent only to Google's public PageSpeed Insights API. Zero server state on Digital Heroes. Recent scans use browser localStorage and stay on your device.
What the four numbers actually represent.
Performance is a weighted average of five lab metrics: Largest Contentful Paint (25%), Total Blocking Time (30%), Cumulative Layout Shift (25%), First Contentful Paint (10%), and Speed Index (10%). Lighthouse simulates a 3G-throttled mid-tier mobile device on Google's servers, then maps each metric onto a log-normal curve calibrated to the median of HTTP Archive's mobile crawl. A score of 90 means your page is in the top decile of the public web on that device profile — that is genuinely difficult to achieve on a Shopify theme without engineering work.
SEO aggregates roughly 14 audits including page title presence and length, meta description, robots.txt validity, indexability (no `noindex`), structured data validity, mobile viewport tag, link-text descriptiveness, hreflang correctness, image `alt` attribute presence, and HTTP 200 status. SEO almost always scores 95+ on a competently-built page; if it does not, the failures are usually misconfigurations (forgotten `noindex`, missing canonical) rather than performance issues.
Accessibility runs axe-core against the rendered DOM and reports about 50 audits including color contrast (WCAG 2.1 AA at 4.5:1 normal, 3:1 large), tap-target size (48×48 px minimum), heading-order sanity, ARIA correctness, and form-label association. Note the well-known limitation: Lighthouse cannot detect every accessibility issue; manual screen-reader review and keyboard-only tests catch what automation misses. The score is a floor, not a ceiling.
Best Practices covers HTTPS coverage of all sub-resources, absence of console errors at load time, absence of known-vulnerable JavaScript libraries (via the public Snyk vulnerability database), Content Security Policy presence, and image aspect-ratio correctness. It is the easiest 100 to earn but the easiest to lose if a careless third-party script gets added.
The numeric thresholds Google publishes are: 90-100 Good, 50-89 Needs Improvement, 0-49 Poor. We mirror those bands in the score color (moss for Good, amber for Needs Improvement, red for Poor) so the visual matches the official rubric.
Lab vs field. Which question are you asking?
Use this tool for a fast, single-URL technical audit. The Lighthouse score is lab data — a single simulated run on Google's emulated mid-tier device. It is excellent for diagnosing what to fix, because every audit comes with a specific recommendation. It is less reliable as a measurement of "how fast my site actually feels" because real users have wildly different devices, networks, browser cache states, and ad-blocker configurations.
For "how fast does it feel to my real users", switch to our Core Web Vitals Checker which surfaces the 28-day p75 field data Google publishes via the Chrome User Experience Report (CrUX). Field data is what affects your search rank; lab data is what tells you the diagnosis.
For a multi-URL audit (5 to 20 pages at once), the flagship Website Audit tool runs the same Lighthouse engine across multiple pages with a consolidated DH-branded scorecard.
For checking specific things on the same URL (DNS, SSL, domain age, registration), the Domain Health Checker bundles four public APIs into one composite view.
For a deeper accessibility audit beyond Lighthouse's automated rules, you need manual review — keyboard-only walk-through, screen-reader test (NVDA on Windows, VoiceOver on macOS), and a focus-order audit. We cover that in our UI/UX accessibility service.
Where each score lands. Realistic benchmarks.
Performance 30-50 on mobile is the typical state of an unoptimized Shopify theme with three to five third-party apps installed (heat-mapping, popup, reviews, chat widget, subscription engine). The fastest single-day fix: defer the chat widget and lazy-load the review widget. That alone usually adds 10-15 points.
Performance 50-75 indicates the theme was built with attention but is hitting a third-party-script ceiling. Audit the chain of `<script src>` tags in `
`. Anything not strictly required for first paint should move to the bottom of `` or be loaded asynchronously. Convert critical hero images to WebP/AVIF with `srcset` for responsive sizes.Performance 75-90 means the engineering is solid and the wins now come from CDN tuning (HTTP/2 push, brotli compression, edge caching of HTML for anonymous traffic). For Shopify, this is where the platform's CDN is doing most of the lifting; adding Hydrogen or moving JavaScript to streaming SSR pushes you into the 90s.
Performance 90-100 is genuinely exceptional. Watch for regressions every time a new third-party script ships; quarterly Lighthouse runs catch the drift before it costs ranking. Set up a Lighthouse CI in your deploy pipeline so the score becomes a hard gate, not an aspiration.
SEO under 95 on a content page is almost always a misconfiguration — a stray `noindex`, a missing canonical, a robots.txt that blocks /products/, or a meta description that runs over 160 characters. The audit findings panel above tells you exactly which.
Accessibility under 90 is usually color contrast plus tap-target sizing. The Color Contrast Checker handles the first; the second is fixed in CSS by setting a minimum 48×48 px hit-area on every interactive element (use padding, not just width/height).
Six questions users ask.
How is the Lighthouse score calculated?
The score is computed by Google's Lighthouse engine and surfaced through the public PageSpeed Insights v5 API. Each of the four categories (Performance, SEO, Accessibility, Best Practices) returns a 0-100 score that is a weighted aggregate of the audits in that category. Performance weights LCP heaviest at 25%, then TBT at 30%, CLS at 25%, then FCP and Speed Index. Our tool calls the API and renders the result; we do not modify the scoring.
Why does the score change between runs?
Lighthouse runs against a virtualized device on Google's servers and the result varies with network jitter, CDN cache state, third-party script load order, and queue depth at PageSpeed Insights itself. Three to five back-to-back runs typically land within 5 to 10 points of each other. For a stable measurement, average three runs or pull 28-day field data via our Core Web Vitals Checker.
Mobile or desktop — which should I optimize for?
Google's mobile-first index uses the mobile score for ranking. Optimize for mobile first; desktop scores generally trail mobile by 10 to 30 points because of the simulated 3G throttling, but the desktop fixes follow the mobile fixes. If your traffic skews 70/30 mobile/desktop, weight mobile work 80% of the time.
What is a good Lighthouse score?
Google's published thresholds: 90-100 is Good, 50-89 is Needs Improvement, 0-49 is Poor. Most Shopify themes ship between 30 and 60 on Performance without optimization; SaaS marketing sites built on Next.js typically hit 80-95 on Performance out of the box. SEO and Best Practices should run 95+ without effort; if they do not, the page has misconfigurations rather than performance problems.
Does this tool store my URL?
No. The URL you enter is sent only to Google's public PageSpeed Insights API. Nothing is logged on Digital Heroes servers. The 'recent scans' panel uses your browser's localStorage and stays on your device. There is no signup, no email collection, no analytics beacon that includes your URL.
What if PageSpeed Insights throttles or fails?
The free PSI quota resets every 24 hours. If you hit the throttle, wait 30 to 60 seconds and retry, or run the same URL on web.dev/measure or pagespeed.web.dev directly — both use the same Lighthouse engine. The error panel in this tool surfaces the upstream message verbatim so you know whether the failure is throttling, an unreachable URL, or a Lighthouse internal error.
Score under 60? Two-week fix.
A 30-minute call covers the top three findings, the engineering shape required, and a fixed-price quote for the lift. Most Shopify Plus stores see +30 Lighthouse points across two weeks of focused work.