# BeaverCheck Audit Report — https://uol.com.br

**Date:** May 25, 2026  
**URL:** https://uol.com.br  
**Overall Grade:** C (77/100)  
**Report:** https://beavercheck.com/results/ab804150-edef-4670-9780-3f5bb3db11d8

## Top Findings

1. **[CRITICAL]** Content-Security-Policy header is missing — Security > Security Headers
2. **[CRITICAL]** HSTS header is missing — Security > Security Headers
3. **[CRITICAL]** No Content-Security-Policy header found — Security > Content Security Policy
4. **[CRITICAL]** Page weighs 12.9 MB (3.9 MB transferred) — Performance > Page Weight Budget
5. **[CRITICAL]** 3 button(s) with no accessible text — Accessibility > Link & Button Quality

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 28 |
| Accessibility | 76 |
| Best Practices | 77 |
| SEO | 92 |

---

## Security

### Security Headers (F — 10/100)

*2 of 10 headers properly configured*

- **[CRITICAL]** HSTS header is missing — Strict-Transport-Security forces browsers to use HTTPS, preventing downgrade attacks. Add the header with a max-age of at least 1 year.
- **[WARNING]** X-Content-Type-Options header is missing — This header prevents MIME-type sniffing, which can lead to XSS attacks. Set it to 'nosniff'.
- **[WARNING]** X-Frame-Options header is missing — This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN.
- **[WARNING]** Referrer-Policy header is missing — Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.
- **[WARNING]** Permissions-Policy header is missing — Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.
- **[CRITICAL]** Content-Security-Policy header is missing — CSP is the most important header for preventing XSS attacks. See the CSP section for detailed analysis.
- **[WARNING]** Cross-Origin-Opener-Policy header is missing — COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.
- **[WARNING]** Cross-Origin-Embedder-Policy header is missing — COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.
- **[PASS]** X-Powered-By header is not present
- **[PASS]** Server header is present without version info
- **[INFO]** Domain is not in the Chrome HSTS preload list (status: unknown) — Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

### Content Security Policy (F — 0/100)

*No enforcing CSP policy found*

- **[CRITICAL]** No Content-Security-Policy header found — CSP is the most effective defense against XSS attacks. Add a Content-Security-Policy header to restrict resource loading.

### TLS & Certificates (A+ — 100/100)

*TLS 1.2, 7 checks passed*

- **[PASS]** TLS 1.2 is used
- **[INFO]** TLS 1.3 is not negotiated — TLS 1.3 offers improved performance and security. Consider enabling it.
- **[PASS]** Strong cipher suite is used
- **[INFO]** HTTP/2 is not negotiated — HTTP/2 provides multiplexing and header compression for better performance.
- **[INFO]** OCSP stapling not enabled — Without stapling, the browser performs a separate OCSP roundtrip on first connection -- adding latency and leaking the visited host to the CA. Enable OCSP stapling on your TLS server.
- **[PASS]** Certificate is valid (expires in 288 days)
- **[PASS]** Certificate chain has 2 certificates
- **[PASS]** Certificate uses modern signature algorithm
- **[PASS]** Certificate covers 2 domain(s)
- **[PASS]** Certificate is issued by a trusted CA

### Cookie Security (A+ — 100/100)

*No cookies set — no cookie security risks*

- **[PASS]** No cookies set — no cookie security risks

### Cookie Hygiene (A+ — 100/100)

*No cookies set -- cookie-hygiene check is N/A*

- **[PASS]** No cookies set

### WAF / Bot Protection (A — 90/100)

*F5 BIG-IP*

- **[PASS]** F5 BIG-IP detected — Detected via: server: BigIP

### security.txt (C — 60/100)

*No security.txt file found*

- **[INFO]** No security.txt file found — security.txt (RFC 9116) provides a standardized way for security researchers to report vulnerabilities. Create one at /.well-known/security.txt with at least a Contact field.

### Cross-Origin Tab Safety (D — 60/100)

*14 of 17 new-tab link(s) missing rel=noopener*

- **[WARNING]** 14 link(s) open in a new tab without rel=noopener — Without rel="noopener", the destination tab can navigate the original tab via window.opener -- a reverse-tabnabbing phishing primitive. Modern browsers default to noopener since Chrome 88 / Firefox 79 / Safari 12.1, but explicit rel="noopener noreferrer" remains the documented best practice for older browsers, in-app webviews, and security scanners.

### CSP Inline-Style Readiness (D — 60/100)

*140 inline style attribute(s) detected*

- **[WARNING]** 140 inline style attribute(s) detected — Each `style=""` attribute forces `style-src 'unsafe-inline'` in any Content-Security-Policy, which negates most of CSP's XSS-mitigation value. 140 inline style(s) is high. Affected element types include: div, span, ul, li, section. Move styles to a stylesheet; use CSS custom properties for runtime-dynamic values; or adopt a nonce/hash CSP policy. Most teams take the stylesheet path because it's also a maintainability win.

### Trusted Types (XSS Sink Hardening) (A+ — 100/100)

*No CSP header -- Trusted Types check is N/A*

- **[PASS]** No CSP header found -- Trusted Types check is N/A

### Bot Challenge Detection (A+ — 100/100)

*Scan reached real page content (no bot-protection interstitial)*

- **[PASS]** No bot-protection interstitial detected -- the rest of the report reflects the real page

### Soft-404 Detection (A+ — 100/100)

*HTTP status is non-2xx -- soft-404 check is N/A*

- **[PASS]** HTTP status is non-2xx -- soft-404 check is N/A

### Empty Page Detection (A+ — 100/100)

*Page has substantive body text and no placeholder / template-leak signals*

- **[PASS]** Page has substantive body text and no placeholder / template-leak signals

### Geo-Restriction Detection (A+ — 100/100)

*No geo-restriction signals detected -- scan reached the page from an allowed region*

- **[PASS]** No geo-restriction detected

### Maintenance Mode Detection (A+ — 100/100)

*No maintenance-mode signals detected -- scan reached a normal page*

- **[PASS]** No maintenance-mode signals detected

### Subresource Integrity Adoption (F — 30/100)

*0% SRI adoption (0/53 third-party resources)*

- **[WARNING]** SRI adoption: 0/53 third-party resources protected (0%) — Of 53 third-party `<script>` / `<link rel=stylesheet>` resources, 0 (0%) declare a Subresource Integrity hash via the `integrity=` attribute. SRI binds the page to the exact bytes of the third-party resource: if the CDN is compromised, attacker-modified bytes won't match the declared hash and the browser refuses to execute the resource.

