nuheara.com website review

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

22 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.0 s.

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

Google Tag Manager costs a phone 1.3 s of main-thread work and 1.2 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.

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

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

8 third-party services load with your homepage (Google Tag Manager, ZenDesk and Facebook and others), adding 2.3 MB and 2.7 s of main-thread time.

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

ZenDesk costs a phone 421 ms of main-thread work and 455 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 452 ms. During a long task the page ignores taps.

86 KiB could be saved by minifying JavaScript.

About 61 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.

Facebook costs a phone 293 ms of main-thread work and 227 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.

16 KiB could be saved by minifying CSS.

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

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

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.

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 visitors wait 4.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 4.4 MB in 247 requests on a phone: scripts 2.9 MB (81), images 1.1 MB (56) and fonts 222 KiB (5). Under 2 MB keeps phones on slow connections fast.

2 images (76 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.

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

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

4 buttons have no accessible name, so screen readers announce just “button”.

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

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

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 15 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 on the page fail this check, rated moderate by axe-core.

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

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

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

1 link has no real href, so search engines can't follow it.

The homepage links to 36 pages on nuheara.com and 18 external pages.

Your Organization JSON-LD is missing 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.

There is no https://www.nuheara.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.

https://www.nuheara.com/video/max-on-max-customer-spotlight has no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=13007660&tm=gtm002&Ver=2&mid=7f5bf35a-f45d-4eea-8716-b7af03519723&bo=1&sid=0ce34ca0dcd911f1a7d131ce3bc34abe&vid=0ce38b00dcd911f1ad1a17bd125701d7&vids=1&msclkid=N&pi=91.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “_tfa is not defined”.

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

Large scripts ship without source maps.

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

The homepage carries about 400 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 9 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 27 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 55 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.