Manifest position 423 · CrUX rank bucket 1000

https://www.wattpad.com

Coverage complete

Coverage-complete report-mode audit across five representative archetypes/conditions.

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 / checkStatusConfidenceEvidence or reason
respect-user-preferences
respects-color-scheme
issueshighThe dark-condition screenshot remains white and home-probe.json reports colorScheme normal, a white body background, no prefers-color-scheme rule.
F01 medium: The public experience stays light when the user requests a dark color scheme.
respect-user-preferences
respects-reduced-motion
passhighReduced-motion probe found no active animations and auto scroll behavior under reduce.
respect-user-preferences
respects-contrast
passhighForced-colors screenshot kept navigation, hero, consent controls, and text visible.
implement-natural-interactions
view-transitions
passhighLive CSS inspection found view-transition rules; the recorded start-reading interaction provides route-transition evidence.
implement-natural-interactions
scroll-driven-animations
passhighLive CSS inspection found animation-timeline/scroll-timeline usage with no observed long scroll tasks.
implement-natural-interactions
physical-gestures
passhighLive CSS inspection found scroll-snap behavior and mobile screenshots show native horizontal content rails.
provide-guided-navigation
scroll-state-aware-chrome
passhighLive CSS contains scroll-timeline behavior and representative screenshots show stable responsive navigation chrome.
provide-guided-navigation
anchored-positioning
passhighLive CSS inspection found anchor-name/position-anchor declarations.
provide-guided-navigation
directs-attention
passhighThe recorded Start reading interaction and clear carousel controls provide directional attention cues.
maximize-content-reduce-noise
no-intrusive-interruptions
issueshighDesktop, mobile, listing, story, search, and login screenshots show a first-load panel for 1,013 partners covering a substantial portion of the viewport. The probe identifies a custom DIV role=dialog without aria-modal.
F02 high: A large consent panel interrupts every audited public route and obscures primary content.
maximize-content-reduce-noise
semantic-dismissible-primitives
issueshighDesktop, mobile, listing, story, search, and login screenshots show a first-load panel for 1,013 partners covering a substantial portion of the viewport. The probe identifies a custom DIV role=dialog without aria-modal.
F02 high: A large consent panel interrupts every audited public route and obscures primary content.
maximize-content-reduce-noise
reduced-chrome
passhighRepresentative screenshots devote the post-consent page primarily to stories, genres, and reading actions.
adapt-to-the-form-factor
responsive-no-horizontal-scroll
passhighMobile layout probes measured 0px horizontal overflow at 360x800 on home and story.
adapt-to-the-form-factor
component-level-responsiveness
passhighLive CSS inspection found @container usage and mobile/desktop captures show components changing composition.
adapt-to-the-form-factor
input-modality-aware
issueshighThe objective DOM probe counted 19 visible controls below 24px on both home and story, and 15 on login. Lighthouse accessibility was 0.97 but does not negate these measured target dimensions.
F03 medium: Numerous interactive targets are smaller than a robust touch target.
support-core-task-success
clear-purpose-and-primary-action
passhighHero and story screenshots clearly state the offer and expose Get started / Start reading actions.
support-core-task-success
primary-flow-completion
issueshighDesktop, mobile, listing, story, search, and login screenshots show a first-load panel for 1,013 partners covering a substantial portion of the viewport. The probe identifies a custom DIV role=dialog without aria-modal.
F02 high: A large consent panel interrupts every audited public route and obscures primary content.
support-core-task-success
clear-system-state-and-recovery
issueshighThe unknown-route request redirects to /user/this-route-does-not-exist-web-uplift, then returns HTTP 404 with the generic homepage title and an h1 aria-label of “s profile”.
F15 medium: An unknown route is interpreted as a user profile and returns a malformed recovery page.
be-fast-and-stable
good-core-web-vitals
issueshighLighthouse measured LCP 6.8s, FCP 5.1s, TTI 21.9s, and CLS 0.117. The mobile layout primitive independently measured CLS 0.136, including a 0.106 shift around 3.8s.
F04 high: The homepage is slow and shifts beyond the good CLS range in the tested mobile profile.
be-fast-and-stable
visual-stability
issueshighLighthouse measured LCP 6.8s, FCP 5.1s, TTI 21.9s, and CLS 0.117. The mobile layout primitive independently measured CLS 0.136, including a 0.106 shift around 3.8s.
F04 high: The homepage is slow and shifts beyond the good CLS range in the tested mobile profile.
be-fast-and-stable
efficient-main-thread
issueshighHAR recorded 203 requests and 3.94MB transferred, including 82 scripts and 93 images. Lighthouse reported 4,174KiB total, about 449KiB unused JS, 41KiB unused CSS, and 2.7s main-thread work.
F05 high: The landing page ships a heavy, script-rich dependency graph with substantial unused code.
be-fast-and-stable
efficient-resource-delivery
issueshighHAR recorded 203 requests and 3.94MB transferred, including 82 scripts and 93 images. Lighthouse reported 4,174KiB total, about 449KiB unused JS, 41KiB unused CSS, and 2.7s main-thread work. The image primitive found 98/100 images without explicit dimensions, 38 oversized, 25 below-fold images not lazy-loaded, and 91 legacy-format assets. Lighthouse failed aspect-ratio and responsive-image audits.
F05 high: The landing page ships a heavy, script-rich dependency graph with substantial unused code.
F09 medium: Image delivery causes stability, clarity, and bandwidth problems.
be-fast-and-stable
trim-unused-and-duplicate-code
issueshighHAR recorded 203 requests and 3.94MB transferred, including 82 scripts and 93 images. Lighthouse reported 4,174KiB total, about 449KiB unused JS, 41KiB unused CSS, and 2.7s main-thread work.
F05 high: The landing page ships a heavy, script-rich dependency graph with substantial unused code.
be-inclusive
names-roles-labels
issueshighThe home probe found unlabeled search inputs and many image-only cover links without textual or ARIA naming; Lighthouse also failed label-content-name-mismatch.
F06 medium: Some controls do not expose a reliable accessible name.
be-inclusive
sufficient-contrast
issueshighLighthouse/axe color-contrast audit failed on the tested homepage. Forced-colors rendering remained usable, so this finding is limited to authored color pairs in normal mode.
F07 medium: Some text does not meet minimum color contrast.
be-inclusive
structure-and-focus
issueshighhome-probe.json reports zero h1 elements and starts the visual hero at h2; login-probe.json also reports zero h1. The story detail correctly has one h1.
F08 medium: Key entry pages omit a level-one heading and use inconsistent landmark structure.
be-inclusive
legible-text
passhighDesktop and mobile screenshots show readable line lengths, unclipped headings, and coherent content grouping.
be-inclusive
zoom-reflow-targets-and-media
issueshighThe objective DOM probe counted 19 visible controls below 24px on both home and story, and 15 on login. Lighthouse accessibility was 0.97 but does not negate these measured target dimensions.
F03 medium: Numerous interactive targets are smaller than a robust touch target.
follow-best-practices
no-console-errors
passhighLighthouse errors-in-console audit passed.
follow-best-practices
sound-document-and-assets
issueshighThe image primitive found 98/100 images without explicit dimensions, 38 oversized, 25 below-fold images not lazy-loaded, and 91 legacy-format assets. Lighthouse failed aspect-ratio and responsive-image audits.
F09 medium: Image delivery causes stability, clarity, and bandwidth problems.
follow-best-practices
browser-platform-hygiene
passhighLighthouse passed deprecations, BFCache, paste prevention, geolocation-on-start, and notification-on-start audits.
be-discoverable
title-and-description
passhighHome, story, and login probes each found descriptive titles and meta descriptions.
be-discoverable
crawlable-and-mobile-friendly
passhighAll sampled anchors had hrefs, viewport meta was present, robots permits public pages, and mobile layouts had no overflow.
be-discoverable
canonical-and-indexing-signals
passhighHome/story/login exposed canonicals; public responses were successful and robots/sitemap signals were present.
be-discoverable
structured-and-shareable-metadata
issueshighThe homepage and story probes found no Open Graph properties; the story has JSON-LD, while the organization/home entity has no JSON-LD.
F10 low: Share-preview metadata is incomplete on representative public pages.
be-private-and-secure
secure-transport-and-headers
issueshighheaders.json reports no CSP, X-Content-Type-Options, Referrer-Policy, or Permissions-Policy. cookies.json reports 18 flagged cookies, including non-Secure analytics and host cookies and broad SameSite=None usage.
F11 high: Important browser security defenses and cookie attributes are missing.
be-private-and-secure
data-minimisation-and-third-parties
issueshighThe tracker probe saw 16 third-party origins and four known trackers. HAR attributed 90 requests and 2.18MB to third-party origins, while the consent UI names 1,013 partners.
F12 high: The first-load third-party and tracking footprint is disproportionate.
be-private-and-secure
in-context-permissions-and-modern-auth
issueshighThe login screen offers Google, Facebook, and email/password. The email probe exposed username and password fields but no passkey action, despite browser WebAuthn support.
F13 medium: The visible authentication choices do not offer a first-party phishing-resistant passkey path.
be-private-and-secure
defensive-browser-policies
issueshighheaders.json reports no CSP, X-Content-Type-Options, Referrer-Policy, or Permissions-Policy. cookies.json reports 18 flagged cookies, including non-Secure analytics and host cookies and broad SameSite=None usage.
F11 high: Important browser security defenses and cookie attributes are missing.
be-resilient
progressive-enhancement
passhighDiscoverability measured 68% raw-HTML coverage on home and 92% on story; neither page was a JS shell.
be-resilient
resilient-runtime-behaviour
issueshighDesktop, mobile, listing, story, search, and login screenshots show a first-load panel for 1,013 partners covering a substantial portion of the viewport. The probe identifies a custom DIV role=dialog without aria-modal.
F02 high: A large consent panel interrupts every audited public route and obscures primary content.
be-resilient
offline-and-installable
issueshighHome and story probes found no web app manifest and no controlling service worker on representative app/content routes.
F14 medium: The app-like reading service exposes neither installability metadata nor an offline fallback.
be-resilient
network-and-http-failure-states
issueshighThe unknown-route request redirects to /user/this-route-does-not-exist-web-uplift, then returns HTTP 404 with the generic homepage title and an h1 aria-label of “s profile”.
F15 medium: An unknown route is interpreted as a user profile and returns a malformed recovery page.
be-internationalised
lang-dir-and-logical-properties
passhighModern home/story templates use en-US, ltr, and logical CSS properties; login exposes a language selector.
be-internationalised
locale-aware-data
issueshighThe global story page renders “Tue, Dec 2, 2025” but story-probe.json finds no time elements, while the site advertises language selection and global reach.
F16 low: Locale-sensitive content is rendered as fixed English text without semantic time markup.
be-internationalised
time-zone-correctness
not-applicablehighNo representative route exposed scheduled events, partial times, or cross-zone coordination; this specific time-zone check does not apply to the sampled content.
be-trustworthy
no-dark-patterns
passhighConsent offers Reject All with prominence equal to Accept, and commercial calls to action are plainly labeled in sampled states.
be-trustworthy
humane-error-handling
passhighEmpty email-login submission produced native, specific “Please fill in this field” feedback for username and password.
be-trustworthy
trustworthy-input-assistance
issueshighlogin-email-probe.json reports required username and password controls with empty autocomplete values. Empty submission uses clear native validation, so this finding is specifically about input assistance.
F17 medium: The email login fields omit autocomplete tokens.
be-trustworthy
safe-commercial-and-account-flows
passmediumPricing/subscription completion was not attempted, but sampled login and premium entry controls were explicit and reversible before commitment.
be-sustainable
optimised-assets
issueshighThe image primitive found 98/100 images without explicit dimensions, 38 oversized, 25 below-fold images not lazy-loaded, and 91 legacy-format assets. Lighthouse failed aspect-ratio and responsive-image audits.
F09 medium: Image delivery causes stability, clarity, and bandwidth problems.
be-sustainable
no-wasteful-work
issueshighHAR recorded 203 requests and 3.94MB transferred, including 82 scripts and 93 images. Lighthouse reported 4,174KiB total, about 449KiB unused JS, 41KiB unused CSS, and 2.7s main-thread work.
F05 high: The landing page ships a heavy, script-rich dependency graph with substantial unused code.
be-sustainable
third-party-and-media-budget
issueshighThe tracker probe saw 16 third-party origins and four known trackers. HAR attributed 90 requests and 2.18MB to third-party origins, while the consent UI names 1,013 partners.
F12 high: The first-load third-party and tracking footprint is disproportionate.
be-agent-ready
structured-agent-capabilities
not-applicablehighNo declared agent-facing intent or transactional agent surface was found; this emerging opportunity is not an obligation for this run.
be-agent-ready
on-device-inference
not-applicablehighNo declared product intent for on-device inference was found on the representative reading, discovery, or login routes.
be-memory-efficient
no-leak-under-repeated-interaction
passmediumAfter repeated story tab/scroll interaction, heap grew 3.2% (30.79MB to 31.76MB) with no Detached* constructor among top retained groups; no unbounded pattern was established.
be-memory-efficient
bounded-footprint
passhighStory heap was about 30.8MB baseline and 31.8MB post-interaction for roughly 700 DOM nodes, proportionate to this media/content page.
be-memory-efficient
no-detached-dom-or-unbounded-listeners
passmediumBefore/after heap summaries show stable closures (35,000 to 35,150), stable Set count, and no Detached* constructor in top retained groups.

Provenance

Canonical report: results/atomic/reports/0423-www_wattpad_com.json
Report SHA-256: fab0aea72f28b67e51a433778a84a686bc4a962fb208dd3bef9c4f58138e17cb
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_wattpad_com/2026-07-20T17-44-54-145Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_wattpad_com/2026-07-20T17-44-54-145Z
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.