Missing SRI on (first 5 examples):
  - https://fonts.googleapis.com/css?family=Archivo:400,500|Arimo:400,500|Bitter:400,500|EB+Garamond:400,500|Lato|Libre+Baskervill|Libre+Franklin:400,500|Lora:400,500|Google+Sans:regular,medium:400,500|Material+Icons|Google+Symbols|Merriweather|Montserrat:400,500|Mukta:400,500|Muli:400,500|Nunito:400,500|Open+Sans:400,500,600|Open+Sans+Condensed:400,600|Oswald:500|Playfair+Display:400,500|Poppins:400,500|Raleway:400,500|Roboto:400,500|Roboto+Condensed:400,500|Roboto+Slab:400,500|Slabo+27px|Source+Sans+Pro|Ubuntu:400,500|Volkhov&display=swap
  - https://www.google-analytics.com/analytics.js
  - https://s0.2mdn.net/instream/video/client.js
  - https://cdn.cxense.com/cx.js
  - https://launchpad.privacymanager.io/latest/launchpad.bundle.js

Fix: add `integrity="sha384-..."` and `crossorigin="anonymous"` attributes. Generators: srihash.org, or in-browser via `await crypto.subtle.digest('SHA-384', bytes)`. Cache-bust the resource URL when you change versions, since the integrity hash will mismatch with old cached bytes.

### CORS Depth (A+ — 100/100)

*No CORS response headers -- the resource is same-origin-only by browser default*

- **[PASS]** No CORS response headers -- the resource is same-origin-only by browser default

### Permissions-Policy Granularity (C — 60/100)

*No Permissions-Policy header set -- powerful features (camera / microphone / geolocation / payment / USB) default to allow-on-same-origin*

- **[WARNING]** Permissions-Policy header not set -- features default to allow-on-same-origin — Without a `Permissions-Policy` (or legacy `Feature-Policy`) header, every powerful browser feature defaults to its spec default policy (typically `self`). A third-party iframe injected via XSS or a misconfigured embed can still request access to the user's camera, microphone, geolocation, payment APIs, USB devices, etc. Explicitly deny features the page doesn't need:

```
Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=(), accelerometer=(), gyroscope=()
```

Features the page legitimately uses can stay enabled with `feature=(self)`.

### Referrer-Policy Strictness (B — 75/100)

*Referrer-Policy header not set -- browser default applies (modern: strict-origin-when-cross-origin; legacy browsers: no-referrer-when-downgrade)*

- **[INFO]** Referrer-Policy header not set -- browser default applies — Without an explicit `Referrer-Policy` header, the browser falls back to its default policy. Modern browsers (Chrome 85+, Firefox 87+, Safari 15+) default to `strict-origin-when-cross-origin`, which is privacy-safe. Legacy browsers default to the leaky `no-referrer-when-downgrade`, which sends the full URL (including path + query) on cross-origin HTTPS-to-HTTPS requests. Set an explicit header to ensure consistent behavior:

```
Referrer-Policy: strict-origin-when-cross-origin
```

This matches the modern browser default and is privacy-safe without breaking referrer-based same-origin analytics.

### Source Map Exposure (A+ — 100/100)

*Source-map probe didn't run on this scan*

- **[PASS]** Source-map probe didn't run on this scan

### HTML Version Disclosure (A+ — 100/100)

*No software-version disclosures in HTML*

- **[PASS]** No software-version disclosures in HTML

### Open Redirect Surface (A+ — 100/100)

*No redirect-shaped query parameters in DOM links*

- **[PASS]** No redirect-shaped query parameters in DOM links

### Auth Security (B — 80/100)

*3 auth-security finding(s) on the login page*

- **[PASS]** Login page detected — The page contains a `type=password` input and at least one identifier field (username / email). Auth-security findings below evaluate the page's hardening posture.
- **[WARNING]** Login form does not contain a recognizable CSRF token — Standard frameworks emit CSRF tokens as a hidden input named `_csrf`, `csrf_token`, `csrfmiddlewaretoken` (Django), `authenticity_token` (Rails), or `__RequestVerificationToken` (ASP.NET). None of those were found. Possibilities: (1) the form posts to an API that uses a custom header or SameSite cookie reliance for CSRF -- legitimate but not visible from this scan, (2) the form is genuinely missing CSRF protection, which would let an attacker submit logins from another origin via a hidden POST. Verify the auth flow has SOME CSRF defense.
- **[INFO]** No password-reset link found on the login page — Login pages should link to a password-reset flow (typically /forgot, /reset, or a 'Forgot password?' link). Absence usually means the reset flow lives elsewhere on the site (separately reachable), but if it's truly missing, users locked out of accounts have no self-service recovery path.

### Subdomain Inventory Exposure (A+ — 100/100)

*No risky subdomain names in certificate SANs*

- **[PASS]** No risky subdomain names in certificate SANs

---

## Advanced Security

### Subresource Integrity (F — 20/100)

*0 of 53 external resources have SRI*

- **[WARNING]** External link from fonts.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.google-analytics.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from s0.2mdn.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn.cxense.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from launchpad.privacymanager.io lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn.cxense.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.youtube.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from c.amazon-adsystem.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from me.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from me.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from sb.scorecardresearch.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from tm.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from tm.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from securepubads.g.doubleclick.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from tm.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from h.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from tm.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from fundingchoicesmessages.google.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from fundingchoicesmessages.google.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from securepubads.g.doubleclick.net lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from h.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from h.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from h.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from h.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from h.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from h.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from h.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from h.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from h.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from h.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from h.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from h.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from h.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from h.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from fundingchoicesmessages.google.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from fundingchoicesmessages.google.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.googletagmanager.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from static.chartbeat.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from conteudo.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from imasdk.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.youtube.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from mfe.fantascope.uol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from cdn.tinypass.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from static.chartbeat.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from launchpad-wrapper.privacymanager.io lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from tm.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from www.googletagmanager.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from s.cdn.turner.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External link from conteudo.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from 4b91477e-f67b-4d81-86db-a9742bd41e9c.edge.permutive.app lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from config.aps.amazon-adsystem.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from geoip.home.uol.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.
- **[WARNING]** External script from tm.jsuol.com.br lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.

### JS Library Vulnerabilities (A+ — 100/100)

*No known vulnerabilities*

- **[PASS]** No known JavaScript library vulnerabilities detected

### Information Leakage (A+ — 100/100)

*No exposures*

- **[INFO]** No security.txt found — Consider adding a security.txt at /.well-known/security.txt.
- **[PASS]** No sensitive files exposed

