livarcticessentials.com website review

8 images could be 308 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

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

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

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

About 434 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

8 third-party services load with your homepage (ContentSquare, Klaviyo and enzuzo.com and others), adding 1.1 MB and 493 ms of main-thread time.

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

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

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

Polyfills for old browsers add 26 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.

Your largest element takes 18.6 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 24.0 s. Good is under 3.8 s.

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

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

Your homepage downloads 14.7 MB in 287 requests on a phone: media 8.3 MB (1), images 3.9 MB (53) and scripts 1.3 MB (94). Under 2 MB keeps phones on slow connections fast.

1 image (130 KiB) is 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.

3 images further down the page (68 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 4.16 g of CO₂e: 499.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

All page content should be contained by landmarks: 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.

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.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Elements with visible text labels do not have matching accessible names. (5 elements).

There are 2 <h1> headlines (“Discover Nordic-inspired, science-backed suppleme…” and “In the Nordics, health isn’t a trend - it’s a way…”). One clear main headline is easier for people and search engines.

Structured data found (ItemList, OnlineStore and Webpage) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected token ']', ..."ivArctic",], ""... is not va)”.

15 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 141 pages on livarcticessentials.com and 6 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles) 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://livarcticessentials.com/collections/all, https://livarcticessentials.com/products/energy-essentials, https://livarcticessentials.com/products/nda-nordic-longevity, https://livarcticessentials.com/products/gut-essentials, https://livarcticessentials.com/products/meno-essentials and https://livarcticessentials.com/products/move-essentials and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 40 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.

1 error was logged to the browser console while the page loaded, for example “Identifier 'fallbackTimer' has already been declared”.

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

The homepage carries about 1,537 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 18 cookies, 1 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 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.