barbadens.com website review

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

Shopify costs a phone 1.0 s of main-thread work and 1.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Shopify, pop-convert.com and Facebook and others), adding 2.7 MB and 2.8 s of main-thread time.

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

20 long tasks block the main thread while loading, the longest for 1.4 s. During a long task the page ignores taps.

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

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

pop-convert.com costs a phone 375 ms of main-thread work and 311 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.

Facebook costs a phone 369 ms of main-thread work and 271 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.

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

Klaviyo costs a phone 201 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.

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

About 10 KiB of CSS is downloaded but never applied on this page.

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

2 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 wait 641 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

The page becomes fully interactive after 25.9 s. Good is under 3.8 s.

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

Your largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner Image”.

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

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

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

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

Diseno_sin_titulo_2.gif weighs 13.1 MB. On a phone connection a single image that size takes seconds.

Your homepage downloads 6.4 MB in 358 requests on a phone: scripts 2.6 MB (155), images 2.6 MB (43) and other files 882 KiB (119). Under 2 MB keeps phones on slow connections fast.

1 image (13.1 MB) 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.

VISITANOS_BANNER_MOVIL_1.png 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).

1 image further down the page (25 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 1.81 g of CO₂e: 217.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

Your <h1> is empty.

The homepage links to 89 pages on barbadens.com and 13 external pages.

There is no https://barbadens.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.

https://barbadens.com/collections/todas-las-camisas, https://barbadens.com/pages/a-tu-medida, https://barbadens.com/collections/pantalones and https://barbadens.com/collections/camisas-mujer have no meta description, so Google writes the search snippet from whatever text it finds.

https://barbadens.com/collections/todas-las-camisas, https://barbadens.com/pages/a-tu-medida, https://barbadens.com/collections/pantalones, https://barbadens.com/collections/camisas-mujer and https://barbadens.com/collections/preventa have no <h1> headline, so visitors and search engines get no clear main topic.

https://barbadens.com/pages/a-tu-medida has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

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 1,035 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 4 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 29 cookies, 6 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.