### Email Security (C — 60/100)

*DMARC: none, SPF: -all, DKIM*

- **[WARNING]** DMARC policy is none — monitoring only — This only monitors, it doesn't block spoofed emails. Change to p=quarantine or p=reject after monitoring DMARC reports.
- **[PASS]** SPF ends in -all (hard fail) — strongest setting
- **[PASS]** DKIM configured (selectors: s1, s2)
- **[INFO]** MTA-STS not configured — MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.
- **[INFO]** TLS-RPT not configured — TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.
- **[INFO]** BIMI not configured — BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

### API Surface (A+ — 100/100)

*No API specs or GraphQL introspection found (probed 11 candidate path(s))*

- **[PASS]** No API specs or GraphQL introspection found (probed 11 path(s))

### Permissions-Policy (D — 40/100)

*No header set*

- **[WARNING]** No Permissions-Policy header — Consider adding a Permissions-Policy header to restrict browser feature access from embedded content.

### CORS Configuration (B — 80/100)

*No CORS headers*

- **[PASS]** No CORS headers present — secure default

---

## Performance

### Page Weight Budget (F — 0/100)

*3.9 MB transferred, 229 requests*

- **[CRITICAL]** Page weighs 12.9 MB (3.9 MB transferred)
- **[WARNING]** JavaScript is 2.4 MB — consider code splitting or lazy loading — Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts.
- **[WARNING]** 229 HTTP requests — consider bundling or reducing — Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests.
- **[INFO]** Estimated 0.82 g CO2 per page load

### Third-Party Impact (D — 50/100)

*100% third-party, 0 ms blocking*

- **[WARNING]** Third-party code accounts for 100% of page weight (3.9 MiB of 3.9 MiB)
- **[PASS]** Third-party blocking time is low (0 ms)

### Text Compression (A+ — 100/100)

*All text resources are compressed*

- **[PASS]** All text resources are compressed

### Image Optimization (C — 65/100)

*82 images, 0 KB saveable*

- **[WARNING]** https://conteudo.imguol.com.br/c/home/layout/vuela... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]**  is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.

### JS Execution Cost (F — 20/100)

*10115ms total JS execution*

- **[WARNING]** https://www.uol.com.br/: 2611ms CPU time
- **[WARNING]** Unattributable: 1289ms CPU time
- **[WARNING]** https://h.jsuol.com.br/assets/?loadComponent=Media...: 1176ms CPU time
- **[WARNING]** https://securepubads.g.doubleclick.net/pagead/mana...: 875ms CPU time
- **[WARNING]** https://4b91477e-f67b-4d81-86db-a9742bd41e9c.edge....: 858ms CPU time
- **[WARNING]** Third-party scripts: 8826ms (87% of total)

### Font Loading (A+ — 100/100)

*7 fonts (153 KB)*

- **[INFO]** 7 font(s) use font-display: swap (FOUT risk but functional)

### JS Bundles (F — 20/100)

*55 scripts, 563 KB unused*

- **[WARNING]** https://securepubads.g.doubleclick.net/pagead/mana...: 129 KB unused (68%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://imasdk.googleapis.com/js/sdkloader/ima3.js: 102 KB unused (68%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://tm.jsuol.com.br/modules/external/Prebid.js: 72 KB unused (55%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://fundingchoicesmessages.google.com/i/8804?e...: 65 KB unused (94%) — Consider code splitting or tree shaking to reduce unused code.
- **[WARNING]** https://www.googletagmanager.com/gtag/js?id=G-BS4Q...: 64 KB unused (38%) — Consider code splitting or tree shaking to reduce unused code.
- **[INFO]** Total unused JavaScript: 563 KB

### Resource Caching (A+ — 100/100)

*All resources properly cached*

- **[PASS]** No caching issues found

### Critical Rendering Path (A+ — 100/100)

*No render-blocking resources*

- **[PASS]** No render-blocking resources detected

### Resource Hints (A — 90/100)

*22 hints, 0 missing preconnects*

- **[INFO]** 1 dns-prefetch redundant with preconnect on same origin — preconnect already does the DNS lookup; adding dns-prefetch to the same origin is at best a no-op. Sample: https://me.jsuol.com.br. Remove the redundant dns-prefetch entries.
- **[INFO]** 1 URL(s) appear in multiple hints — The same href shouldn't appear in multiple hint rels -- one wins, the others are wasted markup and may confuse cache behavior. Sample: https://me.jsuol.com.br (dns-prefetch+preconnect).
- **[PASS]** Page uses 22 resource hint(s)

### HTTP/3 (QUIC) (B — 75/100)

*HTTP/3 not advertised*

- **[INFO]** HTTP/3 (QUIC) is not advertised — HTTP/3 isn't advertised via Alt-Svc and the worker didn't negotiate h3. HTTP/3 reduces handshake latency (1-RTT instead of 2-3 RTTs) and is more resilient on lossy connections. Most modern CDNs (Cloudflare, Fastly, AWS CloudFront, Google Cloud CDN) support HTTP/3 with a single config switch -- consider enabling for mobile-heavy workloads.

### Compression Algorithm (C — 70/100)

*Main response served uncompressed*

- **[INFO]** Main HTML response has no Content-Encoding (uncompressed) — The main HTML document is served without compression. The Text Compression section above lists the broader picture; for the main response specifically, even gzip would shave ~70-80% off most text payloads.

### LCP Image Preload (A+ — 100/100)

*LCP preload audit not available*

- **[PASS]** LCP image preload audit not available for this scan

### Main HTML Cache-Control (A+ — 100/100)

*Main HTML max-age=60 (≤ 5min) is appropriate*

- **[PASS]** Main HTML max-age=60 (≤ 5min) is appropriate

### Server-Timing Observability (B — 85/100)

*No Server-Timing header found*

- **[INFO]** No Server-Timing header found — Server-Timing exposes backend timing breakdowns to browser DevTools (e.g., `db: 45ms; render: 120ms; cache: 2ms`). Useful for diagnosing slow pages without backend log access. Most modern frameworks (Next.js, Cloudflare Workers, Fastly) emit it automatically; absence on a managed platform usually means telemetry headers are stripped at the edge.

### Server Response Intelligence (A+ — 95/100)

*1 server-response signal(s) detected*

- **[INFO]** No `ETag` or `Last-Modified` -- conditional GET not supported — Without either header, browsers can't issue conditional GETs and refresh always re-downloads the full response body even when nothing changed. Add `ETag: "<hash>"` (or `Last-Modified: <date>`) on cacheable responses; the server returns 304 Not Modified when the client's cached copy is still valid, saving bandwidth.

