fajasmariae.eu website review

The page goes through 1 redirect before it starts loading, costing about 3.8 s. Link and advertise the final URL directly.

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

Your mobile performance score is 64. 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 700 ms.

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

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

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

7 third-party services load with your homepage (Shopify, weglot.com and Amazon Web Services and others), adding 290 KiB and 156 ms of main-thread time.

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

37 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

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

Your homepage downloads 9.0 MB in 310 requests on a phone: media 6.6 MB (1), other files 738 KiB (95) and images 699 KiB (43). Under 2 MB keeps phones on slow connections fast.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

25 elements hidden from screen readers can still receive keyboard focus.

Some list items are not inside a list.

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

1 tap target is too small or too close together to hit reliably with a finger.

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

Your title is 84 characters, so Google will cut it off around 60: “Fajas Colombianas MariaE, postquirúrgicas, y uso diario – Fajas MariaE Internacional”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

The homepage links to 66 pages on fajasmariae.eu and 12 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

Your homepage links to https://intl.fajasmariae.com/collections/cinturillas, which answers with an error. Visitors hit a dead end and search engines drop it.

https://intl.fajasmariae.com/collections/mas-vendidos-home, https://intl.fajasmariae.com/collections/nuevo, https://intl.fajasmariae.com/collections/basicos, https://intl.fajasmariae.com/collections/leggings, https://intl.fajasmariae.com/collections/colas-invisibles and https://intl.fajasmariae.com/collections/brasieres use the same meta description. A description written for each page earns more clicks.

https://intl.fajasmariae.com/collections/mas-vendidos-home, https://intl.fajasmariae.com/collections/nuevo, https://intl.fajasmariae.com/collections/basicos, https://intl.fajasmariae.com/collections/moldeadores, https://intl.fajasmariae.com/collections/todos-los-productos and https://intl.fajasmariae.com/collections/leggings and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://intl.fajasmariae.com/collections/mas-vendidos-home, https://intl.fajasmariae.com/collections/todos-los-productos and https://intl.fajasmariae.com/products/short-en-powernet-fu101 have 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 39 found) and read each the way a search engine does.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Opening the homepage sets 10 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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.