Manifest position 755 · CrUX rank bucket 1000
https://trilltrill.jp
Coverage complete
Coverage-complete audit of the homepage, a current article, and terms/policy template.
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 / check | Status | Confidence | Evidence or reason |
|---|---|---|---|
respect-user-preferencesrespects-color-scheme | issues | high | A dark-mode screenshot is visually identical to the light rendering and the computed root colorScheme is normal. F01 medium: The site ignores the user’s dark-color preference |
respect-user-preferencesrespects-reduced-motion | pass | medium | Under emulated reduced motion, matchMedia is true, there are zero active animations, and scroll behavior is auto. |
respect-user-preferencesrespects-contrast | issues | high | axe reports 78 serious color-contrast failures on homepage article authors and dates. F02 high: Text contrast is insufficient across article metadata |
implement-natural-interactionsview-transitions | issues | high | The DOM probe found no active animations or authored transition use on a link-heavy publication experience. F03 low: Navigation changes have no continuity cue |
implement-natural-interactionsscroll-driven-animations | pass | medium | Screenshots and animation probes show no custom scroll animation that fights native scrolling. |
implement-natural-interactionsphysical-gestures | pass | medium | Primary content and pagination use ordinary anchors that work through platform click/tap activation. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The article content is 10,650px tall, while screenshots and DOM show no progress indicator or state-aware reading chrome. F04 low: Long pages provide no scroll-progress or state-aware navigation |
provide-guided-navigationanchored-positioning | pass | medium | Visible category and ranking navigation remains spatially associated with its labels in desktop evidence. |
provide-guided-navigationdirects-attention | pass | medium | The homepage and article use clear image/title groupings and recognizable linked cards. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop and mobile screenshots show a full-page dimmer and consent prompt before any article can be read. F05 high: Consent UI blocks the entire reading experience on arrival |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Four role=dialog nodes lack aria-modal; at 360px the panel is mostly off-screen and produces 778px horizontal overflow. F06 high: Consent dialogs are not robust semantic modals and fail on mobile |
maximize-content-reduce-noisereduced-chrome | issues | high | HAR records 145 requests, 140 third-party requests, 63 scripts, and 68 third-party origins while the consent overlay obscures content. F07 high: Advertising and tracking machinery dominates page cost and attention |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | Layout at a 360px viewport reports scrollWidth 1138px, clientWidth 360px, and horizontalOverflowPx 778 on both home and article. F08 critical: The mobile experience overflows by 778px |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The consent panel is clipped almost completely at 360px and the layout retains a 1138px CSS width. F09 high: Core components do not adapt to the available inline size |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe reports outline-style none for all 30 sampled visible interactive elements. F10 high: Keyboard focus is visually suppressed |
support-core-task-successclear-purpose-and-primary-action | pass | medium | Title, description, visible article cards, and article headline clearly communicate a Japanese lifestyle publication and reading action. |
support-core-task-successprimary-flow-completion | issues | high | At 360px only the right edge of the consent surface is visible, leaving its choice buttons off-screen. F11 high: The primary reading journey is blocked by a broken mobile consent step |
support-core-task-successclear-system-state-and-recovery | pass | medium | Consent UI offers explicit consent, decline, and manage-options recovery controls. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse reports performance 0.37, FCP 6.3s, LCP 18.1s, TBT 770ms, and Speed Index 18.4s. F12 critical: Loading performance is far outside good thresholds |
be-fast-and-stablevisual-stability | pass | medium | Layout observer measured CLS 0.0000069 on home and 0.00065 on article, both well within the good threshold. |
be-fast-and-stableefficient-main-thread | issues | high | Lighthouse reports 6.9s main-thread work, 4.4s JavaScript execution, and 770ms TBT; the HAR contains 63 scripts. F13 high: Third-party JavaScript keeps the main thread busy |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR records 3.08MB in one capture; Lighthouse records 4,886KiB and 1,482KiB potential cache-lifetime savings. F14 high: The page transfers a large, mostly third-party payload |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 1,311KiB unused JavaScript and 62KiB unused CSS. F15 high: Large amounts of shipped CSS and JavaScript are unused |
be-inclusivenames-roles-labels | issues | high | axe finds an unnamed search button and five unnamed pagination/social links. F16 high: Interactive controls lack accessible names |
be-inclusivesufficient-contrast | issues | high | axe reports 78 serious contrast failures, concentrated in bylines and publication dates. F17 high: Secondary text fails minimum contrast |
be-inclusivestructure-and-focus | issues | high | axe reports incorrect heading order and a nested complementary landmark; the probe also shows no visible outlines. F18 high: Heading, landmark, and focus structure is unreliable |
be-inclusivelegible-text | pass | medium | Desktop screenshots show readable primary Japanese headlines and article text with stable alignment. |
be-inclusivezoom-reflow-targets-and-media | issues | high | Lighthouse flags a restrictive viewport and undersized touch targets; raw mobile layout overflows 778px. F19 critical: Zoom and mobile reflow are restricted or broken |
follow-best-practicesno-console-errors | issues | high | Lighthouse fails the console-errors audit. F20 medium: The page logs browser errors |
follow-best-practicessound-document-and-assets | issues | high | The article image audit finds 16 images without dimensions, 10 without srcset, and eight below-fold images not lazy-loaded. F21 medium: Image sizing and delivery metadata are incomplete |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports a deprecated API warning and DevTools Issues failures. F22 medium: Deprecated APIs and browser issues remain |
be-discoverabletitle-and-description | pass | medium | Homepage and article both return specific titles and meta descriptions in raw HTML. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Raw-HTML coverage is 32% on home and 29% on article; mobile layout overflows 778px. F23 high: Crawler-visible content is sparse and mobile rendering is broken |
be-discoverablecanonical-and-indexing-signals | pass | medium | Homepage probe reports a self-referencing HTTPS canonical and robots.txt is reachable. |
be-discoverablestructured-and-shareable-metadata | issues | high | The DOM probe finds zero application/ld+json blocks on the homepage. F24 medium: No structured data describes the publication content |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS is used, but CSP and HSTS are missing; 16 of 20 observed cookies lack Secure, including the Rails session cookie. F25 high: Security headers and cookie transport controls are incomplete |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker capture sees 68 third-party origins and 13 known tracker domains; HAR attributes 140 of 145 requests and 3.04MB to third parties. F26 critical: Tracking starts with an extreme third-party footprint |
be-private-and-securein-context-permissions-and-modern-auth | pass | medium | No browser permission prompt, credential field, auth flow, or exposed secret was observed; secrets scan found zero findings. |
be-private-and-securedefensive-browser-policies | issues | high | CSP and Permissions-Policy are absent, although nosniff, SAMEORIGIN, and strict-origin referrer policy are present. F27 medium: Defensive browser policies are incomplete |
be-resilientprogressive-enhancement | pass | medium | Raw server HTML is non-empty, with title/description and article H1 available without JavaScript. |
be-resilientresilient-runtime-behaviour | issues | high | Lighthouse reports console errors and deprecated API use on the primary path. F28 medium: Runtime errors reduce resilience |
be-resilientoffline-and-installable | not-applicable | high | Not applicable to the observed site capability. |
be-resilientnetwork-and-http-failure-states | pass | medium | Primary navigation uses real href anchors, preserving browser reload/back and native HTTP failure behavior. |
be-internationalisedlang-dir-and-logical-properties | pass | medium | All sampled templates declare lang=ja and render Japanese text in the expected horizontal direction. |
be-internationalisedlocale-aware-data | pass | medium | Visible dates and copy use Japanese ordering and notation appropriate to the declared locale. |
be-internationalisedtime-zone-correctness | pass | medium | No ambiguous live event, deadline, or cross-zone scheduling surface was found; publication dates are simple calendar dates. |
be-trustworthyno-dark-patterns | issues | high | The initial screenshot shows the consent request, while the same fresh-load tracker capture already records 68 third-party origins and known ad/analytics trackers. F29 high: Non-essential tracking occurs while consent is still being requested |
be-trustworthyhumane-error-handling | pass | medium | The only exercised decision flow offers decline and manage-options controls rather than trapping the user. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | Not applicable to the observed site capability. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | Not applicable to the observed site capability. |
be-sustainableoptimised-assets | issues | high | Lighthouse reports a 4,886KiB page and 288KiB image-delivery savings; article images lack dimensions and srcset. F30 high: Assets are not delivered efficiently |
be-sustainableno-wasteful-work | issues | high | Lighthouse estimates 1,311KiB unused JS, 6.9s main-thread work, and 4.4s JS execution. F31 high: Unused code and tag execution waste CPU and energy |
be-sustainablethird-party-and-media-budget | issues | high | HAR shows 140 third-party requests and 3.04MB third-party transfer on initial load. F32 high: There is no effective third-party performance budget |
be-agent-readystructured-agent-capabilities | issues | high | The public article has only 29% raw/rendered content-word coverage and homepage has no JSON-LD. F33 medium: Public content lacks machine-readable structure and has low no-JS coverage |
be-agent-readyon-device-inference | not-applicable | high | Not applicable to the observed site capability. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten repeated top/bottom scroll cycles, heap totals were lower than baseline (889,844 vs 896,651 nodes; 47.28MB vs 47.63MB), showing no retained growth in this interaction. |
be-memory-efficientbounded-footprint | issues | high | Baseline heap contains 896,651 nodes, 3,832,781 edges, and 47.6MB self size before extended interaction. F34 medium: The initial page has a very large DOM/heap footprint |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Heap summaries show no Detached* constructor among top retained constructors, and repeated scrolling did not increase node count. |
Provenance
Canonical report: results/atomic/reports/0755-trilltrill_jp.json
Report SHA-256: 6ff8301bb97469899db390736957ce1416c262d4a04723a963aec06d44a22bed
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/trilltrill_jp/2026-07-22T20-57-22-895Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/trilltrill_jp/2026-07-22T20-57-22-895Z
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.