Website review, no card needed
gani.com.ar website review
Visit site (opens in a new tab)Reviewed 23 October 202641 issues · 79 checks
This review found 41 issues worth fixing on gani.com.ar, 19 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. 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
56FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 5.3 s |
| May 9, 2026 | 5.3 s |
| May 16, 2026 | 5.6 s |
| May 23, 2026 | 5.7 s |
| May 30, 2026 | 5.9 s |
| Jun 6, 2026 | 6.1 s |
| Jun 13, 2026 | 6.1 s |
| Jun 20, 2026 | 5.9 s |
| Jun 27, 2026 | 5.3 s |
| Jul 4, 2026 | 5.2 s |
| Jul 11, 2026 | 5.2 s |
| Jul 18, 2026 | 5.2 s |
| Jul 25, 2026 | 5.3 s |
| Aug 1, 2026 | 5.3 s |
| Aug 8, 2026 | 5.2 s |
| Aug 15, 2026 | 5.2 s |
| Aug 22, 2026 | 5.3 s |
| Aug 29, 2026 | 5.2 s |
| Sep 5, 2026 | 5.2 s |
| Sep 12, 2026 | 5.3 s |
| Sep 19, 2026 | 5.2 s |
| Sep 26, 2026 | 5.2 s |
| Oct 3, 2026 | 5.1 s |
| Oct 10, 2026 | 5.0 s |
| Oct 17, 2026 | 5.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 240 ms |
| May 9, 2026 | 233 ms |
| May 16, 2026 | 218 ms |
| May 23, 2026 | 220 ms |
| May 30, 2026 | 220 ms |
| Jun 6, 2026 | 223 ms |
| Jun 13, 2026 | 228 ms |
| Jun 20, 2026 | 228 ms |
| Jun 27, 2026 | 228 ms |
| Jul 4, 2026 | 227 ms |
| Jul 11, 2026 | 225 ms |
| Jul 18, 2026 | 227 ms |
| Jul 25, 2026 | 227 ms |
| Aug 1, 2026 | 232 ms |
| Aug 8, 2026 | 235 ms |
| Aug 15, 2026 | 237 ms |
| Aug 22, 2026 | 237 ms |
| Aug 29, 2026 | 238 ms |
| Sep 5, 2026 | 238 ms |
| Sep 12, 2026 | 238 ms |
| Sep 19, 2026 | 246 ms |
| Sep 26, 2026 | 239 ms |
| Oct 3, 2026 | 238 ms |
| Oct 10, 2026 | 239 ms |
| Oct 17, 2026 | 244 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.6 s
3.3 s
4.9 s
6.5 s
8.2 s
9.8 s
11.4 s
13.0 s
Speed
Use efficient cache lifetimes
10.8 s · 2.7 MB56 files are served with short cache lifetimes, so returning visitors download them again (2.7 MB).
Reduce unused JavaScript
6.8 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.8 s faster on a phone.
Mobile performance score: 13
13/100Your mobile performance score is 13 (desktop: 14). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.7 s
A phone's processor spends 4.7 s on main-thread work while loading, 3.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
950 ms · 201 KiBAbout 201 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 950 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 1.7 MB and 830 ms of main-thread time.
Improve image delivery
250 ms · 702 KiB12 images could be 702 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
Render-blocking requests
550 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 550 ms.
YouTube adds 427 ms
427 msYouTube costs a phone 427 ms of main-thread work and 971 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.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 269 ms. During a long task the page ignores taps.
Google Tag Manager adds 178 ms
178 msGoogle Tag Manager costs a phone 178 ms of main-thread work and 355 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.
Legacy JavaScript
65 KiBPolyfills for old browsers add 65 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.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 1 ms
1 msYour server sent the HTML in 1 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 LCP: 5.5 s
5.5 sReal visitors wait 5.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 1.37
1.37For real visitors the layout shifts by 1.37 (75th percentile). Good is under 0.1.
Real-user FCP: 4.4 s
4.4 sReal visitors see the first content after 4.4 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 7.9 s
7.9 sThe first text or image appears after 7.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 25.2 s
25.2 sYour largest element takes 25.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “720x830.jpg”. Most of its time is resource load delay (11.1 s).
Speed Index: 24.5 s
24.5 sVisually, the page fills in at 24.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 28.0 s
28.0 sThe page becomes fully interactive after 28.0 s. Good is under 3.8 s.
Cumulative Layout Shift: 1.101
1.101The layout shifts by 1.101 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 669 ms
669 msScripts block taps and scrolling for 669 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 244 ms
244 msReal visitors wait 244 ms for the page to respond to a tap (75th percentile). Good is under 200 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) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 240 ms to 244 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 5.3 s to 5.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user TTFB: 571 ms
571 msReal visitors wait 571 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 4.3 MB in 120 requests
4.3 MBYour homepage downloads 4.3 MB in 120 requests on a phone: scripts 2.6 MB (37), images 1.2 MB (23) and fonts 218 KiB (5). Under 2 MB keeps phones on slow connections fast.
About 1.2 g of CO₂ per visit
1.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.21 g of CO₂e: 145.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Documents must have <title> element to aid in navigation (1 element)
Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
2 checks passed
Every image has alt text
All 34 images in the HTML carry an alt attribute.
6 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 9 WCAG 2.2 A/AA and best-practice rules on the phone render: 6 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (168 characters)
Your meta description is 168 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 2 problems
Structured data found ((untyped), BreadcrumbList and Organization) but with 2 problems, for example “untyped block: missing @context (expected "https://schema.org")”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
One H1 headline
Your <h1> is empty.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
43 internal links, 11 external
The homepage links to 43 pages on gani.com.ar and 11 external pages.
4 checks passed
Title: 42 characters
Your title is a healthy 42 characters: “Colchones Gani | Irresistiblemente cómodos”.
Canonical URL set
The canonical URL is https://www.colchonesgani.com.ar/.
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.colchonesgani.com.ar/sitemap.xml.
AI search readiness
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, description and contact details; logo and sameAs (social profiles) would complete it.
llms.txt published
The site publishes https://www.colchonesgani.com.ar/llms.txt (7 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
10 pages without a title
https://www.colchonesgani.com.ar/c/001, https://www.colchonesgani.com.ar/c/Deco, https://www.colchonesgani.com.ar/c/Almohadas, https://www.colchonesgani.com.ar/c/Combos, https://www.colchonesgani.com.ar/product/000021132060190140 and https://www.colchonesgani.com.ar/product/000011132060190140/Colch%C3%B3n%20Gani%20Aquiles%203.0%20190x140 and 4 others have no <title>, so Google invents the link text in results.
12 pages without a meta description
https://www.colchonesgani.com.ar/c/001, https://www.colchonesgani.com.ar/c/Deco, https://www.colchonesgani.com.ar/c/Almohadas, https://www.colchonesgani.com.ar/c/Combos, https://www.colchonesgani.com.ar/product/000021132060190140 and https://www.colchonesgani.com.ar/product/000011132060190140/Colch%C3%B3n%20Gani%20Aquiles%203.0%20190x140 and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages without an H1
https://www.colchonesgani.com.ar/c/Deco, https://www.colchonesgani.com.ar/c/Almohadas, https://www.colchonesgani.com.ar/c/Combos, https://www.colchonesgani.com.ar/product/000021132060190140, https://www.colchonesgani.com.ar/product/000011132060190140/Colch%C3%B3n%20Gani%20Aquiles%203.0%20190x140 and https://www.colchonesgani.com.ar/product/000011121060190090/Colch%C3%B3n%20Gani%20Zeus%20190x90 and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages slow to respond
https://www.colchonesgani.com.ar/c/001, https://www.colchonesgani.com.ar/c/Colchones, https://www.colchonesgani.com.ar/c/Sommiers, https://www.colchonesgani.com.ar/c/Almohadas, https://www.colchonesgani.com.ar/c/Combos and https://www.colchonesgani.com.ar/product/000011132060190140/Colch%C3%B3n%20Gani%20Aquiles%203.0%20190x140 took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 27 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.
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.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “The Content-Security-Policy directive name ''self'' contains one or more invalid characters. Only ASCII alphanumeric ch…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
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.
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 333 words of copy
The homepage carries about 333 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
Social proof on the page
Social proof on the homepage: 6 testimonial or review blocks and 5 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel 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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
11 other companies contacted
Loading the homepage contacts 11 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 gani.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
- CMS
- Drupal
- Framework
- Angular
- Analytics
- Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on gani.com.ar, including 23 speed issues, 4 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.