Website review, no card needed

ajvaccines.com logo

ajvaccines.com website review

Visit site (opens in a new tab)Reviewed 18 November 202628 issues · 77 checks

This review found 28 issues worth fixing on ajvaccines.com, 9 of them high impact, across 77 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.0 s2.0 sMay 30Nov 72.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.6 s
Jun 13, 20263.8 s
Jun 20, 20263.2 s
Jun 27, 20263.2 s
Jul 4, 20263.1 s
Jul 11, 20263.0 s
Jul 18, 20263.3 s
Aug 8, 20263.5 s
Aug 15, 20263.2 s
Aug 22, 20263.0 s
Aug 29, 20262.8 s
Sep 5, 20262.8 s
Sep 12, 20262.6 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Oct 24, 20262.3 s
Oct 31, 20262.3 s
Nov 7, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
108 ms88 msJun 13Oct 3196 ms
Show as table
DateReal-visitor tap response (INP)
Jun 13, 202692 ms
Jun 20, 202690 ms
Jun 27, 202690 ms
Jul 4, 202692 ms
Jul 11, 202692 ms
Jul 18, 202694 ms
Aug 1, 2026101 ms
Aug 8, 2026106 ms
Aug 15, 2026104 ms
Aug 22, 2026103 ms
Aug 29, 2026104 ms
Sep 5, 2026100 ms
Oct 10, 202696 ms
Oct 17, 202695 ms
Oct 24, 202690 ms
Oct 31, 202696 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of ajvaccines.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ajvaccines.com at 0.4 s0.4 s
  2. ajvaccines.com at 0.8 s0.8 s
  3. ajvaccines.com at 1.1 s1.1 s
  4. ajvaccines.com at 1.5 s1.5 s
  5. ajvaccines.com at 1.9 s1.9 s
  6. ajvaccines.com at 2.3 s2.3 s
  7. ajvaccines.com at 2.6 s2.6 s
  8. ajvaccines.com at 3.0 s3.0 s

Speed

6 to fix66
  • Improve image delivery

    7.6 s · 1.6 MB

    3 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 7.6 s faster on a phone.

  • Reduce unused JavaScript

    900 ms · 147 KiB

    About 147 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Cookiebot and Google Fonts and others), adding 9.0 MB and 107 ms of main-thread time.

  • Mobile performance score: 66

    66/100

    Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.

  • storyblok.com adds 0 ms

    0 ms

    storyblok.com costs a phone 0 ms of main-thread work and 8.7 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Render-blocking requests

    750 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

  • Use efficient cache lifetimes

    150 ms · 36 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (36 KiB).

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 181 ms. During a long task the page ignores taps.

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Reduce unused CSS

    15 KiB

    About 15 KiB of CSS is downloaded but never applied on this page.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 checks passed
  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 603 ms of it running JavaScript. That is comfortably low.

  • Server response: 204 ms

    204 ms

    Your server sent the HTML in 204 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 15.2 s

    15.2 s

    Your largest element takes 15.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content and ads, to provide s…”.

  • Time to Interactive: 15.2 s

    15.2 s

    The page becomes fully interactive after 15.2 s. Good is under 3.8 s.

  • Speed Index: 5.5 s

    5.5 s

    Visually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 2.1 s

    2.1 s

    The first text or image appears after 2.1 s on a phone. Good is under 1.8 s.

  • Tap response (INP) held steady for real visitors

    +2%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 92 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.3 s

    2.3 s

    Real visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.4 s

    1.4 s

    Real visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 477 ms

    477 ms

    Real visitors wait 477 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 39% faster for real visitors

    -39%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.6 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 178 ms

    178 ms

    Scripts block the page for only 178 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

4 to fix28
  • Page weight: 21.9 MB in 69 requests

    21.9 MB

    Your homepage downloads 21.9 MB in 69 requests on a phone: media 19.5 MB (1), images 1.7 MB (4) and scripts 516 KiB (33). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    filters:quality(80) weighs 1.2 MB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    1.6 MB

    2 images are downloaded at several times the size a phone draws them, for example filters:quality(80) at 6,459 px wide, shown at 340 px. Resized copies would save about 1.6 MB.

  • 2 images below the first screen load straight away

    2 images further down the page (1.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 6.2 g of CO₂ per visit

    6.21 g

    By the Sustainable Web Design model, a visit to your homepage emits about 6.21 g of CO₂e: 745.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

3 to fixGoogle 9394
  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

2 checks passed
  • Every image has alt text

    All 3 images in the HTML carry an alt attribute.

  • 32 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 8587
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (168 characters)

    Your meta description is 168 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 22 internal links, 1 external

    The homepage links to 22 pages on ajvaccines.com and 1 external page.

6 checks passed
  • One H1 headline

    Your main headline reads: “Together, we keep the world safe”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “Together, we keep the world safe | AJ Vaccines”.

  • Canonical URL set

    The canonical URL is https://ajvaccines.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://ajvaccines.com/sitemap_index.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://ajvaccines.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

1 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Other pages

1 to fix98
  • 6 pages share a meta description

    https://ajvaccines.com/careers/onboarding, https://ajvaccines.com/diseases, https://ajvaccines.com/news, https://ajvaccines.com/da, https://ajvaccines.com/legal/privacy-policy and https://ajvaccines.com/legal/cookie-policy use the same meta description. A description written for each page earns more clicks.

  • 2 pages with very little text

    https://ajvaccines.com/contact and https://ajvaccines.com/da have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 2 pages slow to respond

    https://ajvaccines.com/careers and https://ajvaccines.com/diseases took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10092
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 100 words

    The homepage has only about 100 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

2 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact” and “Learn more”.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 6 other companies contacted

    Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at ajvaccines.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Nuxt
Hosting
Vercel

Company

Founded
2016
Headquarters
Copenhagen

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on ajvaccines.com, including 10 speed issues, 4 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25