Website review, no card needed

tryneurosmile.com logo

tryneurosmile.com website review

Visit site (opens in a new tab)Reviewed 9 November 202639 issues · 79 checks

This review found 39 issues worth fixing on tryneurosmile.com, 10 of them high impact, across 79 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
5.2 s2.8 sMay 23Nov 73.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20263.5 s
May 30, 20263.9 s
Jun 6, 20263.7 s
Jun 13, 20263.6 s
Jun 20, 20263.4 s
Jun 27, 20263.3 s
Oct 10, 20264.9 s
Oct 17, 20263.9 s
Oct 24, 20263.4 s
Oct 31, 20263.2 s
Nov 7, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
132 ms108 msMay 23Oct 31111 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026117 ms
May 30, 2026121 ms
Jun 6, 2026129 ms
Jun 13, 2026126 ms
Jun 20, 2026111 ms
Jun 27, 2026111 ms
Oct 31, 2026111 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 tryneurosmile.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tryneurosmile.com at 0.7 s0.7 s
  2. tryneurosmile.com at 1.5 s1.5 s
  3. tryneurosmile.com at 2.2 s2.2 s
  4. tryneurosmile.com at 2.9 s2.9 s
  5. tryneurosmile.com at 3.7 s3.7 s
  6. tryneurosmile.com at 4.4 s4.4 s
  7. tryneurosmile.com at 5.2 s5.2 s
  8. tryneurosmile.com at 5.9 s5.9 s

Speed

11 to fix62
  • Use efficient cache lifetimes

    2.3 s · 271 KiB

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

  • Reduce unused JavaScript

    1.7 s · 251 KiB

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

  • Reduce unused CSS

    1.0 s · 114 KiB

    About 114 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.0 s faster on a phone.

  • Mobile performance score: 62

    62/100

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

  • Render-blocking requests

    650 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (alia-prod.com, Klaviyo and Shopify and others), adding 1.7 MB and 418 ms of main-thread time.

  • Improve image delivery

    300 ms · 224 KiB

    12 images could be 224 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Legacy JavaScript

    300 ms · 49 KiB

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

  • alia-prod.com adds 250 ms

    250 ms

    alia-prod.com costs a phone 250 ms of main-thread work and 264 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.

  • Shopify adds 57 ms

    57 ms

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

  • Google Fonts adds 1 ms

    1 ms

    Google Fonts costs a phone 1 ms of main-thread work and 502 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.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 96 ms. During a long task the page ignores taps.

  • Font display

    50 ms

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

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

2 checks passed
  • Main-thread work: 1.7 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

8 to fix50
  • 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.

  • Largest Contentful Paint: 11.0 s

    11.0 s

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

  • Speed Index: 9.1 s

    9.1 s

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

  • Time to Interactive: 11.0 s

    11.0 s

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

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • 54 images without width and height

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

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

  • Tap response (INP) held steady for real visitors

    -7%

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

5 checks passed
  • Real-user CLS: 0.03

    0.03

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

  • Real-user TTFB: 793 ms

    793 ms

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

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

    -15%

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

  • Cumulative Layout Shift: 0.016

    0.016

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

  • Total Blocking Time: 23 ms

    23 ms

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

Images and page weight

4 to fix58
  • Page weight: 2.9 MB in 299 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 299 requests on a phone: other files 971 KiB (169), scripts 833 KiB (61) and fonts 577 KiB (22). Under 2 MB keeps phones on slow connections fast.

  • 9 images in older formats

    9 images (1.1 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.

  • 6 images below the first screen load straight away

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

  • 5 images far larger than shown

    37 KiB

    5 images are downloaded at several times the size a phone draws them, for example neurosmile-page-images-04-68ecb5801938d.webp at 1,080 px wide, shown at 350 px. Resized copies would save about 37 KiB.

  • About 0.8 g of CO₂ per visit

    0.84 g

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

Accessibility

3 to fixGoogle 8594
  • 4 text elements with low contrast

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

  • 68 images without alt text

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

1 checks passed
  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 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

4 to fixGoogle 7778
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (10 characters)

    Your title is only 10 characters: “Neurosmile”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

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

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

  • 24 internal links, 1 external

    The homepage links to 24 pages on tryneurosmile.com and 1 external page.

5 checks passed
  • One H1 headline

    Your main headline reads: “Neurosmile”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • 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://tryneurosmile.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

  • llms.txt published

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

Other pages

4 to fix75
  • 1 linked page hidden from search

    https://tryneurosmile.com/a/loop_subscriptions/get-subscription-link is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    / and https://tryneurosmile.com/a/loop_subscriptions/get-subscription-link all use the title “Neurosmile”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://tryneurosmile.com/pages/supplement, https://tryneurosmile.com/a/loop_subscriptions/get-subscription-link, https://tryneurosmile.com/pages/quiz, https://tryneurosmile.com/policies/privacy-policy, https://tryneurosmile.com/policies/refund-policy and https://tryneurosmile.com/policies/shipping-policy and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://tryneurosmile.com/pages/supplement, https://tryneurosmile.com/pages/contact, https://tryneurosmile.com/apps/parcelpanel, https://tryneurosmile.com/a/loop_subscriptions/get-subscription-link and https://tryneurosmile.com/pages/quiz have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://tryneurosmile.com/pages/contact and https://tryneurosmile.com/apps/parcelpanel 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.

  • 9 internal pages checked

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

3 checks passed
  • Linked pages load

    All 9 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 title

    All 9 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7791
  • 3 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • No analytics detected

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • About 569 words of copy

    The homepage carries about 569 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 Nerve Support”.

  • 15 calls to action

    The homepage has 15 calls to action, for example “Shop Nerve Support”, “Contact” and “Track Your Order”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 29 testimonial or review blocks and 3 trust badges.

  • 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 Tag Manager, 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.

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 cookies (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.

  • 31 other companies contacted

    Loading the homepage contacts 31 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 tryneurosmile.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 6 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Intelligems A B Testing · Kaching Bundles · Klaviyo Email Marketing Sms · Captain Shipping Protection · luckyorange.com · onetext.com

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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on tryneurosmile.com, including 19 speed issues, 4 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