Website review, no card needed

unjected.com logo

unjected.com website review

Visit site (opens in a new tab)Reviewed 12 November 202626 issues · 61 checks

This review found 26 issues worth fixing on unjected.com, 6 of them high impact, across 61 checks. The most urgent: page weight: 45.7 MB in 50 requests. 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

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
2.9 s1.7 sMay 23Oct 32.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.8 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.1 s
Aug 22, 20262.4 s
Aug 29, 20262.8 s
Sep 5, 20262.6 s
Sep 12, 20262.5 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
182 ms76 msMay 23Oct 3128 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202694 ms
May 30, 202689 ms
Jun 6, 202688 ms
Jun 13, 202689 ms
Jun 27, 202689 ms
Jul 4, 202688 ms
Jul 11, 202699 ms
Jul 18, 2026106 ms
Jul 25, 2026113 ms
Aug 22, 2026148 ms
Aug 29, 2026170 ms
Sep 5, 2026154 ms
Sep 12, 2026150 ms
Sep 19, 2026141 ms
Sep 26, 2026128 ms
Oct 3, 2026128 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 unjected.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. unjected.com at 0.8 s0.8 s
  2. unjected.com at 1.6 s1.6 s
  3. unjected.com at 2.4 s2.4 s
  4. unjected.com at 3.1 s3.1 s
  5. unjected.com at 3.9 s3.9 s
  6. unjected.com at 4.7 s4.7 s
  7. unjected.com at 5.5 s5.5 s
  8. unjected.com at 6.3 s6.3 s

Speed

1 to fix
  • Main-thread work: 5.3 s

    A phone's processor spends 5.3 s on main-thread work while loading, 2.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 3 third-party services on the page

    3 third-party services load with your homepage (YouTube, Other Google APIs/SDKs and Google/Doubleclick Ads), adding 259 KiB and 171 ms of main-thread time.

1 checks passed
  • Server response: 1 ms

    1 ms

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

Core Web Vitals

2 to fix100
  • Tap response (INP) got 40% slower for real visitors

    +40%

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

  • 23 images without width and height

    23 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) got 19% slower for real visitors

    +19%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Cumulative Layout Shift: 0.004

    0.004

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

Images and page weight

5 to fix28
  • Page weight: 45.7 MB in 50 requests

    45.7 MB

    Your homepage downloads 45.7 MB in 50 requests on a phone: images 44.5 MB (30), scripts 900 KiB (8) and fonts 100 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 11 images over 500 KB

    11 images weigh 43.5 MB together. On a phone connection a single image that size takes seconds.

  • 13 images below the first screen load straight away

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

  • 8 images in older formats

    8 images (6.6 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 1 image far larger than shown

    404 KiB

    1 image is downloaded at several times the size a phone draws it, for example mobiles-image-01.957ee36c.png at 1,259 px wide, shown at 358 px. Resized copies would save about 404 KiB.

  • About 12.9 g of CO₂ per visit

    12.94 g

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

Accessibility

4 to fixGoogle 8794
  • 9 text elements with low contrast

    9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 5 tap targets too small

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

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 45 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

6 to fixGoogle 10080
  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://unjected.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at unjected.com/robots.txt, the first file search crawlers ask for.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 7 internal links, 11 external

    The homepage links to 7 pages on unjected.com and 11 external pages.

3 checks passed
  • Meta description: 143 characters

    Your meta description is 143 characters: “Unvaccinated dating, friendships and community. Build a profile and get connecting with other likeminded, unvaccinated …”.

  • One H1 headline

    Your main headline reads: “The World's First Unvaccinated Platform”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “World's First Covid-19 Unvaccinated Platform – Unjected”.

AI search readiness

1 to fix88
  • 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://unjected.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.

2 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (618 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 1 page with very little text

    https://unjected.com/contactus.html has 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.

  • 4 internal pages checked

    We fetched 4 pages linked from your homepage and read each the way a search engine does.

7 checks passed
  • Linked pages load

    All 4 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 4 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 4 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7789
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix58
  • 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.

  • Thin social proof

    Social proof on the homepage: 29 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

  • About 502 words of copy

    The homepage carries about 502 words of visible text.

2 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us”, “Download now” and “Contact us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Ads (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie, 1 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 9 other companies contacted

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

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 unjected.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2024.

Stack

E-commerce
Shopify;Shopify Plus
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on unjected.com, including 3 speed issues, 6 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