alhamas.co website review

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

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

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

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

8 third-party services load with your homepage (Clarity, Google Tag Manager and etrusted.com and others), adding 1,020 KiB and 744 ms of main-thread time.

19 images could be 586 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Clarity costs a phone 355 ms of main-thread work and 29 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.

etrusted.com costs a phone 82 ms of main-thread work and 454 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.

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

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

7 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 12.3 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.7 s. Good is under 3.8 s.

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

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

1 image 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 6.8 MB in 970 requests on a phone: images 4.0 MB (100), other files 1.7 MB (753) and scripts 699 KiB (71). Under 2 MB keeps phones on slow connections fast.

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

9 images further down the page (861 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (160 KiB) is 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.92 g of CO₂e: 231.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

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

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 16 characters: “Alhamas-Colombia”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 4 <h1> headlines (“”, “Restablecer tu contraseña” and “¡Hola!”). One clear main headline is easier for people and search engines.

3 links have no real href, so search engines can't follow them.

The homepage links to 260 pages on alhamas.co and 6 external pages.

https://alhamas.co/collections/all, https://alhamas.co/collections/complementos-carrito, https://alhamas.co/collections/sandalias, https://alhamas.co/collections/romero-12cm and https://alhamas.co/collections/cuna-media-plataforma-1 have no meta description, so Google writes the search snippet from whatever text it finds.

https://alhamas.co/collections/all, https://alhamas.co/collections/complementos-carrito, https://alhamas.co/collections/mas-vendidos, https://alhamas.co/collections/alpargatas-con-cintas, https://alhamas.co/collections/alpargatas-con-pulsera and https://alhamas.co/collections/sandalias and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://alhamas.co/cdn/shop/t/2/assets/convertlab-packs-picker.css?v=820' because its MIME…”.

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.

Social proof on the homepage: 1 customer or partner logo. 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.

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 766 words of visible text.

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

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