agentspeed.

gymshark.com

scanned 7/25/2026, 6:40:34 PM · cached · refresh in 18h · rubric 2026.07.4
Built with Shopify
robots.txt present: passrobots.txt allows AI agents: passContent-Signal directives: failllms.txt present: passSitemap present: passLink response headers: warnCanonical URL: passMCP server card: failOAuth authorization metadata: passOAuth resource metadata: passAPI catalog / OpenAPI: failWeb Bot Auth: failMarkdown negotiation: passText-to-markup ratio: failContent without JavaScript: skipHeading hierarchy: failCookie wall blocks content: passPage title: failMeta description: failJSON-LD present: failStructured data validates: skipSchema type coverage: passPaywall / login wall: passAgent Skills manifest: failWebMCP actions: failPrimary action reachable: failReachability: passTime to first byte: passFull render time: skipPage weight: pass55/ 100 · F
At risk

This is how AI agents (not browsers) experience gymshark.com. The score weights five categories of machine-readability; the ticks on the arc are the 30 individual checks behind it.

✉ Email me this report + alert me when it changes ↓

Top fixes

failPage titleReadability

No non-empty <title>. Agents use it as the page label in citations and answers.

Fix: Add a concise <title> tag. Agents often cite it verbatim.

failMeta descriptionReadability

No <meta name="description">. Agents use it as a page summary; add a 50–200 character description.

Fix: Add `<meta name="description" content="...">` to your primary pages. Agents frequently use it as a summary.

failJSON-LD presentStructured data

No JSON-LD blocks found. Add a <script type="application/ld+json"> with a schema.org type for this page.

Fix · Shopify: Add Product, Offer, and BreadcrumbList JSON-LD in theme.liquid (or your SEO app). Most themes ship partial schema, so fill the gaps.

failPrimary action reachableActionability

Page text too sparse to probe; agent has nothing to read.

Fix: If agents cannot identify what you sell within 3 steps, your primary-offer page is under-structured. Add a visible headline, price (or "contact us"), and canonical CTA.

failText-to-markup ratioReadability

Visible text is 0.0% of HTML weight (14/46478 bytes). Low. Markup may be crowding out agent-usable text.

Fix: Heavy ad or navigation markup crowds out agent-usable text. Aim for a text-to-DOM ratio above 15%.

failHeading hierarchyReadability

No headings found. Add at least an <h1>; structure helps agents summarise.

Fix: Use a single H1 and avoid skipping heading levels (H1 → H3).

Don’t lose this report

Get it in your inbox now — and a heads-up whenever gymshark.com’s agent-readiness score changes. Free, unsubscribe anytime.

Fix it

Generated, ready-to-ship files for the gaps above — copy them or download and drop them into your repo.

Add JSON-LD structured data
Paste inside <head>. Use Article/Product instead of Organization on those page types.
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "gymshark.com",
  "url": "https://gymshark.com/"
}
</script>

What the agent receives

The agent’s-eye view
Redirecting...

Show your score

Embed this badge on your site. It links back to this live scan and updates on every rescan.

AgentSpeed score for gymshark.com
<a href="https://agentspeed.com/scan/gymshark.com"><img src="https://agentspeed.com/badge/gymshark.com" alt="AgentSpeed agent-readiness score" height="56"></a>

Track this score

Get this report by email, then a heads-up when gymshark.com’s agent-readiness actually changes — a check regressing, or the composite dropping.

Two things never trigger an email: a score change caused by us publishing a new rubric, because that is a different instrument rather than a change to your site, and movement explained only by timing-derived checks, which shift run to run on a site nobody touched.

Want it on your own schedule, with Slack or a webhook instead of email? Score-drift monitoring is on every paid plan.

Full breakdown

14 pass1 warn12 fail3 skip
Discoverability
pass
robots.txt present
A robots.txt is reachable at the site root.
100/100
pass
robots.txt allows AI agents
All 8 answer-time access agents allowed.
100/100
fail
Content-Signal directivesemerging
No Content-Signal directives. Add e.g. `Content-Signal: ai-train=no, ai-summarize=yes` to declare granular AI usage policy beyond binary allow/disallow.
0/100
pass
llms.txt present
Found /llms.txt (4333 bytes), H1 + at least one link present.
100/100
pass
Sitemap present
sitemap.xml reachable and referenced from robots.txt.
100/100
warn
Link response headers
A Link: header is present but carries none of canonical/alternate/describedby — the relations agents consume.
60/100
pass
Canonical URL
Canonical points to self: https://us.checkout.gymshark.com/.
100/100
fail
MCP server cardemerging
No valid MCP Server Card at /.well-known/mcp/server-card.json. Publish one so agents can discover your tools without HTML scraping.
0/100
pass
OAuth authorization metadataemerging
OAuth authorization-server metadata (RFC 8414) is published, so agents can discover authorization endpoints without out-of-band setup.
100/100
pass
OAuth resource metadataemerging
OAuth protected-resource metadata (RFC 9728) is published, so agents can discover required scopes and authorization servers programmatically.
100/100
fail
API catalog / OpenAPIemerging
No /.well-known/api-catalog (RFC 9727) and no /openapi.json|yaml. Publish one so agents that integrate with APIs can discover your endpoints.
0/100
fail
Web Bot Authemerging
No Web Bot Auth JWKS at /.well-known/http-message-signatures-directory.json. Publish one to allow trusted agents while keeping a default-deny posture for the rest.
0/100
Readability
pass
Markdown negotiationemerging
Requests with Accept: text/markdown return a markdown representation — agents prefer markdown over HTML for summarization and citation.
100/100
fail
Text-to-markup ratio
Visible text is 0.0% of HTML weight (14/46478 bytes). Low. Markup may be crowding out agent-usable text.
0/100
skip
Content without JavaScript
Browser pass unavailable; cannot measure JS dependency.
fail
Heading hierarchy
No headings found. Add at least an <h1>; structure helps agents summarise.
0/100
pass
Cookie wall blocks content
No common consent-modal markers detected.
100/100
fail
Page title
No non-empty <title>. Agents use it as the page label in citations and answers.
0/100
fail
Meta description
No <meta name="description">. Agents use it as a page summary; add a 50–200 character description.
0/100
Structured data
fail
JSON-LD present
No JSON-LD blocks found. Add a <script type="application/ld+json"> with a schema.org type for this page.
0/100
skip
Structured data validates
No JSON-LD blocks present; nothing to validate (covered by structured_data.jsonld_present).
pass
Schema type coverage
Page intent unclear; no specific schema.org type expected.
100/100
Actionability
pass
Paywall / login wall
No paywall or login-wall detected on the landing URL.
100/100
fail
Agent Skills manifestemerging
No Agent Skills manifest at /.well-known/agent-skills.json. Enumerate the tasks agents can perform (search, add-to-cart, contact-support) so they pick the right one without scraping.
0/100
fail
WebMCP actionsemerging
No WebMCP detected. On pages with first-class actions (cart, support, account), embed a WebMCP server so on-page agents invoke tools directly.
0/100
fail
Primary action reachable
Page text too sparse to probe; agent has nothing to read.
0/100
pass
Reachability
HTTP 200 after 1 redirect.
100/100
Performance
pass
Time to first byte
TTFB 233ms. Healthy.
80/100
skip
Full render time
Full-render time unavailable (browser pass skipped or failed).
pass
Page weight
Initial document is a lean 45 KB.
100/100
Beyond the scan

Running AI agents of your own? AgentSpeed also monitors them in production — every run, its latency, cost, and failures, with alerts when something breaks. Free for 10,000 events a month, no credit card.

Start watching free →See plans