Manifest position 511 · CrUX rank bucket 1000
https://mobcup.fm
Coverage complete
Coverage-complete representative audit of six paths/templates. Not covered: authenticated profile/favourites, third-party OAuth completion, destructive account actions, upload after authentication, actual binary download response, and exhaustive item URLs because they require credentials/external identity or duplicate audited templates.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | The screenshot captured with prefers-color-scheme: dark remains a light #f9fbfe page, and the CSS probe found no prefers-color-scheme rule. F01 high: The site does not adapt to the user’s dark colour-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | The reduced-motion probe found zero active animations on the representative listing. |
respect-user-preferencesrespects-contrast | issues | high | The preferences probe found no prefers-contrast or forced-colors CSS; Lighthouse measured the ADVERTISEMENT label at 1.85:1 against #f9fbfe. F02 medium: High-contrast preferences are not explicitly supported, and low-contrast text already fails WCAG. |
implement-natural-interactionsview-transitions | issues | high | CSS inspection found no view-transition declarations on the multi-page browse and detail journeys. F03 low: Route changes use abrupt document swaps with no View Transition enhancement. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation, parallax, scrollytelling, or reveal effect exists on the representative pages, so there is no scroll animation implementation to judge. |
implement-natural-interactionsphysical-gestures | pass | high | Mobile screenshots and DOM inspection show native scrolling and links, with no custom pointer-driven gesture layer fighting platform behavior. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | The long mobile listing keeps compact top and bottom navigation visible while content scrolls, providing persistent orientation without observed JS scroll jank. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover, or edge-positioned menu was present in the tested browse, detail, or login surfaces. |
provide-guided-navigationdirects-attention | pass | high | The bottom navigation visibly highlights the active Ringtone or Wallpaper destination, and detail/list links use descriptive labels. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | The initial desktop screenshot shows a large blocking consent panel over the homepage before the user can reach the content. F04 high: The first visit is interrupted by a modal consent wall that obscures all primary content. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM inspection during the first-visit state found zero dialog elements and zero aria-modal elements while the visible panel blocked the page. F05 medium: The consent overlay is not exposed through a native dialog or equivalent modal semantics. |
maximize-content-reduce-noisereduced-chrome | pass | high | After consent dismissal, the mobile browse templates devote most of the viewport to the media listing; header and bottom navigation remain compact. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800 both listing templates reported 0 horizontal overflow, a 360px content width, and a viewport meta tag. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | CSS inspection found no @container rules even though the same media-card component appears at desktop and mobile widths. F06 low: Reusable listing cards adapt only through global layout rules, not their container. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus/geometry probe found 14 of the first 15 focusable targets under 44 CSS px; tag links were about 26px high. F07 medium: Many interactive tag targets are too short for comfortable touch use. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The listing states “Trending Ringtones Download” and cards expose named titles and a visible Download action. |
support-core-task-successprimary-flow-completion | pass | high | The representative detail page exposes direct “Download .mp3 for Android” and “Download .m4r for iPhone” links without an account wall. |
support-core-task-successclear-system-state-and-recovery | issues | high | A real unknown route returned HTTP 404 but rendered only “404 NOT FOUND” and no usable site link. F08 medium: The 404 state is a dead end with no recovery action. |
be-fast-and-stablegood-core-web-vitals | pass | high | Trace measured LCP/FCP 1.12s and 0ms TBT; Lighthouse measured LCP 0.96s, CLS 0.001 and TBT 0ms. |
be-fast-and-stablevisual-stability | pass | high | Both mobile layouts observed CLS 0 with no shifts after consent dismissal; Lighthouse corroborated CLS 0.001 on initial load. |
be-fast-and-stableefficient-main-thread | pass | high | Trace and layout observers found no long tasks and 0ms total blocking time during the tested listing load. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR recorded 718,174 transferred bytes, 642,756 third-party bytes, and parser-inserted CSS plus a script candidate; the script was 605,068 bytes total while the trace LCP was 1.12s. F09 medium: Third-party and render-blocking delivery dominates an otherwise fast page. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse reported an estimated 23 KiB of unused JavaScript, while HAR showed third-party scripts as the largest transfer class. F10 low: The page ships avoidable JavaScript. |
be-inclusivenames-roles-labels | pass | high | Lighthouse passed link-name and button-name; the wallpaper image audit found no missing alt text. |
be-inclusivesufficient-contrast | issues | high | Lighthouse reported the 10px #bbbbbb ADVERTISEMENT label at 1.85:1 against #f9fbfe, below the required 4.5:1. F11 medium: Text contrast is insufficient for the advertisement label. |
be-inclusivestructure-and-focus | issues | high | Lighthouse failed landmark-one-main and the DOM probe counted zero main or role=main elements on the ringtone listing. F12 medium: The content page has no main landmark. |
be-inclusivelegible-text | pass | high | Mobile screenshots show readable card titles and metadata without clipping or horizontal overflow. |
be-inclusivezoom-reflow-targets-and-media | issues | high | At 360x800 there was no horizontal overflow, but the geometry probe measured numerous tag links at roughly 26px high. F13 medium: Touch targets do not meet the inclusive target-size/reflow bar. |
follow-best-practicesno-console-errors | pass | high | Lighthouse passed the errors-in-console audit on the representative listing. |
follow-best-practicessound-document-and-assets | issues | high | The image primitive found 10 legacy JPEGs, 10 images without srcset, and 9 below-fold images without loading=lazy. F14 medium: The image listing misses modern responsive delivery. |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse best-practices scored 1.0 and reported no browser-console errors; no permission prompt appeared on load. |
be-discoverabletitle-and-description | pass | high | The listing and detail pages expose descriptive titles and meta descriptions in raw server HTML. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | The page has a viewport meta tag, descriptive real href links, robots allows general crawling, and no-JS content coverage is 100%. |
be-discoverablecanonical-and-indexing-signals | issues | high | The DOM probe found no canonical URL; an in-browser request to /sitemap.xml returned 404, although robots.txt allowed general crawling. F15 medium: Canonical and sitemap indexing signals are incomplete. |
be-discoverablestructured-and-shareable-metadata | issues | high | The listing probe found zero Open Graph tags; the detail page had useful AudioObject JSON-LD but no evidence of Open Graph/Twitter preview metadata. F16 low: Rich pages lack social preview metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers primitive found no CSP, HSTS, nosniff, frame protection, Referrer-Policy, or Permissions-Policy; both XSRF-TOKEN and mobcupfm_session lacked Secure. F17 high: Security headers are absent and first-party cookies are not Secure. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | After “Do not consent”, HAR still recorded 18 third-party requests and 642,756 third-party bytes, including Google Ads, Tag Manager, Funding Choices and a Google Analytics collection request. F18 high: Third-party tracking code loads despite the tested reject choice and dominates network bytes. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login surface exposes only Google and Facebook links; no WebAuthn/passkey registration or authentication UI was present. F19 medium: Authentication offers federated providers but no phishing-resistant passkey path. |
be-private-and-securedefensive-browser-policies | issues | high | The headers primitive found HSTS, clickjacking protection, Referrer-Policy and Permissions-Policy all absent, with no CSP frame-ancestors fallback. F20 high: Browser-enforced defensive policies are not configured. |
be-resilientprogressive-enhancement | pass | high | Discoverability measured 100% content coverage without JavaScript on listing and detail pages; both title and metadata survive in raw HTML. |
be-resilientresilient-runtime-behaviour | pass | high | Representative listing, detail and login surfaces rendered stable bounded controls at mobile size, with no cut-off menu or async blank state after consent dismissal. |
be-resilientoffline-and-installable | not-applicable | high | The public media catalogue is a server-rendered, intrinsically network-dependent download site rather than an installed application; offline/installability was judged out of scope. |
be-resilientnetwork-and-http-failure-states | issues | high | The tested 404 returned the correct status but only “404 NOT FOUND”, with no retry, search, navigation, or explanation. F21 medium: HTTP failure pages provide no resilient recovery state. |
be-internationalisedlang-dir-and-logical-properties | issues | high | The document correctly declared lang=en, but CSS inspection found no logical inline/block properties and the root had no explicit direction. F22 low: Styles are not prepared for bidirectional or alternate writing modes. |
be-internationalisedlocale-aware-data | not-applicable | high | The tested public templates expose no dates, currency, locale-formatted numbers, durations, or calendar data requiring locale formatting. |
be-internationalisedtime-zone-correctness | not-applicable | high | The tested pages expose no events, schedules, stored times, or time-zone-sensitive concepts. |
be-trustworthyno-dark-patterns | pass | high | The consent panel gives equally prominent “Do not consent” and “Consent” actions; rejecting it exposed the content without a forced account or continuity step. |
be-trustworthyhumane-error-handling | not-applicable | high | No editable first-party data-entry or validation flow was present; authentication is delegated to external providers and the search field has no required value. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No address, payment, credential, profile, or other personal-data input fields were present on the tested first-party pages. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, cancellation, or sensitive account-management flow was exposed; the tested login entry only delegates to Google or Facebook. |
be-sustainableoptimised-assets | issues | high | The image audit found 10 legacy JPEG images, no responsive srcset on those 10, and 9 below-fold images loaded eagerly. F23 medium: Wallpaper assets are inefficiently encoded and loaded. |
be-sustainableno-wasteful-work | issues | high | HAR attributed about 89.5% of transferred bytes to third parties, led by advertising, consent and analytics scripts. F24 medium: Non-essential third-party background work consumes most transferred bytes. |
be-sustainablethird-party-and-media-budget | issues | high | 18 of 26 requests were third-party and 642,756 of 718,174 transferred bytes were third-party on a simple listing. F25 medium: The third-party budget is disproportionate to the ringtone listing’s user value. |
be-agent-readystructured-agent-capabilities | not-applicable | high | WebMCP exposure is emerging and optional; this public catalogue does not declare an agent-facing transaction or productivity capability. |
be-agent-readyon-device-inference | not-applicable | high | No summarization or language-model task is part of the site’s core ringtone/wallpaper browse and download journey. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After 10 play-control activations, DOM nodes and audio element count stayed at 626 and 0; sampled heap moved only from 2,090,064 to 2,095,472 bytes. Independent post heap was smaller than baseline. |
be-memory-efficientbounded-footprint | pass | medium | Heap summaries measured about 18.1–20.6 MB self size for the listing, proportionate to the rendered catalogue and third-party consent/ad code. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Repeated play activation left DOM node count unchanged; no Detached* constructor appeared among the largest heap constructors and the post snapshot did not grow. |
Provenance
Canonical report: results/atomic/reports/0511-mobcup_fm.json
Report SHA-256: 8a6bafbcb25771a66075f003eda402d22b7a1d0f7e003968a62cb3e49096b102
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/mobcup_fm/2026-07-21T07-13-55-876Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/mobcup_fm/2026-07-21T07-13-55-876Z
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.