evecurls.com website review

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

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

The page goes through 2 redirects before it starts loading, costing about 2.0 s. Link and advertise the final URL directly.

Google Tag Manager costs a phone 1.3 s of main-thread work and 485 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

A phone's processor spends 9.5 s on main-thread work while loading, 4.2 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 Clarity and others), adding 1.1 MB and 2.0 s of main-thread time.

29 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

The HTML itself could arrive about 150 ms sooner: redirects, a slow server response or missing compression delay everything after it.

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

21 KiB JavaScript is shipped twice across bundles.

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

5 KiB could be saved by minifying JavaScript.

Your largest element takes 19.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Beautiful curls, naturally.”.

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 160 ms to 193 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 6.3 MB in 358 requests on a phone: images 3.0 MB (97), scripts 1.9 MB (126) and other files 818 KiB (100). Under 2 MB keeps phones on slow connections fast.

24 images are downloaded at several times the size a phone draws them, for example Eve_Curls_Hero_Mobile.svg at 1,211 px wide, shown at 390 px. Resized copies would save about 1.3 MB.

17 images (1.5 MB) 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.80 g of CO₂e: 215.7 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.

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

Your title is only 9 characters: “Eve Curls”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 55 characters: “Luxury cosmetics brand selling curly haircare products.”. 70 to 160 characters is enough to sell the click.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 76 pages on evecurls.com and 19 external pages.

Your homepage links to /pages/evecurls-quiz, which answers with an error. Visitors hit a dead end and search engines drop it.

/collections/curl-care-products and /collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/curl-care-products, /pages/over-ons, /pages/hoe-te-gebruiken, /pages/untitled-sep-18-11-49-07 and /collections/all have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 27 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=187176441&tm=gtm002&Ver=2&mid=39c9b7e8-8a7c-4872-bff4-c81a14ee9e55&bo=1&sid=2c8829d0da0011f18324bf7aa7729dc0&vid=2c884ba0da0011f1b5c2e328037e5ec1&vids=1&msclkid=N&pi=9.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “s is not a function”.

Chrome logged issues while loading the page (“Cookie”).

5 links from your homepage to your own site are broken, for example https://www.evecurls.com/collections/curl-care-products (network).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

2 links go through two or more redirects, for example https://www.evecurls.com/customer_authentication/redirect?locale=nl&region_country=NL.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

evecurls.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

The page uses urgency cues (a countdown or limited-time wording).

DMARC is set to p=none, so mail pretending to be evecurls.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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