SEO report for www.cookieyes.com

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 cookieyes.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 index found at https://www.cookieyes.com/sitemap.xml listing 12 sitemaps.

  Declared in robots.txt.

  Most recent lastmod: 2026-10-29T07:39:40.611Z.

• ✓

  Canonical URLhigh

  Canonical: https://www.cookieyes.com/

  Points to this page (self-referencing).

• ✓

  Redirectshigh

  1 redirect before the page loaded.

  https://cookieyes.com/ → https://www.cookieyes.com/

  A single redirect to your preferred address is normal; just make sure your own links use the final address.

• ✓

  www / non-wwwmedium

  cookieyes.com redirects to www.cookieyes.com.

• ✓

  hreflangmedium

  8 hreflang link(s).

  All language codes are valid.

Search snippet & sharing 100%

How the page looks in Google results and when shared.

• ✓

  Title tagcritical

  “CookieYes Cookie Consent Solution”

  About 322px of Google's ~580px desktop width.

• ✓

  Meta descriptionhigh

  135 characters, ~865px of ~990px.

  Good length.

  Google sometimes rewrites descriptions to match the search; a good one is still used most often.

• ✓

  Open Graph & social cardsmedium

  Open Graph title and image set.

  Twitter/X card: summary_large_image.

• ✓

  Faviconlow

  Favicon linked (Google shows it next to results).

• ✓

  Languagelow

  lang="en-US"

Content quality 77%

Is there enough clear, useful text that matches what the page targets?

• !

  Word countmedium

  252 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.

  Fix: Add genuinely useful content: key service pages usually need 400+ words to answer what customers ask.

  Count words and keywords with the free word counter

  Read the guide: how to write SEO content

• ✓

  Readabilitymedium

  Flesch reading ease 68 (plain English), about 10 words per sentence.

• !

  Topic focushigh

  2 of 3 title keywords appear in the main content (missing: solution).

  Fix: Use your main title phrases naturally in the opening paragraph and headings.

  Find the phrases people search with the free keyword generator

  Read the guide: how to write SEO content

• ✓

  H1 headingcritical

  “Cookie compliance made simple for businesses of every size”

• ✓

  Heading structuremedium

  9 headings for 252 words.

  Levels are in order.

• ✗

  Text-to-code ratiolow

  1% of the HTML is visible text.

  Fix: Trim unused markup, inline scripts and builder bloat.

AI search readiness 94%

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

  /llms.txt found.

• !

  Question-led contentmedium

  1 heading(s) phrased as questions, e.g. “Why CookieYes is the right fit for your website”.

  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.

  Read the guide: how to write SEO content

• ✓

  Entity clarityhigh

  Identified as: Organization, Person.

  9 official profile link(s) (sameAs).

• ✓

  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 100%

Machine-readable facts for rich results and AI.

• ✓

  JSON-LD present & validhigh

  2 JSON-LD block(s): WebPage, ReadAction, BreadcrumbList, ListItem, WebSite, SearchAction, EntryPoint, PropertyValueSpecification, Organization, ImageObject, SoftwareApplication, Offer.

  All blocks parse correctly.

• ✓

  Required propertiesmedium

  Key types include Google's required properties.

• i

  Breadcrumbslow

  Home page – breadcrumbs not needed.

Links 100%

Internal linking, anchor text and broken links.

• ✓

  Internal linkinghigh

  129 internal and 19 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 38%

Speed signals from the HTML and server. Real-user Core Web Vitals load below.

• ✓

  Server response (TTFB)high

  12 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

  655 kB of HTML – heavy for phones.

  Fix: Remove inline bloat, base64 images and unused markup.

• 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

  1 blocking script(s) and 12 stylesheet(s) in <head>.

  Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.

  Read the guide: Core Web Vitals

• ✗

  Scripts & third partiesmedium

  106 script tag(s); files loaded from 2 other domain(s): cdn-cookieyes.com, googletagmanager.com.

  Fix: Remove unused tracking and widget scripts; every third party adds connection time.

  Read the guide: Core Web Vitals

• !

  Imagesmedium

  129 image(s).

  All images reserve their space.

  1 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.

  0 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.

  Read the guide: image SEO

• ✓

  Cachinglow

  Cache-Control: public, max-age=300, s-maxage=600, stale-while-revalidate=600

• 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 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=63072000; includeSubDomains; preload

• ✓

  Security headerslow

  Present: CSP, nosniff, Referrer-Policy, Permissions-Policy, clickjacking protection.

• ✓

  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, initial-scale=1

• ✓

  Image alt textmedium

  All 129 images have alt text.

• ✗

  Form labelsmedium

  2 of 4 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

  No tel: or mailto: links.

  Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.

  Read the guide: mobile-friendly websites

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.