duffbeauty.se website review

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

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

8 third-party services load with your homepage (zuzana.ai, Google Tag Manager and Klarna and others), adding 1.9 MB and 1.4 s of main-thread time.

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

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

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

zuzana.ai costs a phone 787 ms of main-thread work and 922 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 820 KiB of JavaScript is downloaded but never used on this page.

Google Tag Manager costs a phone 281 ms of main-thread work and 334 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 1,781 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

About 27 KiB of CSS is downloaded but never applied on this page.

16 KiB JavaScript is shipped twice across bundles.

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 9.3 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 20.9 s. Good is under 3.8 s.

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

Visually, the page fills in at 7.2 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 119 ms to 172 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.2 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 13.9 MB in 355 requests on a phone: media 8.2 MB (1), scripts 2.1 MB (77) and images 2.0 MB (54). Under 2 MB keeps phones on slow connections fast.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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.

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

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

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

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

The homepage links to 215 pages on duffbeauty.se and 15 external pages.

https://duffbeauty.se/pages/valj-ditt-startkit, https://duffbeauty.se/collections/vipper and https://duffbeauty.se/collections/strip-lashes use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://duffbeauty.se/collections/accessories-old, whose canonical is https://duffbeauty.se/collections/accessories. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

2 images failed to load on a phone, for example https://duffbeauty.se/.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 379 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 19 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 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.