Independent technical audit

azure.microsoft.com

Overall AI readiness score

A combined result across all audit signals.

Average

AI readiness audit: 7/21/2026Public technical data

Overall AI readiness assessment

How ready azure.microsoft.com is for AI systems

42/100

azure.microsoft.com was independently audited by llmsmap. azure.microsoft.com currently scores 42/100 for AI readiness. The result combines AI-specific files, crawler policy, sitemap discovery, structured homepage data, and—when available—the mobile Google Lighthouse technical profile.

Audit context

llms.txt was not available as a readable text file during the latest check. That removes the shortest first-party map of the site for an AI agent. No separate ai.txt policy was detected; it is optional, but can clarify training, retrieval, and attribution preferences.

robots.txt is available. 11 of 11 tracked AI bots are not blocked. Declared sitemaps: 32. No Schema.org type was detected on the homepage. 0 OpenGraph tags were found and markup completeness is 0%, leaving more entity interpretation to crawlers.

The mobile Lighthouse profile adds Performance 34/100, Accessibility 96/100, Best Practices 69/100, SEO 85/100, and experimental Agentic Browsing 61/100. These signals have a limited weight: they complement rather than replace llms.txt, robots.txt, and structured-data checks.

Confirmed strengths

32 sitemap declarations

Priority improvements

1Restore a readable /llms.txt with canonical links and concise descriptions.
2Add llms-full.txt for richer first-party context.
3Add JSON-LD for the organisation, website, and core entities.
4Complete OpenGraph and canonical homepage metadata.

llms.txt tokens11,733

llms-full.txt tokens—

ai.txt

sitemap.xml

Google Lighthouse technical profile

A mobile Lighthouse measurement. Google’s experimental Agentic Browsing category is explained separately and does not replace the broader llmsmap AI-readiness score.

Mobile · Lighthouse

Performance

Accessibility

Best Practices

Technical SEO

Agentic Browsing

What these results mean

Mobile performance is 34/100, with the largest visible content block appearing in 32.3 s and the browser main thread blocked for 670 ms. Layout shift was 0.127. The main thread is where the browser runs JavaScript, calculates layout, and paints the page; long work there delays both user input and browser-agent actions.

Accessibility scored 96/100, Best Practices 69/100, and technical SEO 85/100. The experimental Agentic Browsing category scored 61/100. It measures signals Google currently tests for software agents and is shown separately from the llmsmap AI-readiness score.

Free the main thread and accelerate the first view

Split long JavaScript tasks, defer non-critical scripts and styles, and shorten blocking request chains. This helps the primary content appear sooner and makes controls usable earlier.

Reduce code that loads without helping the page

Remove unused CSS and JavaScript, load heavy widgets on demand, and limit third-party scripts. Less code means less parsing and background work on the device.

Optimise images and their loading order

Serve correctly sized modern formats, prioritise the primary visual, and lazy-load content below the first viewport.

Reduce network delay

Improve server response time, remove unnecessary redirects and repeat downloads, and use compression, caching, and selective preconnect hints.

FCP19.5 s

First content

LCP32.3 s

Main content

CLS0.127

Layout stability

TBT670 ms

Blocking time

SI19.5 s

Visual speed

Metric glossary

FCP · First content: When the first text or image appeared on screen.
LCP · Main content: When the largest visible element in the first viewport rendered.
CLS · Layout stability: How much content shifted unexpectedly while loading; lower is better.
TBT · Blocking time: How long the browser main thread could not respond quickly to input.
SI · Visual speed: How quickly the visible viewport filled with content.