Manifest position 827 · CrUX rank bucket 1000
https://g1.globo.com
Coverage complete
Atomic coverage complete across 59 registered checks and four representative public templates. Search results, authenticated account flows, live playback internals and every regional section were not covered because they either repeat audited templates or cross into separate/authenticated surfaces.
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 is pixel-identical to the light screenshot and the platform probe reports computed colorScheme "normal". F001 medium: No user-preference-driven dark theme |
respect-user-preferencesrespects-reduced-motion | issues | high | The reduced-motion probe confirms the media query is active but still finds three 1,000 ms document animations, including running animations. F002 medium: Animations remain active with reduced motion requested |
respect-user-preferencesrespects-contrast | pass | high | Forced-colors probe confirmed active system colors, preserving visible yellow links and white controls on black with system border colors. |
implement-natural-interactionsview-transitions | issues | high | The platform probe reports no View Transition support usage while the site exposes hundreds of navigational links and interactive menu/search states. F003 low: Route and state changes do not use View Transitions |
implement-natural-interactionsscroll-driven-animations | pass | high | Platform/CSS inspection found no scroll-linked decorative animation or custom scroll handler behavior to replace; scrolling remains native. |
implement-natural-interactionsphysical-gestures | pass | high | Representative feed and article interactions use native links and scrolling; no custom pointermove/swipe gesture that fights platform behavior was observed. |
provide-guided-navigationscroll-state-aware-chrome | pass | high | Screenshots and DOM show persistent section-labelled header/navigation while the page provides native scroll position and a clear article context. |
provide-guided-navigationanchored-positioning | not-applicable | high | No tooltip, popover or edge-positioned anchored overlay was present in the representative public news paths. |
provide-guided-navigationdirects-attention | pass | high | Article navigation lands on a prominent H1 and visible section label; keyboard focus receives a visible UA/custom outline on primary links. |
maximize-content-reduce-noiseno-intrusive-interruptions | issues | high | Desktop screenshots of the homepage, article, latest-news and videos templates show a large fixed consent prompt covering the lower content, with only a prominent “Prosseguir” action. F004 high: Consent prompt obscures primary content on every entry template |
maximize-content-reduce-noisesemantic-dismissible-primitives | issues | high | The DOM/platform probe finds 0 dialog, 0 popover and 0 details elements despite rendered consent, menu, account and search overlay controls. F005 medium: Overlay UI is not built from semantic top-layer primitives |
maximize-content-reduce-noisereduced-chrome | issues | high | Homepage and listing screenshots devote most of the initial viewport to an empty/ad slot plus the consent panel, leaving little editorial content visible. F006 medium: Advertising and consent chrome dominate the first viewport |
adapt-to-the-form-factorresponsive-no-horizontal-scroll | issues | high | At 360x800, the article layout primitive reports scrollWidth 994, clientWidth 360 and horizontalOverflowPx 634; the probe identifies the off-canvas account drawer and quote carousel extending to 1,988 px. F007 high: Article template overflows by 634 CSS pixels on mobile |
adapt-to-the-form-factorcomponent-level-responsiveness | issues | high | The platform probe finds zero container-query rules; the article quote carousel and drawer overflow while reused global components depend on viewport layout. F008 medium: Reused components do not use component-level responsive rules |
adapt-to-the-form-factorinput-modality-aware | issues | high | The focus/target probe measures the Menu button at 12x2 CSS px and finds several later controls with outline none; some could not receive focus when programmatically focused. F009 medium: Some focusable controls have tiny targets or no visible focus |
support-core-task-successclear-purpose-and-primary-action | pass | high | First-viewport screenshots clearly identify g1 as a news portal; lead headlines and article H1 expose the next reading action. |
support-core-task-successprimary-flow-completion | pass | high | The lead homepage link opened a complete 200-status article with headline, dek, byline, date and body imagery without an account wall. |
support-core-task-successclear-system-state-and-recovery | pass | high | Despite failed recommendation/ad requests recorded in HAR/console, core homepage and article content rendered and remained navigable. |
be-fast-and-stablegood-core-web-vitals | issues | high | Lighthouse reports performance 0.38, LCP 6.4 s, TBT 1,020 ms and TTI 52.6 s; the independent trace reports LCP 5.89 s and TBT 984 ms. F010 high: Homepage load is slow and interaction readiness is poor |
be-fast-and-stablevisual-stability | issues | high | Lighthouse reports CLS 0.106 and identifies CLS culprits; 8 of 10 homepage images and 18 of 20 article images lack explicit dimensions. F011 medium: Load-time layout shift is just outside the good range |
be-fast-and-stableefficient-main-thread | issues | high | The trace records 7 long tasks, a 574 ms longest task and 984 ms total blocking; Lighthouse attributes 8.7 s of main-thread work and 4.8 s script bootup. F012 high: Heavy scripts block the main thread |
be-fast-and-stableefficient-resource-delivery | issues | high | The HAR records 250 requests and 6.21 MB transferred, including parser-inserted critical CSS, many scripts and multiple redirects; 244 requests and 6.06 MB are classified off the main origin. F013 high: Critical delivery is overwhelmed by a large dependency graph |
be-fast-and-stabletrim-unused-and-duplicate-code | issues | high | Lighthouse estimates 2,637 KiB unused JavaScript; the 1.2 MB player bundle alone has about 1.04 MB unused on the homepage. F014 high: Several megabytes of JavaScript are unused during load |
be-inclusivenames-roles-labels | issues | high | Lighthouse accessibility finds unnamed image links and visible-label/accessible-name mismatches for network brand links. F015 medium: Some links have no discernible name or mismatched accessible names |
be-inclusivesufficient-contrast | pass | high | Lighthouse color-contrast audit passed and forced-colors inspection preserved system text/control colors. |
be-inclusivestructure-and-focus | issues | high | The homepage platform probe finds an empty H1; Lighthouse finds malformed list content, and the focus probe finds visible controls that reject focus or suppress outlines. F016 medium: Heading and focus semantics contain gaps |
be-inclusivelegible-text | pass | high | Desktop/mobile article screenshots show a readable headline, comfortable line length, clear dek/byline hierarchy and no text clipping in the primary column. |
be-inclusivezoom-reflow-targets-and-media | issues | high | The article has 634 px horizontal overflow at 360 px and the Menu target is measured at 12x2 px, preventing reliable reflow and touch operation. F017 high: Mobile reflow and target sizing are not consistently usable |
follow-best-practicesno-console-errors | issues | high | Lighthouse records Bastian Failed to fetch errors, CORS failures and advertising API errors in the console. F018 medium: The homepage emits runtime and network errors |
follow-best-practicessound-document-and-assets | issues | high | The image primitive finds dimensions missing on 8/10 homepage and 18/20 article images; it also reports 10/10 homepage image elements without alt, including linked editorial thumbnails. F019 medium: Image markup omits intrinsic dimensions and often usable alternatives |
follow-best-practicesbrowser-platform-hygiene | issues | high | Lighthouse reports two deprecated API warnings, inspector issues and an unload handler in a subframe that prevents BFCache restoration. F020 medium: Deprecated APIs and platform lifecycle blockers remain |
be-discoverabletitle-and-description | pass | high | DOM probes found descriptive, template-specific title and meta description on homepage and article. |
be-discoverablecrawlable-and-mobile-friendly | issues | high | Lighthouse identifies three footer/menu anchors using href="javascript:void(0)" and several unnamed links, despite most content links being real URLs. F021 low: Some navigation links are not crawlable |
be-discoverablecanonical-and-indexing-signals | pass | high | All four paths returned 200; homepage/article expose canonical URLs, robots.txt allows public content and advertises three sitemap indexes. |
be-discoverablestructured-and-shareable-metadata | pass | high | Article probe found Organization/article JSON-LD plus matching og:type, title, description, image and URL metadata. |
be-private-and-securesecure-transport-and-headers | issues | high | Headers show HTTPS and nosniff but no HSTS; CSP is only upgrade-insecure-requests. The cookie audit finds numerous analytics identifiers without Secure and widespread SameSite=None. F022 high: Transport policy and cookie hardening are incomplete |
be-private-and-securedata-minimisation-and-third-parties | issues | high | The tracker primitive observes 85 third-party origins and 25 known tracker hosts; the HAR attributes 244/250 requests and 6.06/6.21 MB to origins outside g1.globo.com. F023 high: The page activates an exceptionally broad tracking footprint |
be-private-and-securein-context-permissions-and-modern-auth | pass | high | No browser permission prompt fired on page load; public news reading requires no authentication. The account surface is separate and was not exercised. |
be-private-and-securedefensive-browser-policies | issues | high | The headers primitive finds no HSTS, frame-ancestors/X-Frame-Options, Referrer-Policy or Permissions-Policy; the CSP has no source restrictions. F024 high: Several browser-enforced defenses are absent |
be-resilientprogressive-enhancement | pass | high | Discoverability comparisons show 86-95% raw-HTML content coverage on home/article/latest and 66% on videos; none is a JS shell and titles/H1/meta survive. |
be-resilientresilient-runtime-behaviour | pass | high | Core content survived multiple failed third-party requests; native article and listing navigation remained usable in rendered and crawler views. |
be-resilientoffline-and-installable | not-applicable | high | This is a content/news MPA rather than an installed application; offline installability is contextual. |
be-resilientnetwork-and-http-failure-states | pass | high | HAR captured failed recommendation/ad requests while core headlines and article content still rendered, demonstrating graceful isolation of non-core failures. |
be-internationalisedlang-dir-and-logical-properties | pass | high | DOM reports html lang="pt-br" and visible Portuguese content/read order is correct under the left-to-right locale. |
be-internationalisedlocale-aware-data | not-applicable | high | The audited publication is deliberately pt-BR and exposes no locale switcher or multi-locale transactional data in scope. |
be-internationalisedtime-zone-correctness | not-applicable | high | No scheduling, recurring-event or user-entered time-zone flow exists in the representative news paths. |
be-trustworthyno-dark-patterns | issues | high | Across templates the consent panel explains personalization and advertising but exposes only the primary “Prosseguir” button; trackers and cookies are already present in fresh sessions. F025 high: Consent presents continuation without an equivalent refusal choice |
be-trustworthyhumane-error-handling | not-applicable | high | The representative public paths contain only a simple search field and no required-data form submission flow to exercise. |
be-trustworthytrustworthy-input-assistance | issues | high | The article metadata/form probe finds the named, labelled search field with autocomplete="off". F026 low: Search input disables browser autocomplete |
be-trustworthysafe-commercial-and-account-flows | not-applicable | high | Checkout, subscription and authenticated account management are separate properties and were outside this public g1 content scope. |
be-sustainableoptimised-assets | issues | high | Homepage inspection finds 6 legacy-format images and only 1 modern-format image; article inspection finds 7 legacy and 0 modern, with 14 images lacking srcset. F027 medium: Image delivery still relies heavily on legacy formats and incomplete responsive markup |
be-sustainableno-wasteful-work | issues | high | The homepage issues 250 requests, loads an offscreen 1.2 MB player and about 800 KB Permutive script, and executes 83 scripts before any video interaction. F028 high: Large background advertising and measurement work runs on initial load |
be-sustainablethird-party-and-media-budget | issues | high | HAR evidence attributes 6.06 MB of 6.21 MB and 244 of 250 requests to non-main origins, disproportionate for a text-led news homepage. F029 high: Third-party code consumes nearly the entire page budget |
be-agent-readystructured-agent-capabilities | not-applicable | high | No declared agent-facing transactional capability exists; emerging WebMCP exposure is optional for this publisher. |
be-agent-readyon-device-inference | not-applicable | high | No user task in the audited paths requires on-device inference; absence is an opportunity, not a failure. |
be-memory-efficientno-leak-under-repeated-interaction | pass | high | Heap comparison after ten full-page scroll cycles decreased from 1,523,846 to 1,511,600 nodes and from 91.57 MB to 90.49 MB, showing no retained growth for the tested interaction. |
be-memory-efficientbounded-footprint | issues | high | The baseline heap summary reports 1,523,846 heap nodes and 91.6 MB self size before meaningful interaction. Repeated scrolling did not increase it, but the starting footprint is high. F030 medium: Initial memory footprint is disproportionate for a news homepage |
be-memory-efficientno-detached-dom-or-unbounded-listeners | pass | medium | The repeated-scroll heap stayed bounded and shrank overall; summaries exposed no growing Detached* constructor population. Confidence is limited because raw snapshots were not manually parsed. |
Provenance
Canonical report: results/atomic/reports/0827-g1_globo_com.json
Report SHA-256: 1ab6ccda99b53d0aa729621d545fb1dfbd91ea6f925aa93b5df1e38389a1940a
Local retained report: runs/2026-07-17T17-27-24-856Z/atomic-reports/g1_globo_com/2026-07-23T06-50-31-377Z/report.json
Local evidence root: runs/2026-07-17T17-27-24-856Z/atomic-reports/g1_globo_com/2026-07-23T06-50-31-377Z
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.