Manifest position 789 · CrUX rank bucket 1000
https://girlschannel.net
Coverage complete
Coverage complete across 58 atomic checks and five representative paths. Live comment submission was excluded as destructive; the associated validation-only check was explicitly not applicable.
All 58 atomic check outcomes
| Principle / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | Dark preference leaves light surfaces unchanged. F-001 medium: The interface is hard-coded to a light palette. |
respect-user-preferencesrespects-reduced-motion | pass | high | getAnimations() returned zero and no auto-advance or non-essential motion was visible. |
respect-user-preferencesrespects-contrast | issues | high | Several text styles fail WCAG contrast and there is no contrast-mode adaptation. F-002 high: Low-contrast text and controls fail the accessibility floor. |
implement-natural-interactionsview-transitions | issues | medium | No view-transition declarations or transition animations were found for route/state changes. F-003 low: Listing, topic and pagination navigation swaps abruptly without directional continuity. |
implement-natural-interactionsscroll-driven-animations | pass | high | No scroll-linked animation or custom animated scrollytelling exists, so no main-thread scroll animation anti-pattern was observed. |
implement-natural-interactionsphysical-gestures | pass | medium | The site relies on native page scrolling and link activation; no custom pointer gesture that fights platform behaviour was observed. |
provide-guided-navigationscroll-state-aware-chrome | issues | medium | The 139,047px topic page has static chrome and no progress/scroll-state response. F-004 medium: Very long pages provide weak position and attention cues. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover or anchored menu was present on the representative templates. |
provide-guided-navigationdirects-attention | issues | medium | Pagination/list-to-topic changes have no directional transition or destination highlight, and overlapping mobile tabs weaken orientation. F-004 medium: Very long pages provide weak position and attention cues. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | No full-screen popup, consent wall or content-obscuring interstitial appeared on load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | pass | medium | No transient modal overlay was triggered in tested flows; disclosures and navigation remained ordinary document content. |
maximize-content-reduce-noisereduced-chrome | pass | medium | The visual frame is simple and topic/list content occupies the main surface without ornamental application chrome. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | Topic overflows by 88px and list navigation overlaps at narrow width. F-005 high: Core listing and topic components do not reliably reflow on narrow screens. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | No container-responsive component was found and reused ranking/new tabs visibly collide at 360px. F-005 high: Core listing and topic components do not reliably reflow on narrow screens. |
adapt-to-the-form-factorinput-modality-aware | issues | high | Many links remove focus outlines; pagination targets measure 34x28px. F-007 high: Keyboard focus and target sizing are inadequate, and zoom is disabled on mobile. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Ranking, new topics, search and comment actions are visible and Japanese labels make each template purpose clear. |
support-core-task-successprimary-flow-completion | pass | medium | Users can open topics, paginate comments and complete a search without an account wall or dead end. |
support-core-task-successclear-system-state-and-recovery | pass | high | The 404 state explains the problem and provides a prominent return-to-top action. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse LCP is 8.6s and TBT 10,680ms; performance score is 0.28. F-008 critical: Mobile loading and main-thread responsiveness are critically slow. |
be-fast-and-stablevisual-stability | pass | high | Homepage CLS was 0 and topic CLS was 0.0011, both in the good range. |
be-fast-and-stableefficient-main-thread | issues | high | TBT is 10,680ms in Lighthouse; trace also observed a 199ms long task. F-008 critical: Mobile loading and main-thread responsiveness are critically slow. |
be-fast-and-stableefficient-resource-delivery | issues | high | A non-deferred classic script, render-blocking CSS, uncached font and uncompressed script are present. F-009 high: Resource delivery includes blocking, uncached and largely unused work. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Estimated savings are 189KiB JS and 15KiB CSS; two large Google tag bundles appear in the Lighthouse load. F-009 high: Resource delivery includes blocking, uncached and largely unused work. |
be-inclusivenames-roles-labels | issues | high | Missing alt, unnamed links/iframes and unlabeled inputs were directly enumerated. F-006 high: Essential controls, images and page regions are not exposed cleanly to assistive technology. |
be-inclusivesufficient-contrast | issues | high | Pink on white is measured at 2.2:1 and other grey labels at 3.94:1. F-002 high: Low-contrast text and controls fail the accessibility floor. |
be-inclusivestructure-and-focus | issues | high | No main landmark and multiple focused links have no visible outline. F-006 high: Essential controls, images and page regions are not exposed cleanly to assistive technology. F-007 high: Keyboard focus and target sizing are inadequate, and zoom is disabled on mobile. |
be-inclusivelegible-text | issues | high | Tabs overlap dates/labels and topic content exceeds the viewport, harming reading and scanability. F-005 high: Core listing and topic components do not reliably reflow on narrow screens. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Mobile markup disables user scaling and pagination targets are only 34x28px. F-007 high: Keyboard focus and target sizing are inadequate, and zoom is disabled on mobile. |
follow-best-practicesno-console-errors | pass | high | errors-in-console passed with no captured console errors. |
follow-best-practicessound-document-and-assets | issues | high | Doctype/charset exist, but image accessibility/responsiveness is poor and asset structure causes multiple audits to fail. F-010 medium: Long listings eagerly load poorly described, non-responsive image assets. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Synchronous XHR and deprecated Topics API use were captured, and Inspector Issues failed. F-011 medium: Third-party integrations use deprecated and main-thread-hostile browser behaviour. |
be-discoverabletitle-and-description | pass | high | Homepage and topic have descriptive titles; homepage has a substantive meta description. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Links use href and robots allows crawling, but mobile zoom is disabled and narrow content overflows. F-005 high: Core listing and topic components do not reliably reflow on narrow screens. F-007 high: Keyboard focus and target sizing are inadequate, and zoom is disabled on mobile. |
be-discoverablecanonical-and-indexing-signals | pass | high | HTTP is 200, canonical is present, robots allows public pages and advertises a current sitemap index. |
be-discoverablestructured-and-shareable-metadata | issues | medium | Open Graph/Twitter tags exist, but no JSON-LD structured entity was found for content/discussion templates. F-012 low: Topic entities lack machine-readable structured data. |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but CSP/HSTS/nosniff are absent and two cookies are not Secure. F-013 high: The HTTPS response omits all major defensive security headers and analytics cookies are insecurely scoped. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | 14 of 19 requests and 258,759 bytes are third-party; known trackers and 400-day cookies are active. F-014 medium: Tracking and third-party work dominate the small content-page transfer budget. |
be-private-and-securein-context-permissions-and-modern-auth | not-applicable | high | No geolocation/notification request and no authentication flow was present in scope. |
be-private-and-securedefensive-browser-policies | issues | high | HSTS, clickjacking protection, Referrer-Policy and Permissions-Policy are all absent. F-013 high: The HTTPS response omits all major defensive security headers and analytics cookies are insecurely scoped. |
be-resilientprogressive-enhancement | pass | high | Raw HTML returned 200 with 100% content coverage; title, H1 and description survive without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | medium | Core MPA navigation and search rendered without fragile shell, cut-off overlay or async blank state. |
be-resilientoffline-and-installable | not-applicable | high | No manifest is exposed; this is a public discussion/content MPA rather than an installable application. |
be-resilientnetwork-and-http-failure-states | pass | medium | The invalid route has clear Japanese error copy and a working route back to the homepage. |
be-internationalisedlang-dir-and-logical-properties | issues | high | Desktop/topic variants return an empty html lang for Japanese content. F-015 medium: Some served templates omit the document language. |
be-internationalisedlocale-aware-data | not-applicable | high | The scoped flows show Japanese-relative timestamps and no user-entered currency/calendar data requiring multi-locale formatting. |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduling, cross-zone event or editable time concept exists in the representative journeys. |
be-trustworthyno-dark-patterns | pass | medium | No consent wall, confirmshaming, forced subscription or disguised primary control appeared in the tested journeys. |
be-trustworthyhumane-error-handling | not-applicable | medium | Search has no invalid state and posting was not submitted to avoid publishing content to a live community. |
be-trustworthytrustworthy-input-assistance | issues | high | Search and comment inputs lack labels and useful autocomplete metadata. F-016 medium: Search and comment inputs lack labels and useful autofill/input assistance. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, account or authentication flow exists in the public anonymous journey. |
be-sustainableoptimised-assets | issues | high | 97 below-fold images are not lazy, with oversized/legacy/non-responsive assets. F-010 medium: Long listings eagerly load poorly described, non-responsive image assets. |
be-sustainableno-wasteful-work | issues | high | Heavy unused JavaScript and analytics work produces 10.68s TBT for a text-focused page. F-008 critical: Mobile loading and main-thread responsiveness are critically slow. F-017 high: Third-party JavaScript is disproportionate to the core text-listing experience. |
be-sustainablethird-party-and-media-budget | issues | high | Third parties are 78% of transfer bytes and duplicate analytics bundles dominate script cost. F-017 high: Third-party JavaScript is disproportionate to the core text-listing experience. |
be-agent-readystructured-agent-capabilities | not-applicable | high | Content is fully available in raw HTML, but no agent action surface or developer intent for agent tooling is evident. |
be-agent-readyon-device-inference | not-applicable | high | No summarisation or inference feature exists, and on-device AI is not necessary to complete the core reading/search journey. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten bottom/top scroll cycles, heap self-size changed from 37,604,766 to 37,681,075 bytes (~0.2%) and node count fell from 562,666 to 562,204, showing no unbounded retained growth. |
be-memory-efficientbounded-footprint | pass | medium | Topic heap is ~37.6MB despite a very long comment page; homepage uses ~3.9MB JS heap with 4,659 live DOM elements, proportionate to the rendered feed. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | The valid repeated-scroll run did not increase node count and total heap remained effectively flat; no accumulating DOM population was observed. |
Provenance
Canonical report: results/atomic/reports/0789-girlschannel_net.json
Report SHA-256: 24a46aa4429a267d47beb95c55e96398d874bd550ddb5695e0828b73c5e452da
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/girlschannel_net/2026-07-23T01-22-49-489Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/girlschannel_net/2026-07-23T01-22-49-489Z
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.