### Page Weight Inventory (F — 35/100)

*229 resources · 3.9 MB · 563 KB savings available*

- **[WARNING]** Page weight 3.9 MB exceeds 1 MB target by 2.9 MB
- **[INFO]** ~563 KB of savings available
- **[WARNING]** 228 third-party resources (100% of weight)
- **[INFO]** 2 resources over 200KB

### Render-Blocking Resources (A+ — 100/100)

*No render-blocking resources detected*

- **[PASS]** No render-blocking resources detected in <head>

### Third-Party Resources (A+ — 100/100)

*No third-party resources detected*


### JavaScript Blocking (B — 84/100)

*2 JS blocking issue(s) detected*

- **[WARNING]** 1 render-blocking <script src> tag(s) without async/defer — Each `<script src=...>` without `async`, `defer`, or `type="module"` blocks HTML parsing while the browser fetches and executes it. The block lasts the entire round-trip + execution time -- on slow networks this translates directly into LCP delay. Add `defer` (executes after parse, in source order) for scripts that interact with the DOM, or `async` (executes whenever ready) for analytics / independent scripts. Module scripts (`type="module"`) are deferred by default.
- **[WARNING]** Total JS execution time is 10.1 s -- over the 3.5s budget — Total JavaScript execution (parse + compile + run) across all scripts exceeds 3.5 seconds. On low-end devices that becomes 7-15+ seconds and shows up directly in TBT and INP. Reduce by: tree-shaking unused dependencies, code-splitting (dynamic `import()`), removing or deferring third-party tracking, and replacing heavy frameworks where they're not needed.

### CSS Performance Depth (A — 90/100)

*1 CSS depth issue(s) detected*

- **[WARNING]** 2 `@font-face` rule(s) without `font-display` -- causes FOIT — An `@font-face` rule without `font-display` causes Flash of Invisible Text (FOIT): the browser hides the styled text for up to 3 seconds while the custom font downloads, then either swaps to fallback (Chrome / Firefox) or stays invisible (older Safari). Add `font-display: swap` (shows fallback immediately, swaps in the custom font when ready) or `font-display: optional` (uses fallback if the font isn't ready in 100ms; never causes visible swap). Either eliminates FOIT outright.

---

## Content Quality

### Links (F — 50/100)

*200 links checked, 190 healthy, 10 broken*

- **[CRITICAL]** 190 of 200 links are healthy
- **[WARNING]** Broken link: https://img.youtube.com — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://securepubads.g.doubleclick.net — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://tm.jsuol.com.br — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://www.gstatic.com — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://me.jsuol.com.br — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://h.jsuol.com.br — Found in <link href>. Returns HTTP 500.
- **[WARNING]** Broken link: https://c.jsuol.com.br — Found in <link href>. Returns HTTP 404.
- **[WARNING]** Broken link: https://conteudo.imguol.com.br — Found in <link href>. Returns HTTP 404.
- **[CRITICAL]** Broken link: https://clube.uol.com.br/?utm_source=home_organic_menu-fi... — Found in <a href>. Returns HTTP 410.
- **[CRITICAL]** Broken link: https://educacao.uol.com.br/ — Found in <a href>. Get "https://educacao.uol.com.br/": context deadline exceeded

### Mixed Content (A+ — 100/100)

*No mixed content detected — all resources use HTTPS.*

- **[PASS]** No mixed content detected — all resources use HTTPS

### Open Graph (A — 90/100)

*Open Graph tags are well configured for social sharing.*

- **[CRITICAL]** og:image is not reachable — The og:image URL could not be fetched. Social platforms won't be able to display it.

### Open Graph / Twitter Card Depth (C — 75/100)

*3 OG/Twitter depth issue(s) detected*

- **[INFO]** og:image aspect ratio 1.00:1 (500×500) is outside Facebook's recommended ~1.91:1 — Facebook's recommended OG image is 1200×630 (1.91:1 aspect ratio). The declared dimensions 500×500 give a ratio of 1.00:1, which Facebook will crop center-to-fit; the result often clips important content from the top/bottom or sides. Use a wider/taller image close to 1.91:1, or accept the cropping consequences.
- **[WARNING]** Twitter card is `summary_large_image` but OG image is 500×500 (ratio 1.00:1) -- closer to square — `twitter:card` is set to `summary_large_image` (the wide-image preview format), but the declared OG image dimensions (500×500, aspect ratio 1.00:1) are closer to square than wide. Twitter will crop the image to fit the wide format, often badly. Either: (1) provide a wider image (~2:1 ratio recommended; minimum 600×314, optimal 1200×630), or (2) change `twitter:card` to `summary` which uses a square thumbnail crop.
- **[INFO]** 2 Twitter Card field(s) differ from Open Graph counterparts — Twitter Cards inherit values from Open Graph tags when the Twitter-specific tag is absent (`twitter:title` falls back to `og:title`, etc.). Explicitly-set Twitter values that DIFFER from OG are usually stale -- the marketing team updates `og:title` for FB/LinkedIn previews and forgets to update `twitter:title` separately, leaving Twitter showing the old text. Mismatches:
  - title: twitter="UOL", og="UOL - Seu universo online"
  - description: twitter="Perfil oficial do UOL. Acompanhe em temp...", og="UOL, a maior empresa brasileira de conte..."

Fix: either remove the redundant Twitter-specific tags (rely on inheritance) or sync them when updating OG.

### Structured Data (A+ — 100/100)

*2 JSON-LD block(s) found — structured data is well configured.*

- **[INFO]** Missing recommended property "sameAs" for Organization — Adding "sameAs" can improve how search engines display your content.
- **[PASS]** 2 JSON-LD blocks found

### Rich Results Eligibility (A+ — 100/100)

*2 JSON-LD block(s) declaring 2 schema type(s)*

- **[PASS]** SiteLinks Search Box markup detected — The page declares a `WebSite` schema with a `potentialAction` of `SearchAction`. This makes the homepage eligible for Google's in-SERP search box -- a high-visibility SERP feature for branded queries.
- **[PASS]** 2 rich-result schema type(s) declared — Inventory of structured-data types on the page (each may unlock a different SERP feature):

Organization, WebSite

Search engines decide whether to render rich results based on content quality + page-level signals; declaring the schema is necessary but not sufficient.

### Image Optimization (F — 25/100)

*7 issues found across 200 images*

- **[WARNING]** 3 images significantly larger than display size — Resizing to display dimensions could save approximately 0 KB.
- **[WARNING]** 181 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
- **[INFO]** 25 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[INFO]** 9 of 200 images use legacy formats
- **[WARNING]** 2 images missing alt text — Alt text is essential for screen readers and SEO. Every meaningful image needs descriptive alt text.
- **[WARNING]** 1 above-fold image(s) marked loading="lazy" (LCP anti-pattern) — Above-fold images marked lazy delay LCP -- the browser waits for the IntersectionObserver to fire before fetching, even though the image is in the initial viewport. Remove `loading="lazy"` on above-the-fold images (especially the LCP candidate). Sample: https://conteudo.imguol.com.br/c/home/layout/vueland/icons/publicidade/selo-pagbank-horizontal-rende.png.
- **[INFO]** 4 image(s) rendered at a different aspect ratio than the source — The displayed dimensions distort the source -- CSS is forcing the image into a container at the wrong ratio, producing visible stretching or squashing. Either crop the source to match or use object-fit: cover (and accept the crop). Sample: https://imguol.com/c/noticias/99/2026/05/21/offer-animes-desktop-1779389658409_v2_225x315.png, https://imguol.com.br/c/flash/home-uol/gif-animated/canalUOLTV-1.gif, https://conteudo.imguol.com.br/c/entretenimento/flash/85/2026/05/06/5-livros-brasileiros-contemporaneos-para-voce-colocar-na-estante-agora-1778102051873_v2_225x315.jpg (+1 more).

### Autoplay Media (A+ — 100/100)

*2 media element(s) found, none autoplay*

- **[PASS]** 2 media element(s) found, none autoplay

---

## Infrastructure

### DNS Records (A+ — 95/100)

*1 A records, 185 ms lookup*

- **[PASS]** Resolves to 1 IPv4 address(es)
- **[INFO]** Single A record — no DNS redundancy — Multiple A records provide failover if one server goes down.
- **[PASS]** Has 1 IPv6 (AAAA) record(s)
- **[PASS]** 3 nameserver(s) configured
- **[PASS]** 1 mail exchanger(s) configured
- **[PASS]** SPF record present in TXT
- **[PASS]** DNS resolution time: 185 ms

### Subdomain Takeover (A+ — 100/100)

*No subdomain takeover risk detected*

- **[PASS]** No CNAME record present

### DNSSEC (B — 80/100)

*Unsigned (DNSSEC not deployed)*

- **[INFO]** DNSSEC is not deployed — The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).

