Manifest position 580 · CrUX rank bucket 1000
https://s.shopee.co.id
Coverage complete
The requested bare short-link host consistently redirected to https://shope.ee/error_page. The audit therefore covers that reachable invalid-link error surface; no valid tokenized destination, catalog, checkout, or account flow was supplied.
Attempts
1 / 3
Judged checks
58 / 58
Blocked
0
Not run
0
This report has no published overall score. Blocked and not-run checks are not passes. A coverage-complete report means every check has a judged outcome; it does not mean every check passed.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | Dark emulation remained a white surface with black text; computed color-scheme was normal and the CSS feature scan found no prefers-color-scheme rule. F001 medium: Add preference-driven dark theme support |
respect-user-preferencesrespects-reduced-motion | pass | high | Under prefers-reduced-motion: reduce, the page exposed zero active animations and zero non-zero transitions. |
respect-user-preferencesrespects-contrast | pass | medium | Forced-colors rendering kept the illustration and error text visible; Lighthouse reported no color-contrast violation. |
implement-natural-interactionsview-transitions | pass | high | The reached static error surface has no route/state control and therefore performs no abrupt state swap; active inventory found no transition interaction to mishandle. |
implement-natural-interactionsscroll-driven-animations | pass | high | The one-screen page has no scroll-linked motion or main-thread scroll animation; CSS and animation probes found no scroll animation implementation or active animation. |
implement-natural-interactionsphysical-gestures | pass | high | Active inventory found no pointer-driven custom gesture, carousel, disclosure, drag target, or platform-fighting gesture handler on the static surface. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | The document fits one viewport and has no navigation chrome that remains static or obscures content while scrolling. |
provide-guided-navigationanchored-positioning | pass | high | Active inventory found no tooltip, popover, menu, dialog, or manually positioned overlay that could drift from its anchor. |
provide-guided-navigationdirects-attention | pass | medium | The one-screen error state presents a single centered message with no navigation movement or competing destination that loses the user’s attention. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Desktop and mobile initial states contain only the error message; no overlay, interstitial, banner, dialog, or popover obscures it. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No overlay or rich disclosure control is present. |
maximize-content-reduce-noisereduced-chrome | pass | high | The surface is visually sparse and gives nearly all of the viewport to the error content, with no app frame or decorative chrome. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800, scrollWidth and clientWidth were both 360 with 0px horizontal overflow; the message reflowed legibly. |
adapt-to-the-form-factorcomponent-level-responsiveness | not-applicable | medium | The reached page has one fixed error component and no reused component shown in differently sized containers. |
adapt-to-the-form-factorinput-modality-aware | not-applicable | high | The page has zero focusable elements, links, buttons, or inputs. |
support-core-task-successclear-purpose-and-primary-action | pass | medium | The visible message clearly states that the requested page cannot be found; there are no competing calls to action. |
support-core-task-successprimary-flow-completion | not-applicable | high | The bare short-link domain contains no encoded destination or transaction flow to complete. |
support-core-task-successclear-system-state-and-recovery | issues | high | The page identifies a not-found state but offers no home link, retry, back action, search, or other recovery control; DOM probe found zero links and buttons. F002 high: Provide a useful recovery path |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse measured LCP/FCP at 4.48s (poor LCP); the trace corroborated a slower-than-needed 1.93s LCP in the local capture. CLS and TBT were 0. F003 high: Bring LCP into the good range |
be-fast-and-stablevisual-stability | pass | high | The mobile layout observer measured CLS 0 with no shifts; Lighthouse also measured CLS 0. |
be-fast-and-stableefficient-main-thread | pass | high | The trace measured 0 long tasks and 0ms total blocking time; layout observation also recorded no long tasks. |
be-fast-and-stableefficient-resource-delivery | issues | high | The 307 redirect adds about 1.2s; all three parser-inserted scripts lack async/defer, and Lighthouse estimated 2.07s render-blocking savings plus 197KiB cache-lifetime savings. F004 high: Remove the render-blocking delivery chain |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimated 134KiB unused JavaScript: 76.7% of the vendor chunk and 54.4% of React, disproportionate for a static error message. F005 medium: Stop shipping React/vendor code for the error page |
be-inclusivenames-roles-labels | pass | medium | There are no interactive controls, form fields, img or canvas elements requiring names/roles/labels; Lighthouse found no naming or role violation. The illustration is CSS decoration. |
be-inclusivesufficient-contrast | pass | medium | Lighthouse found no contrast violation, and the forced-colors capture retained visible text and illustration. |
be-inclusivestructure-and-focus | issues | high | Lighthouse reported no main landmark; the DOM contains no h1-h6 headings or landmarks, leaving the error message structurally unlabelled. F006 high: Give the error page semantic structure |
be-inclusivelegible-text | pass | high | The short error text is centered, unclipped, and comfortably readable at 360px. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The viewport explicitly sets maximum-scale=1 and user-scalable=no; Lighthouse flags this as disabling zoom for low-vision users. F007 high: Allow users to zoom |
follow-best-practicesno-console-errors | issues | high | The page logs a failed-resource error because /static/favicon.ico returns HTTP 404. F008 low: Fix the broken favicon request |
follow-best-practicessound-document-and-assets | pass | medium | The rendered document has an HTML doctype, UTF-8 charset, viewport metadata, and no img elements with sizing/aspect-ratio defects. |
follow-best-practicesbrowser-platform-hygiene | pass | medium | Beyond the separately recorded favicon console error, Lighthouse found no deprecated API/paste/prompt issue; the page has no inputs and triggered no permission UI. |
be-discoverabletitle-and-description | issues | high | The title is the generic implementation label “mkt single page application” and no meta description exists. F009 medium: Use descriptive page metadata |
be-discoverablecrawlable-and-mobile-friendly | issues | high | The page has zero crawlable links, and /robots.txt returns the SPA HTML rather than valid robots directives; the viewport is present but disables scaling. F010 high: Serve a valid robots.txt and crawlable recovery link |
be-discoverablecanonical-and-indexing-signals | issues | high | The requested URL 307-redirects to a generic cross-domain error page with no canonical; both robots.txt and sitemap.xml resolve to the same app shell instead of valid indexing resources. F011 high: Correct indexing and status signals |
be-discoverablestructured-and-shareable-metadata | not-applicable | high | The reached page is a generic error state rather than an article, product, organization, event, or other rich entity. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used and no cookies were set, but the main response lacks CSP, HSTS, X-Content-Type-Options, framing protection, Referrer-Policy, and Permissions-Policy. F012 high: Add baseline security headers |
be-private-and-securedata-minimisation-and-third-parties | pass | medium | No known trackers, cookies, or exposed secrets were found. Requests go only to Shopee-controlled delivery/redirect hosts and total 232KB. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | This error surface has no authentication flow and triggered no permission prompt. |
be-private-and-securedefensive-browser-policies | issues | high | No HSTS, frame-ancestors/X-Frame-Options, Referrer-Policy, Permissions-Policy, or CSP defense is present. F013 medium: Configure browser-enforced defenses |
be-resilientprogressive-enhancement | issues | high | Only 20% of rendered content tokens were present in raw HTML; #root ships empty and noscript says JavaScript is required, so the actual error explanation is unavailable without JS. F014 high: Render the error state without JavaScript |
be-resilientresilient-runtime-behaviour | pass | medium | The small runtime reaches a stable visible error state without clipped overlays or an infinite spinner; the only runtime error is the separately recorded favicon 404. |
be-resilientoffline-and-installable | not-applicable | high | This bare redirect/error endpoint is not an installable application surface and advertises no manifest. |
be-resilientnetwork-and-http-failure-states | issues | high | The invalid root redirects to a generic 200 error page, but provides no useful recovery option and even returns the same SPA shell for robots.txt/sitemap.xml rather than meaningful HTTP failure semantics. F015 high: Use intentional HTTP error and recovery behavior |
be-internationalisedlang-dir-and-logical-properties | pass | medium | The English error text is correctly marked html lang=en; the compact centered layout has no directional control or reading-order defect. |
be-internationalisedlocale-aware-data | not-applicable | high | No date, number, currency, duration, or locale-sensitive datum is rendered. |
be-internationalisedtime-zone-correctness | not-applicable | high | No times, events, recurrence, or time-zone-sensitive data is rendered. |
be-trustworthyno-dark-patterns | pass | high | The error surface has no consent wall, upsell, disguised ad, continuity trap, or manipulative control. |
be-trustworthyhumane-error-handling | not-applicable | high | No form or validation flow exists. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No input field exists. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, consent, authentication, or account-management flow is exposed. |
be-sustainableoptimised-assets | pass | medium | The two decorative PNG resources total about 10KB, and no img element has oversizing, legacy-format, or responsive-source defects. |
be-sustainableno-wasteful-work | issues | high | The static 51-character error state loads 211KB of JavaScript and Lighthouse identifies 134KiB as unused, making the implementation materially heavier than the task requires. F016 medium: Use a lightweight error implementation |
be-sustainablethird-party-and-media-budget | issues | high | 231,974 of 232,120 transferred bytes come from cross-origin Shopee delivery/redirect hosts, predominantly React/vendor JavaScript, disproportionate to a static error message. F017 medium: Reduce cross-origin delivery cost |
be-agent-readystructured-agent-capabilities | not-applicable | high | The invalid-link error endpoint exposes no commerce/product action or other safe capability for an agent to invoke. |
be-agent-readyon-device-inference | not-applicable | high | On-device inference would not improve this deterministic error message. |
be-memory-efficientno-leak-under-repeated-interaction | not-applicable | high | The page has no representative interaction to repeat; no synthetic interaction was fabricated. |
be-memory-efficientbounded-footprint | pass | medium | The loaded SPA error state retained 82,622 heap nodes and 4.29MB self size, a bounded single-state footprint with no evidence of runaway allocation. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | The baseline heap summary showed no Detached* constructor among the dominant populations; with no repeated interaction, no accumulating listener/timer path was present to exercise. |
Provenance
Canonical report: results/atomic/reports/0580-s_shopee_co_id.json
Report SHA-256: e6018eb1a67cc8d9f2944e3681f7680b75bc6e125f5b3d2c6af8cba78a12713c
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/s_shopee_co_id/2026-07-21T17-28-54-499Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/s_shopee_co_id/2026-07-21T17-28-54-499Z
Catalog SHA-256: sha256:78ccfdb2d483f4c57d9dafed80fd86c6265585a56457c8dcfddc254b80fb44d7
Raw screenshots, HARs, traces, heaps, and other browser artifacts are retained at the local evidence root and intentionally are not committed. Artifact paths in the canonical report are relative to that root.