alexoo.com website review

11 images could be 742 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and omnisnippet1.com and others), adding 1.0 MB and 1.1 s of main-thread time.

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

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

Google Tag Manager costs a phone 711 ms of main-thread work and 514 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 63 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.

About 306 KiB of JavaScript is downloaded but never used on this page.

Shopify costs a phone 258 ms of main-thread work and 382 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.

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

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

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.

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.

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

Real visitors wait 222 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-11-07, real Chrome visitors' tap response (inp) went from 137 ms to 198 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Your homepage downloads 5.6 MB in 372 requests on a phone: images 3.2 MB (53), scripts 1.1 MB (153) and other files 895 KiB (150). Under 2 MB keeps phones on slow connections fast.

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

22 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious 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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

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

The homepage links to 107 pages on alexoo.com and 2 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://alexoo.it/en-us/collections/saldi, https://alexoo.it/en-us/collections/novita, https://alexoo.it/en-us/collections/scarpe, https://alexoo.it/en-us/collections/stivali, https://alexoo.it/en-us/collections/stivaletti and https://alexoo.it/en-us/collections/sneakers and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 281 words of visible text.

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