AvocadoScore audit · linear.app
linear.app
Performance needs significant, prioritized work across the site.
Fix this firstUnblock the initial rendercritical · medium effort · 3 pagesThis verdict weights real-user data (Chrome UX Report). Cold lab first-visits shown below run slower.
- Mobile perfMedian Google Lighthouse Performance score across scanned pages, mobile viewport. 90+ excellent · 50–89 needs work · under 50 poor.
- 44/100Unripe
- SEO readyComposite of 12 SEO health checks on the homepage: HTTPS, title, meta description, structured data, Open Graph, canonical, H1, viewport, etc.
- 92/100Ripe
- AI readyComposite of 17 AI-readiness checks across three pillars. Access: robots.txt policies for 10 AI crawlers (citation vs training), CDN/firewall gates, snippet directives. Comprehension: llms.txt, validated structured data, server-rendered content, heading outline. Trust: author/organization provenance, content dates.
- 76/100Almost ripe
Scanned 11 days ago3 pagesNumber of pages successfully scanned. Free preview scans 3 pages; the paid Full audit covers up to 100.4 views
What you’re not seeing yet
Your 3 sampled pages averaged 44 on mobile performance — we don’t know which of the other 929 pages are dragging that median. The full audit scans up to 100 of your most important pages so you can find the templates costing you traffic.
Pages we found but didn’t scan
7-day refund · no questions
Overview
Key findings
The headline takeaways, in plain English.
- 1In cold lab tests, 3 of 3 scanned pages render in the "Unripe" band (the overall verdict above weights real-user data, which is faster).
- 2Median mobile LCP is 11.2 s — about 4.5× the 2.5 s target.
- 3The biggest opportunity: Set long cache lifetimes for static assets — affects 3 pages.
- 4The heaviest page ships 1.5 MB of JavaScript — a primary cause of slow loads.
- 5Strengths: accessibility, SEO and best practices score well — focus effort on performance.
AI & search visibility
Can AI answer engines find, read and cite your site?
More people now ask ChatGPT, Perplexity and Claude instead of Googling. This section answers whether those answer engines can reach your content, understand it, and cite you — the audit other tools skip.
AI agents can read your site; a few quick additions would make it easier to cite.
Fix next: add structured data — see the action plan for copy-paste fixes.
OG image qualityOpen Graph image is the thumbnail shown anywhere your page is shared — Slack, LinkedIn, iMessage, Discord. Many LLM answer interfaces use it too.
https://linear.app/static/og/homepage.jpg

