fluchos.com website review

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

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

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

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

6 third-party services load with your homepage (Klaviyo, Shopify and Bugsnag and others), adding 7.9 MB and 202 ms of main-thread time.

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

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

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

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

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

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

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

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.

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 10.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 15.4 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 see the first content after 1.8 s (75th percentile). Good is under 1.8 s.

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

2 images 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 236 ms to 227 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 11.5 MB in 255 requests on a phone: media 7.3 MB (1), images 2.6 MB (107) and other files 635 KiB (70). Under 2 MB keeps phones on slow connections fast.

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

3 images are downloaded at several times the size a phone draws them, for example F2065-NEBRASKA-NUT.jpg at 1,080 px wide, shown at 324 px. Resized copies would save about 101 KiB.

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

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

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

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.

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

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

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.

Your title is 70 characters, so Google will cut it off around 60: “Fluchos Official Online Store | Comfortable footwear for men and women”.

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://fluchos.es)”.

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

The homepage links to 250 pages on fluchos.com and 10 external pages.

/en/collections/slip-on-invierno-de-hombre, /en/collections/calcetines-hombre, /en/collections/cuidado-y-limpieza, /en/pages/clasicos, /en/collections/originals-hombre and /en/collections/profesionales-hombre and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

/en/collections/hombre-invierno, /en/collections/botines-invierno-de-hombre, /en/collections/zapatos-hombre-invierno, /en/collections/deportivos-hombre-invierno, /en/collections/slip-on-invierno-de-hombre and /en/collections/mocasines-invierno-de-hombre and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

92 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://fluchos.com/en/account.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

fluchos.com is registered until Nov 2026. If it lapses, the site and its email stop working and someone else can buy the name. Renew it, and turn on auto-renew.

fluchos.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

fluchos.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage carries about 461 words of visible text.

DMARC is set to p=none, so mail pretending to be fluchos.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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