Manifest position 870 · CrUX rank bucket 1000
https://note.com
Coverage complete
Coverage-complete representative audit of public discovery, listing, article, login and 404 archetypes. Authenticated creation, purchase, subscription, settings and account cancellation were not covered because no credentials or transactions were available.
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 | The dark-mode screenshot remains white, and the emulated-media probe reports color-scheme: normal with body background rgb(255,255,255) while prefers-color-scheme: dark matches. F01 medium: The interface ignores the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Emulated reduced-motion matched and the page exposed no active animations to suppress. |
respect-user-preferencesrespects-contrast | pass | high | Lighthouse color-contrast audit passed with no failing nodes, and the high-contrast black-on-white surfaces remained legible. |
implement-natural-interactionsview-transitions | issues | medium | The preference/CSS probe found no active animations, no scroll timelines and no authored transition evidence across the homepage and article navigation surfaces. F02 low: Navigation and route/state changes have no authored visual continuity. |
implement-natural-interactionsscroll-driven-animations | pass | high | No custom scroll animation timeline or active animation was found, avoiding main-thread scroll-linked motion. |
implement-natural-interactionsphysical-gestures | pass | high | Mobile feed browsing uses native scrolling and responsive card/list arrangements without custom drag listeners observed in the inspected DOM. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | The article header is sticky and preserves primary login/navigation access while reading. |
provide-guided-navigationanchored-positioning | pass | high | No tooltip, menu or overlay requiring viewport-edge anchoring appeared on the tested paths. |
provide-guided-navigationdirects-attention | pass | high | Clear section headings, article title hierarchy, sticky chrome and distinct current navigation pills guide attention. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | No full-viewport interstitial appeared on initial load; the fixed-large-overlay probe returned zero. |
maximize-content-reduce-noisesemantic-dismissible-primitives | not-applicable | high | No dialog, popover, disclosure or other dismissible overlay was present on any representative path. |
maximize-content-reduce-noisereduced-chrome | pass | high | Primary viewports devote most space to content cards or article media/text, with a compact 65px header. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | At 360x800, both homepage and article reported scrollWidth=clientWidth=360 and zero horizontal overflow. |
adapt-to-the-form-factorcomponent-level-responsiveness | pass | high | The same feed changes from multi-column cards on desktop to compact image-right rows on mobile, and article content reflows to 360px without overflow. |
adapt-to-the-form-factorinput-modality-aware | issues | high | After focusing the username input, the computed focus probe reported outline: none and box-shadow: none; the component classes also remove focus outlines. F03 medium: The login input does not expose a visible programmatic focus treatment. |
support-core-task-successclear-purpose-and-primary-action | pass | high | Homepage search, topic pills and featured content make discovery clear; article title, author and content are immediately identifiable. |
support-core-task-successprimary-flow-completion | pass | high | Unauthenticated users can discover an article from the homepage and read it without a login wall; tested article content rendered fully. |
support-core-task-successclear-system-state-and-recovery | issues | high | Activating the login button with empty fields left focus on BODY and the invalid-state probe found no field validation message, :invalid target, or useful live-region error. F04 medium: Empty login submission does not present clear inline recovery feedback. |
be-fast-and-stablegood-core-web-vitals | issues | high | Mobile Lighthouse measured LCP 10.3 s, TBT 370 ms, Speed Index 7.5 s and performance 0.59; the trace corroborates FCP around 690 ms while the mobile layout recorded two long tasks. F05 high: Homepage loading is slow enough to fail the Core Web Vitals baseline. |
be-fast-and-stablevisual-stability | pass | high | Homepage CLS was 0.004 and article CLS was 0 with no horizontal overflow; all inspected images had dimensions. |
be-fast-and-stableefficient-main-thread | issues | high | Mobile Lighthouse measured LCP 10.3 s, TBT 370 ms, Speed Index 7.5 s and performance 0.59; the trace corroborates FCP around 690 ms while the mobile layout recorded two long tasks. Lighthouse estimates 512 KiB unused JavaScript and 21 KiB unused CSS, with 1.8 s JavaScript execution and 3.2 s main-thread work. F05 high: Homepage loading is slow enough to fail the Core Web Vitals baseline. F07 medium: Large amounts of JavaScript and CSS are unused during the tested homepage load. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR captured 166 requests and 3,246,381 transferred bytes, including 83 images (1.73 MB) and 58 scripts (1.39 MB); Lighthouse estimates 790 KiB image-delivery savings. F06 high: The homepage ships a large request and image payload for a feed landing page. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 512 KiB unused JavaScript and 21 KiB unused CSS, with 1.8 s JavaScript execution and 3.2 s main-thread work. F07 medium: Large amounts of JavaScript and CSS are unused during the tested homepage load. |
be-inclusivenames-roles-labels | issues | high | Lighthouse axe audit label-content-name-mismatch failed on 40 profile links because the visible name/time text is not included in the aria-label. F08 medium: Visible creator labels do not match their accessible names. |
be-inclusivesufficient-contrast | pass | high | Lighthouse color-contrast audit passed with no failing elements. |
be-inclusivestructure-and-focus | pass | high | Skip link, semantic main/navigation landmarks and sequential heading order were present; the remaining focus-style defect is recorded under input modality. |
be-inclusivelegible-text | pass | high | Desktop and 360px screenshots show readable body and heading sizes with comfortable article line length and reflow. |
be-inclusivezoom-reflow-targets-and-media | pass | high | Viewport meta is width=device-width, both mobile layouts reflow without overflow, and Lighthouse target-size passed. |
follow-best-practicesno-console-errors | pass | high | Lighthouse errors-in-console audit passed with an empty error list. |
follow-best-practicessound-document-and-assets | pass | high | HTML doctype and UTF-8 charset passed; all 100 inspected images had intrinsic dimensions. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse valid-source-maps flags _next/static/chunks/87606-cad16c65e603c413.js as a large first-party file without a source map. F09 low: A large first-party JavaScript chunk lacks a production source map. |
be-discoverabletitle-and-description | pass | high | Homepage and article provide descriptive titles and meta descriptions that match visible purpose/content. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Discoverability evidence found only 10% raw/rendered word coverage: raw HTML had 236 text characters versus 4,433 rendered, and the crawler screenshot showed only a loading indicator. The article archetype itself was server-rendered. F10 high: The dynamic homepage feed is largely unavailable to non-JavaScript crawlers. |
be-discoverablecanonical-and-indexing-signals | pass | high | Both tested public pages return 200, provide self-canonicals and indexable robots metadata; robots.txt points to a gzipped sitemap. |
be-discoverablestructured-and-shareable-metadata | pass | high | Article provides BlogPosting JSON-LD with author and timestamp plus complete Open Graph metadata; homepage provides Open Graph metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers evidence found HTTPS and CSP, but no HSTS, X-Content-Type-Options, Referrer-Policy or Permissions-Policy. Cookie evidence found three identifier cookies without Secure and several SameSite=None cookies. F11 high: Transport hardening and cookie policy leave avoidable downgrade and policy gaps. |
be-private-and-securedata-minimisation-and-third-parties | issues | medium | Tracker evidence identified Google Tag Manager among three third-party origins; the HAR shows the analytics script at about 160 KB and high priority, although DOM evidence confirms it is async. F12 low: The public homepage loads analytics before any demonstrated user choice. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | The login screenshot and form probe show Google, X, Apple, email/note ID and password options, with no WebAuthn/passkey affordance. F13 medium: The sign-in surface does not offer a passkey path. |
be-private-and-securedefensive-browser-policies | issues | high | Headers evidence found HTTPS and CSP, but no HSTS, X-Content-Type-Options, Referrer-Policy or Permissions-Policy. Cookie evidence found three identifier cookies without Secure and several SameSite=None cookies. F11 high: Transport hardening and cookie policy leave avoidable downgrade and policy gaps. |
be-resilientprogressive-enhancement | issues | high | With JavaScript unavailable, the crawler screenshot remains at a loading indicator and raw HTML preserves only 10% of rendered content words, while article content demonstrates that SSR is feasible on the same platform. F14 high: The homepage’s core discovery content is not progressively enhanced. |
be-resilientresilient-runtime-behaviour | pass | high | Representative home, listing, article and login paths rendered without console errors or broken overlay state. |
be-resilientoffline-and-installable | issues | medium | The DOM found no manifest link, the service-worker registration probe returned an empty list, and no offline surface was exposed. F15 low: The public content platform is neither installable nor registered for offline handling. |
be-resilientnetwork-and-http-failure-states | pass | high | An invalid route shows a clear Japanese 404 explanation, home/signup links and an alternate content link. |
be-internationalisedlang-dir-and-logical-properties | issues | medium | The DOM reports lang=ja-JP, but stylesheet inspection found 181 physical left/right declarations and only one logical-property rule, making RTL adaptation fragile. F16 medium: CSS is not ready for bidirectional layout despite correctly declared Japanese language. |
be-internationalisedlocale-aware-data | pass | high | Article timestamps are localized in Japanese and machine-readable through a time datetime and JSON-LD datePublished. |
be-internationalisedtime-zone-correctness | pass | high | The article machine-readable timestamp carries an explicit +09:00 offset in both time and JSON-LD. |
be-trustworthyno-dark-patterns | pass | high | The tested public and login screens use straightforward login/registration labels, no forced modal and no disguised consent or upsell. |
be-trustworthyhumane-error-handling | issues | high | Activating the login button with empty fields left focus on BODY and the invalid-state probe found no field validation message, :invalid target, or useful live-region error. F04 medium: Empty login submission does not present clear inline recovery feedback. |
be-trustworthytrustworthy-input-assistance | pass | high | Login username and password fields expose autocomplete=username and current-password respectively. |
be-trustworthysafe-commercial-and-account-flows | issues | high | The login screenshot and form probe show Google, X, Apple, email/note ID and password options, with no WebAuthn/passkey affordance. F13 medium: The sign-in surface does not offer a passkey path. |
be-sustainableoptimised-assets | issues | high | The images primitive found 63 oversized images, 54 without srcset, 98 legacy-format images and no modern-format images among 100 inspected; HAR attributed 1.73 MB to images. F17 high: Feed images are substantially over-delivered and overwhelmingly use legacy formats. |
be-sustainableno-wasteful-work | pass | high | Trace recorded no >50ms main-thread tasks in its capture window and the page had no continuous active animations; analytics was limited to one identified tracker origin. |
be-sustainablethird-party-and-media-budget | issues | medium | HAR captured 166 requests and 3,246,381 transferred bytes, including 83 images (1.73 MB) and 58 scripts (1.39 MB); Lighthouse estimates 790 KiB image-delivery savings. Tracker evidence identified Google Tag Manager among three third-party origins; the HAR shows the analytics script at about 160 KB and high priority, although DOM evidence confirms it is async. The images primitive found 63 oversized images, 54 without srcset, 98 legacy-format images and no modern-format images among 100 inspected; HAR attributed 1.73 MB to images. F06 high: The homepage ships a large request and image payload for a feed landing page. F12 low: The public homepage loads analytics before any demonstrated user choice. F17 high: Feed images are substantially over-delivered and overwhelmingly use legacy formats. |
be-agent-readystructured-agent-capabilities | issues | medium | The agent probe found no WebMCP registration even though public articles have clear summarisation and discovery value; article JSON-LD is present but is metadata rather than a callable capability. F18 low: The content platform exposes no structured agent capability surface. |
be-agent-readyon-device-inference | not-applicable | high | No site-provided AI inference feature was presented; browser API availability alone does not make this check applicable. |
be-memory-efficientno-leak-under-repeated-interaction | issues | medium | Heap summaries rose from 1,063,081 nodes / 50,219,780 bytes to 1,457,060 nodes / 65,562,296 bytes after ten bottom/top traversals, a roughly 37% node and 31% self-size increase. The evidence does not isolate a detached-node leak, so confidence is medium. F19 medium: Repeated feed traversal grows an already large heap substantially. |
be-memory-efficientbounded-footprint | issues | medium | Heap summaries rose from 1,063,081 nodes / 50,219,780 bytes to 1,457,060 nodes / 65,562,296 bytes after ten bottom/top traversals, a roughly 37% node and 31% self-size increase. The evidence does not isolate a detached-node leak, so confidence is medium. F19 medium: Repeated feed traversal grows an already large heap substantially. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | Neither heap summary listed Detached, Listener or Timer constructors among the reported largest constructor populations; no detached-node claim is made. |
Provenance
Canonical report: results/atomic/reports/0870-note_com.json
Report SHA-256: 1e2d0229c0dc73fb6647d8a007538ca025e1f1e75d3d17c382696ab3886521f6
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/note_com/2026-07-23T13-31-33-107Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/note_com/2026-07-23T13-31-33-107Z
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.