### CAA Records (B — 80/100)

*No CAA records (any CA may issue certificates)*

- **[INFO]** No CAA records published — Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.

### Reverse DNS (B — 75/100)

*0/2 IPs match cert SAN*

- **[INFO]** PTR for 200.147.35.149 does not match any cert SAN: 200-147-35-149-149.static.uol.com.br — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
- **[INFO]** PTR lookup failed for 2804:49c:3102:401:ffff:ffff:ffff:36: lookup 2804:49c:3102:401:ffff:ffff:ffff:36: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

### Multi-Resolver DNS Speed (A+ — 100/100)

*Mean 15ms across 3 resolvers (spread 26ms)*

- **[PASS]** Quad9: 1ms
- **[PASS]** Cloudflare: 17ms
- **[PASS]** Google: 27ms

### Redirect Chain (A — 90/100)

*1 redirect(s), 983 ms total*

- **[PASS]** Single redirect
- **[INFO]** WWW normalization redirect
- **[INFO]** Redirect overhead: 983 ms total

### IPv6 Readiness (A+ — 100/100)

*IPv6 reachable (227 ms)*

- **[PASS]** IPv6 is configured and reachable at 2804:49c:3102:401:ffff:ffff:ffff:36

### Crawlability (A+ — 100/100)

*robots.txt present, sitemap with 4 URLs*

- **[PASS]** robots.txt is present
- **[PASS]** sitemap.xml is present
- **[PASS]** sitemap.xml is valid XML
- **[PASS]** sitemap.xml contains 4 entries
- **[PASS]** robots.txt references sitemap

### URL Variants (B — 75/100)

*www/non-www, trailing slash, HTTP→HTTPS*

- **[CRITICAL]** Both www and non-www versions serve content
- **[PASS]** HTTP correctly 301-redirects to HTTPS

### Domain Intelligence (A+ — 100/100)

*uol.com.br — 30 years, 6 months old*

- **[PASS]** Domain registered until Apr 24, 2034 (8 years remaining)
- **[INFO]** DNSSEC is not enabled — DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
- **[WARNING]** Registrar lock is NOT enabled — The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

---

## Compliance

### WCAG Compliance (A+ — 100/100)

*No testable criteria*


### Cookie Consent & Privacy (A+ — 100/100)

*privacy policy found*

- **[PASS]** Privacy policy link found
- **[PASS]** Terms of service link found
- **[INFO]** No cookie consent banner detected
- **[INFO]** This is an automated check, not legal advice — BeaverCheck detects technical indicators of consent management. This does not constitute a legal compliance assessment. Consult a privacy professional for GDPR/CCPA compliance.

### Consent UX Depth (A+ — 100/100)

*No consent-UX depth issues detected*

- **[PASS]** No consent-UX depth issues detected

### Tracker Inventory (A+ — 100/100)

*1 known tracker(s) detected*

- **[PASS]** 1 known tracker(s) detected — Inventory of trackers loaded by the page (matched against a curated SDK URL registry):

analytics: Google Analytics (UA)

Each entry maps a script URL pattern to a known vendor SDK. This is purely informational -- consent posture / pre-consent firing is graded by the consent analyzer.

### Language & i18n (A — 90/100)

*Lang attribute present*

- **[PASS]** <html lang> attribute is present
- **[PASS]** <html lang> value is valid
- **[INFO]** No Content-Language HTTP header
- **[INFO]** Language signals are inconsistent — The <html lang> attribute and Content-Language header should agree.

### Hreflang Configuration (A+ — 100/100)

*No hreflang tags on this page*

- **[PASS]** No hreflang tags found (single-language site)

### Internationalization Extras (A+ — 100/100)

*No additional i18n signals detected*

- **[PASS]** No additional i18n signals detected

### Readability & Typography (A+ — 100/100)

*Font sizes and tap targets checked*


### Viewport Configuration (B — 80/100)

*Viewport properly configured*

- **[PASS]** Viewport meta tag is present
- **[WARNING]** width=device-width is not set
- **[PASS]** User zooming is allowed

### Accessibility Statement (B — 70/100)

*No accessibility statement detected*

