Website review, no card needed

junodx.com logo

junodx.com website review

Visit site (opens in a new tab)Reviewed 22 November 202640 issues · 82 checks

This review found 40 issues worth fixing on junodx.com, 15 of them high impact, across 82 checks. The most urgent: use efficient cache lifetimes. 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
2.6 s2.4 sAug 22Sep 122.4 s
Show as table
DateReal-visitor load time (LCP)
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.4 s

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 junodx.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

13 to fix47
  • Use efficient cache lifetimes

    2.9 s · 3.5 MB

    37 files are served with short cache lifetimes, so returning visitors download them again (3.5 MB).

  • Reduce unused JavaScript

    3.7 s · 2.7 MB

    About 2.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.7 s faster on a phone.

  • archive.org adds 1.6 s

    1.6 s

    archive.org costs a phone 1.6 s of main-thread work and 14.4 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 47

    47/100

    Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 5.0 s

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

  • Improve image delivery

    700 ms · 9.8 MB

    20 images could be 9.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (archive.org, YouTube and Facebook and others), adding 15.9 MB and 2.4 s of main-thread time.

  • Reduce unused CSS

    590 ms · 211 KiB

    About 211 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 590 ms faster on a phone.

  • Font display

    700 ms

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

  • YouTube adds 506 ms

    506 ms

    YouTube costs a phone 506 ms of main-thread work and 996 KiB 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.

  • 10 long tasks on the main thread

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

  • Render-blocking requests

    350 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 350 ms.

  • Shopify adds 12 ms

    12 ms

    Shopify costs a phone 12 ms of main-thread work and 318 KiB 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.

  • Legacy JavaScript

    250 ms · 56 KiB

    Polyfills for old browsers add 56 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

  • Minify JavaScript

    150 ms · 20 KiB

    20 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 201 ms

    201 ms

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

Core Web Vitals

4 to fix46
  • Largest Contentful Paint: 14.4 s

    14.4 s

    Your largest element takes 14.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 17.2 s

    17.2 s

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

  • Time to Interactive: 65.9 s

    65.9 s

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

  • Total Blocking Time: 756 ms

    756 ms

    Scripts block taps and scrolling for 756 ms in total while the page loads. Good is under 200 ms.

  • Largest content (LCP) held steady for real visitors

    -3%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.4 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.

2 checks passed
  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix60
  • Page weight: 17.3 MB in 188 requests

    17.3 MB

    Your homepage downloads 17.3 MB in 188 requests on a phone: images 11.8 MB (41), scripts 4.5 MB (55) and other files 440 KiB (76). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    181 KiB

    2 images are downloaded at several times the size a phone draws them, for example shopify-icons-02_1024x1024_v-1664305878.png at 1,024 px wide, shown at 150 px. Resized copies would save about 181 KiB.

  • 3 images in older formats

    3 images (349 KiB) 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 below the first screen load straight away

    1 image further down the page (125 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 4.9 g of CO₂ per visit

    4.90 g

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

Accessibility

8 to fixGoogle 8989
  • 45 tap targets too small

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

  • 6 text elements with low contrast

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

  • ARIA toggle fields must have an accessible name (1 element)

    ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (13 elements)

    All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 25 links without text

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 47 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

3 to fixGoogle 10085
  • Title is long (71 characters)

    Your title is 71 characters, so Google will cut it off around 60: “Juno Diagnostics | At-Home Prenatal Testing with Fast, Accurate Results”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Peace of mind with prenatal screenings”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 102 internal links, 90 external

    The homepage links to 102 pages on junodx.com and 90 external pages.

5 checks passed
  • Meta description: 76 characters

    Your meta description is 76 characters: “Experience early, accurate prenatal testing from home with Juno Diagnostics.”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Product.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

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

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://junodx.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

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

  • Text is in the HTML

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

Other pages

2 to fix90
  • 3 pages without a meta description

    https://junodx.com/collections/prenatal-tests, https://junodx.com/pages/downloadables and https://junodx.com/pages/before-you-begin have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://junodx.com/pages/patient-testimonials and https://junodx.com/blogs/news have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • 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

4 to fixGoogle 5474
  • 2 broken images

    2 images failed to load on a phone, for example https://web.archive.org/web/20230703193335/https://cdn.shopify.com/s/files/1/0671/0630/8345/products/Amazon-Product-Page-Birch-Box-Mockup-Angle1-pink1-bg_1_542aa4b3-1c4e-4505-bd97-99a342ba229c_720x.jp.

  • 5 third-party cookies

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).

  • 2 JavaScript errors while loading

    2 errors were 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”).

2 checks passed
  • Tap targets are thumb-sized

    32 of 33 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Thin social proof

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

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

  • About 953 words of copy

    The homepage carries about 953 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Tests” and “How to: Register from Amazon”.

  • 14 calls to action

    The homepage has 14 calls to action, for example “Start shopping”, “Shop Tests” and “How to: Register from Amazon”.

  • 6 short forms

    6 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Klaviyo and Meta Pixel (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.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies, 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.

  • 17 other companies contacted

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

Apps on your store

Your storefront loads 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

  • The footer still says © 2023.

Stack

Framework
jQuery
E-commerce
Shopify
Hosting
Cloudflare

Company

Headquarters
San Diego

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on junodx.com, including 17 speed issues, 3 SEO issues and 2 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