- ✓ReachableHTTP 200
- ✓Content-Typeimage/jpeg
- ✓File size270.5 KB
Crawl-as-bot diffWe fetch your homepage twice — once with a regular browser UA, once claiming to be GPTBot — and compare the content each receives. Big drops mean LLM crawlers see a stripped page.
Homepage · GPTBot UA
GPTBot sees 9,258 chars · browser sees 9,215 chars
GPTBot sees 100% of the content a browser sees — essentially identical.
llms.txt contentllms.txt is the emerging standard (https://llmstxt.org) — a short markdown file at the site root that LLM answer engines pull as a 'site map for AI'.
145 links · 2 sections
- ✓/llms.txt presentHTTP 200
- ✓Has main heading# Title found
- ✓Link coverage145 markdown links
- ✓Sections2 `##` sections
- ✓/llms-full.txtHTTP 200 — richer LLM context
Robots.txt advisorrobots.txt tells crawlers (Google, GPTBot, ClaudeBot…) which paths they may visit and where to find your sitemap. Misconfigurations here invisibly tank crawling.
1 group · 1 sitemap ref
- ✓robots.txt present1 user-agent group
- ✓Allows crawlers`User-agent: *` permits standard crawling
- ✓Sitemap declared1 sitemap ref
- ✕AI bot policiesNo explicit policy for GPTBot, ClaudeBot, Google-Extended, etc. — decide and declare
- ✓Crawl-delayNo crawl-delay — crawlers use their own pacing
Readiness
SEO & AI Readiness
Two scorecards derived from the homepage HTML, robots.txt and AI-specific well-known files. The differentiating analysis no other tool does.
A few readiness gaps to close — the checklists below name what’s missing or weak on the homepage and in robots.txt.
SEO checklist
11/12 passing- ✕Structured data (JSON-LD)No JSON-LD — search engines lose rich-result context
▸ 11 passing checks — show all
- ✓HTTPSServed over HTTPS
- ✓Sitemapsitemap.xml present
- ✓robots.txtPresent
- ✓Title tag43 chars
- ✓Meta description64 chars
- ✓Canonical URLhttps://linear.app
- ✓Open GraphComplete (title, description, image)
- ✓Twitter Cardsummary_large_image
- ✓H1 headingExactly one H1
- ✓Language declaration<html lang="en">
- ✓Viewport metaSet
AI readiness — three pillars
10/17 passingCan AI crawlers fetch the site at all?
Once fetched, can they parse and chunk it?
Can they attribute and date the content?
Access — Can AI crawlers fetch the site at all?
3/5 passing- !AI answer-engine accessOAI-SearchBot, ChatGPT-User, Claude-User, PerplexityBot, Perplexity-User are restricted in robots.txt — ChatGPT search, Perplexity and Claude can't read or cite the site through these crawlers
- !Search-index crawlers (AI surfaces)Googlebot, Bingbot partially restricted — AI surfaces built on these indexes see a reduced site
▸ 3 passing checks — show all
- ✓Training-crawler stanceNo training opt-outs declared — content may be used for model training (5 tokens checked)
- ✓CDN / firewall gateGPTBot sees 100% of the content a browser sees — essentially identical.
- ✓Snippet directivesNo nosnippet / max-snippet / noai restrictions
Comprehension — Once fetched, can they parse and chunk it?
7/10 passing- ✕Structured data (validated)No JSON-LD — answer engines have nothing structured to parse
- !Heading outlineLevel skips (H1→H3) — broken hierarchy confuses chunk-based retrieval
- !RSS/Atom feedNo feed advertised in <head> — several AI systems ingest feeds for freshness
▸ 7 passing checks — show all
- ✓/llms.txtPresent — AI-friendly content map
- ✓/llms-full.txtPresent — expanded LLM context
- ✓Server-rendered content35437 words in initial HTML
- ✓Semantic HTMLUses main, header, footer, nav
- ✓Open Graph metadataComplete
- ✓Sitemap freshnesssitemap.xml carries <lastmod> dates — recrawl prioritization works
- ✓Consent wallNo consent-manager wall detected
Trust — Can they attribute and date the content?
0/2 passing- !Author / Organization markupNo Person/Organization schema or <meta name="author">
- !Content datesNo datePublished/dateModified in structured data — answer engines can't judge freshness
AI bot policies (robots.txt)
10 bots tracked▸ Show all 10 bots
| Bot | Vendor | Role | Status |
|---|---|---|---|
| GPTBot | OpenAI | trainingModel-training opt-out token — blocking it protects IP and does NOT affect AI-search citations. | MixedMixed — some paths allowed, others disallowed for this bot. |
| OAI-SearchBot | OpenAI | citationLive retrieval/citation crawler — blocking it removes the site from AI answers. | MixedMixed — some paths allowed, others disallowed for this bot. |
| ChatGPT-User | OpenAI | citationLive retrieval/citation crawler — blocking it removes the site from AI answers. | MixedMixed — some paths allowed, others disallowed for this bot. |
| ClaudeBot | Anthropic | trainingModel-training opt-out token — blocking it protects IP and does NOT affect AI-search citations. | MixedMixed — some paths allowed, others disallowed for this bot. |
| Claude-User | Anthropic | citationLive retrieval/citation crawler — blocking it removes the site from AI answers. | MixedMixed — some paths allowed, others disallowed for this bot. |
| Google-Extended | trainingModel-training opt-out token — blocking it protects IP and does NOT affect AI-search citations. | MixedMixed — some paths allowed, others disallowed for this bot. | |
| PerplexityBot | Perplexity | citationLive retrieval/citation crawler — blocking it removes the site from AI answers. | MixedMixed — some paths allowed, others disallowed for this bot. |
| Perplexity-User | Perplexity | citationLive retrieval/citation crawler — blocking it removes the site from AI answers. | MixedMixed — some paths allowed, others disallowed for this bot. |
| Applebot-Extended | Apple | trainingModel-training opt-out token — blocking it protects IP and does NOT affect AI-search citations. | MixedMixed — some paths allowed, others disallowed for this bot. |
| CCBot | Common Crawl | trainingModel-training opt-out token — blocking it protects IP and does NOT affect AI-search citations. | MixedMixed — some paths allowed, others disallowed for this bot. |
Declare a policy either way so the intent is clear — see the action plan for a copy-paste robots.txt block.
Readiness is sampled on the site homepage; deeper pages may differ. AI bot policies follow the llms.txt proposal and the established robots.txt convention.
Deep dive
Performance analysis
Where this site stands against its peers, which viewport is the weak link, the slowest pages, and the issues that recur most.
Performance vs peersEstimated percentile rank of this site's average mobile performance score within its peer group, assuming a roughly normal spread. A rough positioning estimate, not a precise figure.
At 44/100, this site is below the Next.js site (peer median 55).
Mobile vs desktopAverage mobile vs desktop Lighthouse performance across scanned pages. Mobile almost always lags; a large gap means mobile users get a much worse experience than desktop testing suggests.
Mobile runs 29 points behind desktop — most of the slowness lives on phones.
- /about46 → 84 −38
- /contact55 → 80 −25
- /32 → 54 −22
Slowest pagesThe scanned pages with the highest mobile Largest Contentful Paint — your slowest-loading pages, where optimization pays off most.
- 114.4 s/perf 32/100
- 211.2 s/aboutperf 46/100
- 310.2 s/contactperf 55/100
Ranked by mobile LCP (Largest Contentful Paint).
Most frequent issuesHow often each issue recurs across the scanned pages. Fixing a high-frequency issue once at the template level often resolves it everywhere.
- Minimize main-thread work3 pages · 100%
- Render-blocking requests3 pages · 100%
- Background and foreground colors do not have a sufficient contrast ratio.3 pages · 100%
- Buttons do not have an accessible name3 pages · 100%
- Document does not have a meta description3 pages · 100%
- Forced reflow3 pages · 100%
- Issues were logged in the `Issues` panel in Chrome Devtools3 pages · 100%
- Missing source maps for large first-party JavaScript3 pages · 100%
Core Web Vitals
How fast your site really is
Real-user experience from the Chrome UX Report (p75, 28-day window). Lab metrics below show cold first-visit timings.
Page Weight
Resource breakdown
Pages average 2.9 MB across 301 requests. Third-party scripts add 0 B on top.
- JavaScript1.1 MB39%
- Images183 KB6%
- CSS106 KB4%
- Fonts398 KB13%
- Other1.1 MB38%
Heaviest page: / at 4.2 MB over 406 requests.
Deep dive
Resource intelligence
Where time and bytes are going across your site — the specific vendors and code paths behind the totals.
Main-thread time
Average per page · 3.9 s- Script evaluation1.3 s34%
- Other1.3 s34%
- Script parse / compile422 ms11%
- Style + layout337 ms9%
- Garbage collection225 ms6%
- Parse HTML165 ms4%
- Paint + composite73 ms2%
Image format breakdown
100% modern (WebP / AVIF)- avif549 KB
Technology
Detected stack
What we recognised from the homepage HTML, response headers and DNS. Used to tailor stack-specific recommendations.
Site health
Security, compression and SEO hygiene
Headers, compression and cross-page duplicates checked on the homepage. These are the basics a professional site is expected to get right.
Security headersScore across 6 OWASP-baseline HTTP response headers on the homepage. 100 = all present with strong values; 0 = none set.
8 pass · 2 warn · 0 fail
- ✓Strict-Transport-SecurityHSTS — tells browsers "only use HTTPS for this domain." Without it, a man-in-the-middle can downgrade users to HTTP on first visit.max-age=63072000 · includeSubDomains
- !Content-Security-PolicyCSP — first-line defence against XSS and data-injection. Defines which scripts/styles/images can load and from where.Present but uses 'unsafe-inline' or 'unsafe-eval' — weakens protection
- ✓X-Frame-OptionsPrevents your pages being embedded in <iframe> on someone else's site (clickjacking protection).Equivalent CSP frame-ancestors directive present
- ✓X-Content-Type-OptionsStops browsers from MIME-sniffing — keeps untrusted uploads from being executed as scripts.nosniff
- ✓Referrer-PolicyControls how much of the referring URL leaks to third parties. Default leaks the full URL including paths and query.same-origin
- !Permissions-PolicyRestricts which browser features (camera, geolocation, payment) the page may use.Missing — no explicit restriction on browser features (camera, geo, etc.)
- ✓Exposed secretsNo live API keys or private keys found in the served HTML
- ✓Mixed contentNo insecure http:// subresources on the page
- ✓Outdated JS librariesNo known-vulnerable library versions detected in page scripts
- ✓Cookie security flagsNo cookies set on the homepage response
Compression & cacheHow the homepage HTML is delivered: which compression encoding the server used (Brotli > gzip > none) and whether Cache-Control is set sensibly.
Action Plan
What to fix
Root-cause groupings, sequenced by effort. Each card opens a ready-to-paste task you can create in Jira or Linear with one click.
- 01Set long cache lifetimes for static assets⚡ quick win
- 02Fix crawlability issues⚡ quick win
- 03Address accessibility gaps⚡ quick win
- 04Unblock AI answer-engine crawlers in robots.txt⚡ quick win
- 01Unblock the initial render
- 02Right-size and modernize images
- 03Add Schema.org structured data
- 04Reduce total page weight
- 01Cut and defer JavaScript
Unblock the initial render
CSS and JavaScript in the critical path delay first paint — visitors stare at a blank screen, and Largest Contentful Paint (a Google ranking signal) suffers.
Impact — Largest Contentful Paint is a Google ranking signal. Sites in the slowest quartile of their category see 30–50% less organic search traffic than faster peers.
- ·Render-blocking requests — Est savings of 3,830 ms
- ·Reduce unused CSS — Est savings of 74 KiB
- ·Minify CSS — Est savings of 19 KiB
▸ Steps (4)
- 1.Inline critical above-the-fold CSS and defer the rest.
- 2.Add async or defer to render-blocking scripts.
- 3.Preload the LCP image and key fonts so the browser discovers them early.
- 4.Remove unused CSS rules from above-the-fold stylesheets.
- For your stack
- 1.Use next/font so fonts do not block render.
- 2.Avoid importing large global CSS; prefer per-component styles.
Cut and defer JavaScript
Large scripts block the browser’s main thread, so the page looks loaded but does not respond to taps or clicks. This is the most common cause of a slow mobile experience and directly drives up bounce rate.
Impact — Heavy JavaScript is the #1 driver of slow mobile sites — 53% of mobile users abandon pages that take longer than 3 seconds to load (Google mobile-speed research).
- ·Minimize main-thread work — 5.6 s
- ·Reduce unused JavaScript — Est savings of 174 KiB
- ·Reduce JavaScript execution time — 2.0 s
- ·Legacy JavaScript — Est savings of 9 KiB
▸ Steps (4)
- 1.Audit the bundle to find the largest dependencies (a bundle analyzer or source-map-explorer).
- 2.Code-split so route- and below-the-fold code loads on demand instead of upfront.
- 3.Remove or replace heavy third-party scripts; load non-critical ones with async/defer or after first interaction.
- 4.Drop legacy polyfills and transpilation targets that modern browsers no longer need.
- For your stack
- 1.Use next/dynamic to lazy-load heavy components.
- 2.Run @next/bundle-analyzer to find oversized chunks.
- 3.Set a modern browserslist so Next.js stops shipping legacy transforms.
Set long cache lifetimes for static assets
Without long cache headers, repeat visitors re-download assets that never changed — slower return visits and wasted bandwidth.
Impact — Returning visitors slow their own experience without caching. Small fix, compounding gain: every repeat visit benefits.
- ·Use efficient cache lifetimes — Est savings of 88 KiB
▸ Steps (3)
- 1.Set Cache-Control: max-age of up to a year for fingerprinted static assets.
- 2.Use content hashing in filenames so you can cache aggressively and still ship updates.
- 3.Configure caching at the CDN or host layer rather than per request.
Fix crawlability issues
If search engines cannot follow your links or understand their text, pages will not be discovered or rank — directly capping organic traffic.
Impact — Crawlability issues directly cap organic search traffic. Search engines cannot rank what they cannot follow or understand.
▸ Steps (3)
- 1.Use real <a href> elements for navigation, not click handlers on <div>s.
- 2.Give links descriptive text instead of “click here” or “read more”.
- 3.Ensure important pages are linked from somewhere crawlable.
Address accessibility gaps
Accessibility issues exclude users of assistive technology and create legal exposure (ADA / European Accessibility Act). Many fixes also help SEO.
Impact — About 15% of users have a disability (WHO). Accessibility gaps both exclude these users and create ADA/EAA compliance risk in the US and EU.
▸ Steps (3)
- 1.Give interactive elements and dialogs accessible names (aria-label or visible text).
- 2.Ensure every meaningful image has descriptive alt text.
- 3.Check color contrast meets WCAG AA.
Unblock AI answer-engine crawlers in robots.txt
These are not training bots — they are the live retrieval crawlers ChatGPT search, Perplexity and Claude use to read a page before citing it in an answer. Blocking them removes the site from AI answers entirely, while training opt-outs (GPTBot, CCBot…) can stay blocked with no citation impact.
Impact — Buyers increasingly ask ChatGPT, Perplexity and Claude for recommendations. A site these crawlers cannot read cannot be cited — the traffic goes to a competitor whose site they can.
- ·Blocked/restricted: OAI-SearchBot, ChatGPT-User, Claude-User, PerplexityBot, Perplexity-User
User-agent: OAI-SearchBot Allow: / User-agent: ChatGPT-User Allow: / User-agent: Claude-User Allow: / User-agent: PerplexityBot Allow: / User-agent: Perplexity-User Allow: /
▸ Steps (3)
- 1.Open robots.txt and find the rules covering the blocked crawlers below.
- 2.Allow the search/citation crawlers (keep training-bot blocks if IP protection is the goal — they are separate tokens).
- 3.Deploy and verify with the free readiness checker.
Right-size and modernize images
Oversized images waste bandwidth and slow the largest element on the page. On mobile connections this is often the single biggest load-time cost.
Impact — Images account for roughly 25% of an average mobile page (HTTP Archive). Every MB of unoptimized images adds 1–2 seconds of mobile load time.
- ·Improve image delivery — Est savings of 244 KiB
▸ Steps (4)
- 1.Serve images at the dimensions they are displayed, with srcset for different screen sizes.
- 2.Use modern formats (WebP/AVIF) with fallbacks.
- 3.Lazy-load below-the-fold images.
- 4.Compress images — aim well under 200 KB for most photos.
- For your stack
- 1.Use the next/image component — it handles sizing, modern formats and lazy-loading automatically.
Add Schema.org structured data
Schema.org JSON-LD tells search engines and answer engines what each page is — an Organization, an Article, a Product, an FAQ. Pages with structured data earn richer search results and are easier for LLMs to summarize and cite accurately.
Impact — Structured data is a low-risk SEO and AI-visibility win: it doesn’t change your design but materially improves how engines understand and present your pages.
- ·No JSON-LD structured data found on any scanned page
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "linear.app",
"url": "https://linear.app",
"logo": "https://linear.app/logo.png",
"sameAs": [
"https://www.linkedin.com/company/your-company",
"https://twitter.com/your-handle"
]
}
</script>▸ Steps (4)
- 1.Add an Organization + WebSite schema to your homepage (identity for the whole site).
- 2.Add BreadcrumbList to section pages so engines understand your hierarchy.
- 3.Add page-type schema where it fits — Article/BlogPosting on posts, FAQPage on Q&A, Product on product pages.
- 4.Validate with Google’s Rich Results Test before shipping.
Reduce total page weight
Heavy pages cost real money for users on metered mobile data and load slowly on weak connections — a meaningful share of every site’s traffic.
Impact — Every additional megabyte of page weight typically adds 1–2 seconds of mobile load time on a slow connection (HTTP Archive).
- ·Avoid enormous network payloads — Total size was 4,280 KiB
▸ Steps (3)
- 1.Enable text compression (Brotli or Gzip) for all text assets.
- 2.Trim the largest payloads — usually JavaScript and images.
- 3.Remove unused third-party embeds and scripts.
Shipped a fix? Open the task list or hit ↻ Re-scan in the header — the comparison shows what moved.
Detail
Per-page results
Mobile metrics shown. Click a row for the full per-page deep dive — LCP element, page weight breakdown, top failing checks.
| Page | PerfMobile Performance score (0–100). | LCPLargest Contentful Paint — when the biggest visible element finishes rendering. Lab value. Target ≤ 2.5 s. | CLSCumulative Layout Shift — total visual jank during load. Unitless. Target ≤ 0.1. | TBTTotal Blocking Time — total main-thread blocking time during load. Target ≤ 200 ms. | WeightTotal page transfer size — HTML + CSS + JS + images + fonts. |
|---|---|---|---|---|---|
| /→ | 32 | 14.4 s | 0.000 | 1.2 s | 4.2 MB |
| /about→ | 46 | 11.2 s | 0.000 | 461 ms | 2.3 MB |
| /contact→ | 55 | 10.2 s | 0.000 | 159 ms | 2.3 MB |
3 of 3 pages scanned successfully. Each row links to the full per-page report with mobile + desktop side by side.
Coverage
Scan coverage
Pages were discovered via sitemap and sampled across URL patterns. Issues found on a sampled page very likely affect the rest of its pattern group.
Discovery & sampling detail▸
Coverage
Scan coverage
Pages were discovered via sitemap and sampled across URL patterns. Issues found on a sampled page very likely affect the rest of its pattern group.
- Discovered
- 932
- Sampled
- 3
- Scanned OK
- 3
- Failed
- 0
Methodology
How we measured this
Every page measured with Google PageSpeed Insights (1 run per page per viewport — quick scan). Real-user data, where shown, comes from the Chrome UX Report.
- ▸Lab data is a cold first visit from Google's US infrastructure; real users with warm caches and in other regions will differ.
- ▸Mobile is emulated on throttled slow-4G; desktop is unthrottled. Only public pages are scanned.
- ▸Quick scan (1 run/page) — upgrade to a paid scan for median-of-3 accuracy.
Full deep-dive on every check at /methodology.
Share
Embed this badge anywhere
A live SVG badge — embeds in your README, site footer, or blog post. Updates whenever you re-scan.
Public report URL
https://avocadoscore.io/r/8ccaeca5-5b95-4b52-9e05-e3defe5a4f62Markdown (for README)
[](https://avocadoscore.io/r/8ccaeca5-5b95-4b52-9e05-e3defe5a4f62)HTML (for site footer)
<a href="https://avocadoscore.io/r/8ccaeca5-5b95-4b52-9e05-e3defe5a4f62"><img src="https://avocadoscore.io/api/scans/8ccaeca5-5b95-4b52-9e05-e3defe5a4f62/badge?metric=verdict" alt="AvocadoScore — overall verdict" /></a>Next Steps
Where to go from here
- 1Start this week. Knock out the 4 quick wins from the Action Plan — small effort, immediate gain.
- 2Re-scan after each round of fixes. Hit Re-scan in the header after each round — the comparison shows what moved and what didn’t.
Free preview · 3 of 932 pages
Want this depth on every page?
You've seen the format. The Full audit takes the same lens across 929 more pages you can't see yet — and ships the result as one ranked fix list your engineer can act on.
- Median of 3 PageSpeed runs per page (vs 1 in the preview) — stable numbers you can ship from
- Up to 100 pages — covers /pricing, /checkout, and every template that matters
- Per-page deep dives: LCP element, named offenders, third-party impact
- Plain-English fix list with effort estimates in dev-weeks
- 3 free re-runs included — re-scan after every release at no extra cost
- 7-day refund, no questions, no “please tell us why”
One-time · No subscription · 7-day refund