MDPI

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.

Per llmstxt.org, group key pages under "## Section" headings as "[name](url)" links.

Fix: Add "## Docs" / "## Products" sections listing your key pages as markdown links.

Per llmstxt.org, follow the H1 with a "> short summary" blockquote.

Fix: Add a "> One-sentence description of your site." blockquote under the H1.

Found https://mdpi.com/llms.txt.

First line is a top-level "# Title" heading.

Crawled 4 of 12 discovered pages beyond the homepage.

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

Only 90 of 123 images have alt attributes (73%).

Fix: Add alt text to every <img>. Screen readers and AI vision models both rely on it to caption images.

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 ~4342 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.

Only 0/123 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, footer.

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

Detected 1 cookie-banner element but none look agent-hostile (small, dismissible, or offer a reject option).

22 headings, no level skips.

Language declared as "en".

328 internal links found.

Exactly one <h1> on the homepage.

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

All 4 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: Remove ARIA attributes that aren't allowed on the element's role.

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 8 of 17 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.

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.

2 of 11 agent-critical accessibility audits failed (Links do not have a discernible name, `[aria-*]` attributes do not match their roles) — 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: 70/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.

No HTML5 validation hints (pattern / minlength / maxlength / min / max) on any data-collecting form input.

Fix: Publish input constraints via HTML attributes so agents and browsers can validate client-side.

1.79s (field data from CrUX) — needs improvement.

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.

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

`[aria-hidden="true"]` elements do not contain focusable descendents 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.

Buttons have an accessible name passed.

Document has a `<title>` element passed.

Input buttons have discernible text. passed.

1/1 data-collecting forms mark required fields.

0.050 (field data from CrUX) — good.

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.

No Content-Security-Policy header on the homepage.

Fix: Add a Content-Security-Policy. Even a strict default-src directive cuts XSS blast radius dramatically. Start in report-only mode to find violations.

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

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

No Referrer-Policy header on the homepage.

Fix: Add `Referrer-Policy: strict-origin-when-cross-origin` so outbound links don't leak full URLs (including query strings) to third parties.

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.

x-akamai-transformed: 9 - 0 pmb=mRUM,1 (Akamai)

Homepage scheme is https:.

http://mdpi.com → https://www.mdpi.com/ (2 hops).

No stack-trace markers in the first 5KB.

Valid for 147 more days (Dec 15 23:59:59 2026 GMT, issuer: DigiCert Global G3 TLS ECC SHA384 2020 CA1).

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

X-Frame-Options: SAMEORIGIN.