edx.org

Scores

What this costs you

AI agents and answer engines are mostly failing to find, understand, or act on this site today. Every month this stands, AI-referred demand flows to competitors who are machine-ready.

Critical exposures

• Machine interfaces not advertised. Nothing in the HTML or HTTP headers points agents to your machine-readable surfaces. If an agent can't find the interface, the interface doesn't exist to it.
• API not described as a service. Your API exists but isn't described with WebAPI metadata. Procurement agents comparing vendors can't classify it, so it drops off shortlists.
• Performance score 0/100. Slow pages hit agent fetch timeouts before content loads. A page that times out is a page the agent reports as unavailable.
• SEO score 60/100. The fundamentals classic search uses are also what AI engines ground on. Weak fundamentals here compound every gap above.

Operational friction

• High Integration Tax for AI Procurement Agents: no OpenAPI contract or MCP server. The site takes real inputs, but agents have no typed way to submit them. Each integration needs a human engineer, so autonomous buyers route to vendors who are callable today.

Issues & fixes

• Server response over 800ms — consider caching/CDN
• HTML is 2406KB — trim markup or lazy-load
• 39 external scripts — audit and defer
• 11 stylesheets — consolidate
• Title length 70 — aim for 10–65 chars
• No H1 found

Embed the badge

Show the live score in your README. The badge updates on every re-audit and greys out when the report is older than 30 days.

[![Agent-Ready badge](https://api.santosautomation.com/v1/badge?url=edx.org)](https://www.santosautomation.com/reports/edx.org)