Website review, no card needed
easy.com.ar website review
Visit site (opens in a new tab)Reviewed 28 October 202648 issues · 87 checks
This review found 48 issues worth fixing on easy.com.ar, 21 of them high impact, across 87 checks. The most urgent: google Tag Manager adds 2.8 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
55FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 6.1 s |
| May 16, 2026 | 6.3 s |
| May 23, 2026 | 6.6 s |
| May 30, 2026 | 6.8 s |
| Jun 6, 2026 | 7.1 s |
| Jun 13, 2026 | 7.0 s |
| Jun 20, 2026 | 6.5 s |
| Jun 27, 2026 | 6.5 s |
| Jul 4, 2026 | 6.2 s |
| Jul 11, 2026 | 6.0 s |
| Jul 18, 2026 | 6.1 s |
| Jul 25, 2026 | 6.2 s |
| Aug 1, 2026 | 6.4 s |
| Aug 8, 2026 | 6.5 s |
| Aug 15, 2026 | 6.5 s |
| Aug 22, 2026 | 6.4 s |
| Aug 29, 2026 | 6.3 s |
| Sep 5, 2026 | 6.0 s |
| Sep 12, 2026 | 5.4 s |
| Sep 19, 2026 | 4.8 s |
| Sep 26, 2026 | 4.2 s |
| Oct 3, 2026 | 4.0 s |
| Oct 10, 2026 | 4.1 s |
| Oct 17, 2026 | 4.2 s |
| Oct 24, 2026 | 4.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 299 ms |
| May 16, 2026 | 305 ms |
| May 23, 2026 | 310 ms |
| May 30, 2026 | 314 ms |
| Jun 6, 2026 | 322 ms |
| Jun 13, 2026 | 331 ms |
| Jun 20, 2026 | 339 ms |
| Jun 27, 2026 | 339 ms |
| Jul 4, 2026 | 337 ms |
| Jul 11, 2026 | 328 ms |
| Jul 18, 2026 | 323 ms |
| Jul 25, 2026 | 319 ms |
| Aug 1, 2026 | 313 ms |
| Aug 8, 2026 | 313 ms |
| Aug 15, 2026 | 313 ms |
| Aug 22, 2026 | 314 ms |
| Aug 29, 2026 | 320 ms |
| Sep 5, 2026 | 329 ms |
| Sep 12, 2026 | 340 ms |
| Sep 19, 2026 | 345 ms |
| Sep 26, 2026 | 348 ms |
| Oct 3, 2026 | 344 ms |
| Oct 10, 2026 | 340 ms |
| Oct 17, 2026 | 340 ms |
| Oct 24, 2026 | 341 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
1.0 s
2.0 s
2.9 s
3.9 s
4.9 s
5.9 s
6.9 s
7.9 s
Speed
Google Tag Manager adds 2.8 s
2.8 sGoogle Tag Manager costs a phone 2.8 s of main-thread work and 2.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Improve image delivery
1.5 s · 780 KiB17 images could be 780 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.
vtexassets.com adds 1.9 s
1.9 svtexassets.com costs a phone 1.9 s of main-thread work and 3.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 12.9 s
A phone's processor spends 12.9 s on main-thread work while loading, 7.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 11
11/100Your mobile performance score is 11 (desktop: 29). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,471 HTML elements
The page has 3,471 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, vtexassets.com and TikTok and others), adding 6.9 MB and 5.2 s of main-thread time.
Reduce unused JavaScript
2.1 MBAbout 2.1 MB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
900 ms · 251 KiBAbout 251 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 541 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
442 KiB44 files are served with short cache lifetimes, so returning visitors download them again (442 KiB).
storyly.io adds 50 ms
50 msstoryly.io costs a phone 50 ms of main-thread work and 948 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.
Minify JavaScript
145 KiB145 KiB could be saved by minifying JavaScript.
Legacy JavaScript
59 KiBPolyfills for old browsers add 59 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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 77 ms
77 msYour server sent the HTML in 77 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.54
0.54For real visitors the layout shifts by 0.54 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 10.1 s
10.1 sYour largest element takes 10.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Ahorra hasta $60.000 en tu compra | EASY”.
Time to Interactive: 46.4 s
46.4 sThe page becomes fully interactive after 46.4 s. Good is under 3.8 s.
Speed Index: 14.6 s
14.6 sVisually, the page fills in at 14.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 6.0 s
6.0 sThe first text or image appears after 6.0 s on a phone. Good is under 1.8 s.
Total Blocking Time: 2.4 s
2.4 sScripts block taps and scrolling for 2.4 s in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.321
0.321The layout shifts by 0.321 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 421 ms
421 msReal visitors wait 421 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
16 images without width and height
16 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 299 ms to 341 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Largest content (LCP) got 31% faster for real visitors
-31%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 6.1 s to 4.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 8.6 MB in 332 requests
8.6 MBYour homepage downloads 8.6 MB in 332 requests on a phone: scripts 4.3 MB (91), images 2.2 MB (84) and other files 793 KiB (141). Under 2 MB keeps phones on slow connections fast.
11 images below the first screen load straight away
11 images further down the page (364 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.4 g of CO₂ per visit
2.45 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.45 g of CO₂e: 293.5 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
13 buttons without a name
13 buttons have no accessible name, so screen readers announce just “button”.
72 tap targets too small
72 tap targets are too small or too close together to hit reliably with a finger.
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.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (29 elements)
All page content should be contained by landmarks: 29 elements on the page fail 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.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (11 elements).
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
46 internal links, 3 external
The homepage links to 46 pages on easy.com.ar and 3 external pages.
7 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “Aprovechá en Easy todo lo que tenemos para Construir, Remodelar, Renovar, y Decorar tus espacios. ¡Comprá online en el …”.
One H1 headline
Your main headline reads: “Easy”.
Title: 59 characters
Your title is a healthy 59 characters: “Easy | Construcción, Renovación, Deco y Diseño para tu Casa”.
Canonical URL set
The canonical URL is https://www.easy.com.ar/.
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.easy.com.ar/sitemap.xml.
AI search readiness
Some text only appears after JavaScript runs
43%The HTML your server sends has 139 of the 327 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://www.easy.com.ar/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.
2 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Other pages
7 linked pages hidden from search
https://www.easy.com.ar/13421, https://www.easy.com.ar/13820, https://www.easy.com.ar/14387, https://www.easy.com.ar/14381, https://www.easy.com.ar/14385 and https://www.easy.com.ar/14384 and 1 other are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
3 pages share a title
/, https://www.easy.com.ar/medios-de-pago and https://www.easy.com.ar/servicios-e-instalaciones all use the title “Easy | Construcción, Renovación, Deco y Diseño para tu Casa”. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages share a meta description
https://www.easy.com.ar/13421, https://www.easy.com.ar/medios-de-pago, https://www.easy.com.ar/servicios-e-instalaciones, https://www.easy.com.ar/13820, https://www.easy.com.ar/14387 and https://www.easy.com.ar/14381 and 3 others use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://www.easy.com.ar/13421, https://www.easy.com.ar/ideas-e-inspiracion, https://www.easy.com.ar/medios-de-pago, https://www.easy.com.ar/servicios-e-instalaciones, https://www.easy.com.ar/locales and https://www.easy.com.ar/13820 and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages slow to respond
https://www.easy.com.ar/servicios-e-instalaciones, https://www.easy.com.ar/14385, https://www.easy.com.ar/14384, https://www.easy.com.ar/14386 and https://www.easy.com.ar/banos-y-cocinas took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 36 found) and read each the way a search engine does.
4 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
28 small tap targets
28 of 64 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Unexpected end of JSON input JSON.parse (<anonymous>)”.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 checks passed
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 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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 327 words of copy
The homepage carries about 327 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager, Hotjar and TikTok Pixel.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel 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.
40 cookies set on arrival
40Opening the homepage sets 40 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.
44 other companies contacted
Loading the homepage contacts 44 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 easy.com.ar, 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 | Hotjar
- Hosting
- AWS
Company
- Founded
- 1993
- Headquarters
- Santiago
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 easy.com.ar, including 25 speed issues, 1 SEO issue 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.