SEO report for eventuallymaking.io

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 eventuallymaking.io…

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://eventuallymaking.io/sitemap_index.xml listing 1 sitemap.

  Declared in robots.txt.

  No lastmod dates – add accurate ones so search engines know what changed.

• ✓

  Canonical URLhigh

  Canonical: https://eventuallymaking.io/

  Points to this page (self-referencing).

• ✓

  Redirectshigh

  Loads directly with no redirects.

• ✓

  www / non-wwwmedium

  www.eventuallymaking.io redirects to eventuallymaking.io.

• ✓

  hreflangmedium

  3 hreflang link(s).

  All language codes are valid.

Search snippet & sharing 71%

How the page looks in Google results and when shared.

• !

  Title tagcritical

  “Eventuallymaking”

  About 157px of Google's ~580px desktop width – short; use the space.

  Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.

  On WordPress: Edit the page and scroll to the Yoast SEO or Rank Math box (install one of these free plugins if you have neither), then fill in the SEO title.

  Preview and measure your title with the free title tag checker

  Read the guide: how to write title tags

• ✓

  Meta descriptionhigh

  104 characters, ~655px 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

  No favicon linked.

  Fix: Add a square favicon at least 48×48px.

  On WordPress: Appearance → Customize → Site Identity → Site Icon (Settings → General in newer versions).

• ✓

  Languagelow

  lang="en"

Content quality 67%

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

• !

  Word countmedium

  393 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 49 (fairly difficult), about 12 words per sentence.

  Fix: Use shorter sentences and everyday words – aim for a score of 50+ for customer-facing pages.

  Read the guide: how to write SEO content

• i

  Topic focushigh

  No title keywords to compare.

• ✓

  H1 headingcritical

  “Eventuallymaking”

• !

  Heading structuremedium

  13 headings for 393 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.

  Read the guide: the on-page SEO checklist

• ✗

  Text-to-code ratiolow

  1% of the HTML is visible text.

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

AI search readiness 78%

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

  4 heading(s) phrased as questions, e.g. “Is Proprietary Software Over?”.

• !

  Entity clarityhigh

  Identified as: Person.

  No sameAs links to official profiles (Google Business Profile, LinkedIn, Facebook, Companies House…).

  Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.

  Make the code with the free local business schema generator

  Read the guide: schema markup

• ✓

  Freshness signalsmedium

  The page shows when it was published or last updated.

• ✗

  Trust pages (E-E-A-T)medium

  Links found to about; missing contact and privacy.

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

Machine-readable facts for rich results and AI.

• ✓

  JSON-LD present & validhigh

  3 JSON-LD block(s): WebSite, Blog, Person, BlogPosting, WebPage, ReadAction.

  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

  18 internal and 1 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 69%

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

• !

  Server response (TTFB)high

  1011 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).

  Fix: Use page caching or a CDN (e.g. Cloudflare) so HTML is served from the edge.

• !

  HTML sizemedium

  191 kB of HTML.

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

• ✓

  Compressionmedium

  Compressed with gzip.

• !

  Render-blocking resourceshigh

  0 blocking script(s) and 3 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

  4 script tag(s); files loaded from 1 other domain(s): writizzy.b-cdn.net.

• ✓

  Imagesmedium

  2 image(s).

  All images reserve their space.

  2 use WebP/AVIF or responsive srcset.

• ✗

  Cachinglow

  No Cache-Control header.

  Fix: Set Cache-Control so browsers and CDNs can reuse the page.

• ✓

  HTTP/3low

  Server advertises HTTP/3 (faster on mobile networks).

Security 67%

Visitor safety signals that browsers and Google check.

• ✓

  HTTPScritical

  Secure HTTPS with no mixed content.

• ✓

  HTTP → HTTPS redirecthigh

  http:// redirects to https://.

• ✗

  HSTSmedium

  No Strict-Transport-Security header.

  Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.

  Read the guide: the technical SEO checklist

• ✗

  Security headerslow

  Present: none.

  Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).

  Read the guide: the technical SEO checklist

• ✗

  Server fingerprintlow

  X-Powered-By reveals “Nuxt”.

  Fix: Remove X-Powered-By so attackers can't see your software versions.

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 2 images have alt text.

• ✗

  Form labelsmedium

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