Website review, no card needed
fabrics.cl website review
Visit site (opens in a new tab)Reviewed 4 November 202640 issues · 89 checks
This review found 40 issues worth fixing on fabrics.cl, 12 of them high impact, across 89 checks. The most urgent: main-thread work: 22.5 s. 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- #59,636 of 118,015 reviewed websitesbeats 44%
- #39,187 of 67,064 online storesbeats 36%
- #37,469 of 61,148 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 213 ms |
| May 23, 2026 | 216 ms |
| May 30, 2026 | 225 ms |
| Jun 6, 2026 | 227 ms |
| Jun 13, 2026 | 227 ms |
| Jun 20, 2026 | 228 ms |
| Jun 27, 2026 | 227 ms |
| Jul 4, 2026 | 230 ms |
| Jul 11, 2026 | 233 ms |
| Jul 18, 2026 | 233 ms |
| Jul 25, 2026 | 234 ms |
| Aug 1, 2026 | 240 ms |
| Aug 8, 2026 | 246 ms |
| Aug 15, 2026 | 251 ms |
| Aug 22, 2026 | 254 ms |
| Aug 29, 2026 | 262 ms |
| Sep 5, 2026 | 260 ms |
| Sep 12, 2026 | 258 ms |
| Sep 19, 2026 | 258 ms |
| Sep 26, 2026 | 254 ms |
| Oct 3, 2026 | 248 ms |
| Oct 10, 2026 | 243 ms |
| Oct 17, 2026 | 242 ms |
| Oct 24, 2026 | 242 ms |
| Oct 31, 2026 | 243 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
Main-thread work: 22.5 s
A phone's processor spends 22.5 s on main-thread work while loading, 3.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Clarity and Google Tag Manager and others), adding 2.6 MB and 1.6 s of main-thread time.
Reduce unused JavaScript
1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Shopify adds 672 ms
672 msShopify costs a phone 672 ms of main-thread work and 1.1 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.
Render-blocking requests
750 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Reduce unused CSS
300 ms · 74 KiBAbout 74 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.
Google Tag Manager adds 295 ms
295 msGoogle Tag Manager costs a phone 295 ms of main-thread work and 562 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.
Clarity adds 297 ms
297 msClarity costs a phone 297 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.
2,146 HTML elements
The page has 2,146 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 123 ms
123 msKlaviyo costs a phone 123 ms of main-thread work and 314 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.
azurefd.net adds 27 ms
27 msazurefd.net costs a phone 27 ms of main-thread work and 329 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.
Use efficient cache lifetimes
235 KiB11 files are served with short cache lifetimes, so returning visitors download them again (235 KiB).
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 220 ms. During a long task the page ignores taps.
Improve image delivery
218 KiB11 images could be 218 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
36 KiBPolyfills for old browsers add 36 KiB JavaScript that modern phones do not need.
Minify JavaScript
9 KiB9 KiB could be saved by minifying JavaScript.
Duplicated JavaScript
6 KiB6 KiB JavaScript is shipped twice across bundles.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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: 7 ms
7 msYour server sent the HTML in 7 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.
Time to Interactive: 27.1 s
27.1 sThe page becomes fully interactive after 27.1 s. Good is under 3.8 s.
Total Blocking Time: 748 ms
748 msScripts block taps and scrolling for 748 ms in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 4.1 s
4.1 sYour largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Fabrics”.
Real-user INP: 224 ms
224 msReal visitors wait 224 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Speed Index: 5.1 s
5.1 sVisually, the page fills in at 5.1 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 213 ms to 243 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 698 ms
698 msReal visitors wait 698 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 5.3 MB in 475 requests
5.3 MBYour homepage downloads 5.3 MB in 475 requests on a phone: scripts 2.5 MB (125), other files 1.5 MB (269) and images 893 KiB (42). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
HOME_SLIDER_MOBILE_3_1.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).
About 1.5 g of CO₂ per visit
1.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.51 g of CO₂e: 180.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
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.
14 links without text
14 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (8 elements)
Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h4 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 9 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is short (68 characters)
Your meta description is only 68 characters: “Inspírate en Fabrics y crea junto a nosotros el hogar de tus sueños.”. 70 to 160 characters is enough to sell the click.
One H1 headline
Your <h1> is empty.
242 internal links, 6 external
The homepage links to 242 pages on fabrics.cl and 6 external pages.
6 checks passed
Title: 56 characters
Your title is a healthy 56 characters: “Fabrics | Ropa de cama, telas, baño, muebles y cortinas.”.
Canonical URL set
The canonical URL is https://fabrics.cl/.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://fabrics.cl/sitemap.xml.
AI search readiness
No llms.txt
There is no https://fabrics.cl/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.
3 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 (823 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages without a meta description
https://fabrics.cl/pages/bienvenido-a-fabrics-cl, https://fabrics.cl/pages/contacto-formulario and https://fabrics.cl/pages/seguimiento-mi-pedido have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://fabrics.cl/pages/bienvenido-a-fabrics-cl, https://fabrics.cl/pages/politicas-de-despacho and https://fabrics.cl/pages/seguimiento-mi-pedido have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 96 found) and read each the way a search engine does.
5 checks passed
Linked pages load
5 pages of 15 loaded without an error (the rest turned automated requests away).
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 5 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “jQuery is not defined”.
2 checks passed
Tap targets are thumb-sized
44 of 52 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 238 words
The homepage has only about 238 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
2 checks passed
5 short forms
5 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, 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.
6 cookies set on arrival
6Opening the homepage sets 6 cookies, 3 of them by other companies (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.
34 other companies contacted
Loading the homepage contacts 34 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 fabrics.cl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on fabrics.cl, including 18 speed issues, 2 SEO issues and 5 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.