ShipworkSite inspection
Checks

Crawlability

PaginationAre paginated pages set up right?Internal searchIs site search eating crawl budget?URL parametersAre parameters creating duplicates?Log analyserWhat does Googlebot actually crawl?Robots builderNeed a robots.txt file?Soft 404sAre pages “not found” but returning 200?JavaScriptCan crawlers see it without running JS?FreshnessIs my site quietly going stale?Robots.txtDoes robots.txt say what I think?

Indexing

Sitemap lastmodAre my sitemap dates valid?SitemapIs my sitemap actually fetchable?IndexingIs Google allowed to index my pages?CanonicalsIs Google indexing the wrong URL?Index signalsDo sitemap and index signals agree?Sitemap generatorNeed a sitemap.xml for my site?Bulk URL statusWhere does each of these URLs really land?Redirect builderNeed the redirect rules?RedirectsAre my URLs answering directly, over HTTPS?

On-page

Keyword ideasWhat are people searching for?SERP previewHow does my page look in Google?Content qualityAre your pages too thin or too alike?Image weightAre images slowing the page?CannibalizationAre pages competing with each other?On-page checkDoes the page use its target phrase?ImagesAre my images accessible and loading?Meta tag builderWhat should my title and share tags say?DuplicatesDo my pages compete for one query?

Links

Orphan pagesWhich pages can no link reach?Link graphHow deep do your pages sit?Anchor textDo links say what they point at?Outbound linksAre external links still alive?Broken linksAre internal links sending visitors nowhere?

Structured data

Rich resultsIs my markup eligible for a rich result?Structured dataIs my product schema valid?Schema coverageDo my key pages carry structured data?Social previewHow does my page look when shared?Schema vs pageDoes markup match the page price?Schema builderNeed valid JSON-LD?

International

Hreflang sitemapDo page and sitemap hreflang agree?HreflangDo my language versions link back?Hreflang builderNeed the hreflang tags?Page DoctorWhy is this page not doing well?Redirect planMy site has dead links — what redirects do I write?Sitemap diffIs anything missing from my sitemap?Robots simulatorWhat does my robots.txt actually block?Can Googlebot?Can Googlebot fetch this URL?
Every error, explainedGuides
Pricing Learn Error guides Run free audit

+1 free check

Welcome to Shipwork

Sign in free and your next check this month is on us.

Continue with GoogleContinue with email

We email you a 6-digit code. No password.

No card needed. Reports and watches follow you to any device.

What does a Lighthouse score of 62 mean?

A Lighthouse performance score of 62 sits in the orange band: “needs improvement”. It is a lab estimate from one simulated load, not a ranking factor on its own. Here is how the number is built and what to do about it.

Published

The score bands

ScoreColourMeaning
90 to 100GreenGood
50 to 89OrangeNeeds improvement
0 to 49RedPoor

So a 62 is in the lower part of “needs improvement”. The same bands apply to the accessibility, best practices and SEO categories, but those scores measure different things: an accessibility score of 62 means a weighted share of the accessibility audits failed, not that the page is slow.

How the performance score is weighted

In current Lighthouse versions, the performance score is a weighted average of five lab metrics, each scored against real-world data:

  • Total Blocking Time: 30%
  • Largest Contentful Paint: 25%
  • Cumulative Layout Shift: 25%
  • First Contentful Paint: 10%
  • Speed Index: 10%

Total Blocking Time, Largest Contentful Paint and Cumulative Layout Shift make up 80% of the score, so a 62 usually means at least one of those three is weak. Open the report and look at which metric is red or orange first.

Why it changes between runs

Lighthouse loads the page once on a simulated mid-range phone and slow connection. Network conditions, server response time, third-party scripts, ads and A/B tests change between runs, so a score can move several points without any change to the site. Run it three to five times and use the median before deciding anything.

What moves the score

  • High Total Blocking Time: reduce or defer JavaScript, remove unused apps and tags, and split long tasks.
  • Slow Largest Contentful Paint: serve the main image in a modern format at the right size, do not lazy-load it, preload it if needed, and speed up the server response.
  • Layout shift: give images, embeds and ad slots fixed dimensions, and avoid inserting banners above content after load.
  • Slow First Contentful Paint: cut render-blocking CSS and fonts, and cache HTML at the edge where you can.

Lab score versus real users

Google’s page experience signals use field data, the Core Web Vitals measured from real Chrome users, not the Lighthouse lab score. A page can score 62 in the lab and still pass Core Web Vitals for real visitors, or the reverse. Check both: Shipwork’s Core Web Vitals check reads the real-user data from the Chrome UX Report, and the Lighthouse check shows the lab scores side by side.

Find out if this is happening to you

Shipwork shows Lighthouse lab scores next to real-user Core Web Vitals from the Chrome UX Report. Free, no account, no signup. Paste your store address.

Check real-user speed

Questions

Is a Lighthouse score of 62 bad?
It is in the 50 to 89 “needs improvement” band. It is worth fixing the weakest metric, but real-user Core Web Vitals matter more for search.
Does the Lighthouse score affect Google rankings?
Not directly. Google uses field Core Web Vitals from real Chrome users as one page experience signal, not the lab score.
Why does my score change every time I run it?
Each run is one simulated load, and network, server and third-party script timing vary. Use the median of several runs.

Keep reading