neurogum.com website review

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

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

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

8 third-party services load with your homepage (Shopify, alia-prod.com and rebuyengine.com and others), adding 2.7 MB and 1.9 s of main-thread time.

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

9 images could be 452 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

alia-prod.com costs a phone 334 ms of main-thread work and 417 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 costs a phone 223 ms of main-thread work and 891 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.

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

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

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

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

8 KiB could be saved by minifying JavaScript.

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

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

4 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Neuro”.

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

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

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

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

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

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

Your homepage downloads 7.3 MB in 439 requests on a phone: scripts 3.1 MB (158), images 1.9 MB (31) and other files 1.6 MB (184). Under 2 MB keeps phones on slow connections fast.

c81f8f48ad814b849a607b2035da1413.thumbnail.0000000000.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

Elements must only use permitted ARIA attributes: 5 elements on the page fail this check, rated serious by axe-core.

1 frame has no title, so screen-reader users cannot tell what it contains.

2 images have no alt text, which hurts accessibility and image search.

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

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

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

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

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

The homepage links to 112 pages on neurogum.com and 11 external pages.

https://neurogum.com/collections/all and https://neurogum.com/pages/ambassadors-partners all use the title “Neuro Products | Gum & Mints for Focus, Energy, Calm & Sleep”. Search engines can't tell which page to show for a search, so each competes with the others.

https://neurogum.com/collections/all and https://neurogum.com/pages/ambassadors-partners use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://neurogum.com/pages/ambassadors-partners, whose canonical is https://neurogum.com/collections/all. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://neurogum.com/products/energy-caffeine-mints, https://neurogum.com/collections/all, https://neurogum.com/collections/neuro-bundles, https://neurogum.com/pages/store-locator, https://neurogum.com/products/calm-focus-gum and https://neurogum.com/products/energy-caffeine-gum and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://action.dstillery.com/orbserv/nspix?adv=cl172935946111751&ns=9078&nc=Neuro-Gum-Site-Visitor&ncv=58.

5 errors were logged to the browser console while the page loaded, for example “Error: <svg> attribute height: Expected length, "auto".”.

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

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

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

The homepage carries about 996 words of visible text.

Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Tag Manager, Klaviyo and LinkedIn Insight and 7 mores (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.

Opening the homepage sets 53 cookies (measured from a US location before any click).

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.

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