Website review, no card needed
tricot.cl website review
Visit site (opens in a new tab)Reviewed 28 October 202648 issues · 92 checks
This review found 48 issues worth fixing on tricot.cl, 22 of them high impact, across 92 checks. The most urgent: improve image delivery. 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
59F- #121,256 of 124,051 reviewed websitesbeats 2%
- #69,259 of 69,761 online storesbeats 1%
- #262 of 291 Salesforce Commerce Cloud storesbeats 9%
Closest competitors among Salesforce Commerce Cloud stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.7 s |
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 223 ms |
| May 16, 2026 | 220 ms |
| May 23, 2026 | 217 ms |
| May 30, 2026 | 216 ms |
| Jun 6, 2026 | 219 ms |
| Jun 13, 2026 | 220 ms |
| Jun 20, 2026 | 221 ms |
| Jun 27, 2026 | 222 ms |
| Jul 4, 2026 | 224 ms |
| Jul 11, 2026 | 225 ms |
| Jul 18, 2026 | 225 ms |
| Jul 25, 2026 | 225 ms |
| Aug 1, 2026 | 227 ms |
| Aug 8, 2026 | 229 ms |
| Aug 15, 2026 | 231 ms |
| Aug 22, 2026 | 232 ms |
| Aug 29, 2026 | 231 ms |
| Sep 5, 2026 | 229 ms |
| Sep 12, 2026 | 229 ms |
| Sep 19, 2026 | 228 ms |
| Sep 26, 2026 | 227 ms |
| Oct 3, 2026 | 227 ms |
| Oct 10, 2026 | 226 ms |
| Oct 17, 2026 | 226 ms |
| Oct 24, 2026 | 225 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
Improve image delivery
1.3 s · 2.9 MB31 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.
Render-blocking requests
2.5 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Use efficient cache lifetimes
1.5 s · 639 KiB30 files are served with short cache lifetimes, so returning visitors download them again (639 KiB).
Mobile performance score: 27
27/100Your mobile performance score is 27 (desktop: 33). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,981 HTML elements
The page has 4,981 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.9 s
A phone's processor spends 4.9 s on main-thread work while loading, 3.3 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 (Google Tag Manager, Google CDN and Clarity and others), adding 2.1 MB and 1.7 s of main-thread time.
Reduce unused JavaScript
450 ms · 1,006 KiBAbout 1,006 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused CSS
900 ms · 122 KiBAbout 122 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Google Tag Manager adds 627 ms
627 msGoogle Tag Manager costs a phone 627 ms of main-thread work and 878 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 CDN adds 353 ms
353 msGoogle CDN costs a phone 353 ms of main-thread work and 733 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 237 ms. During a long task the page ignores taps.
Legacy JavaScript
33 KiBPolyfills for old browsers add 33 KiB JavaScript that modern phones do not need.
Minify JavaScript
12 KiB12 KiB could be saved by minifying JavaScript.
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: 9 ms
9 msYour server sent the HTML in 9 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.
Real-user CLS: 0.32
0.32For real visitors the layout shifts by 0.32 (75th percentile). Good is under 0.1.
Time to Interactive: 28.5 s
28.5 sThe page becomes fully interactive after 28.5 s. Good is under 3.8 s.
Cumulative Layout Shift: 1.133
1.133The layout shifts by 1.133 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 8.9 s
8.9 sYour largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Blusas mujer”.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 238 ms
238 msReal visitors wait 238 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.7 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 978 ms
978 msReal visitors wait 978 ms for your server to start answering (75th percentile). Good is under 800 ms.
69 images without width and height
69 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 526 ms
526 msScripts block taps and scrolling for 526 ms in total while the page loads. Good is under 200 ms.
Speed Index: 5.2 s
5.2 sVisually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 223 ms to 225 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Images and page weight
Page weight: 6.7 MB in 192 requests
6.7 MBYour homepage downloads 6.7 MB in 192 requests on a phone: images 3.5 MB (89), scripts 2.3 MB (40) and other files 391 KiB (51). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
S-BLUSAS-HOME-360x337-TD.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).
1 image far larger than shown
75 KiB1 image is downloaded at several times the size a phone draws it, for example tricot-cancer-mujer.png at 3,660 px wide, shown at 100 px. Resized copies would save about 75 KiB.
8 images in older formats
8 images (427 KiB) are 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.
3 images below the first screen load straight away
3 images further down the page (242 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.9 g of CO₂ per visit
1.91 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.91 g of CO₂e: 229.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
4 elements use ARIA attributes their role does not allow, which confuses screen readers.
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
5 elements hidden from screen readers can still receive keyboard focus.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Form elements should have a visible label (1 element)
Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 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.
55 links without text
55 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4 and h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 100 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 11 failed. 4 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 (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
609 internal links, 27 external
The homepage links to 609 pages on tricot.cl and 27 external pages.
6 checks passed
Meta description: 133 characters
Your meta description is 133 characters: “Encuentra vestuario para hombre, mujer y niños al mejor precio. ¡Compra online y aprovecha despacho gratis por compras …”.
Title: 41 characters
Your title is a healthy 41 characters: “Moda y estilo al mejor precio | Tricot.cl”.
Canonical URL set
The canonical URL is https://www.tricot.cl/.
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://www.tricot.cl/sitemap_index.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 (1,623 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.tricot.cl/llms.txt (12 KiB, 53 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://www.tricot.cl/seguimiento-pedidos has no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://www.tricot.cl/TRICOT-APP.html, https://www.tricot.cl/mis-favoritos and https://www.tricot.cl/bolsa-decompras use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://www.tricot.cl/seguimiento-pedidos and https://www.tricot.cl/bolsa-decompras have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.tricot.cl/seguimiento-pedidos 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 172 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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
3 low-resolution images
3 images are served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
29 of 36 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: 7 testimonial or review blocks. 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.
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 570 words of copy
The homepage carries about 570 words of visible text.
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: Google Tag Manager.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 3 mores (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.
30 cookies set on arrival
30Opening the homepage sets 30 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.
42 other companies contacted
Loading the homepage contacts 42 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 tricot.cl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- Entel Chile S.A.
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on tricot.cl, including 24 speed issues, 2 SEO issues and 4 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.