If an important capability exists only after a script runs, a JavaScript failure is no longer a minor UI problem — part of the store offer disappears for users, search or AI systems.
Implementation in progress
HTML-first: core facts and actions are available immediately
We found 16 areas where JavaScript could hide not decorative elements but important data and actions: navigation, delivery, payment, product content and parts of the purchase flow. I defined an HTML-first approach: critical capability exists immediately, JavaScript improves the experience.
Case at a glanceAudited the JavaScript dependencies, defined the target HTML-first architecture and prioritized implementation by criticality.
Sixteen dependent blocks are grouped into five workstreams. Each has a defined baseline for what must be available before JavaScript.
01HTML baseline→02JavaScript→03Enhanced UX
Navigation, commercial terms and important product content should not disappear just because a script fails.
HTML-first is about commerce resilience, not an SSR preference
If navigation, delivery, purchase terms or important product content appear only after JavaScript runs, a script failure stops being a minor UI issue and removes part of the store offer for users, search or AI systems. The goal is a usable commercial baseline in HTML, with JavaScript enhancing the experience.
Key finding02
Sixteen problem areas across five workstreams
The issues are grouped into navigation, regionality, purchase, product content and additional UX.
Navigation & structure
Catalog and important links exist in HTML rather than appearing only after a script runs.
Region & delivery
Region, delivery terms and fallback behavior have a clear initial state.
Purchase & terms
The buy action and key commercial terms do not disappear completely without JavaScript.
Content & trust
Descriptions, specifications, reviews and Q&A exist independently of tabs and modals.
Additional UI
Gallery, recommendations, favorites and filters each get an explicit baseline behavior.
Why visual inspection alone is not enough
After JavaScript runs, the interface may look complete, but that does not show what exists in the source HTML. The inventory found cases where navigation, regional conditions, commercial facts and parts of the purchase journey were missing or incomplete without the client layer.
What must work before JavaScript
Critical facts and core actions exist in HTML; JavaScript adds convenience and interaction.
HTML baseline
Critical facts, links and core actions are available immediately.
JavaScript on top
Scripts improve the interface but are not the only source of important content.
What this means in practice
For each block, ask one simple question: what should the user still see and do before JavaScript loads?
Navigation
Catalog and important footer links exist as HTML; JavaScript handles disclosure and animation.
Regionality
A fallback region and core delivery terms exist first; auto-detection remains an enhancement.
Purchase
A core action and key conditions exist first; JavaScript makes the interaction faster and richer.
Product page
Tabs control presentation, while the underlying content is already present on the page.
SSR is one implementation option
Server-side rendering can be part of the solution. The simpler criterion is whether the required fact or core action actually exists in HTML before the client interface runs.
What users and crawlers can lose without JavaScript
The problem was not one SEO tag: part of the commercial experience existed only after scripts executed.
Before: critical areas depend on JS
Catalog navigation, regional terms, buy actions, descriptions, delivery, reviews, and part of the gallery could be missing or incomplete.
Target: HTML carries the baseline
Navigation, key facts, and primary actions are present immediately; JavaScript adds fast add-to-cart, calculators, modals, and other enhancements.
Context & measurement
- Context
- Large e-commerce business · real initiative
- Scale / period
- 16 dependent blocks · 5 workstreams · implementation in progress
What to measure after implementation
After implementation, measure critical facts in HTML, key actions without JavaScript, extraction success, crawl/render consistency and CWV/conversion guardrails.
Commerce resilience
Facing a similar challenge?
Tell me where SEO is blocked by product, engineering or data.