www.postgresql.org

Report from 8/10/2026, 1:39:54 PM https://www.postgresql.org
Latest run · lab, cold cache
59
8/10/2026
28-day score · p75 · the standard
59
11 runs
CRR100%latest
SSD28%latest
TC666 toklatest
TTFUT164 ms28-day p75

Scored by v3 · source-of-truth hashes: score db860d6ac94e · thresholds e94f8b33e500 — verifiable against the canonical scorer.

The 28-day score is the p75 of nightly runs — the stable number to cite. Deterministic metrics (CRR/SSD/TC) show their latest value (they move only when the site changes); timing (TTFUT) and answer-fidelity (AF) are smoothed by 28-day p75 — the same lab-vs-field split Core Web Vitals uses. Synthetic daily measurement, not real-user field data.

Core Agent Vitals badge  Embed this badge

Show your agent-readiness score anywhere — it links back to this report.

[![Core Agent Vitals](https://agentvitals.dev/badge/postgresql.org.svg)](https://agentvitals.dev/results?url=https%3A%2F%2Fwww.postgresql.org)
<a href="https://agentvitals.dev/results?url=https%3A%2F%2Fwww.postgresql.org"><img src="https://agentvitals.dev/badge/postgresql.org.svg" alt="Core Agent Vitals" height="20"></a>
What AI tells your customers about youAgent confidence: LOW
🟡Business namePostgreSQL · guessed from page text (no structured data)
Categorynot found
Pricenot applicable · not applicable to this page type
Locationnot applicable · not applicable to this page type
Hoursnot applicable · not applicable to this page type
Productsnot applicable · not applicable to this page type
🟡DescriptionThe official site for PostgreSQL, the world's most advanced open source database · guessed from page text (no structured data)

An agent is likely to fabricate missing details rather than say “I don’t know”. 0/3 applicable facts come from machine-readable structured data.

59
Overall score
weighted CAV (0–100)
FAIL
0–4950–8990–100

Metrics

100%
CRR Content Recovery Good
0.28
SSD Semantic Signal Density Poor
666 tok
TC Token Cost Good
51 ms
TTFUT Time to First Useful Token N/A

Token Cost breakdown

Where the page's tokens go (≈2,711 across regions). Most tokens are real content — the agent isn't paying much for chrome.

Content
92.1% · 2,498
Chrome (nav / header / footer)
7.9% · 213
Boilerplate (cookie / ad)
0% · 0
Other
0% · 0

Final screenshot

Final screenshot of https://www.postgresql.org

Diagnostics

high SSD Low signal-to-noise for agents

content vs chrome/boilerplate

Evidencesignal 0.47 · JSON-LD 0/1 · missing: structured-data
ImpactAgent spends tokens parsing nav/boilerplate instead of content.
Effort30–90 min

Fix: Wrap the real content in <main>/<article>, cut repeated nav/boilerplate, and keep the primary content dense and early in the DOM.

Rendered profile: headless

Agent Discoverability 71/100 · Needs Work

Access & discovery checks — separate from the gated CAV metrics above. Click an issue for business impact, what we measured, and how to fix. · Take the Agent Readiness course →

Agent files & endpoints

llms.txt Absent at /llms.txt and /.well-known/llms.txt Learn →
robots.txt (AI bots) Major AI bots allowed Learn →
sitemap.xml Found at /sitemap.xml Learn →
JSON-LD structured data No JSON-LD found Learn →
~ agents.json Absent (emerging standard) Learn →
~ WebMCP endpoint Absent (emerging standard) Learn →
~ OpenAPI / API docs No OpenAPI/Swagger found Learn →

Issues (6)

llms.txt present high impact Absent at /llms.txt and /.well-known/llms.txt

Business impact llms.txt is the robots.txt for AI: it tells agents what your site is, what matters, and where to find it. Without it AI guesses — and guessing means inaccurate recommendations and lost visibility.

What we measured We fetch /llms.txt and /.well-known/llms.txt and validate the spec (H1 title + a one-line blockquote summary). We also note /llms-full.txt (your full content as Markdown).

How to fix Create /llms.txt with a short summary + key pages; optionally /llms-full.txt with full content in Markdown.

Learn how to implement →

# Your Site
> One-line description for AI agents.

## Key pages
- /products — catalog
- /pricing — plans
- /docs — documentation

Spec: https://llmstxt.org

Structured data (JSON-LD) medium impact No JSON-LD found

Business impact Schema.org JSON-LD tells agents what a page IS (product, article, business) with typed fields (price, rating, hours). Without it agents extract less reliably.

What we measured We parse <script type=application/ld+json>, validate it, and check for populated @type fields.

How to fix Add JSON-LD: Organization/LocalBusiness on the homepage, Product on product pages, Article on posts.

Learn how to implement →

<script type="application/ld+json">{"@context":"https://schema.org","@type":"Organization","name":"Your Co","url":"https://example.com"}</script>

Spec: https://schema.org/

~ Server response (TTFB) low impact 831ms (good ≤800, warn ≤1800)

Business impact Slow servers cause agents to time out and move on. Fast response keeps you in the running.

What we measured We time the response (time-to-first-byte) against good (<800ms) / warn (<1800ms) thresholds.

How to fix Use a CDN, caching and an optimized origin to get TTFB under 800ms.

Spec: https://web.dev/ttfb/

~ agents.json discovery low impact Absent (emerging standard)

Business impact agents.json describes what your site can DO for agents (services, endpoints, capabilities) — an emerging discovery standard. Early adopters get native agent integration.

What we measured We check /agents.json and /.well-known/agents.json for a valid configuration.

How to fix Publish /agents.json describing your site's capabilities and actions.

Learn how to implement →

Spec: https://github.com/wild-card-ai/agents-json

~ WebMCP endpoint low impact Absent (emerging standard)

Business impact WebMCP lets agents call actions on your site directly (book, buy, query) instead of scraping the DOM. Early adopters get native AI-agent interoperability.

What we measured We check /.well-known/webmcp and /webmcp.json for a valid actions array.

How to fix Add a WebMCP endpoint exposing your key actions to agents.

Learn how to implement →

Spec: https://webmcp.org

~ API documentation low impact No OpenAPI/Swagger found

Business impact Programmatic agents prefer a typed API. An OpenAPI/Swagger spec lets them integrate without scraping.

What we measured We probe /openapi.json, /swagger.json, /api-docs and /.well-known/openapi.json.

How to fix Publish an OpenAPI spec at a well-known path.

Learn how to implement →

Spec: https://www.openapis.org/

Passed audits (5)

✓ robots.txt allows AI bots✓ No CAPTCHA wall✓ No content-blocking cookie wall✓ No login wall on public content✓ XML sitemap present + fresh

Transport & Trust (SEC 1.0.0)

HTTPS, HSTS, CSP, sniffing, referrer and CORS posture. Diagnostic only — this does not affect the CAV score. A security header does not make a page more legible to an agent, so scoring it would reward a CDN toggle that changes nothing an agent can recover. We measure it and say so.

81Transport posture (0–100, unscored)
3pass
1warn
1fail
Per-header findings (6)
HeaderEvidence
✅ HTTPSserved over HTTPS
✅ HSTSmax-age=31536000
✅ Content-Security-Policypolicy present, script-src does not allow inline
❌ X-Content-Type-Optionsmissing nosniff
⚠️ Referrer-Policyno referrer-policy header (browser default applies)
➖ CORS exposureno CORS headers on the document (normal for an HTML page)
Full profile — how to improve · unused JS · network · timing

How to improve

mediumSplit the heaviest unused bundle

js — 159 KiB transferred, 52.7% unused (third-party)

EvidenceCDP JS coverage: 84 KiB of this bundle is never executed on load.
Impact~-84 KiB transfer; lower Token Cost + faster agent parse.
Effort30–90 min
FixDynamic-import() the below-the-fold parts of js, or drop unused dependencies. It is third-party — lazy-load or remove it.
mediumCut third-party weight

googletagmanager.com — 280 KiB, 2 requests

EvidenceThird-party is 40.5% of total transfer (5 requests); googletagmanager.com is the largest.
ImpactFewer bytes + main-thread stalls before your content settles for an agent.
Effort1–3 h
FixLazy-load, self-host, or remove googletagmanager.com; defer non-critical third-party scripts.

Third-party impact

5 third-party requests · 302 KiB (40.5% of transfer) — code an agent must also fetch/run before your content settles. Fewer, lazier third-parties = faster, cheaper agent reads.

Third-party domainReqsTransferMain-thread
googletagmanager.com2280 KiB
google-analytics.com321 KiB

Wasted JavaScript (by bundle)

Transfer-accurate — each bundle's transfer size × its unused %, ranked by wasted bytes (the biggest code-splitting wins). Unused JS also inflates Token Cost (TC).

BundleTransferUnusedWasted
https://www.googletagmanager.com/gtag/js?id=G-FGJ68XB9NC&cx=c&_slc=1 3P159 KiB52.7%84 KiB
https://www.googletagmanager.com/gtm.js?id=GTM-WC97NKC 3P121 KiB62%75 KiB
https://www.google-analytics.com/analytics.js 3P21 KiB50.9%11 KiB
https://www.postgresql.org/media/js/main.js?73aab7452 KiB63.6%1 KiB
https://www.postgresql.org/media/js/theme.js?73aab7450 KiB64.4%0 KiB

Network

22Requests
745 KiBTransferred
5Scripts
40.5%3rd-party
0Long tasks
Script (5)
304 KiB
Image (5)
295 KiB
Font (3)
89 KiB
Stylesheet (5)
45 KiB
Document (1)
6 KiB
Other (1)
5 KiB
XHR (1)
0 KiB
Fetch (1)
0 KiB
Heaviest requests (22)
URLTypeStatusTransfer
https://www.googletagmanager.com/gtag/js?id=G-FGJ68XB9NC&cx=c&_slc=1Script200159 KiB
https://www.googletagmanager.com/gtm.js?id=GTM-WC97NKCScript200121 KiB
https://www.postgresql.org/media/img/misc/banner.jpgImage200111 KiB
https://www.postgresql.org/media/img/misc/bugs.jpgImage20067 KiB
https://www.postgresql.org/media/img/misc/training.jpgImage20062 KiB
https://www.postgresql.org/media/img/about/press/elephant.pngImage20049 KiB
https://www.postgresql.org/media/webfonts/latin.woff2Font20039 KiB
https://www.postgresql.org/media/webfonts/fa-solid-900.woff2Font20038 KiB
https://www.postgresql.org/media/css/bootstrap-4.4.1.min.cssStylesheet20023 KiB
https://www.google-analytics.com/analytics.jsScript20021 KiB
https://www.postgresql.org/dyncss/base.css?73aab745Stylesheet20012 KiB
https://www.postgresql.org/media/webfonts/fa-regular-400.woff2Font20012 KiB
https://www.postgresql.org/media/css/fontawesome.css?73aab745Stylesheet2008 KiB
https://www.postgresql.org/media/img/PostgreSQL_Badge1.svgImage2007 KiB
https://www.postgresql.org/Document2006 KiB
https://www.postgresql.org/favicon.icoOther2005 KiB
https://www.postgresql.org/media/js/main.js?73aab745Script2002 KiB
https://www.postgresql.org/media/css/open-sans-woff2.cssStylesheet2001 KiB
https://www.postgresql.org/media/css/open-sans-woff.cssStylesheet2001 KiB
https://www.google-analytics.com/j/collect?v=1&_v=j102&a=479040254&t=pageview&_s=1&dl=https%3A%2F%2Fwww.postgresql.org%2F&ul=en-us&dt=PostgreSQL%3A%20The%20world%27s%20most%20advanced%20open%20source%20database&sr=800x600&vp=1350x940&_u=YEBAAEABAAAAACAAI~&jid=933863450&gjid=444007951&cid=1549042697.1786097616&tid=UA-1345454-1&_gid=60072687.1786097616&_r=1&_slc=1&gtm=45He6852n81WC97NKCza200&gcd=13l3l3l3l1l1&dma=0&tag_exp=115938465~115938468~118395335~118897920~118897930~119527019~119896802&z=911593664XHR2000 KiB
https://www.postgresql.org/media/js/theme.js?73aab745Script2000 KiB
https://www.google-analytics.com/g/collect?v=2&tid=G-FGJ68XB9NC&gtm=45je6852v9126506705za20g&_p=1786097615789&gcd=13l3l3l3l2l1&npa=0&dma=0&_eu=ABAI&are=1&cid=1549042697.1786097616&frm=0&ngs=1&pscdl=noapi&rcb=11&sr=800x600&uaa=&uab=&uafvl=&uam=&uamb=0&uap=&uapv=&uaw=0&ul=en-us&_s=1&tag_exp=115616985~115938465~115938469~118897920~118897930~119527019~119896802&dl=https%3A%2F%2Fwww.postgresql.org%2F&dt=PostgreSQL%3A%20The%20world%27s%20most%20advanced%20open%20source%20database&sid=1786097615&sct=1&seg=0&en=page_view&_fv=1&_ss=1&_ee=1&gap.uat=115938465~115938468~118395335~118897920~118897930~119527019~119896802&tfd=855Fetch2040 KiB
Analyzing…
running mobile + desktop · ~30s