Manifest position 31 · CrUX rank bucket 1000

https://ameblo.jp

Coverage complete

Coverage-complete multi-template audit. Authenticated authoring, account management, checkout, and destructive account flows were outside scope because they require credentials or live user data.

Attempts

2 / 3

Judged checks

58 / 58

Blocked

Not run

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-preferences `respects-color-scheme`	issues	high	The representative home, article, category, ranking, and error templates were actively inspected for this outcome. F01 medium: The site does not adapt to the user’s dark color preference.
respect-user-preferences `respects-reduced-motion`	pass	high	The reduced-motion probe matched the preference and found zero running animations with scroll behavior auto.
respect-user-preferences `respects-contrast`	pass	high	The contrast probe preserved visible green/white control colors and Lighthouse reported no color-contrast failure.
implement-natural-interactions `view-transitions`	issues	high	State transitions were inspected in the carousel and route templates. F02 low: Carousel and route state changes do not use View Transitions.
implement-natural-interactions `scroll-driven-animations`	not-applicable	high	No scroll-linked animation or scrollytelling surface was present on the representative templates, so there is no scroll-driven motion implementation to judge.
implement-natural-interactions `physical-gestures`	pass	high	The carousel provides explicit previous, pause, and next controls on desktop and mobile, avoiding a gesture-only interaction.
provide-guided-navigation `scroll-state-aware-chrome`	issues	high	Scroll-aware chrome was inspected over the 12,706px homepage. F03 low: Long pages provide no scroll-state-aware orientation.
provide-guided-navigation `anchored-positioning`	not-applicable	high	No tooltip, anchored menu, or transient popover use case was present on the representative public templates.
provide-guided-navigation `directs-attention`	pass	high	Ranking order, movement arrows, section headings, and carousel position controls visibly guide attention on representative listing/home surfaces.
maximize-content-reduce-noise `no-intrusive-interruptions`	issues	high	The representative home, article, category, ranking, and error templates were actively inspected for this outcome. F04 high: A consent interstitial obscures article content and even the 404 recovery page on load.
maximize-content-reduce-noise `semantic-dismissible-primitives`	issues	high	Overlay primitives and semantics were inspected in the rendered article DOM. F05 medium: Consent overlays are custom div dialogs without complete modal semantics.
maximize-content-reduce-noise `reduced-chrome`	issues	high	The representative home, article, category, ranking, and error templates were actively inspected for this outcome. F22 medium: Article content is crowded by legacy chrome and consent UI.
adapt-to-the-form-factor `responsive-no-horizontal-scroll`	issues	high	The representative home, article, category, ranking, and error templates were actively inspected for this outcome. F06 critical: Legacy article templates omit the viewport meta tag and render a desktop canvas on mobile.
adapt-to-the-form-factor `component-level-responsiveness`	issues	high	Component behavior and container-query usage were inspected across wide and narrow home layouts. F07 low: Reusable surfaces rely on viewport behavior rather than component-level responsiveness.
adapt-to-the-form-factor `input-modality-aware`	pass	high	Lighthouse did not report target-size failures; primary controls are large, visible buttons on mobile and are native anchors/buttons.
support-core-task-success `clear-purpose-and-primary-action`	pass	high	The heading says “Amebaでブログを書こう” and prominent registration/login actions are visible on desktop and mobile.
support-core-task-success `primary-flow-completion`	issues	high	Registration resolves to the dedicated signup endpoint, but article reading is interrupted by the consent wall reported in F04. F04 high: A consent interstitial obscures article content and even the 404 recovery page on load.
support-core-task-success `clear-system-state-and-recovery`	pass	high	The invalid route returns a branded Japanese 404 state with recovery content behind the separately reported consent interruption; normal templates rendered without blank loading shells.
be-fast-and-stable `good-core-web-vitals`	issues	high	The representative home, article, category, ranking, and error templates were actively inspected for this outcome. F08 high: The homepage has a very slow lab LCP.
be-fast-and-stable `visual-stability`	pass	high	Observed CLS was 0 on home and ranking and 0.037 on the article, within the good threshold.
be-fast-and-stable `efficient-main-thread`	pass	high	Trace TBT was 56ms with one 106ms task; Lighthouse TBT was 91.5ms, indicating bounded main-thread blocking despite slow loading.
be-fast-and-stable `efficient-resource-delivery`	issues	high	The representative home, article, category, ranking, and error templates were actively inspected for this outcome. F09 high: Heavy images and blocking chains delay primary content.
be-fast-and-stable `trim-unused-and-duplicate-code`	issues	high	The representative home, article, category, ranking, and error templates were actively inspected for this outcome. F10 medium: Unused and third-party JavaScript adds avoidable load cost.
be-inclusive `names-roles-labels`	issues	high	The representative home, article, category, ranking, and error templates were actively inspected for this outcome. F11 medium: Some controls and graphics have incorrect or missing accessible names.
be-inclusive `sufficient-contrast`	pass	high	Lighthouse reported no color-contrast failure and controls remained distinguishable under prefers-contrast: more.
be-inclusive `structure-and-focus`	issues	high	The representative home, article, category, ranking, and error templates were actively inspected for this outcome. F12 medium: Heading and list semantics are malformed on the homepage.
be-inclusive `legible-text`	pass	high	Home, category, and ranking text uses readable sizing, spacing, and alignment where the responsive templates are active; the legacy article reflow failure is recorded separately.
be-inclusive `zoom-reflow-targets-and-media`	issues	high	The representative home, article, category, ranking, and error templates were actively inspected for this outcome. F13 critical: Article pages fail mobile reflow and present text at an unreadable scale.
follow-best-practices `no-console-errors`	pass	high	Lighthouse completed with no run warnings and did not report a console-errors or uncaught-exception failure.
follow-best-practices `sound-document-and-assets`	issues	high	The representative home, article, category, ranking, and error templates were actively inspected for this outcome. F14 medium: Images lack intrinsic dimensions and many are oversized or legacy encoded.
follow-best-practices `browser-platform-hygiene`	issues	high	The representative home, article, category, ranking, and error templates were actively inspected for this outcome. F15 medium: Third-party code uses a deprecated API and the page blocks BFCache.
be-discoverable `title-and-description`	issues	high	The representative home, article, category, ranking, and error templates were actively inspected for this outcome. F16 medium: Representative article pages omit a meta description.
be-discoverable `crawlable-and-mobile-friendly`	issues	high	Links and robots are crawlable, but the representative article lacks the viewport meta and fails mobile-friendly rendering. F06 critical: Legacy article templates omit the viewport meta tag and render a desktop canvas on mobile.
be-discoverable `canonical-and-indexing-signals`	issues	high	The representative home, article, category, ranking, and error templates were actively inspected for this outcome. F17 low: The conventional root sitemap URL returns 404.
be-discoverable `structured-and-shareable-metadata`	issues	high	The article has BlogPosting and Open Graph metadata, but the organization homepage has no JSON-LD entity block. F18 low: The public portal homepage has social tags but no entity structured data.
be-private-and-secure `secure-transport-and-headers`	issues	high	The representative home, article, category, ranking, and error templates were actively inspected for this outcome. F19 high: Transport is HTTPS, but security headers and cookie attributes are weak.
be-private-and-secure `data-minimisation-and-third-parties`	issues	high	The representative home, article, category, ranking, and error templates were actively inspected for this outcome. F20 high: The public homepage loads a broad tracking footprint before a consent choice is shown there.
be-private-and-secure `in-context-permissions-and-modern-auth`	pass	high	No permission prompt appeared on load; the audited templates contain no hosted password form and registration/login are delegated to the dedicated auth origin.
be-private-and-secure `defensive-browser-policies`	issues	high	The representative home, article, category, ranking, and error templates were actively inspected for this outcome. F21 high: Browser-enforced defense policies are incomplete.
be-resilient `progressive-enhancement`	pass	high	Homepage raw HTML preserves 91% of rendered content and the article ships title/H1/content in server HTML rather than an empty JS shell.
be-resilient `resilient-runtime-behaviour`	issues	high	The article runtime exposes content but combines an incomplete custom modal with a non-responsive legacy canvas. F04 high: A consent interstitial obscures article content and even the 404 recovery page on load. F06 critical: Legacy article templates omit the viewport meta tag and render a desktop canvas on mobile.
be-resilient `offline-and-installable`	not-applicable	high	A public content/community portal is not an installable app in the audited scope; offline installation is contextual and no manifest is advertised.
be-resilient `network-and-http-failure-states`	pass	high	A deliberately invalid URL returned an explicit branded 404 page rather than a blank shell or false success.
be-internationalised `lang-dir-and-logical-properties`	pass	high	The homepage declares html lang=ja and Japanese reading order is correct; no RTL promise is made for this single-language portal.
be-internationalised `locale-aware-data`	not-applicable	high	The audited public experience is deliberately Japanese and exposed no locale-switching or user-entered locale-sensitive data flow.
be-internationalised `time-zone-correctness`	not-applicable	high	No scheduling, recurring event, or cross-time-zone transaction flow was present in the representative public templates.
be-trustworthy `no-dark-patterns`	pass	high	The consent surface presents equally prominent “Do not consent” and “Consent” actions, and registration/login labels state their purpose without confirmshaming.
be-trustworthy `humane-error-handling`	not-applicable	high	No user-data form submission flow exists on the audited public portal/article templates; search controls were not submitted as an account or transactional form.
be-trustworthy `trustworthy-input-assistance`	not-applicable	high	No address, payment, sign-in, or sign-up form fields are hosted on the audited ameblo.jp templates; authentication routes to a separate origin.
be-trustworthy `safe-commercial-and-account-flows`	not-applicable	high	Checkout, subscription, and account-management surfaces are outside the representative public ameblo.jp templates; the visible registration link routes to auth.user.ameba.jp.
be-sustainable `optimised-assets`	issues	high	The representative home, article, category, ranking, and error templates were actively inspected for this outcome. F23 high: Image delivery is disproportionate for a portal homepage.
be-sustainable `no-wasteful-work`	issues	high	The representative home, article, category, ranking, and error templates were actively inspected for this outcome. F24 medium: Analytics and advertising perform avoidable background requests.
be-sustainable `third-party-and-media-budget`	issues	high	The representative home, article, category, ranking, and error templates were actively inspected for this outcome. F25 high: Third-party and promotional media dominate the network budget.
be-agent-ready `structured-agent-capabilities`	not-applicable	high	The audited surfaces publish and read blog content but expose no agent-executable transaction or productivity capability for which WebMCP tools would be appropriate.
be-agent-ready `on-device-inference`	not-applicable	high	No summarisation, language-model, or other inference feature is offered by the audited public templates, so on-device inference has no current use case.
be-memory-efficient `no-leak-under-repeated-interaction`	pass	high	After ten representative carousel advances, nodes rose 274,425→274,817 (+0.14%) and self size 14,811,819→14,858,621 bytes (+0.32%), a small bounded delta rather than unbounded retained growth.
be-memory-efficient `bounded-footprint`	pass	high	The interactive homepage retained about 14.9MB self size and 275k snapshot nodes, proportionate to its media-rich Next.js portal surface.
be-memory-efficient `no-detached-dom-or-unbounded-listeners`	pass	high	Neither heap summary exposes a Detached* constructor among retained populations, and repeated carousel interaction produced only a 392-node net delta.

Provenance

Canonical report: results/atomic/reports/0031-ameblo_jp.json
Report SHA-256: 6f85a56f17d01fd0b45f19e178ee16e658ebfd4dbf94a9b65df982d291842d26
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/ameblo_jp/2026-07-25T17-16-24-868Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/ameblo_jp/2026-07-25T17-16-24-868Z
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.