Manifest position 512 · CrUX rank bucket 1000
https://pt.erome.com
Coverage complete
Coverage-complete unauthenticated public-site audit across four representative MPA templates.
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 | Computed CSS contained no prefers-color-scheme/color-scheme handling; light-preference and default screenshots were pixel-identical, leaving the interface hard-coded dark. F01 medium: Theme is hard-coded dark rather than preference-aware |
respect-user-preferencesrespects-reduced-motion | pass | high | No active animation was returned by getAnimations() on the audited surfaces, so there is no non-essential motion to suppress. |
respect-user-preferencesrespects-contrast | pass | high | The high-contrast preference screenshot retained visible text and controls with no clipping or disappearance. |
implement-natural-interactionsview-transitions | issues | high | CSS inspection found no view-transition rules and page navigation uses full-document abrupt swaps. F02 low: Route changes do not preserve visual continuity |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No scroll-linked animation or parallax exists on the representative pages, so there is no scroll-animation implementation to judge. |
implement-natural-interactionsphysical-gestures | pass | high | The feed uses native document scrolling without custom pointer handlers or gesture traps. |
provide-guided-navigationscroll-state-aware-chrome | issues | high | The 4,918px mobile explore feed has static chrome and no progress/scroll-state treatment; CSS inspection found no scroll timeline or scroll-state implementation. F03 low: The long feed offers no scroll-state orientation |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip or edge-positioned transient overlay was exposed in the representative public flow. |
provide-guided-navigationdirects-attention | pass | high | Active feed tabs use a clear pink underline and headings orient the current Explore view. |
maximize-content-reduce-noiseno-intrusive-interruptions | pass | high | Load screenshots show the requested content immediately with no content-obscuring interstitial. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Rendered DOM contains three Bootstrap-style .modal elements and two custom dropdown-menu lists, but zero dialog, popover, or details elements. F04 low: Overlays use custom Bootstrap-era primitives |
maximize-content-reduce-noisereduced-chrome | pass | high | The browse template devotes nearly all space below a 50px nav to media content. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | high | Both 360px layout captures report scrollWidth 360, clientWidth 360 and zero horizontal overflow. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | Reusable feed cards adapt only through global layout CSS; CSS inspection found no container queries or container-type declarations. F05 low: Reusable feed cards are not container-responsive |
adapt-to-the-form-factorinput-modality-aware | issues | high | Programmatically focusing the first ten visible links/buttons produced outline: none 0px and no box-shadow on every sampled control. F06 high: Keyboard focus is invisible on primary controls |
support-core-task-successclear-purpose-and-primary-action | pass | high | The landing screen clearly identifies photo/video sharing and exposes sign-in plus Explore; the browse H1 and tabs clarify the feed. |
support-core-task-successprimary-flow-completion | pass | high | The unauthenticated landing-to-Explore-to-album journey completed without a wall or dead end. |
support-core-task-successclear-system-state-and-recovery | pass | high | The site returns a real HTTP 404 and renders the Portuguese H1 “Página não encontrada” for an unknown route. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse mobile throttling measured LCP 5,634ms (poor), despite a fast unthrottled trace LCP of 1,338ms; CLS remained 0.001 and TBT 10ms. F07 medium: Throttled mobile LCP is poor |
be-fast-and-stablevisual-stability | pass | high | Layout observer reported CLS 0 and Lighthouse reported CLS 0.0012. |
be-fast-and-stableefficient-main-thread | pass | high | Trace recorded zero long tasks and 0ms TBT; Lighthouse TBT was 10ms. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR found five first-party CSS/JS parser-inserted high/very-high-priority candidates plus third-party scripts; Lighthouse reported an LCP discovery failure. F08 medium: Critical resource delivery delays LCP |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Scripts transfer 289,681 bytes; Google Tag Manager alone is 153,386 bytes and ad-provider plus ad SDK add 76,600 bytes, a disproportionate non-core share. F09 medium: Analytics and ad code dominate JavaScript bytes |
be-inclusivenames-roles-labels | issues | high | Lighthouse accessibility found two images in the landing disclaimer without alt attributes: the background and logo. F10 medium: Landing imagery lacks accessible alternatives |
be-inclusivesufficient-contrast | pass | high | Lighthouse accessibility scored 0.94 and did not report a color-contrast failure; screenshots remain legible. |
be-inclusivestructure-and-focus | issues | high | The explore page has a reasonable H1/H2 structure, but every sampled visible control suppresses the keyboard focus indicator. F06 high: Keyboard focus is invisible on primary controls |
be-inclusivelegible-text | pass | high | Desktop/mobile screenshots show unclipped text with consistent Montserrat rendering and readable spacing. |
be-inclusivezoom-reflow-targets-and-media | pass | high | Viewport allows scaling and narrow layouts reflow without horizontal overflow; media controls were not needed on the sampled image album. |
follow-best-practicesno-console-errors | pass | high | Lighthouse did not report a console-error audit failure during the explore load. |
follow-best-practicessound-document-and-assets | pass | high | Lighthouse confirmed doctype and charset; rendered thumbnails preserve declared aspect ratios. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse found a deprecated unload listener in libraries.js and four BFCache failure reasons, including that unload handler. F11 low: Deprecated unload handling blocks BFCache |
be-discoverabletitle-and-description | pass | high | Landing, explore and album templates each expose descriptive titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | high | Links use real href values, viewport metadata is present, and robots.txt permits all audited routes. |
be-discoverablecanonical-and-indexing-signals | issues | high | Pages return 200 with canonical/hreflang and robots allows indexing, but /sitemap.xml returns 404 and the Swedish hreflang is incorrectly declared as se rather than sv. F12 medium: Indexing signals contain sitemap and hreflang defects |
be-discoverablestructured-and-shareable-metadata | issues | high | The album has Open Graph/Twitter tags but no JSON-LD, and og:url is http:// while its canonical and served URL are https://. F13 low: Album share metadata is internally inconsistent |
be-private-and-securesecure-transport-and-headers | issues | high | HTTPS and HSTS are present, but CSP, nosniff, clickjacking protection, Referrer-Policy, and Permissions-Policy are absent. F14 high: Browser-enforced security headers are largely absent |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The load contacts 33 third-party origins, including Google Analytics and two ad-tech hosts; GA cookies are non-Secure, SameSite=None, and persist for 400 days. F15 high: Tracking and ad-tech footprint is excessive by default |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | Authentication exposes Google, Reddit, Twitter and email routes, but no passkey/WebAuthn affordance was present in the audited sign-in entry surface. No permission prompt fired on load. F16 medium: Sign-in offers no phishing-resistant option |
be-private-and-securedefensive-browser-policies | issues | high | HSTS is strong, but no CSP frame-ancestors/X-Frame-Options, Referrer-Policy, Permissions-Policy, nosniff, or Trusted Types policy was delivered. F14 high: Browser-enforced security headers are largely absent |
be-resilientprogressive-enhancement | pass | high | Discoverability captures show 100% raw-HTML content coverage on Explore and FAQ with title/H1/description present without JS. |
be-resilientresilient-runtime-behaviour | pass | high | Representative navigation, dropdown-hidden states, feed rendering and album display completed without cut-off or runtime failure. |
be-resilientoffline-and-installable | not-applicable | high | The manifest exists, but this streaming/media service is intrinsically network-dependent; offline operation is not a reasonable core-flow requirement. |
be-resilientnetwork-and-http-failure-states | pass | high | An unknown route returns HTTP 404 with an explicit Portuguese not-found heading rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | issues | high | html lang=pt and hreflang variants exist, but CSS inspection found no logical inline/block properties and the Swedish alternate uses invalid hreflang se. F17 medium: Localization foundations are incomplete |
be-internationalisedlocale-aware-data | not-applicable | high | The representative public pages expose no dates, currency, durations, or other locale-formatted data. |
be-internationalisedtime-zone-correctness | not-applicable | high | The representative public pages expose no events, schedules, or time-zone-sensitive concepts. |
be-trustworthyno-dark-patterns | pass | high | The audited public browse flow did not display confirmshaming, forced continuity, consent nagging, or a disguised checkout. |
be-trustworthyhumane-error-handling | not-applicable | high | No editable form is part of the public browse flow; authentication forms were not submitted with user data. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No address, payment, sign-up, or text-entry form is part of the representative public browse flow. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | No checkout/subscription flow was present and authenticated account management was outside the unauthenticated public scope. |
be-sustainableoptimised-assets | issues | high | Images audit found 38 legacy-format images, 22 without srcset, and 15 without explicit dimensions; no AVIF/WebP images were observed. F18 medium: Feed images miss modern delivery features |
be-sustainableno-wasteful-work | pass | high | The 6.6s trace reported no long tasks and the HAR showed no repeated background-fetch loop. |
be-sustainablethird-party-and-media-budget | issues | high | HAR transferred 752,432 bytes across 55 requests; third-party analytics/ad scripts account for at least 229,986 script bytes before user interaction. F19 medium: Third-party script cost is disproportionate |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing intent or transactional agent surface was evident; this emerging capability is contextual. |
be-agent-readyon-device-inference | not-applicable | high | No user task on the audited public pages calls for on-device inference; this emerging capability is contextual. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | After ten top-to-bottom feed scroll cycles, heap self size decreased 153KB and node count changed only +69. |
be-memory-efficientbounded-footprint | pass | high | Baseline heap was 8.26MB self size and 146,244 nodes, proportionate to a 100-thumbnail media listing. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | high | The repeated-scroll before/after heap pair remained effectively bounded with no retained-size growth signal. |
Provenance
Canonical report: results/atomic/reports/0512-pt_erome_com.json
Report SHA-256: b580887b9508c258714a49ff870172d00dcf74616d1fc01f654910d46fd70a5b
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/pt_erome_com/2026-07-21T07-25-31-874Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/pt_erome_com/2026-07-21T07-25-31-874Z
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.