shopalexis.com website review

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

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

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

8 third-party services load with your homepage (actionbase.ai, Google Tag Manager and Shopify and others), adding 2.6 MB and 1.5 s of main-thread time.

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

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

Google Tag Manager costs a phone 479 ms of main-thread work and 560 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 527 KiB of JavaScript is downloaded but never used on this page.

actionbase.ai costs a phone 488 ms of main-thread work and 213 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 93 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.

Shopify costs a phone 172 ms of main-thread work and 1.5 MB 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.

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

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

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

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

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

4 KiB could be saved by minifying CSS.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors see the first content after 3.6 s (75th percentile). Good is under 1.8 s.

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

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

Real visitors wait 3.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 363 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.9 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

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

Your homepage downloads 4.9 MB in 335 requests on a phone: images 2.2 MB (123), scripts 1.5 MB (81) and other files 815 KiB (109). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example bvv6c5hpbT8L6aZNw31F6_whHycJTccopy.webp at 3,392 px wide, shown at 90 px. Resized copies would save about 2.7 MB.

3 images weigh 2.1 MB together. On a phone connection a single image that size takes seconds.

9 images (2.8 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.

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

Scrollable region must have keyboard access: 12 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.

1 image has no alt text, which hurts accessibility and image search.

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

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

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

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

Headings skip levels (h3 → 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 119 pages on shopalexis.com and 13 external pages.

There is no https://www.shopalexis.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

Your homepage links to https://www.shopalexis.com/collections/new-arrivals, https://www.shopalexis.com/collections/tops and https://www.shopalexis.com/collections/sets, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.shopalexis.com/collections/dresses, https://www.shopalexis.com/collections/shorts-pants, https://www.shopalexis.com/collections/skirts, https://www.shopalexis.com/collections/jackets-robes and https://www.shopalexis.com/collections/suiting use the same meta description. A description written for each page earns more clicks.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

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

Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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 55 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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