SEO report for wioai.com
https://wioai.com/ · checked Wed, 04 Nov 2026 21:23 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).
- Scripts & third partiesmedium
46 script tag(s); files loaded from 1 other domain(s): fonts.googleapis.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- 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.
- Render-blocking resourceshigh
1 blocking script(s) and 2 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- Open Graph & social cardsmedium
Open Graph title or image missing.
Fix: Add og:title, og:description, og:image (1200×630 PNG/JPG, absolute URL) and twitter:card=summary_large_image.
On WordPress: Yoast SEO and Rank Math add these tags for you. Set a sharing image in the plugin's Social tab on each page.
- Readabilitymedium
Flesch reading ease 31 (fairly difficult), about 12 words per sentence.
Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.
- Heading structuremedium
41 headings for 997 words – a lot for the amount of text.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
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 wioai.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://wioai.com/sitemap.xml with 3,425 URLs.
Declared in robots.txt.
This page is listed in it.
Most recent lastmod: 2026-10-31T14:53:18.
- ✓
Canonical URLhigh
Canonical: https://wioai.com
Points to this page (self-referencing).
- ✓
Redirectshigh
Loads directly with no redirects.
- ✓
www / non-wwwmedium
www.wioai.com redirects to wioai.com.
Search snippet & sharing 92%
How the page looks in Google results and when shared.
- ✓
Title tagcritical
“WIO AI — Discover and Compare AI Tools”
About 379px of Google's ~580px desktop width.
- ✓
Meta descriptionhigh
137 characters, ~854px 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 83%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
997 words of main content (inside <main>).
Google has no minimum word count – this is a rough guide to whether the page answers the question in full.
- !
Readabilitymedium
Flesch reading ease 31 (fairly difficult), about 12 words per sentence.
Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.
- ✓
Topic focushigh
4 of 4 title keywords appear in the main content.
- ✓
H1 headingcritical
“Find the right AI tool. Trust what you read. WIO Karo, Chill Karo!”
- !
Heading structuremedium
41 headings for 997 words – a lot for the amount of text.
Levels are in order.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- !
Text-to-code ratiolow
6% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 75%
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
8 heading(s) phrased as questions, e.g. “How we review & verify”.
- ✗
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 all three: about, contact and privacy.
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
59 internal and 0 external links.
- ✓
Anchor text qualitymedium
No link text points to two different pages.
- ✓
Broken links (sample)high
Checked 12 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
191 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
132 kB of HTML.
- ✓
Compressionmedium
Compressed with gzip.
- !
Render-blocking resourceshigh
1 blocking script(s) and 2 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- ✗
Scripts & third partiesmedium
46 script tag(s); files loaded from 1 other domain(s): fonts.googleapis.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- !
Imagesmedium
13 image(s).
All images reserve their space.
2 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.
13 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.
On WordPress: Install a free image optimiser plugin (such as EWWW Image Optimizer or Smush) to shrink images and serve WebP.
- ✓
Cachinglow
Cache-Control: s-maxage=300, stale-while-revalidate=31535700
- ✓
HTTP/3low
Server advertises HTTP/3 (faster on mobile networks).
Security 100%
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; includeSubDomains; preload
- ✓
Security headerslow
Present: CSP, nosniff, Referrer-Policy, Permissions-Policy, clickjacking protection.
- ✓
Server fingerprintlow
No X-Powered-By header (server: cloudflare).
Mobile & accessibility 83%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width, initial-scale=1
- ✓
Image alt textmedium
All 13 images have alt text.
- ✓
Form labelsmedium
All 2 form fields are labelled.
- ✓
Link nameslow
Every link has a readable name.
- ✗
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.