SEO report for www.pixiebrix.com
https://www.pixiebrix.com/ · checked Wed, 04 Nov 2026 22:37 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).
- Render-blocking resourceshigh
2 blocking script(s) and 3 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- H1 headingcritical
12 H1 headings – one clear H1 is best practice.
Fix: Use one H1 that states the page topic with its main keyword.
- Heading structuremedium
83 headings for 1396 words – a lot for the amount of text.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- Anchor text qualitymedium
Same text used for different pages: “book demo”, “read the case study”.
Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.
- Scripts & third partiesmedium
41 script tag(s); files loaded from 8 other domain(s): cdn.prod.website-files.com, ajax.googleapis.com, cdn.jsdelivr.net, cdnjs.cloudflare.com, unpkg.com, googletagmanager.com….
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
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 pixiebrix.com…
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.pixiebrix.com/sitemap.xml with over 6,712 URLs (we read the first 1 MB).
Declared in robots.txt.
This page is listed in it.
Most recent lastmod: 2026-11-03T15:31:07.495Z.
- ✓
Canonical URLhigh
Canonical: https://www.pixiebrix.com
Points to this page (self-referencing).
- ✓
Redirectshigh
1 redirect before the page loaded.
https://pixiebrix.com/ → https://www.pixiebrix.com/
A single redirect to your preferred address is normal; just make sure your own links use the final address.
- ✓
www / non-wwwmedium
pixiebrix.com redirects to www.pixiebrix.com.
Search snippet & sharing 88%
How the page looks in Google results and when shared.
- ✓
Title tagcritical
“PixieBrix: Agent Activity. Real-Time Enforcement. One Platform.”
About 567px of Google's ~580px desktop width.
- !
Meta descriptionhigh
257 characters, ~1598px of ~990px.
Long – Google will probably truncate it.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
Fix: Write a 140–155 character description that answers the searcher's question and invites the click.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="en"
Content quality 67%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
1,396 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 50 (fairly easy), about 10 words per sentence.
- ✓
Topic focushigh
7 of 7 title keywords appear in the main content.
- !
H1 headingcritical
12 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
83 headings for 1396 words – a lot for the amount of text.
11 skipped level(s), e.g. H2 → H4.
2 empty heading(s).
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- !
Text-to-code ratiolow
9% 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
1 heading(s) phrased as questions, e.g. “Ready for security and productivity at scale?”.
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
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- !
Trust pages (E-E-A-T)medium
Links found to contact and privacy; missing about.
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 75%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
48 internal and 14 external links.
- ✗
Anchor text qualitymedium
Same text used for different pages: “book demo”, “read the case study”.
1 vague link(s) like “click here” or “read more”.
8 link(s) with no text at all.
Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.
- ✓
Broken links (sample)high
Checked 12 internal link(s).
No broken links found.
Performance 38%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
43 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
112 kB of HTML.
- i
Compressionmedium
Couldn't be measured from our server (our fetch decodes compressed pages before we see them). Check in your browser's developer tools that HTML is sent with br or gzip.
- ✗
Render-blocking resourceshigh
2 blocking script(s) and 3 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- ✗
Scripts & third partiesmedium
41 script tag(s); files loaded from 8 other domain(s): cdn.prod.website-files.com, ajax.googleapis.com, cdn.jsdelivr.net, cdnjs.cloudflare.com, unpkg.com, googletagmanager.com….
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- ✗
Imagesmedium
107 image(s).
107 without width/height – can cause layout shift (CLS).
3 image(s) after the first three aren't lazy-loaded.
The first image is lazy-loaded – if it's the main (LCP) image, that delays it. Don't lazy-load images visible on arrival.
6 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
No Cache-Control header.
Fix: Set Cache-Control so browsers and CDNs can reuse the page.
- i
HTTP/3low
Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.
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: CSP, clickjacking protection.
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 70%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width, initial-scale=1
- ✓
Image alt textmedium
All 107 images have alt text.
- ✗
Link nameslow
8 link(s) have no readable name for screen readers.
Fix: Add text or aria-label to icon-only links.
- ✗
Tap-to-contactmedium
No tel: or mailto: links.
Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.
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.
- i
Contact details on pagemedium
No phone number found.
No postcode found (fine for service-area businesses).
- i
Map & directionslow
No map or directions link.