eviteshop.se website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and aimerce.ai and others), adding 1.2 MB and 763 ms of main-thread time.

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

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

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

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

Google Tag Manager costs a phone 278 ms of main-thread work and 343 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 251 ms of main-thread work and 489 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 2,082 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

27 KiB JavaScript is shipped twice across bundles.

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

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

3 KiB could be saved by minifying CSS.

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

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

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

The layout shifts by 0.121 while loading, so content jumps under the reader's thumb. Good is under 0.1.

3 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 4.8 MB in 409 requests on a phone: other files 2.0 MB (244), images 1.3 MB (43) and scripts 1.2 MB (94). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example ugc-imke-roose-smart-niet-als-advertentie-hd-35069.jpg at 540 px wide, shown at 135 px. Resized copies would save about 122 KiB.

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

15 buttons have no accessible name, so screen readers announce just “button”.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

The homepage links to 102 pages on eviteshop.se and 7 external pages.

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

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

4 errors were logged to the browser console while the page loaded, for example “❌ [WAIT-FOR-UTILS] Growi cookie utilities not loaded after 5 retries (500ms total)”.

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 319 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 23 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 37 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.