Manifest position 822 · CrUX rank bucket 1000
https://in.pinterest.com
Coverage complete
Coverage-complete audit of four representative public archetypes and preference/mobile/failure conditions.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | The dark-mode screenshot remains a white/light-grey surface and the DOM reports color-scheme: normal under prefers-color-scheme: dark. F01 high: The public experience ignores the system dark-colour preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | evaluate under prefers-reduced-motion: reduce found zero active animations. |
respect-user-preferencesrespects-contrast | pass | high | Lighthouse passed colour contrast and the preference probe confirmed prefers-contrast emulation with relevant CSS rules present. |
implement-natural-interactionsview-transitions | issues | high | The interaction video shows the consent layer disappearing and content changing without a directional or continuity cue; no active View Transition was observed. F02 medium: Major state changes are abrupt. |
implement-natural-interactionsscroll-driven-animations | pass | high | The recorded smooth scroll produced no long interaction task and no active scripted animation was found under reduced motion. |
implement-natural-interactionsphysical-gestures | pass | high | The public page relies on native scrolling; the recorded scroll remained controllable and no custom gesture trap was observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The interaction video shows a long content page with no progress or scroll-state response in its navigation chrome. F03 medium: The site chrome does not communicate scroll state. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, anchored popover, or edge-positioned menu was present in the audited unauthenticated paths. |
provide-guided-navigationdirects-attention | issues | high | The interaction video shows the consent layer disappearing and content changing without a directional or continuity cue; no active View Transition was observed. F02 medium: Major state changes are abrupt. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop, Explore and login captures all open with a viewport-dimming consent or login layer over the content; Explore is blocked by login before interaction. F04 high: Load-time overlays repeatedly obscure the primary content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The document probe finds a DIV role=dialog aria-modal=true; no <dialog> is present. F05 medium: The cookie modal is an ad-hoc ARIA dialog rather than the platform dialog primitive. |
maximize-content-reduce-noisereduced-chrome | pass | high | Desktop captures devote the page body to imagery and discovery content with a compact top navigation outside the prompted overlays. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At 360x800, layout reports scrollWidth 929 versus visual viewport 360, 569 px overflow; the screenshot clips headings and most of the consent dialog off-screen. F06 critical: The mobile homepage is horizontally clipped and unusable. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | Document probe confirms container-query CSS is shipped, and desktop cards adapt across the homepage and Explore layouts. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focused skip link computes outline:none and box-shadow:none; Lighthouse fails target-size for the Pinterest app controls. F07 high: Keyboard focus and touch-target treatment are insufficient. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The first viewport clearly states “Create the life you love on Pinterest” with Join and Log in actions. |
support-core-task-successprimary-flow-completion | pass | high | The representative unauthenticated login journey reaches a labelled email/password form with login, Google and signup choices; completion requiring real credentials was not fabricated. |
support-core-task-successclear-system-state-and-recovery | issues | high | A nonexistent URL renders the normal homepage rather than a clear 404/recovery state, while HAR records two 404 API calls and Lighthouse logs them as console errors. F08 high: Failure and recovery states are misleading or absent. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse reports LCP 18.4 s, CLS 0.463 and TBT 510 ms (performance score 0.23); trace corroborates 4.21 s LCP and two long tasks in a separate run. F09 critical: Core Web Vitals are far outside good thresholds. |
be-fast-and-stablevisual-stability | issues | high | Lighthouse reports LCP 18.4 s, CLS 0.463 and TBT 510 ms (performance score 0.23); trace corroborates 4.21 s LCP and two long tasks in a separate run. F09 critical: Core Web Vitals are far outside good thresholds. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse reports LCP 18.4 s, CLS 0.463 and TBT 510 ms (performance score 0.23); trace corroborates 4.21 s LCP and two long tasks in a separate run. F09 critical: Core Web Vitals are far outside good thresholds. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR captures 159 requests and 6,436,533 transferred bytes, including 78 scripts (2.90 MB), 45 images (2.46 MB) and 4 media requests (820 KB). F10 high: The unauthenticated landing page ships a very heavy dependency graph. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR records 78 script requests and 2.90 MB script transfer; Lighthouse identifies large first-party bundles and missing/403 source maps. F11 high: JavaScript dominates the initial load. |
be-inclusivenames-roles-labels | pass | high | Lighthouse passed image-alt and accessible naming audits; login inputs have programmatic Email and Password labels. |
be-inclusivesufficient-contrast | pass | high | Lighthouse colour-contrast audit passed on the homepage. |
be-inclusivestructure-and-focus | issues | high | The focused skip link computes outline:none and box-shadow:none; Lighthouse fails target-size for the Pinterest app controls. F07 high: Keyboard focus and touch-target treatment are insufficient. |
be-inclusivelegible-text | pass | high | Desktop screenshots show readable typography, comfortable line lengths and clear heading hierarchy on the public landing and Explore pages. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The 360 px screenshot is clipped with 569 px horizontal overflow and Lighthouse fails the target-size audit. F12 medium: Reflow and touch target accessibility fail on mobile. |
follow-best-practicesno-console-errors | issues | high | Lighthouse records a FedCM NetworkError and two first-party 404 requests during load; HAR confirms 404 responses. F13 medium: The page logs avoidable runtime and network errors. |
follow-best-practicessound-document-and-assets | issues | high | The image probe reports 36/36 images without width/height, 27 oversized, 35 below-fold not lazy, 11 without srcset and no modern-format images. F14 medium: Image delivery lacks robust sizing and responsive optimisation. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports a BFCache blocker and missing/403 source maps for large first-party modules. F15 medium: Browser platform hygiene has measurable regressions. |
be-discoverabletitle-and-description | pass | high | DOM reports title “Pinterest - India” and a descriptive meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Discoverability reports 1% rendered-word coverage, isJsShell:true and no raw-HTML h1; the crawler screenshot contains almost no core content. F17 high: The homepage core content is effectively a JavaScript shell for non-JS crawlers. |
be-discoverablecanonical-and-indexing-signals | issues | high | The live DOM canonical is https://www.pinterest.com/ while the audited URL is https://in.pinterest.com/; Lighthouse fails the canonical audit. F16 high: The India homepage publishes an invalid cross-locale canonical. |
be-discoverablestructured-and-shareable-metadata | pass | high | The page exposes JSON-LD plus six Open Graph tags matching Pinterest’s visible public identity. |
be-private-and-securesecure-transport-and-headers | issues | high | Cookies audit finds five cookies flagged insecure, including non-Secure g_state, _b and _routing_id and multiple SameSite=None cookies; CSP permits unsafe-inline and Permissions-Policy is missing. No client secrets were found. F18 high: Cookie and CSP posture is weaker than the transport baseline. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence finds nine third-party origins and Pinterest tracker endpoints; HAR attributes 137/159 requests and 6.28 MB to cross-origin hosts before consent was acted on. F19 high: Substantial tracking and third-party activity occurs on the initial experience. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | Login exposes email/password and Google/QR options; no passkey/WebAuthn affordance was observed. F20 medium: The observed login surface does not offer phishing-resistant authentication. |
be-private-and-securedefensive-browser-policies | issues | high | Cookies audit finds five cookies flagged insecure, including non-Secure g_state, _b and _routing_id and multiple SameSite=None cookies; CSP permits unsafe-inline and Permissions-Policy is missing. No client secrets were found. F18 high: Cookie and CSP posture is weaker than the transport baseline. |
be-resilientprogressive-enhancement | issues | high | Raw HTML is 1.1 MB yet contains only 7 content tokens and 1% of rendered words; without JavaScript the homepage is a shell. A board detail fares better at 57%. F21 high: The homepage does not progressively expose its core discovery content. |
be-resilientresilient-runtime-behaviour | issues | high | At 360x800, layout reports scrollWidth 929 versus visual viewport 360, 569 px overflow; the screenshot clips headings and most of the consent dialog off-screen. F06 critical: The mobile homepage is horizontally clipped and unusable. |
be-resilientoffline-and-installable | pass | high | Runtime confirms a service worker interface and linked manifest; the public shell has an installability foundation. Offline task completion was not claimed beyond this check’s app foundation. |
be-resilientnetwork-and-http-failure-states | issues | high | The synthetic missing route shows the normal homepage and HAR records failed first-party calls without a visible recovery state. F22 high: HTTP failures do not lead to intentional recovery UI. |
be-internationalisedlang-dir-and-logical-properties | pass | high | HTML lang=en, 37 hreflang variants, and logical-property CSS were observed. |
be-internationalisedlocale-aware-data | not-applicable | high | The representative public paths display no dates, currencies, numbers, durations or calendar data requiring locale formatting. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative public paths expose no event or time-zone-sensitive data. |
be-trustworthyno-dark-patterns | pass | high | Cookie dialog presents Reject all, Let me choose and Accept all at the same level; login and signup commitments are plainly labelled. |
be-trustworthyhumane-error-handling | issues | high | After requestSubmit() with empty email and password, the captured form remains visually unchanged with no clear inline error or recovery instruction. F23 medium: The login form did not expose visible empty-submit guidance in the exercised state. |
be-trustworthytrustworthy-input-assistance | pass | high | Observed signup/login fields use email, current-password/new-password and bday autocomplete tokens. |
be-trustworthysafe-commercial-and-account-flows | issues | high | Login exposes email/password and Google/QR options; no passkey/WebAuthn affordance was observed. F20 medium: The observed login surface does not offer phishing-resistant authentication. |
be-sustainableoptimised-assets | issues | high | HAR transfers 2.46 MB of images and 820 KB of media; image audit finds 27 oversized and zero modern-format images. F24 high: The media payload is disproportionate for the first unauthenticated viewport. |
be-sustainableno-wasteful-work | issues | high | The landing page performs 159 requests, including 78 scripts and 19 fetch/XHR requests, while Lighthouse reaches only 0.23 performance. F25 high: Initial background work and fetching are excessive. |
be-sustainablethird-party-and-media-budget | issues | high | HAR transfers 2.46 MB of images and 820 KB of media; image audit finds 27 oversized and zero modern-format images. F24 high: The media payload is disproportionate for the first unauthenticated viewport. |
be-agent-readystructured-agent-capabilities | not-applicable | high | Pinterest exposes no declared agent-facing transaction or productivity surface in the audited unauthenticated scope; this emerging capability is treated as an opportunity, not a failure. |
be-agent-readyon-device-inference | not-applicable | high | No audited task calls for on-device generation or summarisation, so built-in inference is not required. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten top-to-bottom scroll cycles, heap self size fell from 71.37 MB to 70.21 MB; node count rose only 1.8% across independently loaded snapshots, with no evidence of unbounded retained growth. |
be-memory-efficientbounded-footprint | issues | high | Heap summary contains about 1.12 million V8 snapshot nodes and 71.4 MB self size; runtime reports 56.0 MB used JS heap and 1,294 DOM elements. Repeated scroll did not increase total self size. F26 medium: The baseline memory footprint is high for an unauthenticated landing page. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Neither heap summary lists Detached* constructors among retained populations, and total self size did not grow after repeated scrolling. |
Provenance
Canonical report: results/atomic/reports/0822-in_pinterest_com.json
Report SHA-256: bbf006dd2c8888a0de1ce607472059b44d027fe089472bc83d9f86edb7141c65
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/in_pinterest_com/2026-07-23T06-09-44-686Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/in_pinterest_com/2026-07-23T06-09-44-686Z
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.