Manifest position 572 · CrUX rank bucket 1000
https://www.ojogodobicho.com
Coverage complete
All 58 catalog checks received a conclusive outcome across six 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 | Under prefers-color-scheme: dark, the probe reports colorScheme "normal", body background rgb(255,255,255), and text rgb(34,34,34); the dark screenshot remains light. F01 medium: The site ignores the user’s dark-mode preference. |
respect-user-preferencesrespects-reduced-motion | pass | medium | No authored continuous or auto-advancing motion was observed; under reduced-motion emulation document.getAnimations() returned none. |
respect-user-preferencesrespects-contrast | pass | medium | Forced-colors and prefers-contrast emulation produced black surfaces, white text, and yellow links that remained visible. |
implement-natural-interactionsview-transitions | issues | high | DOM/CSS inspection across five MPA templates found no view-transition-name or @view-transition rule; navigation performs a full visual swap. F02 low: Page changes are abrupt and do not preserve spatial context. |
implement-natural-interactionsscroll-driven-animations | not-applicable | high | No parallax, scrollytelling, or scroll-linked animation exists on the representative templates. |
implement-natural-interactionsphysical-gestures | not-applicable | high | The portal exposes no swipe, drag, carousel, pull-to-refresh, or other custom gesture surface. |
provide-guided-navigationscroll-state-aware-chrome | pass | medium | Long content pages retain a stable, conventional document flow and do not use sticky chrome that needs scroll-state adaptation. |
provide-guided-navigationanchored-positioning | issues | high | Rendered source positions .rjb-drop with position:absolute; top:42px; left:0 and has no anchor-name, position-anchor, or position-try fallback. F03 low: Dropdown navigation is manually positioned. |
provide-guided-navigationdirects-attention | pass | medium | Results and contact templates show visible breadcrumb context and clear page headings after navigation. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Lighthouse notification-on-start identifies notifpush.com/scripts/wpn2.js. This interrupts users before any notification-related action. F04 high: A third-party script requests notification permission on page load. |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | Lighthouse notification-on-start identifies notifpush.com/scripts/wpn2.js. This interrupts users before any notification-related action. F04 high: A third-party script requests notification permission on page load. |
maximize-content-reduce-noisereduced-chrome | pass | medium | Screenshots show a restrained shared header/navigation and content occupies the main reading area; no decorative application frame crowds the text. |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | pass | medium | Layout evidence at 390×844 reports scrollWidth 390, clientWidth 390, and horizontalOverflowPx 0 on home, results, and statistics. |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | DOM/CSS inspection shows @media(max-width:767px) rules for navigation and footer, but no @container/container-type usage across representative templates. F05 low: Components rely on global media queries rather than their available container. |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus probe found 8 of the first 30 focusable controls with neither outline nor box-shadow after programmatic focus. F06 medium: Keyboard focus is not consistently visible. |
support-core-task-successclear-purpose-and-primary-action | pass | medium | The homepage identifies the portal and prominently links to “DEU NO POSTE”; the results page H1 explicitly identifies today’s result. |
support-core-task-successprimary-flow-completion | pass | medium | The primary information-retrieval journey completed from homepage navigation to the dated results page without login or dead end. |
support-core-task-successclear-system-state-and-recovery | pass | medium | A nonexistent URL renders a titled Erro 404 page with explanation, global navigation, site map direction, and contact recovery. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse measured LCP 7.6 s and Time to Interactive 10.5 s (performance 0.72), despite CLS 0. F07 high: Largest Contentful Paint is slow under Lighthouse mobile conditions. |
be-fast-and-stablevisual-stability | pass | medium | Layout observers on home, results, and statistics measured CLS 0 with no recorded shifts; the logo has explicit dimensions. |
be-fast-and-stableefficient-main-thread | issues | high | The trace recorded two long tasks, longest 400.28 ms, with 456.39 ms total blocking time; the mobile layout observer also saw a 123 ms long task. F08 high: Third-party scripts block the main thread. |
be-fast-and-stableefficient-resource-delivery | issues | high | HAR captured 141 requests and 2,541,549 transferred bytes; 122 requests and 2,516,086 bytes were third-party. Scripts alone transferred 1,848,603 bytes. F09 high: The lightweight page has a large, third-party-dominated network load. |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | HAR lists multiple overlapping ad/video stacks (MGID, Vidoomy, Aniview, DoubleClick, Clever, servg1) among the largest resources; 39 scripts transferred 1.85 MB. F10 high: Advertising and analytics code dominates the shipped JavaScript. |
be-inclusivenames-roles-labels | issues | high | Lighthouse found three focusable MGID ad links with no discernible name and a 1×1 advertising iframe without a title. F11 high: Third-party ad links and an iframe lack accessible names. |
be-inclusivesufficient-contrast | issues | high | Lighthouse measured 1.77:1 contrast between #0033cc links and surrounding #222 text and found no non-color cue for three representative links. F12 medium: Inline links are distinguishable only by low-contrast color. |
be-inclusivestructure-and-focus | issues | high | Lighthouse reports no main landmark and an H1-to-H5 heading jump for “Navegue pelo site”; representative probes likewise found no MAIN element. F13 medium: The document landmark and heading hierarchy are incomplete. |
be-inclusivelegible-text | pass | medium | Mobile screenshots show readable text, sensible wrapping, and no clipping across home, results, statistics, dreams, and contact templates. |
be-inclusivezoom-reflow-targets-and-media | pass | medium | The page allows scaling, reflows at 390 px without overflow, and mobile navigation rows are approximately 48 px tall; no authored audio/video requires captions. |
follow-best-practicesno-console-errors | pass | medium | Lighthouse errors-in-console passed with an empty error list. |
follow-best-practicessound-document-and-assets | pass | medium | DOM has viewport metadata and authored images have explicit width, height, alt text, and correct aspect ratio; Lighthouse found no doctype/charset/image-ratio failure. |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse failed notification-on-start and inspector-issues; the latter contains extensive cookie-policy issues from ad vendors. F14 medium: The page triggers a permission prompt on load and logs browser inspector issues. |
be-discoverabletitle-and-description | pass | medium | All five representative templates expose descriptive, template-specific titles and meta descriptions. |
be-discoverablecrawlable-and-mobile-friendly | pass | medium | Representative pages have viewport metadata and real href navigation; Googlebot fetch of robots.txt returned 200 and permits public content. |
be-discoverablecanonical-and-indexing-signals | pass | medium | Home and content probes expose canonical URLs and index/follow; Googlebot fetches of robots.txt and sitemap.xml both returned 200 and the sitemap is populated. |
be-discoverablestructured-and-shareable-metadata | pass | medium | Home has three JSON-LD blocks and six Open Graph tags; results has two JSON-LD blocks and six Open Graph tags aligned with visible page titles. |
be-private-and-securesecure-transport-and-headers | issues | high | Cookie audit found four cookies flagged, including three without Secure and two 400-day analytics cookies. CSP only upgrades/blocks mixed content and does not restrict script sources. F15 high: Cookies and CSP do not provide a strong secure default. |
be-private-and-securedata-minimisation-and-third-parties | issues | high | Tracker evidence found 31 third-party origins and known Google tracking domains; HAR attributes 2.52 MB and 122 requests to third parties. F16 high: The tracking and advertising footprint is disproportionate to the content. |
be-private-and-securein-context-permissions-and-modern-auth | issues | high | Lighthouse traces an on-load notification request to notifpush.com before the user expresses intent; no relevant notification control appears in the first viewport. F17 high: Notification permission is requested out of context. |
be-private-and-securedefensive-browser-policies | issues | high | Headers evidence shows no X-Content-Type-Options, no X-Frame-Options/frame-ancestors, and no Permissions-Policy. The CSP has no source restrictions. F18 medium: Several browser-enforced defenses are absent. |
be-resilientprogressive-enhancement | pass | medium | Discoverability evidence shows server-rendered content: home raw HTML retains title/H1/meta and 65% word coverage; results retains 97% and is not a JS shell. |
be-resilientresilient-runtime-behaviour | pass | medium | The mobile menu opens/closes with stable DOM count, and representative templates render without clipped horizontal content. |
be-resilientoffline-and-installable | not-applicable | high | This is a public text/results portal rather than an app-like workflow; installability and offline app behavior are not necessary for its primary task. |
be-resilientnetwork-and-http-failure-states | pass | medium | A representative missing route provides an intentional, actionable 404 recovery page rather than a blank shell. |
be-internationalisedlang-dir-and-logical-properties | pass | medium | All representative pages declare html lang="pt-BR" and render Portuguese reading order correctly; no RTL locale is offered. |
be-internationalisedlocale-aware-data | pass | medium | Dated result content is rendered in localized Brazilian Portuguese form, including “Terça-Feira, 21 de Julho de 2026”. |
be-internationalisedtime-zone-correctness | not-applicable | high | The audited public pages publish draw dates but expose no appointments, user-local times, recurring schedules, or cross-time-zone event workflow. |
be-trustworthyno-dark-patterns | issues | high | Lighthouse confirms notification permission is requested automatically on page load, before context or a user gesture. F19 high: The unsolicited notification prompt is a nagging consent pattern. |
be-trustworthyhumane-error-handling | not-applicable | high | No user-input form exists on the representative contact or primary result templates. |
be-trustworthytrustworthy-input-assistance | not-applicable | high | No user-input fields exist on the representative pages, so autofill assistance is not applicable. |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | The audited site states it does not take bets and exposes no checkout, subscription, consent transaction, or first-party account-management flow. |
be-sustainableoptimised-assets | issues | high | Images evidence reports the sole authored image as PNG with no srcset; it is displayed at 295 px from a 480 px source. F20 low: The logo has no responsive source and uses a legacy raster format. |
be-sustainableno-wasteful-work | issues | high | HAR records 46 XHR/fetch requests plus overlapping ad auctions, analytics, push, and video scripts; trace blocking time is 456.39 ms. F21 high: The page performs substantial non-content background work. |
be-sustainablethird-party-and-media-budget | issues | high | Of 2.54 MB transferred, 2.52 MB was third-party; the authored page has one small image, while ad/video stacks account for most bytes. F22 high: Third-party and media cost is not proportionate to this text-first portal. |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared intent requests agent-facing transactions or WebMCP capabilities; this public information portal remains accessible to agents through server-rendered HTML and metadata. |
be-agent-readyon-device-inference | not-applicable | high | Summarization or language-model inference is not needed to complete the portal’s primary result lookup task. |
be-memory-efficientno-leak-under-repeated-interaction | pass | medium | Ten open/close cycles of the real mobile-menu interaction left DOM nodes at 292, JS heap unchanged at 10,440,520 bytes in the same session, and the menu closed. |
be-memory-efficientbounded-footprint | pass | medium | Heap summaries measured 11.3–15.7 MB self size; the live authored DOM had 292 elements. This is bounded, though third-party advertising explains run-to-run variance. |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | Heap summaries contain no Detached* constructor among reported populations, and repeated menu toggling did not add DOM nodes or heap bytes in-session. |
Provenance
Canonical report: results/atomic/reports/0572-www_ojogodobicho_com.json
Report SHA-256: d3fc34a579cb49d86a2000330dc2e4846accd24bab9d5a051a6fd79c896707bd
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_ojogodobicho_com/2026-07-21T16-03-51-892Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/www_ojogodobicho_com/2026-07-21T16-03-51-892Z
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.