Manifest position 152 · CrUX rank bucket 1000
https://maynoe.com
Coverage complete
Coverage-complete audit of four representative states. External destinations, duplicate pagination pages, and absent commerce/account flows were not exercised.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | The dark-condition screenshot is pixel-identical in size and appearance to the default capture, while the preferences probe reports colorScheme "normal" and the CSS probe finds no color-scheme, prefers-color-scheme, or light-dark() usage. F01 low: The fixed dark palette does not participate in the user’s color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | issues | high | The CSS probe found 11 transitions and 2 animations but no prefers-reduced-motion rule; the reduced-motion probe still observed a 1000 ms animation. F02 low: Transitions and animations have no reduced-motion override. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors screenshot keeps title, navigation boundary, card titles, and content visible. |
implement-natural-interactionsview-transitions | issues | high | The CSS feature probe found no view-transition CSS and the MPA document contains no cross-document transition rule. F03 low: Cross-document navigation swaps abruptly. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation, parallax, scrollytelling, carousel, or reveal behavior exists on the representative templates. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The site exposes ordinary links and a video player, with no swipe, pull, drag, snap-carousel, or other gesture-driven flow to evaluate. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The mobile layout is 3,425 px tall, while the screenshots and CSS probe show static navigation with no progress indicator, shrinking header, scroll-state query, or equivalent position feedback. F04 low: Long listing pages provide no scroll-state feedback or return affordance. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, anchored popover, or edge-positioned menu is present on the representative paths. |
provide-guided-navigationdirects-attention | pass | high | DOM exposes current-menu-item/aria-current and headings plus pagination preserve location in the listing hierarchy. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Load screenshots show content immediately with no full-viewport interstitial or obscuring consent wall. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | DOM inspection identifies <div class="clean-grid-responsive-menu-icon"></div> as the menu trigger; it is absent from the focusable-controls probe and exposes no name, role, expanded state, or controlled target. F05 high: The mobile menu trigger is an unlabelled, non-keyboard-operable div. |
maximize-content-reduce-noisereduced-chrome | pass | high | Screenshots devote the viewport primarily to the content grid/video with a compact masthead and navigation strip. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360×800, scrollWidth and clientWidth are both 360 with 0 px horizontal overflow; the grid collapses to one column. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The CSS probe found no @container rule and 104 physical-direction declarations; the grid changes at the viewport level only. F06 medium: Responsive behavior is viewport-only rather than component-aware. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Focused links and player controls report outline style "none"; the menu trigger is not focusable, and seven player controls are 28×28 px, below a comfortable touch target. F07 high: Keyboard focus and touch targets are inadequate on primary controls. |
support-core-task-successclear-purpose-and-primary-action | pass | high | The first viewport presents a named media catalog and directly linked thumbnails; the detail first viewport presents the named video and prominent play control. |
support-core-task-successprimary-flow-completion | pass | high | A representative listing link reaches the detail template; initializing the player resolves a 473-second MP4 with readyState 4 and no media error. |
support-core-task-successclear-system-state-and-recovery | pass | high | A deliberately missing URL returns HTTP 404 and a visible “requested page cannot be found” state with search, recent posts, categories, and navigation recovery links. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP at 3.5 s (score 0.65), although the local trace measured 1.4 s; CLS was 0 and TBT was 3 ms. F08 medium: Throttled LCP is outside the good range. |
be-fast-and-stablevisual-stability | pass | high | Mobile layout observation reports CLS 0 and Lighthouse reports CLS 0; all homepage images have dimensions. |
be-fast-and-stableefficient-main-thread | pass | high | Trace records zero long tasks and 0 ms total blocking time; Lighthouse TBT is 3 ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR summary identifies four VeryHigh parser-inserted stylesheets and parser-inserted jQuery/jquery-migrate scripts; Google Fonts also sits on the critical path. F09 medium: Parser-blocking CSS and legacy scripts lengthen the critical path. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse reports about 68 KiB of unused JavaScript in gtag; the HAR records gtag as the largest resource at 160,795 transferred bytes. F10 medium: Analytics is the largest script and ships substantial unused code. |
be-inclusivenames-roles-labels | issues | high | The images primitive reports all 12 homepage thumbnails without meaningful alt text and 10 missing on the detail page; several SVG-only player buttons have no aria-label or text. F11 high: Content thumbnails and custom player controls lack robust accessible names. |
be-inclusivesufficient-contrast | pass | high | Lighthouse contrast audit passes and forced-colors visual evidence keeps essential text and controls distinguishable. |
be-inclusivestructure-and-focus | issues | high | Lighthouse flags an H1-to-H3 heading-order skip; the detail page has two H1s, and focused elements report outline style none. F12 high: Heading hierarchy and focus presentation are not accessible. |
be-inclusivelegible-text | pass | high | Desktop/mobile screenshots show unclipped titles with strong yellow-on-black contrast and readable spacing; no horizontal overflow occurs. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The viewport is width=device-width, initial-scale=1, maximum-scale=1; player controls are 28×28 px and the 473-second video exposes zero track elements. F13 high: User zoom is restricted, player controls are undersized, and the video has no captions track. |
follow-best-practicesno-console-errors | pass | high | Lighthouse reports no browser errors logged to the console. |
follow-best-practicessound-document-and-assets | issues | high | The detail images primitive reports 4 images without dimensions, 6 oversized images, 6 without responsive sources, and 5 below-fold images not lazy-loaded. F14 medium: Detail-page assets are inconsistently sized and delivered. |
follow-best-practicesbrowser-platform-hygiene | pass | high | Lighthouse reports no deprecated APIs and no BFCache blocker; no permission prompt or paste-prevention behavior appeared. |
be-discoverabletitle-and-description | issues | high | DOM and Lighthouse evidence show a descriptive title but no meta[name=description] on the home and detail templates. F15 medium: Pages have titles but no meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Lighthouse passes crawlable anchors, robots validity, indexability and title; viewport meta is present and mobile layout has no overflow. |
be-discoverablecanonical-and-indexing-signals | issues | high | The homepage metadata probe reports canonical null; detail pages do expose a self-canonical and robots.txt points to a valid WordPress sitemap. F16 low: The homepage omits a canonical URL. |
be-discoverablestructured-and-shareable-metadata | issues | high | The detail probe finds no Open Graph tags and no JSON-LD despite the page representing a named video with a poster and duration. F17 medium: Video detail pages lack share-preview and structured entity metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | The headers primitive reports missing CSP, HSTS, nosniff, clickjacking, Referrer-Policy and Permissions-Policy; both analytics cookies are non-Secure, SameSite=None, and 400 days long. F18 high: HTTPS is used, but baseline security headers and cookie protections are absent. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker primitive finds Google Tag Manager and Google Analytics across 5 third-party origins; two analytics cookies are created on load for 400 days, and third parties transfer 223,220 bytes. F19 high: Tracking starts on load and persists for 400 days without an observed consent choice. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | The public content site requests no browser permissions and exposes no authentication flow. |
be-private-and-securedefensive-browser-policies | issues | high | No CSP/frame-ancestors or X-Frame-Options, HSTS, Referrer-Policy, Permissions-Policy, or X-Content-Type-Options is present. F20 high: Browser-enforced defensive policies are not configured. |
be-resilientprogressive-enhancement | pass | high | Raw HTML contains 100% of homepage rendered content tokens and 61% on detail; neither page is a JS shell, and titles/headings/content remain server-rendered. |
be-resilientresilient-runtime-behaviour | pass | high | The server-rendered MPA navigation and player initialize without console errors; no clipped overlay or fragile async shell appeared on representative paths. |
be-resilientoffline-and-installable | not-applicable | high | This is a server-rendered media/content site rather than an installable application; an offline app shell is not necessary for its stated browsing flow. |
be-resilientnetwork-and-http-failure-states | pass | high | The tested 404 returns the correct status and a useful recovery page with search and navigation rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | issues | high | Both listing and detail DOM report html lang="en-US" while the visible content is predominantly Burmese; the CSS probe finds 0 logical and 104 physical-direction declarations. F21 high: The Burmese-language experience is declared as English and uses only physical CSS directions. |
be-internationalisedlocale-aware-data | not-applicable | high | Representative pages expose no user-facing dates, currencies, quantities, or locale-sensitive input/output. |
be-internationalisedtime-zone-correctness | not-applicable | high | The site exposes no events, schedules, recurring intervals, or user-facing time-zone data. |
be-trustworthyno-dark-patterns | pass | high | No consent wall, forced continuity, confirmshaming, auto-play media, or disguised primary action appeared in the tested first-load and playback states. |
be-trustworthyhumane-error-handling | not-applicable | high | No data-entry or validation flow exists; the only form is a basic GET search and the tested 404 provides recovery. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No address, payment, sign-in, sign-up, or comparable autofill flow exists. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, consent purchase, authentication, or account-management flow exists. |
be-sustainableoptimised-assets | issues | high | All 12 homepage thumbnails are JPEG; detail evidence finds six oversized images and six without responsive sources. F22 medium: Image delivery leaves avoidable byte and resolution waste. |
be-sustainableno-wasteful-work | pass | high | Trace shows no long tasks or ongoing main-thread blocking; below-fold homepage images are lazy-loaded and the video uses preload=none. |
be-sustainablethird-party-and-media-budget | issues | high | The homepage sends 223,220 third-party bytes, including a 160,795-byte analytics script; the detail DOM also embeds a third-party jads.co advertising iframe. F23 medium: Third-party analytics, fonts and advertising consume disproportionate resources. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared intent or functional commerce/productivity workflow requires agent-facing tools; this emerging capability is outside the public media catalog scope. |
be-agent-readyon-device-inference | not-applicable | high | No summarization, generation, or language-model feature exists for which on-device inference would improve the current catalog/video task. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After 20 menu toggles in a fresh load, heap self-size was 6.51 MB versus a 6.18 MB baseline and node count 131,545 versus 128,413; the modest single-cycle difference does not show unbounded retained growth. |
be-memory-efficientbounded-footprint | pass | medium | Baseline heap is 6.18 MB self-size with 128,413 nodes, proportionate to the WordPress listing plus analytics and thumbnails. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Post-interaction top constructors contain no Detached* population; the bounded toggle interaction increased heap modestly rather than accumulating an obvious detached-node class. |
Provenance
Canonical report: results/atomic/reports/0152-maynoe_com.json
Report SHA-256: bc36adeb27c2116ddf5a98c8cd4d465ad2bfe063acbd8078604795f2be139244
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/maynoe_com/2026-07-18T19-11-11-304Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/maynoe_com/2026-07-18T19-11-11-304Z
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.