SEO report for react19.org

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 react19.org…

Indexing & crawling 75%

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

  No XML sitemap found at /sitemap.xml or in robots.txt.

  Fix: Create an XML sitemap listing every page and submit it in Google Search Console.

  Make one with the free XML sitemap generator

  Read the guide: XML sitemaps

• ✗

  Canonical URLhigh

  No canonical tag.

  Fix: Add <link rel="canonical" href="(this page's full URL)"> – only point it elsewhere for true duplicates.

  Read the guide: duplicate content

• ✓

  Redirectshigh

  Loads directly with no redirects.

• ✓

  www / non-wwwmedium

  www.react19.org redirects to react19.org.

Search snippet & sharing 79%

How the page looks in Google results and when shared.

• !

  Title tagcritical

  “Home - React19”

  About 146px 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.

  Preview and measure your title with the free title tag checker

  Read the guide: how to write title tags

• ✓

  Meta descriptionhigh

  152 characters, ~978px 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-gb"

Content quality 46%

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

• ✓

  Word countmedium

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

• i

  Readabilitymedium

  Not enough paragraph text to score readability.

• ✗

  Topic focushigh

  0 of 1 title keywords appear in the main content (missing: home).

  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

  “We are a grassroots organization dedicated to research and collaboration with institutions and providers to increase understanding and awareness for patients suffering lasting effects due to Long COVID and/or post COVID vaccine.”

  The H1 shares no keywords with the title.

  Fix: Use one H1 that states the page topic with its main keyword.

• !

  Heading structuremedium

  24 headings for 556 words – a lot for the amount of text.

  1 skipped level(s), e.g. H2 → H4.

  1 empty heading(s).

  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

  7% of the HTML is visible text.

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

AI search readiness 72%

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.

  Make one with the free llms.txt generator

  Read the guide: do you need llms.txt?

• ✓

  Question-led contentmedium

  4 heading(s) phrased as questions, e.g. “What is Post Vaccination Syndrome?”.

• !

  Entity clarityhigh

  Identified as: Organization.

  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

  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 all three: about, contact and privacy.

Structured data 100%

Machine-readable facts for rich results and AI.

• ✓

  JSON-LD present & validhigh

  1 JSON-LD block(s): Organization, WebSite, SearchAction, WebPage, Article.

  All blocks parse correctly.

• ✓

  Required propertiesmedium

  Key types include Google's required properties.

  Recommended but missing: Organization.logo, Article.image, Article.datePublished, Article.author.

• i

  Breadcrumbslow

  Home page – breadcrumbs not needed.

Links 75%

Internal linking, anchor text and broken links.

• ✓

  Internal linkinghigh

  122 internal and 13 external links.

• ✗

  Anchor text qualitymedium

  Same text used for different pages: “watch the video”, “read more”.

  16 vague link(s) like “click here” or “read more”.

  1 link(s) with no text at all.

  Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.

  Check every link's wording with the free anchor text checker

  Read the guide: internal linking

• ✓

  Broken links (sample)high

  Checked 12 internal link(s).

  No broken links found.

Performance 53%

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

• !

  Server response (TTFB)high

  1258 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

  101 kB of HTML.

• ✓

  Compressionmedium

  Compressed with gzip.

• ✗

  Render-blocking resourceshigh

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

  20 script tag(s); files loaded from 3 other domain(s): fonts.googleapis.com, youtube.com, googletagmanager.com.

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

  Read the guide: Core Web Vitals

• !

  Imagesmedium

  43 image(s).

  All images reserve their space.

  1 image(s) after the first three aren't lazy-loaded.

  1 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: no-store, no-cache, must-revalidate, post-check=0, pre-check=0

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

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: nosniff, Referrer-Policy, clickjacking protection.

  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

  No X-Powered-By header (server: cloudflare).

Mobile & accessibility 58%

Usable on phones and by everyone – Google indexes the mobile version.

• ✓

  Mobile viewportcritical

  viewport: width=device-width, initial-scale=1

• ✗

  Image alt textmedium

  25 of 43 images have no alt attribute.

  Fix: Describe each meaningful image in its alt attribute (use alt="" for decorative ones).

  Read the guide: image SEO

• ✓

  Form labelsmedium

  All 2 form fields are labelled.

• ✗

  Link nameslow

  1 link(s) have no readable name for screen readers.

  Fix: Add text or aria-label to icon-only links.

  Read the guide: internal linking

• ✗

  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.