we-ar4.com website review

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

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

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

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

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

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

Klaviyo costs a phone 203 ms of main-thread work and 309 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.

8 third-party services load with your homepage (Klaviyo, Crazy Egg and Forter and others), adding 855 KiB and 436 ms of main-thread time.

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

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

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

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

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

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

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 6.5 MB in 378 requests on a phone: images 3.8 MB (9), other files 1.5 MB (262) and scripts 864 KiB (74). Under 2 MB keeps phones on slow connections fast.

4 images weigh 2.2 MB together. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example 4_a662e620-c44f-4da7-a622-ac907aec191c_2800x.jpg at 2,400 px wide, shown at 390 px. Resized copies would save about 2.0 MB.

2_cf45fd64-c62e-4333-96a7-3c68151672c8_2800x.jpg 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.83 g of CO₂e: 219.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

There are 3 <h1> headlines (“”, “CAPSULE 024 THE YEAR OF IT” and “THE CAROLYN CAMISOLE”). One clear main headline is easier for people and search engines.

The homepage links to 87 pages on we-ar4.com and 1 external page.

https://www.we-ar4.com/pages/frequently-asked-questions, https://www.we-ar4.com/pages/join-our-mail-list, https://www.we-ar4.com/collections/new-arrivals, https://www.we-ar4.com/collections/the-bessette-edit, https://www.we-ar4.com/collections/on-the-street and https://www.we-ar4.com/collections/the-gift-edit and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

4 of 14 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 “Access to fetch at 'https://analytics-integration.onrender.com/analytics?shopDomain=we-ar-4.myshopify.com' from origin …”.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 156 words of visible text; thin pages give Google and first-time buyers little to go on.

Before a visitor clicks anything, the page loads Klaviyo (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 10 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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.