nfsupplementseu.com website review

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

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

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

8 third-party services load with your homepage (rebuyengine.com, Google Tag Manager and Clarity and others), adding 2.0 MB and 821 ms of main-thread time.

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

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

rebuyengine.com costs a phone 255 ms of main-thread work and 704 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 Tag Manager costs a phone 200 ms of main-thread work and 310 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 costs a phone 26 ms of main-thread work and 709 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.

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

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

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

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

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

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

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 “Logan King, founder of NF Supplements, holding a bottle wit…”.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.9 MB in 333 requests on a phone: scripts 1.4 MB (89), other files 1.1 MB (167) and images 720 KiB (43). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example Blood_Pressure_Support.webp at 2,048 px wide, shown at 40 px. Resized copies would save about 257 KiB.

3 images (353 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.

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

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

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

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

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

There are 2 <h1> headlines (“” and “We third-party test every batch.”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 38 pages on nfsupplementseu.com and 14 external pages.

https://nfsupplementseu.com/a/loop_subscriptions/customer is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://nfsupplementseu.com/pages/contact, https://nfsupplementseu.com/pages/about-us, https://nfsupplementseu.com/a/loop_subscriptions/customer, https://nfsupplementseu.com/collections/anti-ageing, https://nfsupplementseu.com/collections/antioxidants-anti-inflammatory and https://nfsupplementseu.com/collections/blood-pressure-heart-health and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://nfsupplementseu.com/a/loop_subscriptions/customer has no <h1> headline, so visitors and search engines get no clear main topic.

https://nfsupplementseu.com/pages/about-us, https://nfsupplementseu.com/a/loop_subscriptions/customer and https://nfsupplementseu.com/collections/anti-ageing took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 28 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=137035667&Ver=2&mid=56ff8236-4b81-462b-8e71-9116bf4b2a4a&bo=1&sid=4ca992e0ddd711f19a86d5d7553c384f&vid=4ca9a7f0ddd711f1b3fc619119d76cd5&vids=1&msclkid=N&pi=918639831&l.

1 error was logged to the browser console while the page loaded, for example “Failed to execute 'observe' on 'IntersectionObserver': parameter 1 is not of type 'Element'.”.

The homepage carries about 2,353 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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 25 cookies, 3 of them by other companies (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 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.