naddirect.com website review

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

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and POWr and others), adding 1.7 MB and 1.4 s of main-thread time.

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

About 840 KiB of JavaScript is downloaded but never used on this page.

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

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

Google Tag Manager costs a phone 366 ms of main-thread work and 344 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.

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

Klaviyo costs a phone 261 ms of main-thread work and 530 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.

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

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

18 KiB could be saved by minifying CSS.

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

Polyfills for old browsers add 42 KiB JavaScript that modern phones do not need.

33 KiB could be saved by minifying JavaScript.

1 image could be 15 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 149 ms to 161 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 1.6 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.1 MB in 307 requests on a phone: media 5.5 MB (2), scripts 2.2 MB (130) and other files 842 KiB (121). Under 2 MB keeps phones on slow connections fast.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

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

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

The homepage links to 155 pages on naddirect.com and 22 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.

https://naddirect.com/collections/human-performance, https://naddirect.com/collections/longevity, https://naddirect.com/collections/sexual-health, https://naddirect.com/collections/sleep-circadian-rhythm, https://naddirect.com/collections/hair-skin and https://naddirect.com/collections/metabolic-syndrome-weight-loss have no meta description, so Google writes the search snippet from whatever text it finds.

https://naddirect.com/collections/human-performance, https://naddirect.com/collections/longevity, https://naddirect.com/collections/sexual-health, https://naddirect.com/collections/sleep-circadian-rhythm, https://naddirect.com/collections/hair-skin and https://naddirect.com/collections/metabolic-syndrome-weight-loss and 6 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.

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

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 2,136 words of visible text.

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

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

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