Lighthouse SEO Score: 100 on an Ecommerce Category Page
A Lighthouse SEO score of 100 is easy to fake on a tiny static page. It is harder on a real ecommerce category page with product cards, images, pricing, stock state, filters, canonicals, structured data, and a backend that still has to feed fresh commercial data.
I ran Lighthouse on June 17, 2026 for `https://www.cigge.se/e-cigaretter/engangs-vape`. The desktop result was clean across the board: 100 Performance, 100 Accessibility, 100 Best Practices, and 100 SEO. The mobile result held up as well: 97 Performance, 100 Accessibility, 100 Best Practices, and 100 SEO.
That does not mean the page is “done” with SEO. It means the technical base is strong enough that SEO work can focus on content, intent, internal links, commercial data, and authority instead of fighting broken markup, slow rendering, or messy crawl signals.
The Result
| Lighthouse audit | Desktop | Mobile |
|---|---|---|
| --- | ---: | ---: |
| Performance | 100 | 97 |
| Accessibility | 100 | 100 |
| Best Practices | 100 | 100 |
| SEO | 100 | 100 |
The tested URL was a live ecommerce category page, not a stripped demo route. That matters. Category pages are usually where headless ecommerce gets messy first.
Among Swedish vape ecommerce pages I have worked with or tested, I have not seen a faster category-page result. I would only call it Sweden's fastest vape site after a controlled competitor benchmark, but this page is a serious candidate: perfect Lighthouse scores on desktop, 97 mobile performance, and real commerce data on the page.
A product detail page has one main product. A category page has many products, many images, sorting, filters, pagination, product availability, price changes, marketing text, and internal linking. The page has to serve shoppers, search engines, and the CMS team at the same time.
What a Lighthouse SEO Score Proves
Lighthouse is an automated audit tool from Google’s Chrome team. It checks performance, accessibility, best practices, SEO, and other web quality signals. Google PageSpeed Insights also uses Lighthouse for lab diagnostics.
A green score is not a ranking guarantee. Google’s own documentation treats 90 and above as good, and a perfect 100 as hard to sustain once a page carries real product data and production scripts.
So I read this Lighthouse SEO score as a technical proof point, not a victory lap. The page passes the baseline checks that often block ecommerce SEO: crawlable HTML, proper metadata, accessible structure, stable performance, and no obvious browser or security mistakes.
Why Ecommerce Makes This Hard
Ecommerce pages create SEO failure modes that do not show up on simple marketing pages.
Product grids can ship too much JavaScript. Product images can destroy performance if they are not sized and prioritized correctly. Filters can create crawl traps. Pagination can split signals. CMS descriptions can break heading structure. Variant URLs can create duplicate pages. Stock updates can force broad cache purges. Backend image URLs can leak local or private paths. Structured data can drift away from what the shopper sees.
One weak layer can drag the whole page down.
This score came from treating the category page as a system, not as a template with a few meta tags. That same system view sits behind my work on scaling ecommerce with Next.js→.
The SEO Work Behind the Score
The important work happened before the Lighthouse run.
We cleaned category canonicals so page one and paginated category routes share a consistent base. That reduces duplicate-page confusion and keeps pagination from fighting the main category URL.
We restored a template H1 fallback when the editable category description does not provide one. That sounds small, but missing H1s were one of the clearest technical SEO defects in the crawl data.
We fixed sitemap origin handling so public URLs resolve from the correct storefront origin instead of leaking backend assumptions. A sitemap should be boring. If it contains wrong hosts, non-indexable URLs, or blocked URLs, it wastes crawl attention.
We tightened localized canonicals and hreflang return links. Multilingual ecommerce SEO fails when each language points outward but does not receive a matching return path.
We also hardened product and merchant structured data. Ecommerce schema has to match reality: product, offer, availability, merchant details, and shipping details need to line up with the page and the backend state.
The Crawl Cleanup Was Bigger Than One Score
The Lighthouse screenshot is a clean artifact, but the deeper SEO value came from the crawl fixes around it.
A follow-up technical audit showed the direction clearly:
| Issue type | Before | After |
|---|---|---|
| --- | ---: | ---: |
| Robots-blocked URLs | 1,612 | 7 |
| Missing H1s | 999 | 67 |
| Non-indexable URLs in sitemap | 1,185 | 14 |
| Missing hreflang return links | 102 | 4 |
| Multiple H1s | 245 | 2 |
| Non-sequential H1 structure | 2,529 | 2 |
Those are the numbers I care about more than the green circles. Lighthouse tells me the page passes a high-quality lab check. Crawl data tells me the site is becoming easier for search engines to understand at scale.
Performance Needed Cache Discipline
The performance score did not come from one image tweak.
The storefront uses a Next.js frontend over a PrestaShop backend. That setup gives you speed when cache boundaries are clear, and pain when invalidation is too broad.
We moved toward scoped invalidation instead of site-wide purges. Product events, stock events, category changes, manufacturer updates, image changes, CMS edits, and blog/bootstrap events do not all need the same blast radius. When a stock event purges the whole storefront, users pay for it with slower pages and colder caches.
The better model is simple: invalidate the smallest useful set of cache tags, then let the frontend keep serving stable category and product pages quickly. The same engineering pattern shows up in my custom CRM CMS with Next.js→ work: give editors power without letting dynamic data damage the frontend.
That is why the category page can carry real ecommerce data and still reach 100 desktop performance and 97 mobile performance.
Clean HTML Still Matters
Modern ecommerce teams often treat SEO as metadata plus schema. That is too narrow.
The page still needs semantic HTML. It needs one sensible H1. It needs category copy that can be edited without breaking the document. It needs product links that render as links. It needs images with proper dimensions and alt text. It needs canonical URLs that do not change because a filter or pagination state got mixed into the wrong layer.
This is where the PageBuilder and rich-text work matters. A CMS editor should make content easier, not create malformed category HTML. The Tiptap React editor→ work helped keep editable blocks practical while still respecting the storefront’s HTML and safety rules.
The same rule applied when I rebuilt older content systems during a headless WordPress migration→: keep the editor experience flexible, but keep the public HTML predictable.
What I Would Not Claim From This
I would not claim that a Lighthouse 100 SEO score means the page will rank first.
Search rankings still depend on query intent, product range, pricing, brand trust, internal linking, backlinks, content quality, user behavior, and how Google interprets the whole site.
I would also not use Lighthouse as the only performance source. Lab results are useful because they are repeatable. Field data matters because it comes from real users on real devices and networks.
The honest claim is narrower and stronger: this ecommerce category page passed a strict technical quality gate while still behaving like a commercial page.
The Practical Takeaway
For ecommerce SEO, I want the technical platform to get out of the way.
That means category pages render useful HTML. Canonicals and sitemaps tell one story. Hreflang is reciprocal. Product data and structured data match. Caches stay warm after small backend changes. Editors can add content without damaging the page structure. Images load fast without hiding the product.
When those pieces line up, a Lighthouse SEO score like this becomes possible. More important, the SEO team can spend time on the work that actually compounds: content, product coverage, internal links, conversion, and authority.
I see the Lighthouse result as evidence of engineering quality. The score is the visible part. The value is the system behind it.
