Website review, no card needed
fluchos.es website review
Visit site (opens in a new tab)Reviewed 8 November 202633 issues · 83 checks
This review found 33 issues worth fixing on fluchos.es, 10 of them high impact, across 83 checks. The most urgent: page weight: 14.0 MB in 219 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
78C- #60,650 of 120,410 reviewed websitesbeats 44%
- #39,759 of 68,161 online storesbeats 36%
- #38,002 of 62,115 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 249 ms |
| May 23, 2026 | 279 ms |
| May 30, 2026 | 324 ms |
| Jun 6, 2026 | 349 ms |
| Jun 13, 2026 | 358 ms |
| Jun 20, 2026 | 357 ms |
| Jun 27, 2026 | 358 ms |
| Jul 4, 2026 | 359 ms |
| Jul 11, 2026 | 360 ms |
| Jul 18, 2026 | 360 ms |
| Jul 25, 2026 | 356 ms |
| Aug 1, 2026 | 354 ms |
| Aug 8, 2026 | 356 ms |
| Aug 15, 2026 | 360 ms |
| Aug 22, 2026 | 348 ms |
| Aug 29, 2026 | 328 ms |
| Sep 5, 2026 | 306 ms |
| Sep 12, 2026 | 282 ms |
| Sep 19, 2026 | 272 ms |
| Sep 26, 2026 | 268 ms |
| Oct 3, 2026 | 265 ms |
| Oct 10, 2026 | 260 ms |
| Oct 17, 2026 | 255 ms |
| Oct 24, 2026 | 251 ms |
| Oct 31, 2026 | 242 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Render-blocking requests
1.3 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
4,182 HTML elements
The page has 4,182 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
900 ms · 486 KiB6 images could be 486 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.
6 third-party services on the page
6 third-party services load with your homepage (Klaviyo, Shopify and scalapay.com and others), adding 10.3 MB and 116 ms of main-thread time.
Shopify adds 44 ms
44 msShopify costs a phone 44 ms of main-thread work and 9.9 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.
Mobile performance score: 71
71/100Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
300 ms · 57 KiBAbout 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.
Main-thread work: 2.3 s
A phone's processor spends 2.3 s on main-thread work while loading, 391 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
164 KiB7 files are served with short cache lifetimes, so returning visitors download them again (164 KiB).
Minify JavaScript
150 ms · 3 KiB3 KiB could be saved by minifying JavaScript.
Reduce unused JavaScript
92 KiBAbout 92 KiB of JavaScript is downloaded but never used on this page.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 68 ms. During a long task the page ignores taps.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 66 ms
66 msYour server sent the HTML in 66 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Largest Contentful Paint: 7.9 s
7.9 sYour largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 13.3 s
13.3 sThe page becomes fully interactive after 13.3 s. Good is under 3.8 s.
Real-user INP: 205 ms
205 msReal visitors wait 205 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Speed Index: 5.3 s
5.3 sVisually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 249 ms to 242 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 516 ms
516 msReal visitors wait 516 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.012
0.012The layout barely moves while loading (CLS 0.012, good is under 0.1).
Total Blocking Time: 21 ms
21 msScripts block the page for only 21 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 14.0 MB in 219 requests
14.0 MBYour homepage downloads 14.0 MB in 219 requests on a phone: media 9.7 MB (1), images 2.8 MB (99) and scripts 631 KiB (61). Under 2 MB keeps phones on slow connections fast.
4 images below the first screen load straight away
4 images further down the page (714 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
4 images far larger than shown
136 KiB4 images are downloaded at several times the size a phone draws them, for example D9782-CALF-TABACO.jpg at 1,080 px wide, shown at 324 px. Resized copies would save about 136 KiB.
About 4.0 g of CO₂ per visit
3.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.97 g of CO₂e: 475.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
73 text elements with low contrast
73 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
85 images without alt text
85 images have no alt text, which hurts accessibility and image search.
Contentinfo landmark should not be contained in another landmark (1 element)
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)
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)
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)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
15 links without text
15 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
257 internal links, 10 external
The homepage links to 257 pages on fluchos.es and 10 external pages.
6 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “Descubre la última tendencia en diseño, calidad y comodidad de tus zapatos Fluchos de hombre y mujer ¡Visita la nueva c…”.
Title: 31 characters
Your title is a healthy 31 characters: “Fluchos - Tienda Online Oficial”.
Canonical URL set
The canonical URL is https://fluchos.es/.
Structured data in place
Structured data found: Organization and WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://fluchos.es/sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (995 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://fluchos.es/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
7 pages without a meta description
https://fluchos.es/collections/slip-on-invierno-de-hombre, https://fluchos.es/collections/calcetines-hombre, https://fluchos.es/collections/cuidado-y-limpieza, https://fluchos.es/pages/clasicos, https://fluchos.es/collections/originals-hombre and https://fluchos.es/collections/profesionales-hombre and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
11 pages without an H1
https://fluchos.es/collections/hombre-invierno, https://fluchos.es/collections/botines-invierno-de-hombre, https://fluchos.es/collections/zapatos-hombre-invierno, https://fluchos.es/collections/deportivos-hombre-invierno, https://fluchos.es/collections/slip-on-invierno-de-hombre and https://fluchos.es/collections/mocasines-invierno-de-hombre and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://fluchos.es/collections/zapatos-hombre-invierno and https://fluchos.es/collections/deportivos-hombre-invierno took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 119 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
81 distorted images
81 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
53 of 63 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 470 words of copy
The homepage carries about 470 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop now”.
2 calls to action
The homepage has 2 calls to action, for example “Contact” and “Shop now”.
5 short forms
5 short forms (2 fields at most) are right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
6 trackers load before any consent
6Before 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.
13 cookies set on arrival
13Opening the homepage sets 13 cookies (measured from a US location before any click).
No consent tool detected
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.
23 other companies contacted
Loading the homepage contacts 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at fluchos.es, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Multifeeds · Scalapay On Site Messaging · Klaviyo Email Marketing Sms · Langify · Orbe Geolocation · Scalapay Widget Installer Prod · Infinite Scroll
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on fluchos.es, including 14 speed issues, 2 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.