novomins.com website review

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

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

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

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

8 third-party services load with your homepage (Reviews.io, Klaviyo and Shopify and others), adding 1.8 MB and 1.3 s of main-thread time.

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

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

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

Reviews.io costs a phone 340 ms of main-thread work and 415 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.

Klaviyo costs a phone 196 ms of main-thread work and 427 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 170 ms of main-thread work and 298 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.

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

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

17 KiB could be saved by minifying JavaScript.

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

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

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.

3 KiB could be saved by minifying CSS.

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

Your largest element takes 7.1 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 9.8 s (Speed Index). Good is under 3.4 s.

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

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

Your homepage downloads 5.2 MB in 453 requests on a phone: scripts 1.8 MB (103), other files 1.2 MB (229) and images 1.1 MB (67). Under 2 MB keeps phones on slow connections fast.

BF_Bundles_Banner_-_Mobile_3x_839c91a0-4acf-4449-9e92-eb9bdb 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 1.48 g of CO₂e: 177.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 dropdown has no label.

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 link inside paragraphs relies on colour alone to stand out.

Some lists contain elements other than list items, which screen readers announce wrongly.

1 tap target is too small or too close together to hit reliably with a finger.

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

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

Elements marked as presentational should be consistently ignored: 18 elements on the page fail this check, rated minor by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 3 elements on the page fail 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. (9 elements).

Your title is 67 characters, so Google will cut it off around 60: “Novomins © | Doctor Founded | Gummy Vitamins & Supplements | B-Corp”.

Your meta description is 166 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 397 pages on novomins.com and 15 external pages.

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

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

1 image failed to load on a phone, for example https://cdnjs.cloudflare.com/ajax/libs/flag-icon-css/4.1.4/flags/4x3/gb.svg.

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

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,280 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Klaviyo, Meta Pixel, Pinterest Tag and Reddit Pixel and 1 more (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 28 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 52 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.