- **[WARNING]** No accessibility statement detected — Sites are increasingly expected to publish an accessibility statement. Required by EU Web Accessibility Directive 2016/2102 for public-sector bodies; recommended best practice elsewhere. Common URLs: /accessibility, /accessibility-statement, /a11y.

### GDPR Article 13 Disclosures (F — 12/100)

*1 / 8 Art. 13 categories matched in homepage body*

- **[WARNING]** GDPR Article 13 disclosure coverage: 1 / 8 categories — Scanned the homepage body text AND the linked /privacy page for GDPR Article 13 disclosures. Matched 1 of 8 categories: Legal basis for processing. Missing: Data Protection Officer contact (where applicable), Data retention period, Data subject rights (access, erasure, rectification, etc.), Identity / contact details of the data controller, International data transfers, Recipients of personal data, Right to lodge a complaint with a supervisory authority. Note: only the FIRST same-origin privacy-policy link is followed; deeper sub-pages (e.g. /legal/data-subject-rights) are not fetched.

### Third-Party Trackers (B — 80/100)

*14 trackers detected*

- **[INFO]** 14 third-party trackers detected — Found 5 analytics, 7 advertising, 0 marketing, 1 tag manager, 0 session-replay, 0 heatmap trackers.
- **[WARNING]** 7 advertising/retargeting trackers detected — Advertising trackers collect user data for ad targeting. Under GDPR, these typically require explicit consent.

### Cookie & Tracker Inventory (A+ — 100/100)

*0 cookies · 14 trackers · 0 pre-consent*

- **[INFO]** 14 third-party tracker(s) detected on page

### Tracking Pixel Inventory (B — 90/100)

*2 tracking pixel(s) on the page*

- **[INFO]** 2 tracking pixel(s) on the page (2 domain(s)) — Tracking pixels are 1x1 / 2x2 cross-origin <img> tags that fire a GET request when the browser renders them -- no JavaScript, no cookies needed. They're how trackers survive when users disable JS or block third-party cookies, and they bypass most ad-blocker rules that target script src. Each one needs explicit disclosure under GDPR Art 7 / CCPA / ePrivacy because the request itself transmits the page URL + IP + user-agent + referrer to the tracker. Audit each surfaced domain: is it disclosed in your privacy policy? Is it conditional on the cookie banner? Affected domains: me.jsuol.com, rtl-home.stc.uol.com.

### Browser Fingerprinting (A+ — 100/100)

*No browser-fingerprinting libraries detected*

- **[PASS]** No browser-fingerprinting libraries detected

### Cross-Site Cookies (SameSite=None) (A+ — 100/100)

*No cookies on the page*

- **[PASS]** No cookies set on the page response

### Beacon Tracking (sendBeacon) (A+ — 100/100)

*No navigator.sendBeacon usage detected in inline scripts*

- **[PASS]** No navigator.sendBeacon usage detected in inline scripts

---

## Legal

### Legal Page Ecosystem (F — 0/100)

*0 of 7 expected legal pages detected*

- **[WARNING]** Privacy Policy not detected — No link matching common Privacy Policy URL patterns or link text was found. Most websites are expected to have a Privacy Policy, especially those collecting user data.
- **[WARNING]** Terms of Service not detected — No link matching common Terms of Service URL patterns or link text was found. Most websites are expected to have a Terms of Service, especially those collecting user data.
- **[INFO]** Cookie Policy not detected — No link matching common Cookie Policy URL patterns or link text was found. Most websites are expected to have a Cookie Policy, especially those collecting user data.
- **[INFO]** Accessibility Statement not detected — No link matching common Accessibility Statement URL patterns or link text was found. Most websites are expected to have a Accessibility Statement, especially those collecting user data.
- **[INFO]** DMCA / Copyright Notice not detected — No link matching common DMCA / Copyright Notice URL patterns or link text was found. Most websites are expected to have a DMCA / Copyright Notice, especially those collecting user data.
- **[INFO]** Refund / Returns Policy not detected — No link matching common Refund / Returns Policy URL patterns or link text was found. Most websites are expected to have a Refund / Returns Policy, especially those collecting user data.
- **[INFO]** Acceptable Use Policy not detected — No link matching common Acceptable Use Policy URL patterns or link text was found. Most websites are expected to have a Acceptable Use Policy, especially those collecting user data.

### Copyright Notice (C — 55/100)

*No copyright notice detected*

- **[INFO]** No copyright notice detected — No copyright notice detected in the page content. While not legally required in most jurisdictions (copyright exists automatically), a notice is standard practice and signals site ownership.

### Regulatory Indicators

*1 regulatory indicator(s) detected*

- **[INFO]** This is a technical scan, not a legal assessment — BeaverCheck detects technical indicators that may suggest regulatory relevance. This is not a compliance audit and should not be relied upon for legal decisions. Consult qualified legal counsel for compliance assessments.
- **[INFO]** HIPAA indicators detected (weak confidence) — Indicators suggesting HIPAA may be relevant: Text mentions: phi. Health Insurance Portability and Accountability Act — protects sensitive patient health information.

### Third-Party Data Sharing

*1 third-party service(s) detected*

- **[INFO]** Data inventory for transparency purposes — This inventory identifies third-party services that receive data from your site visitors. Under regulations like GDPR (Article 30), maintaining records of data processing activities is commonly considered a best practice. This automated scan provides a starting point — it may not capture all data flows.
- **[INFO]** 1 third-party services across 1 categories — 1 third-party services detected across 1 categories: Analytics (1). Each of these services receives some user data from your site visitors.
- **[INFO]** Google Analytics (Analytics) — Detected via script URL. Typically collects: Page views, User behavior, Demographics, Device info, IP address. Privacy policy: https://policies.google.com/privacy. Data Processing Agreement available.

### Compliance Badges (B — 70/100)

*1 compliance badge(s) detected*

- **[PASS]** Better Business Bureau badge detected — Found via body text: 'bbb'. Note: the presence of a badge does not verify the certification is current or valid.

---

## Availability

### CDN & Delivery (D — 50/100)

*No CDN detected*

- **[WARNING]** No CDN detected — A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.

### HTTP Caching (A — 90/100)

*max-age=60 (1 minute)*

- **[PASS]** Cache-Control header is set
- **[PASS]** Effective TTL: 1 minute (max-age=60)
- **[INFO]** No ETag or Last-Modified header — Conditional requests (304 Not Modified) are not possible without validators.

### Operational Status Page (B — 80/100)

*No status page link detected*

- **[INFO]** No operational status page link detected — Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.

### Transport Security (B — 75/100)

*HTTP/3, HSTS, and TLS version analysis*

