Audit · stripe.com
Dual-axis lens: Performance (Core Web Vitals, real Chrome users) + Citation-readiness (10-characteristic LLM checklist).
Axis 1 — Performance (Core Web Vitals)
Strong100%Real Chrome user data (28-day p75). Mobile + desktop. Source: Google Chrome UX Report.
Mobile (phone)
LCPgood
2164ms
Largest Contentful Paint
INPgood
152ms
Interaction to Next Paint
CLSgood
0
Cumulative Layout Shift
FCPneeds improvement
1998ms
First Contentful Paint
TTFBneeds improvement
1152ms
Time to First Byte
Desktop
LCPgood
1226ms
Largest Contentful Paint
INPgood
77ms
Interaction to Next Paint
CLSgood
0
Cumulative Layout Shift
FCPgood
1082ms
First Contentful Paint
TTFBgood
615ms
Time to First Byte
Deep dive: full stripe.com report · mobile · desktop
https://stripe.comAxis 2 — Citation-readiness (LLM-discoverability)
OK54%10-characteristic checklist (Aleyda Solis). Server-rendered HTML parsed as a GPTBot/PerplexityBot would see it. HTTP 200 · 1893w body · 139ms fetch
Hard-block: credible, differentiated, fresh at 0.0. Without these, LLM citation is functionally impossible regardless of other scores.
AAccessible
100%1893 words of static body content. Crawlers can extract.
AUseful
100%Body=1893w · headings=33 · structured-data blocks=2. Heuristic for content depth + organization.
ARecognizable
100%Organization schema: ✓ · name ✓ · url ✓ · logo/image ✓ · sameAs ✓
DExtractable
40%4/5 H2s are quote-ready (≥25 chars, ≥5 words) · DefinedTerm ✗ · FAQ blocks=0
Fix: Rewrite H2 headings as quote-ready sentences (≥5 words, descriptive). Add DefinedTerm schema for key concepts. ≤1 FAQ block per page.
📋 Rewrite these 1 H2 heading(s) so LLM crawlers can quote them as standalone sentences (target ≥25 chars + ≥5 words)text
BEFORE: <h2>What’s happening</h2>
AFTER: <h2>What’s happening — [add 2-4 descriptive words so it reaches ≥5 words + ≥25 chars]</h2>📋 Add DefinedTermSet schema for your key concepts (lifts Extractable +0.30)json-ld
{
"@context": "https://schema.org",
"@type": "DefinedTermSet",
"@id": "https://stripe.com/#glossary",
"name": "(your concept area) Glossary",
"url": "https://stripe.com/glossary",
"hasDefinedTerm": [
{
"@type": "DefinedTerm",
"name": "(Term 1)",
"description": "(1-2 sentence definition)",
"inDefinedTermSet": "https://stripe.com/#glossary"
},
{
"@type": "DefinedTerm",
"name": "(Term 2)",
"description": "(1-2 sentence definition)",
"inDefinedTermSet": "https://stripe.com/#glossary"
}
]
}📋 Optional: add ONE FAQPage block per page (>1 triggers schema-spam penalty)json-ld
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What does this site do?",
"acceptedAnswer": {
"@type": "Answer",
"text": "(answer in 1-3 sentences)"
}
},
{
"@type": "Question",
"name": "How is this different from alternatives?",
"acceptedAnswer": {
"@type": "Answer",
"text": "(answer in 1-3 sentences)"
}
}
]
}AConsistent
100%Brand "Stripe" in title=✓ · in nav/header=✓
DCorroborated
25%28 external links · 0 to authoritative sources (.gov/.edu/wikipedia/web.dev/etc.).
Fix: Cite ≥3 authoritative sources (gov/edu/wikipedia/standards bodies/peer-reviewed). Build off-site presence (Wikipedia citation, Reddit organic, LinkedIn).
📋 Add ≥3 outbound links to authoritative sources matching your topichtml
<!-- Pick 3-5 sources relevant to your domain. Examples by topic: -->
<!-- Web performance / dev -->
<a href="https://web.dev/articles/vitals">web.dev Core Web Vitals</a>
<a href="https://developer.mozilla.org/en-US/docs/Web/Performance">MDN Web Performance</a>
<a href="https://developer.chrome.com/docs/crux/">Chrome UX Report</a>
<!-- Schema / standards -->
<a href="https://schema.org/Organization">schema.org reference</a>
<a href="https://w3.org/TR/">W3C specifications</a>
<!-- Health / science -->
<a href="https://www.nih.gov/health-information">NIH Health Info</a>
<a href="https://www.cdc.gov/">CDC</a>
<a href="https://pubmed.ncbi.nlm.nih.gov/">PubMed</a>
<!-- Finance / business -->
<a href="https://www.sec.gov/edgar.shtml">SEC EDGAR</a>
<a href="https://www.federalreserve.gov/">Federal Reserve</a>FCredible
0%Person schema ✗ · sameAs=0 · /about or /methodology link=✗ · datePublished=✗ · dateModified=✗
Fix: Add Person schema with sameAs[] (≥2 profiles). Link /about + /methodology in nav/footer. Add datePublished + dateModified to Article schema.
📋 Add Person schema (operator/author identity)json-ld
{
"@context": "https://schema.org",
"@type": "Person",
"@id": "https://stripe.com/about#author",
"name": "(your full name — operator or primary author)",
"jobTitle": "Founder",
"url": "https://stripe.com/about",
"sameAs": [
"https://twitter.com/YOUR_HANDLE",
"https://www.linkedin.com/in/YOUR_HANDLE",
"https://github.com/YOUR_HANDLE"
],
"worksFor": {
"@id": "https://stripe.com#org"
}
}📋 Add datePublished + dateModified to your Article/WebPage schemajson-ld
"datePublished": "2026-01-15",
"dateModified": "2026-06-28"FDifferentiated
0%0 POV markers detected (e.g. "our view", "we found", "we recommend").
Fix: Add explicit POV sentences ("Our view: …", "We measured …", "We recommend …"). LLMs cite pages with stance more than encyclopedic neutrality.
📋 Add explicit POV sentences in the body text (LLMs cite pages with stance more than neutral encyclopedic content)markdown
> Our view: (your specific stance on the topic this page covers)
> We measured (a number you actually measured) and found (insight).
> We recommend (specific action) because (reason backed by your data).FFresh
0%dateModified ≤90d (schema)=✗ · Last-Modified header ≤90d=✗ · visible "updated YYYY" text=✗
Fix: Add dateModified to schema; serve Last-Modified header; render visible "Last verified YYYY-MM-DD" near content.
📋 Add visible "Last verified" stamp near contenthtml
<p class="text-xs text-gray-500">
Last verified <time datetime="2026-06-28">2026-06-28</time>
</p>📋 Add datePublished + dateModified to Article/WebPage schemajson-ld
{
"@type": "WebPage",
"datePublished": "2026-01-15",
"dateModified": "2026-06-28"
}📋 Set HTTP Last-Modified response header (web framework-specific)text
# Express / Node:
res.setHeader('Last-Modified', new Date().toUTCString());
# Next.js middleware (middleware.ts):
import { NextResponse } from 'next/server';
export function middleware() {
const res = NextResponse.next();
res.headers.set('Last-Modified', new Date().toUTCString());
return res;
}BTransactable
75%6 affordance keywords · mailto=✗ · contact/pricing/signup link=✓
Fix: Make the citation actionable: clear CTA, contact page, pricing, or mailto. Visitors who arrive from an LLM citation should be able to act.
📋 Add a visible mailto contact (LLM citation arrivals need somewhere to act)html
<a href="mailto:contact@stripe.com">contact@stripe.com</a>Prioritized fixes with copy-paste code
Ordered by impact across both axes. Top 6. Click the snippet rows to expand the exact code to copy.
- high[credible] Add Person schema with sameAs[] (≥2 profiles). Link /about + /methodology in nav/footer. Add datePublished + dateModified to Article schema.Lifts Credible from 0.00 → 1.00 (gap 1.00).
📋 Add Person schema (operator/author identity)json-ld
{ "@context": "https://schema.org", "@type": "Person", "@id": "https://stripe.com/about#author", "name": "(your full name — operator or primary author)", "jobTitle": "Founder", "url": "https://stripe.com/about", "sameAs": [ "https://twitter.com/YOUR_HANDLE", "https://www.linkedin.com/in/YOUR_HANDLE", "https://github.com/YOUR_HANDLE" ], "worksFor": { "@id": "https://stripe.com#org" } }📋 Add datePublished + dateModified to your Article/WebPage schemajson-ld
"datePublished": "2026-01-15", "dateModified": "2026-06-28" - medium[differentiated] Add explicit POV sentences ("Our view: …", "We measured …", "We recommend …"). LLMs cite pages with stance more than encyclopedic neutrality.Lifts Differentiated from 0.00 → 1.00 (gap 1.00).
📋 Add explicit POV sentences in the body text (LLMs cite pages with stance more than neutral encyclopedic content)markdown
> Our view: (your specific stance on the topic this page covers) > We measured (a number you actually measured) and found (insight). > We recommend (specific action) because (reason backed by your data). - medium[fresh] Add dateModified to schema; serve Last-Modified header; render visible "Last verified YYYY-MM-DD" near content.Lifts Fresh from 0.00 → 1.00 (gap 1.00).
📋 Add visible "Last verified" stamp near contenthtml
<p class="text-xs text-gray-500"> Last verified <time datetime="2026-06-28">2026-06-28</time> </p>📋 Add datePublished + dateModified to Article/WebPage schemajson-ld
{ "@type": "WebPage", "datePublished": "2026-01-15", "dateModified": "2026-06-28" }📋 Set HTTP Last-Modified response header (web framework-specific)text
# Express / Node: res.setHeader('Last-Modified', new Date().toUTCString()); # Next.js middleware (middleware.ts): import { NextResponse } from 'next/server'; export function middleware() { const res = NextResponse.next(); res.headers.set('Last-Modified', new Date().toUTCString()); return res; } - medium[extractable] Rewrite H2 headings as quote-ready sentences (≥5 words, descriptive). Add DefinedTerm schema for key concepts. ≤1 FAQ block per page.Lifts Extractable from 0.40 → 1.00 (gap 0.60).
📋 Rewrite these 1 H2 heading(s) so LLM crawlers can quote them as standalone sentences (target ≥25 chars + ≥5 words)text
BEFORE: <h2>What’s happening</h2> AFTER: <h2>What’s happening — [add 2-4 descriptive words so it reaches ≥5 words + ≥25 chars]</h2>📋 Add DefinedTermSet schema for your key concepts (lifts Extractable +0.30)json-ld
{ "@context": "https://schema.org", "@type": "DefinedTermSet", "@id": "https://stripe.com/#glossary", "name": "(your concept area) Glossary", "url": "https://stripe.com/glossary", "hasDefinedTerm": [ { "@type": "DefinedTerm", "name": "(Term 1)", "description": "(1-2 sentence definition)", "inDefinedTermSet": "https://stripe.com/#glossary" }, { "@type": "DefinedTerm", "name": "(Term 2)", "description": "(1-2 sentence definition)", "inDefinedTermSet": "https://stripe.com/#glossary" } ] }📋 Optional: add ONE FAQPage block per page (>1 triggers schema-spam penalty)json-ld
{ "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "What does this site do?", "acceptedAnswer": { "@type": "Answer", "text": "(answer in 1-3 sentences)" } }, { "@type": "Question", "name": "How is this different from alternatives?", "acceptedAnswer": { "@type": "Answer", "text": "(answer in 1-3 sentences)" } } ] } - medium[corroborated] Cite ≥3 authoritative sources (gov/edu/wikipedia/standards bodies/peer-reviewed). Build off-site presence (Wikipedia citation, Reddit organic, LinkedIn).Lifts Corroborated from 0.25 → 1.00 (gap 0.75).
📋 Add ≥3 outbound links to authoritative sources matching your topichtml
<!-- Pick 3-5 sources relevant to your domain. Examples by topic: --> <!-- Web performance / dev --> <a href="https://web.dev/articles/vitals">web.dev Core Web Vitals</a> <a href="https://developer.mozilla.org/en-US/docs/Web/Performance">MDN Web Performance</a> <a href="https://developer.chrome.com/docs/crux/">Chrome UX Report</a> <!-- Schema / standards --> <a href="https://schema.org/Organization">schema.org reference</a> <a href="https://w3.org/TR/">W3C specifications</a> <!-- Health / science --> <a href="https://www.nih.gov/health-information">NIH Health Info</a> <a href="https://www.cdc.gov/">CDC</a> <a href="https://pubmed.ncbi.nlm.nih.gov/">PubMed</a> <!-- Finance / business --> <a href="https://www.sec.gov/edgar.shtml">SEC EDGAR</a> <a href="https://www.federalreserve.gov/">Federal Reserve</a> - low[transactable] Make the citation actionable: clear CTA, contact page, pricing, or mailto. Visitors who arrive from an LLM citation should be able to act.Lifts Transactable from 0.75 → 1.00 (gap 0.25).
📋 Add a visible mailto contact (LLM citation arrivals need somewhere to act)html
<a href="mailto:contact@stripe.com">contact@stripe.com</a>
Share or embed
Free to embed. The widget links back to vitalslens.com so we can keep the audit free.
Embed snippet
<iframe src="https://webvitalstool.com/embed/audit?url=stripe.com" width="100%" height="640" frameborder="0" loading="lazy" title="VitalsLens audit · stripe.com"></iframe>
Want fleet monitoring across multiple URLs? VitalsLens Pro — €19/mo.