Manifest position 817 · CrUX rank bucket 1000
https://pet.gree-apps.net
Coverage complete
Coverage-complete report-mode audit. The entry redirects to a desktop brochure for the raw-CDP desktop profile and to a GREE login journey for Lighthouse mobile emulation; both were treated as representative paths.
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 screenshot is pixel-equivalent to the default capture and the platform probe reports colorScheme "normal" with no dark-theme treatment. F01 medium: The page ignores the user’s dark color-scheme preference. |
respect-user-preferencesrespects-reduced-motion | pass | high | Reduced-motion emulation reports zero active animations; the page adds no motion that must be suppressed. |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors screenshot preserves visible content/control boundaries; primary text remains distinguishable. |
implement-natural-interactionsview-transitions | issues | high | DOM/CSS inspection found no view-transition declarations across the three full-page content routes. F02 low: Navigation changes have no transition continuity. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | The audited templates contain no scrollytelling or state that calls for scroll-linked animation. |
implement-natural-interactionsphysical-gestures | pass | high | The manga template provides Swiper previous/next and swipe interaction rather than a custom pointer-only drag implementation. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The mobile home capture is several screens tall, while DOM/CSS evidence shows neither sticky progress/navigation nor scroll-state feedback. F03 low: Long pages provide no scroll-position guidance. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, menu, or popover requiring anchored edge-aware positioning exists. |
provide-guided-navigationdirects-attention | pass | high | Each route sets an active navigation item and uses a clear content heading/icon treatment. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Initial screenshot shows content directly with no modal, consent wall, or full-screen interruption. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The probe identifies .noticeHead as an H2 and .close as a SPAN with no role or tabindex; both respond to click but are absent from keyboard navigation. F04 high: The expandable support notice is mouse-only custom UI. |
maximize-content-reduce-noisereduced-chrome | pass | high | The page reserves the large majority of width for game content; the stable sidebar remains secondary. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At a 360x800 viewport, layout reports no viewport meta and a 980 CSS-pixel layout viewport; screenshots show tiny text and controls across home, manga, and SNS. F05 high: Mobile browsers receive a desktop canvas scaled down to 36.7%. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The platform probe finds no container-query usage; fixed 768px content images and a 180px carousel margin are visible in rendered DOM. F06 medium: Components do not adapt to their available width. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The support disclosure controls are not keyboard focusable, and one page-top link computes outline:none while focused. F07 high: Input modality support is incomplete. |
support-core-task-successclear-purpose-and-primary-action | issues | high | The home screenshot presents branding and troubleshooting first; navigation labels are literally "test" and no named start/play action appears in the control inventory. F08 high: The first viewport does not expose a clear primary action. |
support-core-task-successprimary-flow-completion | issues | high | HAR records 302 -> 307 -> 302 before the content page, while Lighthouse with a mobile user agent lands on id.gree.net rather than the audited content URL. F09 high: The primary journey is fragmented across three redirects and a separate login origin. |
support-core-task-successclear-system-state-and-recovery | pass | high | The browser-specific access problem is surfaced in a named disclosure and the direct interaction probe confirms it opens and closes successfully. |
be-fast-and-stablegood-core-web-vitals | issues | high | The raw-CDP trace reports FCP 3941.51ms and LCP 4193.03ms; Lighthouse’s redirected mobile journey is slower still and is retained only as corroboration for that journey. F10 high: Loading performance misses the good LCP range. |
be-fast-and-stablevisual-stability | pass | high | Layout observation after load reports CLS 0 with no shift entries. |
be-fast-and-stableefficient-main-thread | pass | high | Trace reports zero long tasks and 0ms total blocking time. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR reports 36 requests/862,797 transferred bytes, three redirects, two VeryHigh parser stylesheets, and parser-inserted scripts without async/defer; trace load ends at 4501.54ms. F11 high: Resource delivery is delayed by redirects, parser-blocking assets, and third-party weight. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR shows 231,293 script bytes including jQuery 1.11.1, LAB 2.0.3, analytics, and Tag Manager on a page whose only bespoke interaction is a disclosure toggle. F12 medium: Legacy and likely non-critical scripts inflate a mostly static page. |
be-inclusivenames-roles-labels | issues | high | The image audit reports 6 of 7 images without alt; DOM shows empty SNS links and all three nav destinations named "test"; the custom disclosure controls have no roles. F13 high: Important images, links, and controls lack accessible names. |
be-inclusivesufficient-contrast | pass | high | Forced-colors capture keeps the visible content distinct; no target-page contrast failure was directly observed. |
be-inclusivestructure-and-focus | issues | high | There is no main landmark in rendered markup; the notice H2/span controls cannot receive focus, and a focused page-top link has outline:none. F14 high: Document structure and focus handling exclude keyboard users. |
be-inclusivelegible-text | issues | high | The 360px screenshots render the 980px fixed page at 0.367 scale, making sidebar and explanatory copy impractically small. F15 high: Text is too small on mobile because the desktop page is scaled down. |
be-inclusivezoom-reflow-targets-and-media | issues | high | All three content templates omit viewport meta and render a desktop-width document in the mobile capture. F16 high: Mobile zoom/reflow expectations are not met. |
follow-best-practicesno-console-errors | pass | high | An active open/close interaction with error and unhandledrejection listeners recorded no runtime errors. |
follow-best-practicessound-document-and-assets | issues | high | The image primitive reports 7/7 images without width/height, 7/7 without srcset, 7 legacy PNGs, and 6 below-fold images without lazy loading. F17 medium: Image markup omits intrinsic dimensions and responsive delivery. |
follow-best-practicesbrowser-platform-hygiene | issues | high | DOM contains duplicate page-top IDs, javascript:void(0) navigation, HTTP internal hrefs, and mouse-only click handlers. F18 medium: The page uses fragile browser-platform patterns. |
be-discoverabletitle-and-description | issues | high | manga-dom.json and sns-dom.json both report an empty document title and empty meta description. F19 high: Two representative content routes have empty titles and descriptions. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | All three internal nav labels are "test" and their authored hrefs are http://jp.apps.gree.net/...; robots.txt and sitemap.xml both return 404. F20 high: Navigation links are not descriptive and use insecure HTTP destinations. |
be-discoverablecanonical-and-indexing-signals | pass | high | Home and both representative static routes expose self-referential HTTPS canonical links and return rendered 200 documents. |
be-discoverablestructured-and-shareable-metadata | issues | high | Home og:url points to http://apps.gree.net/95, static routes emit empty Open Graph values, and the probe finds no JSON-LD. F21 medium: Share and structured metadata is stale or empty. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers evidence reports missing CSP, HSTS, X-Content-Type-Options, clickjacking protection, Referrer-Policy, and Permissions-Policy. F22 high: The document lacks baseline defensive response headers. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence finds 10 third-party origins and Google Analytics, DoubleClick, Tag Manager, and UserHeat; HAR attributes 34/36 requests and 862,536 bytes to non-entry origins. F23 high: The page sends a disproportionate tracking footprint before any visible consent. |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No permission request appears on load; the login handoff is user-initiated and presents conventional authentication choices. |
be-private-and-securedefensive-browser-policies | issues | high | Headers evidence reports missing CSP, HSTS, X-Content-Type-Options, clickjacking protection, Referrer-Policy, and Permissions-Policy. F22 high: The document lacks baseline defensive response headers. |
be-resilientprogressive-enhancement | pass | high | Discoverability comparison reports 100% rendered-word coverage in raw HTML, no empty mount, and title/H1/description available without JavaScript. |
be-resilientresilient-runtime-behaviour | pass | high | The representative disclosure opens and closes repeatedly without errors; content is server-rendered rather than dependent on reactive state. |
be-resilientoffline-and-installable | not-applicable | high | This public marketing/content surface does not present itself as an installable offline application. |
be-resilientnetwork-and-http-failure-states | issues | high | Both /robots.txt and /sitemap.xml return a bare server 404; the core entry journey also traverses several origins without an explanatory intermediate/retry state. F24 medium: Failure handling falls back to generic server behavior. |
be-internationalisedlang-dir-and-logical-properties | pass | high | All templates declare html lang=ja, matching the explicitly Japanese-only content. |
be-internationalisedlocale-aware-data | not-applicable | high | The Japanese-only content renders no locale-sensitive dates, currencies, or numeric data. |
be-internationalisedtime-zone-correctness | not-applicable | high | No time, event, recurrence, or scheduling data appears on the audited routes. |
be-trustworthyno-dark-patterns | pass | high | No consent manipulation, forced continuity, disguised advertisement, or obstructive cancel flow appears on the audited public routes. |
be-trustworthyhumane-error-handling | not-applicable | high | The content templates contain no user-submitted form; login error navigation could not be retained as an artifact and is not used for a verdict. |
be-trustworthytrustworthy-input-assistance | issues | high | The login DOM shows email and password inputs without autocomplete=username and autocomplete=current-password. F25 medium: The login flow does not declare autofill purpose tokens. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout, subscription, cancellation, or account-management surface is exposed in the audited public route set. |
be-sustainableoptimised-assets | issues | high | Images account for 602,775 transferred bytes; all audited img elements are PNG without responsive sources, and six below-fold images load eagerly. F26 medium: Asset delivery is heavier than the static content warrants. |
be-sustainableno-wasteful-work | issues | high | Known trackers run across four domains and Tag Manager alone transfers 156,876 bytes; two analytics fetches fail/abort during capture. F27 medium: Background analytics work dominates a simple static page. |
be-sustainablethird-party-and-media-budget | issues | high | The HAR attributes 862,536 of 862,797 transferred bytes to origins other than the entry origin, including 178KB+ of analytics/tag scripts. F28 medium: Third-party work consumes nearly the entire transfer budget. |
be-agent-readystructured-agent-capabilities | not-applicable | high | The surface is a read-only game brochure with no safe agent-executable task or form beyond an external login handoff. |
be-agent-readyon-device-inference | not-applicable | high | The surface has no summarisation, generation, or other inference use case. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | After ten open/close cycles, retained self-size increased only 156,457 bytes (3.1%) across isolated captures, with no Detached constructor in the top summary. |
be-memory-efficientbounded-footprint | pass | medium | Baseline heap summary is proportionate for the static page at 108,726 nodes and 4,985,444 self-size bytes. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Neither baseline nor post-interaction top-constructor summary contains Detached nodes; repeated toggles add no handlers in authored code. |
Provenance
Canonical report: results/atomic/reports/0817-pet_gree-apps_net.json
Report SHA-256: a9da70da475845b3c5013c40327d7c9e009644fc875a6e0bde5207201785f3cf
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/pet_gree-apps_net/2026-07-23T05-20-24-010Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/pet_gree-apps_net/2026-07-23T05-20-24-010Z
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.