Website review, no card needed

neupril.com logo

neupril.com website review

Visit site (opens in a new tab)Reviewed 20 November 202642 issues · 86 checks

This review found 42 issues worth fixing on neupril.com, 14 of them high impact, across 86 checks. The most urgent: page weight: 218.0 MB in 551 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

Real-visitor load time (LCP)75th percentile, phones
3.0 s2.6 sMay 30Nov 142.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.7 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20262.9 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20262.9 s
Jul 18, 20262.8 s
Jul 25, 20262.8 s
Aug 1, 20262.8 s
Aug 8, 20262.7 s
Aug 15, 20262.7 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.7 s
Sep 12, 20262.7 s
Sep 19, 20262.8 s
Sep 26, 20262.8 s
Oct 3, 20262.9 s
Oct 10, 20262.9 s
Oct 17, 20262.8 s
Oct 24, 20262.7 s
Oct 31, 20262.7 s
Nov 7, 20262.8 s
Nov 14, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
152 ms128 msMay 30Nov 14138 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026136 ms
Jun 6, 2026142 ms
Jun 13, 2026141 ms
Jun 20, 2026139 ms
Jun 27, 2026144 ms
Jul 4, 2026142 ms
Jul 11, 2026146 ms
Jul 18, 2026149 ms
Jul 25, 2026143 ms
Aug 1, 2026140 ms
Aug 8, 2026144 ms
Aug 15, 2026138 ms
Aug 22, 2026140 ms
Aug 29, 2026138 ms
Sep 5, 2026137 ms
Sep 12, 2026137 ms
Sep 19, 2026137 ms
Sep 26, 2026137 ms
Oct 3, 2026137 ms
Oct 10, 2026137 ms
Oct 17, 2026134 ms
Oct 24, 2026131 ms
Oct 31, 2026133 ms
Nov 7, 2026137 ms
Nov 14, 2026138 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 neupril.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. neupril.com at 4.4 s4.4 s
  2. neupril.com at 8.7 s8.7 s
  3. neupril.com at 13.1 s13.1 s
  4. neupril.com at 17.4 s17.4 s
  5. neupril.com at 21.8 s21.8 s
  6. neupril.com at 26.1 s26.1 s
  7. neupril.com at 30.5 s30.5 s
  8. neupril.com at 34.8 s34.8 s

Speed

15 to fix30
  • Reduce unused JavaScript

    2.3 s · 715 KiB

    About 715 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

  • Main-thread work: 10.7 s

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

  • Mobile performance score: 30

    30/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (replocdn.com, Clarity and rebuyengine.com and others), adding 214.0 MB and 2.0 s of main-thread time.

  • Shopify adds 187 ms

    187 ms

    Shopify costs a phone 187 ms of main-thread work and 212.2 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.

  • Improve image delivery

    800 ms · 1.5 MB

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

  • replocdn.com adds 766 ms

    766 ms

    replocdn.com costs a phone 766 ms of main-thread work and 758 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.

  • Render-blocking requests

    650 ms

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

  • Use efficient cache lifetimes

    350 ms · 176 KiB

    20 files are served with short cache lifetimes, so returning visitors download them again (176 KiB).

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    300 ms · 127 KiB

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

  • Clarity adds 330 ms

    330 ms

    Clarity costs a phone 330 ms of main-thread work and 30 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.

  • rebuyengine.com adds 199 ms

    199 ms

    rebuyengine.com costs a phone 199 ms of main-thread work and 332 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.

  • 2,206 HTML elements

    The page has 2,206 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Klaviyo adds 171 ms

    171 ms

    Klaviyo costs a phone 171 ms of main-thread work and 313 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 · 67 KiB

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

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 17 ms

    17 ms

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

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

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

  • Real-user CLS: 0.28

    0.28

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

  • Largest Contentful Paint: 541.4 s

    541.4 s

    Your largest element takes 541.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A bottle of Neupril, a Methylfolate supplement, next to a f…”.

  • Speed Index: 17.3 s

    17.3 s

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

  • Time to Interactive: 541.7 s

    541.7 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Cumulative Layout Shift: 0.176

    0.176

    The layout shifts by 0.176 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -1%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

4 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 95 ms

    95 ms

    Real visitors wait 95 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 371 ms

    371 ms

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

Images and page weight

2 to fix60
  • Page weight: 218.0 MB in 551 requests

    218.0 MB

    Your homepage downloads 218.0 MB in 551 requests on a phone: media 211.8 MB (16), images 1.9 MB (47) and scripts 1.8 MB (88). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    41 KiB

    1 image is downloaded at several times the size a phone draws it, for example neupril-kids-methylfolate-methyl-b12-liquid-drops.png at 1,080 px wide, shown at 155 px. Resized copies would save about 41 KiB.

  • 4 images below the first screen load straight away

    4 images further down the page (157 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 61.8 g of CO₂ per visit

    61.79 g

    By the Sustainable Web Design model, a visit to your homepage emits about 61.79 g of CO₂e: 7415.0 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

8 to fixGoogle 8289
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 6 tap targets too small

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

  • 5 text elements with low contrast

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 17 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 (2 elements)

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

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

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

2 to fixGoogle 9291
  • 2 H1 headlines

    There are 2 <h1> headlines (“You Have Folate Gaps, Neupril Fills Them” and “You Have Folate Gaps, Neupril is a Methylfolate S…”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected non-whitespace character after JSON at position 8)”.

  • 68 internal links, 12 external

    The homepage links to 68 pages on neupril.com and 12 external pages.

6 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Neupril is a Methylfolate supplement that fills the MTHFR gap 50% of people have. Supports energy, mood, focus, and lon…”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Neupril | The Future of Brain Health Is Methylated”.

  • Canonical URL set

    The canonical URL is https://neupril.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://neupril.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.

3 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,948 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://neupril.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 1 page without a meta description

    https://neupril.com/blogs/news has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://neupril.com/pages/mthfr-and-folate, https://neupril.com/pages/how-neupril-works and https://neupril.com/pages/contact 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 21 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

2 to fixGoogle 9687
  • 10 small tap targets

    10 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://neupril.com/cdn/shop/t/33/assets/component-price.css?v=4405' because its MIME type…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • 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 1,100 words of copy

    The homepage carries about 1,100 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Try Methylfolate Drops” and “Shop Now”.

  • 15 calls to action

    The homepage has 15 calls to action, for example “Contact Us”, “Try Methylfolate Drops” and “Shop Black Friday Sale”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: a star rating and “45K+ reviews”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • 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

  • 10 trackers load before any consent

    10

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 5 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 37 cookies set on arrival

    37

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

  • 56 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 neupril.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 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Triplewhale · Gempages Builder · Kaching Bundles · Klaviyo Email Marketing Sms · Rebuy Personalization Engine · Upcart · jsdelivr.net · rebuyengine.com · socialsnowball.io

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

Stack

E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on neupril.com, including 24 speed issues, 2 SEO issues and 1 conversion gap. 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