Website review, no card needed
elclon.com.uy website review
Visit site (opens in a new tab)Reviewed 23 October 202647 issues · 89 checks
This review found 47 issues worth fixing on elclon.com.uy, 13 of them high impact, across 89 checks. The most urgent: render-blocking 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.9 s |
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.8 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.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 186 ms |
| May 9, 2026 | 190 ms |
| May 16, 2026 | 188 ms |
| May 23, 2026 | 188 ms |
| May 30, 2026 | 188 ms |
| Jun 6, 2026 | 187 ms |
| Jun 13, 2026 | 189 ms |
| Jun 20, 2026 | 190 ms |
| Jun 27, 2026 | 190 ms |
| Jul 4, 2026 | 190 ms |
| Jul 11, 2026 | 194 ms |
| Jul 18, 2026 | 194 ms |
| Jul 25, 2026 | 197 ms |
| Aug 1, 2026 | 196 ms |
| Aug 8, 2026 | 205 ms |
| Aug 15, 2026 | 215 ms |
| Aug 22, 2026 | 220 ms |
| Aug 29, 2026 | 224 ms |
| Sep 5, 2026 | 223 ms |
| Sep 12, 2026 | 223 ms |
| Sep 19, 2026 | 223 ms |
| Sep 26, 2026 | 225 ms |
| Oct 3, 2026 | 227 ms |
| Oct 10, 2026 | 228 ms |
| Oct 17, 2026 | 236 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
How it loaded on a phone
0.6 s
1.1 s
1.7 s
2.2 s
2.8 s
3.4 s
3.9 s
4.5 s
Speed
Render-blocking requests
1.9 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Mobile performance score: 48
48/100Your mobile performance score is 48 (desktop: 65). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.5 s
A phone's processor spends 4.5 s on main-thread work while loading, 2.6 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, fcdn.app and Facebook and others), adding 3.0 MB and 2.5 s of main-thread time.
Improve image delivery
900 ms · 915 KiB49 images could be 915 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.
Reduce unused JavaScript
450 ms · 463 KiBAbout 463 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.
Google Tag Manager adds 848 ms
848 msGoogle Tag Manager costs a phone 848 ms of main-thread work and 480 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.
fcdn.app adds 668 ms
668 msfcdn.app costs a phone 668 ms of main-thread work and 2.0 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.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 508 ms. During a long task the page ignores taps.
Facebook adds 331 ms
331 msFacebook costs a phone 331 ms of main-thread work and 232 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
300 KiB9 files are served with short cache lifetimes, so returning visitors download them again (300 KiB).
2,183 HTML elements
The page has 2,183 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 31 KiBAbout 31 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 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: 21 ms
21 msYour server sent the HTML in 21 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: 13.5 s
13.5 sThe page becomes fully interactive after 13.5 s. Good is under 3.8 s.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 5.0 s
5.0 sYour largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Martinazzo”.
Real-user INP: 261 ms
261 msReal visitors wait 261 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 186 ms to 236 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Speed Index: 4.0 s
4.0 sVisually, the page fills in at 4.0 s (Speed Index). Good is under 3.4 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 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.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
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: 3.1 MB in 139 requests
3.1 MBYour homepage downloads 3.1 MB in 139 requests on a phone: images 1.8 MB (85), scripts 1.2 MB (21) and stylesheets 38 KiB (2). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
oferta-calabaza-halloween-chica-c-golosinas-oferta-calabaza- 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).
7 images below the first screen load straight away
7 images further down the page (261 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.87 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.87 g of CO₂e: 104.2 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
39 buttons without a name
39 buttons have no accessible name, so screen readers announce just “button”.
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (141 elements)
All page content should be contained by landmarks: 141 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
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.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (21 characters)
Your title is only 21 characters: “El Clon Tienda Online”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
454 internal links, 11 external
The homepage links to 454 pages on elclon.com.uy and 11 external pages.
6 checks passed
Meta description: 121 characters
Your meta description is 121 characters: “Donde todo es una oferta. Los mejores precios del mercado Uruguayo. Visitanos en nuestra web o en nuestras 25 sucursale…”.
One H1 headline
Your main headline reads: “El Clon”.
Canonical URL set
The canonical URL is https://www.elclon.com.uy/.
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://www.elclon.com.uy/sitemap.
AI search readiness
No Organization structured data
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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,049 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.elclon.com.uy/llms.txt (6 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages hidden from search
https://www.elclon.com.uy/catalogo and https://www.elclon.com.uy/alimentos/alimentos/alimentos-en-general are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
11 pages without a meta description
https://www.elclon.com.uy/catalogo, https://www.elclon.com.uy/alimentos/alimentos/aceites, https://www.elclon.com.uy/alimentos/alimentos/arroz, https://www.elclon.com.uy/alimentos/alimentos/bebidas-c-alcohol, https://www.elclon.com.uy/alimentos/alimentos/bebidas-s-alcohol and https://www.elclon.com.uy/alimentos/alimentos/dulces and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 197 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.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to manifest at 'https://f.fcdn.app/assets/manifest.json' from origin 'https://www.elclon.com.uy' has been blocke…”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
224 of 229 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 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 482 words of copy
The homepage carries about 482 words of visible text.
2 checks passed
2 short forms
2 short forms (3 fields at most) are right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 2 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.
28 cookies set on arrival
28Opening the homepage sets 28 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.
24 other companies contacted
Loading the homepage contacts 24 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 elclon.com.uy, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on elclon.com.uy, including 22 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.