Sapo

The page registers no tools via the WebMCP browser API (navigator.modelContext).

Fix: Expose your actions to AI agents with the WebMCP browser API: register tools via navigator.modelContext.registerTool. Optionally also publish a /.well-known/webmcp.json tool catalog as a discovery signpost.

Crawled 12 of 12 discovered pages beyond the homepage.

Lighthouse Agentic Browsing audits ran.

Built on WordPress.

Homepage ignored Accept: text/markdown and returned HTML.

Fix: Serve a markdown version of high-value pages when the client asks for text/markdown. AI summarisers, chatbots and IDE agents prefer markdown — fewer tokens, no DOM noise.

Homepage contains ~4376 elements — well above the 1500-element budget.

Fix: Trim the homepage DOM: an AI agent has to read all of it before acting, and this page is several times over budget. Long product carousels, hidden modal markup and large tracker scripts are common culprits.

Detected 1 heading level skip (e.g. h1 → h3).

Fix: Tighten the heading order so each level only steps down by one. Skipped levels confuse both screen-readers and AI structural extractors.

Only 0/333 images have width+height — large CLS risk.

Fix: Set width and height on every <img> so the browser reserves space before the image loads. A layout that shifts while loading makes an AI agent mis-click the element it targeted.

8 of 12 pages are missing <title> and/or <h1>: /cultura-lifestyle/filmes-series-tv/filmes, /cultura-lifestyle/filmes-series-tv/series, /cultura-lifestyle/filmes-series-tv/estreias, /cultura-lifestyle/a-mesa/receitas, /desporto/outras-modalidades, /dossies, /parceiros, /incendios.

Fix: Make sure every page sets a unique <title> and exactly one <h1>. The title is how an AI agent confirms it landed on the right page after navigating.

Homepage server response contains 3571 words of visible text — content is reachable without executing JavaScript.

Language declared as "pt".

333 of 333 <img> tags have alt attributes.

513 internal links found.

All four landmark elements present (main, header, footer, nav).

Exactly one <h1> on the homepage.

All 12 pages return ≥80 words of visible text without JavaScript.

Lighthouse flagged this audit — agents may be unable to perceive or operate the affected elements.

Fix: Give every link discernible text (avoid bare icons / "click here") so agents know where it goes.

A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page.

The page registers no tools via the navigator.modelContext browser API, so an AI agent has no structured way to operate it.

Fix: Expose your site’s actions to AI agents with the WebMCP browser API: call navigator.modelContext.registerTool({ name, description, inputSchema, execute }) from your page so an agent can invoke them. Implement it directly, or with a library like the @mcp-b polyfill (https://mcp-b.ai). Spec: https://github.com/webmachinelearning/webmcp.

1 of 8 agent-critical accessibility audits failed (Links do not have a discernible name) — an agent may be unable to identify or operate the affected elements.

Fix: Fix the failing agent-accessibility audits listed below (accessible names on controls, valid ARIA roles/relationships, nothing interactive hidden from the tree).

Lighthouse accessibility score: 85/100. Agents read the page through its accessibility tree, so this is a proxy for how navigable your site is to an AI agent.

Fix: Resolve the failing accessibility audits below — each one removes an element or relationship an agent would otherwise be blind to.

No autocomplete attributes on any data-collecting form field.

Fix: Add autocomplete hints (email, tel, name, etc.) so form-filling agents and browsers can populate fields without guessing.

0/1 data-collecting forms expose errors via ARIA attributes.

Fix: Wire inputs to their error containers with `aria-describedby` and toggle `aria-invalid` on validation failure. Agents that can't see styled error text rely on these attributes.

6 of 7 visible interactive form fields have labels.

Fix: Associate every input with a label — either wrap it in <label>, link via for/id, or set aria-label / aria-labelledby.

`[aria-*]` attributes match their roles passed.

`[aria-hidden="true"]` is not present on the document `<body>` passed.

`[aria-hidden="true"]` elements do not contain focusable descendents passed.

`[aria-*]` attributes are valid and not misspelled passed.

`[aria-*]` attributes have valid values passed.

Buttons have an accessible name passed.

Document has a `<title>` element passed.

1/1 data-collecting forms mark required fields.

All 1 data-collecting forms include pattern/min/max constraints.

0.009

0.020 (field data from CrUX) — good.

379ms (field data from CrUX) — good.

1 form missing annotations

Lists the [WebMCP tools](http://goo.gle/webmcp-docs) registered at the time of analysis.

No tool catalog was found at /.well-known/webmcp.json (or /.well-known/webmcp). The catalog is a community convention, not part of the WebMCP standard, so this does not affect WebMCP presence.

Fix: Consider also publishing a tool catalog at /.well-known/webmcp.json: a JSON document with a "spec" of "webmcp/0.1" and a "tools" array, where each tool declares a name and a clear description. It is a community convention (optional, not part of the WebMCP standard) that lets crawlers and agents discover your tools without executing JavaScript.

Found 3 http:// references in the homepage HTML — browsers will block these resources.

Fix: Update every http:// resource URL to https:// (or use protocol-relative `//`). Common offenders: image CDNs and legacy embed snippets.

/.well-known/oauth-authorization-server returned 404.

Fix: Publish /.well-known/oauth-authorization-server so AI agents discovering your OAuth setup can negotiate flows automatically. Required if your site offers an authenticated API.

/.well-known/oauth-protected-resource returned 404.

Fix: Publish /.well-known/oauth-protected-resource so AI agents discovering your OAuth setup can negotiate flows automatically. Required if your site offers an authenticated API.

No Web Bot Auth signature headers — sites can't verify agent identity.

Fix: Web Bot Auth (IETF HTTP Message Signatures over Signature / Signature-Input) lets you cryptographically verify which agent is hitting you. Several CDNs offer turn-key support; otherwise skip until vendor support matures.

HSTS configured (max-age=31536000) but missing includeSubDomains.

Fix: Add `includeSubDomains` so subdomains inherit the policy.

CSP header present.

Homepage scheme is https:.

http://sapo.pt → https://sapo.pt/ (1 hop).

No stack-trace markers in the first 5KB.

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

Valid for 109 more days (Nov 7 23:59:59 2026 GMT, issuer: GeoTrust TLS RSA CA G1).

Server / X-Powered-By headers don't leak product version.

X-Content-Type-Options: nosniff.

X-Frame-Options: SAMEORIGIN.