- **[INFO]** HTTP/3 (QUIC) not advertised — HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.
- **[WARNING]** Missing Strict-Transport-Security header — HSTS tells browsers to only use HTTPS, preventing SSL stripping attacks.

### Health Check Endpoint (B — 80/100)

*No conventional health endpoint found*

- **[INFO]** No conventional health endpoint found — Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.

### CDN Cache Observability (B — 85/100)

*No CDN cache-status headers in the response*

- **[INFO]** No CDN cache-status headers in the response — Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.

---

## Accessibility

### Landmark Structure (C — 60/100)

*44 landmarks*

- **[CRITICAL]** No <main> landmark found — Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
- **[PASS]** 2 <nav> landmark(s) found
- **[PASS]** All <nav> elements are properly labeled
- **[WARNING]** Skip navigation link is missing (WCAG 2.4.1) — Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

### Heading Hierarchy (C — 55/100)

*390 headings, 1 skip(s)*

- **[WARNING]** Multiple H1 headings (5 found) — A page should have only one H1. Multiple H1s dilute the document outline.
- **[WARNING]** Heading level skipped: H1 → H3 (missing H2) — Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
- **[WARNING]** 4 empty heading(s) — Empty headings appear in the document outline but provide no information.

### Heading Text Quality (A — 85/100)

*2 heading-text-quality issue(s) detected*

- **[INFO]** 1 heading(s) are too short (≤2 characters) to convey meaning — Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected:
  - H2: "+"
- **[INFO]** 14 heading(s) are all-uppercase (excluding short acronyms) — Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

### Alt Text Quality (D — 40/100)

*3 of 208 images have issues*

- **[CRITICAL]** 3 image(s) missing alt attribute — Images without alt text are invisible to screen readers.
- **[CRITICAL]** 3 image-in-link without alt text — An image inside a link with no alt creates an empty link.
- **[PASS]** 205 image(s) with good alt text

### Form Accessibility (C — 55/100)

*3 of 287 controls have issues*

- **[CRITICAL]** 3 control(s) without accessible label — Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
- **[PASS]** 284 control(s) properly labeled

### Link & Button Quality (F — 18/100)

*148 issue(s) across 1213 links and 103 buttons*

- **[CRITICAL]** 3 link(s) with no accessible text — Links without text are announced as raw URLs by screen readers.
- **[WARNING]** 142 link(s) with generic text — Generic link text like 'click here' doesn't describe the destination.
- **[WARNING]** 18 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.
- **[CRITICAL]** 3 button(s) with no accessible text — Icon-only buttons need an aria-label so screen readers can announce them.
- **[PASS]** 1050 link(s) with descriptive text

### Form Input Types (A+ — 100/100)

*287 form control(s) checked, no type mismatches*

- **[PASS]** No input-type mismatches detected

### Form Input Quality (B — 82/100)

*2 input-semantic issue(s) across 287 form control(s)*

- **[INFO]** 1 password field(s) missing or with invalid `autocomplete` — Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="pass">.
- **[INFO]** 1 login form field(s) missing `autocomplete=username` (or `email`) — On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="email" name="user">.

### Mobile Keyboard & Autofill (A+ — 100/100)

*No autofill-eligible form controls*

- **[PASS]** No autofill-eligible form controls (no name/email/tel/address fields)

### Document Language (A+ — 100/100)

*Lang attribute set to "pt-br"*

- **[PASS]** <html lang="pt-br"> is set and valid

### Tabindex Anti-Patterns (C — 60/100)

*4 positive, 0 -1-on-focusable*

- **[WARNING]** Positive tabindex on <input id="input-email">: tabindex=2 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <input id="input-pass">: tabindex=3 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <a>: tabindex=4 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
- **[WARNING]** Positive tabindex on <input>: tabindex=5 — Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.

### Iframe Accessibility (D — 40/100)

*12/15 iframe(s) missing title; 0 placeholder(s)*

- **[WARNING]** <iframe> missing title attribute (src="about:blank") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
- **[WARNING]** <iframe> missing title attribute (src="https://tm.uol.com.br/mercurio.html") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
- **[WARNING]** <iframe> missing title attribute (src="") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
- **[WARNING]** <iframe> missing title attribute (src="about:blank") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
- **[WARNING]** <iframe> missing title attribute (src="about:blank") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
- **[WARNING]** <iframe> missing title attribute (src="about:blank") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
- **[WARNING]** <iframe> missing title attribute (src="https://cdn.permutive.app/topics.html") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
- **[WARNING]** <iframe> missing title attribute (src="") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
- **[WARNING]** <iframe> missing title attribute (src="https://tm.uol.com.br/purge-clients.html?name=DEretargeting&expname=DEretargeti…") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
- **[WARNING]** <iframe> missing title attribute (src="https://tm.uol.com.br/purge-clients.html?name=dynad_rt&expname=dynad_rt_exp&exp…") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
- **[WARNING]** <iframe> missing title attribute (src="https://acdn.adnxs.com/dmp/async_usersync.html") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
- **[WARNING]** <iframe> missing title attribute (src="https://eus.rubiconproject.com/usync.html") — WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

### Tap Target Adequacy (A+ — 100/100)

*All tap targets meet WCAG 2.5.5/2.5.8 sizing*

- **[PASS]** All tap targets meet WCAG 2.5.5 (44x44px) sizing

### Mobile-Readable Font Sizes (B — 90/100)

*95% of visible text renders at >= 12 CSS px (15 below threshold)*

- **[INFO]** 15 text node(s) render below 12 CSS pixels on mobile — Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <a> 10.0px ("ASSINE UOL"); <span> 10.0px ("outras loterias"); <span> 10.0px ("áries"); <span> 10.0px ("touro"); <span> 10.0px ("gêmeos").

---

## UX

### 404 Error Page (F — 35/100)

*HTTP 404, bare page*

- **[PASS]** Correct 404 status code returned
- **[WARNING]** Bare server default 404 page — The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

### Favicon & Branding (C — 65/100)

*9 icon(s) detected*

- **[WARNING]** No favicon.ico at site root — Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
- **[PASS]** HTML icon links detected
- **[PASS]** Apple touch icon present
- **[PASS]** Multiple icon sizes detected

### Web Manifest (A+ — 95/100)

*PWA-ready*

- **[PASS]** Meets PWA install criteria
- **[PASS]** Name present: UOL - O melhor conteúdo
- **[PASS]** 192x192 icon present
- **[PASS]** 512x512 icon present
- **[PASS]** Display mode: standalone

### PWA Depth (A+ — 95/100)

