LiveJournal

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.

Could not identify a known website platform (custom stack or unrecognised).

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 ~1908 elements — heavy.

Fix: Aim for under 1500 elements on the homepage. Heavier DOMs slow first paint and overflow some AI crawlers' parse buffers.

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.

8 of 9 images have alt attributes (89%).

Fix: Add alt text to the remaining images. Empty alt="" is fine for purely-decorative graphics.

Only 4/9 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.

Missing landmark elements: main.

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

Language declared as "en-us".

70 internal links found.

Exactly one <h1> on the homepage.

All 12 reachable key pages have both a <title> and <h1>.

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

3 of 10 agent-critical accessibility audits failed (Buttons do not have an accessible name, Links do not have a discernible name, `<frame>` or `<iframe>` elements do not have a title) — 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 flagged this audit — agents may be unable to perceive or operate the affected elements.

Fix: Give every <button> discernible text or an aria-label so agents can identify it.

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

Fix: Add a title to every <iframe> so agents can identify embedded content.

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.

Only 5 of 8 visible interactive form fields have labels.

Fix: Associate every input with a label. Form-filling agents (and screen readers) need it to know what to type into each field.

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

0.548

0.280 (field data from CrUX) — poor.

Fix: A layout that shifts while loading makes an AI agent mis-click the element it targeted. Eliminate CLS by setting explicit width/height on images and embeds, avoiding inserted content above existing content, and reserving space for ad slots.

2.20s (field data from CrUX) — poor.

Fix: Every request an AI agent makes pays this server latency, and agents make many requests per task. Reduce TTFB with edge caching, a CDN, and shipping less server-side work per request.

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.

Lighthouse accessibility score: 73/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.

0/1 data-collecting forms mark required fields.

Fix: Add the `required` attribute (or `aria-required="true"`) to mandatory inputs. Form-filling agents skip optional fields by default — without markers they over-fill.

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

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

`[role]`s have all required `[aria-*]` attributes passed.

`[role]` values are valid passed.

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

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

Document has a `<title>` element passed.

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

6 forms 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.

No Strict-Transport-Security header on the homepage.

Fix: Add `Strict-Transport-Security: max-age=15768000; includeSubDomains` so browsers and agents refuse to downgrade to http for at least six months.

/.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.

http://livejournal.com did not respond: invalid redirect Location: https:///.

Fix: Listen on port 80 and 301-redirect every request to the https:// origin.

No `X-Content-Type-Options: nosniff` header.

Fix: Add `X-Content-Type-Options: nosniff` to prevent browsers (and some agents) from re-interpreting your responses as a different content type.

CSP header present.

Homepage scheme is https:.

No stack-trace markers in the first 5KB.

Homepage HTML references no http:// resources.

Referrer-Policy: no-referrer-when-downgrade.

Valid for 249 more days (Mar 28 14:51:51 2027 GMT, issuer: GlobalSign GCC R3 DV TLS CA 2020).

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

CSP frame-ancestors directive present.