Reliability & safety
Availability over time, HTTPS behavior and carefully selected public security controls.
Technical score v0.1 is a 0–100 homepage health score. Once a website is observed, its earlier baseline is replaced with the following reproducible calculation.
score = availability + HTTPS + speed + title + description + commerce schemaSpeed points are calculated as max(0, 20 − floor(response_ms ÷ 250)). Scores are capped at 100. Ties are ordered alphabetically.
One server-side homepage request cannot describe checkout quality, mobile usability, delivery experience or business popularity. It is useful as a technical observation, but it is not yet a complete commerce index.
The active scoring formula is applied consistently across country indexes. Local categories and market context can differ, but a technical signal has the same definition and weight wherever it is observed.
Our crawler requests the public HTTPS homepage, follows redirects, reads at most 512 KB of HTML and stops after a bounded timeout. It does not sign in, add products to a cart, place orders or attempt to bypass access controls.
Each observation stores the time, response status, response duration, detected metadata and the score produced by that methodology version. A refreshed observation can move a score in either direction.
Global methodology does not imply a single worldwide leaderboard. Rankings are published within countries and relevant categories only when coverage is broad enough. We disclose tracked and observed counts, and retain the prototype label while most entries remain baselines.
This is a proposed framework, not the formula currently used on store profiles. We will validate weights against collected data and publish changes before activating them.
Availability over time, HTTPS behavior and carefully selected public security controls.
Mobile LCP, INP and CLS from eligible Chrome UX Report data, with lab data labelled separately.
Product discoverability, working catalogue signals, structured product data and transparent policies.
Indexability, metadata, canonicals, sitemaps and durable category/product information architecture.
Visible contact, returns, delivery and privacy information—not subjective reputation claims.
Observation freshness, repeatability, coverage and owner-verified facts, with explicit confidence.
Traffic or market-reach rankings require sufficiently representative, country-level evidence. We will not reverse-engineer visits from technical signals or mix self-reported analytics with unverified estimates. If introduced, popularity will be a separate dimension with its own confidence and methodology.
Real-user experience metrics and the rationale for evaluating their 75th percentile.
Chrome UX ReportCrUX methodology ↗Eligibility, collection and aggregation constraints for public field data.
Google Search CentralMerchant listing structured data ↗Product and Offer markup used to describe purchasable products.
OWASPSecure Headers Project ↗Vendor-neutral guidance for interpreting public HTTP security controls.
Tranco research rankingRanking methodology ↗Research on stability, aggregation and manipulation risks in popularity lists.
HTTP ArchiveWeb Almanac methodology ↗Large-scale public web measurement and documented dataset limitations.