*1 PWA signal(s) surfaced*

- **[INFO]** Manifest has no maskable icon — Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

### Dark Mode Support (D — 40/100)

*No dark mode signals*

- **[INFO]** No dark mode signals detected — Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
- **[INFO]** Detection limited to meta tags and inline styles — External CSS files may contain prefers-color-scheme rules not visible to this scan.

### Print Stylesheet (D — 40/100)

*No print styles*

- **[INFO]** No print-specific styles detected — When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

### Navigation UX (F — 15/100)

*No navigation patterns*

- **[PASS]** 2 navigation landmark(s) detected
- **[INFO]** No breadcrumbs, search, or skip link detected — These navigation aids help users orient themselves and find content efficiently, especially on large sites.

### Mobile UX Depth (A+ — 97/100)

*2 mobile-depth signal(s) detected*

- **[INFO]** No `<meta name="theme-color">` -- browser chrome falls back to default — Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
- **[INFO]** iOS auto-link for phone numbers disabled (`format-detection: telephone=no`) — The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

---

## SEO

### Canonical URL (A — 92/100)

*Properly configured*

- **[PASS]** Canonical tag present
- **[PASS]** Canonical is self-referencing
- **[PASS]** Canonical matches final URL after redirects
- **[PASS]** Canonical target returns 200
- **[INFO]** Canonical points to a different domain
- **[INFO]** Page not found in sitemap.xml

### Meta Tags (A — 90/100)

*Title: 25 chars*

- **[PASS]** Page title is set
- **[WARNING]** Title is only 25 characters — consider expanding
- **[PASS]** Meta description length (160 chars) is optimal
- **[INFO]** Title and H1 are identical — Consider differentiating — the title is for search results, the H1 is for the page.

### Title Style Depth (A+ — 100/100)

*Title style is clean -- consistent separator, no stale year, no keyword stuffing*

- **[PASS]** Title style is clean

### Content Depth (A+ — 100/100)

*7503 words, Very Difficult*

- **[PASS]** Page has 7503 words — good depth for search engines
- **[INFO]** Reading level: Very Difficult (grade 19)

### Internal Links (A+ — 95/100)

*629 internal, 584 external*

- **[PASS]** 629 internal links (52%)
- **[PASS]** 88% of links use descriptive anchor text
- **[INFO]** Page has 1213 links — consider reducing
- **[INFO]** 629 internal / 584 external links

### Image SEO (A+ — 95/100)

*208 images, 205 descriptive filenames*

- **[INFO]** 3 image(s) have hash/generic filenames
- **[INFO]** 3 image(s) missing alt text — see Accessibility tab

### Hreflang

*0 hreflang tags*


### Hreflang URL Quality (A+ — 100/100)

*No hreflang tags on the page*

- **[PASS]** No hreflang tags on the page

### Hreflang Completeness (A+ — 100/100)

*No hreflang tags on this page -- check is N/A (single-language site or unannotated)*

- **[PASS]** No hreflang tags found -- completeness check is N/A

### Sitemap Freshness (C — 70/100)

*Sitemap exists but no <lastmod> entries*

- **[INFO]** Sitemap has no <lastmod> entries — Without lastmod, Google can't tell which URLs have changed since the last crawl -- it falls back to crawling everything periodically. Adding lastmod (date or ISO 8601 timestamp) on each <url> entry signals freshness so the crawler prioritizes recently-modified pages.

### Sitemap × Robots Consistency (A+ — 100/100)

*No sitemap-vs-robots conflicts in the URL sample*

- **[PASS]** All 4 sampled sitemap URLs are crawlable per robots.txt

### Sitemap Hygiene (A+ — 100/100)

*Sitemap structure / size look healthy (4 URLs, 2 KB)*

- **[PASS]** Sitemap structure / size look healthy (4 URLs)

### Markup Quality (A+ — 100/100)

*No markup-quality issues detected*

- **[PASS]** No markup-quality issues detected

---

## Sustainability

### CO2 Per Page Load (D — 50/100)

*1.11g CO2 per view*

- **[WARNING]** 1.11g CO2 per page view — This page transfers 3.9 MB, producing an estimated 1.11g of CO2 per visit using the Sustainable Web Design model (v4). Breakdown: data center 0.21g, network 0.19g, end-user device 0.71g.
- **[INFO]** At 10,000 monthly views: 133.0 kg CO2/year — With 10,000 page views per month, this page would generate approximately 133.0 kg of CO2 annually — equivalent to charging 16624 smartphones.

### Green Hosting (D — 50/100)

*Unknown*

- **[INFO]** Hosting provider could not be identified — Without knowing the provider, we cannot determine their energy sourcing. Check with your hosting provider about their renewable energy commitments.
- **[INFO]** Green hosting status based on known provider commitments — Green hosting detection uses a curated database of provider renewable energy commitments. This is not a real-time verification. For authoritative checks, visit thegreenwebfoundation.org.

### Repeat Visit Weight (A+ — 100/100)

*88% cached*

- **[PASS]** 88% reduction on repeat visits — Returning visitors download only 483 KB (vs 4007 KB first visit). 219 of 229 resources are served from browser cache, saving 0.97g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.13g CO2 (first visit: 1.11g)

### Carbon Budget (D — 50/100)

*64th percentile*

- **[WARNING]** 1.11g CO2 — above the median website (0.60g) — Heavier than an estimated 36% of websites. Reducing page weight, optimizing images, and removing unused JavaScript would lower the carbon footprint. See the Performance tab.
- **[INFO]** Estimated 64th percentile — Compared to: top 10% = 0.20g, target = 0.50g, median = 0.60g per page view.

### Transfer Efficiency (B — 80/100)

*86% efficient*

- **[INFO]** Transfer efficiency: 86% — An estimated 563 KB (14%) could be eliminated: 0 KB via better compression, 0 KB via modern image formats, 563 KB of unused JavaScript. This wasted data produces 0.16g of unnecessary CO2 per page view.

### Web Font Weight Variants (C — 70/100)

*23 font weights loaded across 1 famil(y/ies)*

- **[WARNING]** 23 font weights loaded -- likely 100+ KB of unused payload — Loading 23 font weights typically transfers 200-400 KB just for fonts. Most pages legitimately use 2-3 weights (regular + bold, maybe medium). Audit which weights your stylesheet actually applies and trim the Google Fonts URL accordingly. Affected families: Archivo.

---

---

*Generated by [BeaverCheck](https://beavercheck.com) — https://beavercheck.com/results/ab804150-edef-4670-9780-3f5bb3db11d8*