SEO report for www.chakra.dev
https://www.chakra.dev/ · checked Wed, 11 Nov 2026 19:45 GMT
Fix these first
- Entity clarityhigh
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- JSON-LD present & validhigh
No JSON-LD structured data.
Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).
- H1 headingcritical
2 H1 headings – one clear H1 is best practice.
Fix: Use one H1 that states the page topic with its main keyword.
- Heading structuremedium
53 headings for 1094 words – a lot for the amount of text.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- Question-led contentmedium
No headings phrased as questions.
Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.
- Trust pages (E-E-A-T)medium
Links found to privacy; missing about and contact.
Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.
- HTML sizemedium
487 kB of HTML – heavy for phones.
Fix: Remove inline bloat, base64 images and unused markup.
- Image alt textmedium
3 of 3 images have no alt attribute.
Fix: Describe each meaningful image in its alt attribute (use alt="" for decorative ones).
Real-world speed Google PageSpeed
Loading Core Web Vitals from Google… this can take up to 30 seconds.
Authority & backlinks
Looking up which websites link to chakra.dev…
Indexing & crawling 100%
Can search engines reach, read and index this page?
- ✓
Status codecritical
The page returned HTTP 200.
- ✓
Indexablecritical
No noindex instruction – the page can appear in search.
- ✓
robots.txthigh
robots.txt found.
Googlebot is allowed to crawl this page.
- ✓
XML sitemaphigh
Sitemap found at https://www.chakra.dev/sitemap.xml with 8 URLs.
Declared in robots.txt.
This page is listed in it.
No lastmod dates – add accurate ones so search engines know what changed.
- ✓
Canonical URLhigh
Canonical: https://www.chakra.dev/
Points to this page (self-referencing).
- ✓
Redirectshigh
1 redirect before the page loaded.
https://chakra.dev/ → https://www.chakra.dev/
A single redirect to your preferred address is normal; just make sure your own links use the final address.
- ✓
www / non-wwwmedium
chakra.dev redirects to www.chakra.dev.
Search snippet & sharing 100%
How the page looks in Google results and when shared.
- ✓
Title tagcritical
“Expert-Authored Tasks and Benchmarks for Frontier AI | Chakra”
About 569px of Google's ~580px desktop width.
- ✓
Meta descriptionhigh
125 characters, ~774px of ~990px.
Good length.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="en"
Content quality 57%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
1,094 words of main content (menus and footer excluded).
Google has no minimum word count – this is a rough guide to whether the page answers the question in full.
- !
Readabilitymedium
Flesch reading ease 34 (fairly difficult), about 13 words per sentence.
Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.
- ✓
Topic focushigh
5 of 5 title keywords appear in the main content.
- !
H1 headingcritical
2 H1 headings – one clear H1 is best practice.
The H1 shares no keywords with the title.
Fix: Use one H1 that states the page topic with its main keyword.
- ✗
Heading structuremedium
53 headings for 1094 words – a lot for the amount of text.
11 skipped level(s), e.g. H2 → H4.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- ✗
Text-to-code ratiolow
1% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 50%
Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?
- ✓
AI crawler accesshigh
Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.
- ✓
Snippet controlshigh
No snippet restrictions – search and AI answers can quote this page.
- ✗
llms.txtlow
No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.
Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.
- ✗
Question-led contentmedium
No headings phrased as questions.
Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.
- ✗
Entity clarityhigh
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- ✓
Freshness signalsmedium
The page shows when it was published or last updated.
- ✗
Trust pages (E-E-A-T)medium
Links found to privacy; missing about and contact.
Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.
Structured data 0%
Machine-readable facts for rich results and AI.
- ✗
JSON-LD present & validhigh
No JSON-LD structured data.
Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).
Links 100%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
24 internal and 7 external links.
- ✓
Anchor text qualitymedium
No link text points to two different pages.
- ✓
Broken links (sample)high
Checked 8 internal link(s).
No broken links found.
Performance 72%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
237 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
- ✗
HTML sizemedium
487 kB of HTML – heavy for phones.
Fix: Remove inline bloat, base64 images and unused markup.
- ✓
Compressionmedium
Compressed with br.
- ✓
Render-blocking resourceshigh
0 blocking script(s) and 0 stylesheet(s) in <head>.
- !
Scripts & third partiesmedium
12 script tag(s); files loaded from 4 other domain(s): framerusercontent.com, googletagmanager.com, events.framer.com, customer-mb33ed4q3zhr0if9.cloudflarestream.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- !
Imagesmedium
3 image(s).
All images reserve their space.
The first image is lazy-loaded – if it's the main (LCP) image, that delays it. Don't lazy-load images visible on arrival.
3 use WebP/AVIF or responsive srcset.
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
- !
Cachinglow
Cache-Control: public, max-age=0, must-revalidate
Fix: Set Cache-Control so browsers and CDNs can reuse the page.
- ✓
HTTP/3low
Server advertises HTTP/3 (faster on mobile networks).
Security 92%
Visitor safety signals that browsers and Google check.
- ✓
HTTPScritical
Secure HTTPS with no mixed content.
- ✓
HTTP → HTTPS redirecthigh
http:// redirects to https://.
- ✓
HSTSmedium
HSTS: max-age=31536000
- ✗
Security headerslow
Present: nosniff.
Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).
- ✓
Server fingerprintlow
No X-Powered-By header (server: cloudflare).
Mobile & accessibility 67%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width
- ✗
Image alt textmedium
3 of 3 images have no alt attribute.
Fix: Describe each meaningful image in its alt attribute (use alt="" for decorative ones).
- ✗
Form labelsmedium
11 of 12 form field(s) have no label.
Fix: Give every form field a <label> or aria-label (a placeholder isn't a label).
- ✓
Link nameslow
Every link has a readable name.
- ✓
Tap-to-contactmedium
One-tap contact: email.
Local SEO not scored
This site doesn't look like a local business, so these checks are shown for information and not scored.
- i
LocalBusiness markuphigh
No LocalBusiness structured data.
- ✓
Contact details on pagemedium
No phone number found.
No postcode found (fine for service-area businesses).
An email link is shown.
- i
Map & directionslow
No map or directions link.