Website review, no card needed
gandhi.com.mx website review
Visit site (opens in a new tab)Reviewed 24 October 202649 issues · 88 checks
This review found 49 issues worth fixing on gandhi.com.mx, 19 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. 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
61DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.0 s |
| May 9, 2026 | 2.9 s |
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 3.5 s |
| Sep 12, 2026 | 3.7 s |
| Sep 19, 2026 | 3.6 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.3 s |
| Oct 10, 2026 | 3.2 s |
| Oct 17, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 312 ms |
| May 9, 2026 | 308 ms |
| May 16, 2026 | 325 ms |
| May 23, 2026 | 350 ms |
| May 30, 2026 | 371 ms |
| Jun 6, 2026 | 383 ms |
| Jun 13, 2026 | 384 ms |
| Jun 20, 2026 | 378 ms |
| Jun 27, 2026 | 371 ms |
| Jul 4, 2026 | 351 ms |
| Jul 11, 2026 | 333 ms |
| Jul 18, 2026 | 330 ms |
| Jul 25, 2026 | 336 ms |
| Aug 1, 2026 | 337 ms |
| Aug 8, 2026 | 333 ms |
| Aug 15, 2026 | 315 ms |
| Aug 22, 2026 | 293 ms |
| Aug 29, 2026 | 295 ms |
| Sep 5, 2026 | 304 ms |
| Sep 12, 2026 | 311 ms |
| Sep 19, 2026 | 307 ms |
| Sep 26, 2026 | 297 ms |
| Oct 3, 2026 | 282 ms |
| Oct 10, 2026 | 261 ms |
| Oct 17, 2026 | 254 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.9 s
1.8 s
2.8 s
3.7 s
4.6 s
5.5 s
6.5 s
7.4 s
Speed
Reduce unused JavaScript
3.0 s · 2.7 MBAbout 2.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Use efficient cache lifetimes
2.4 s · 772 KiB25 files are served with short cache lifetimes, so returning visitors download them again (772 KiB).
Reduce unused CSS
1.2 s · 137 KiBAbout 137 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 30
30/100Your mobile performance score is 30 (desktop: 39). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.1 s
A phone's processor spends 5.1 s on main-thread work while loading, 2.9 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 (vtexassets.com, vtexsuite.com and Google Tag Manager and others), adding 5.1 MB and 2.3 s of main-thread time.
vtexassets.com adds 952 ms
952 msvtexassets.com costs a phone 952 ms of main-thread work and 3.5 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.
Minify JavaScript
900 ms · 160 KiB160 KiB could be saved by minifying JavaScript.
vtexsuite.com adds 470 ms
470 msvtexsuite.com costs a phone 470 ms of main-thread work and 681 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
400 ms · 130 KiBPolyfills for old browsers add 130 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.
Google Tag Manager adds 389 ms
389 msGoogle Tag Manager costs a phone 389 ms of main-thread work and 378 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.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 376 ms. During a long task the page ignores taps.
Render-blocking requests
300 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.
Improve image delivery
150 ms · 5 KiB1 image could be 5 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
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.
Duplicated JavaScript
3 KiB3 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 59 ms
59 msYour server sent the HTML in 59 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.66
0.66For real visitors the layout shifts by 0.66 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 18.2 s
18.2 sYour largest element takes 18.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Día de muertos”.
First Contentful Paint: 7.1 s
7.1 sThe first text or image appears after 7.1 s on a phone. Good is under 1.8 s.
Time to Interactive: 22.9 s
22.9 sThe page becomes fully interactive after 22.9 s. Good is under 3.8 s.
Speed Index: 9.5 s
9.5 sVisually, the page fills in at 9.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.3 s
1.3 sScripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.
Real-user INP: 241 ms
241 msReal visitors wait 241 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.0 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 312 ms to 254 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.081
0.081The layout barely moves while loading (CLS 0.081, good is under 0.1).
Images and page weight
Page weight: 3.2 MB in 183 requests
3.2 MBYour homepage downloads 3.2 MB in 183 requests on a phone: scripts 2.1 MB (94), other files 393 KiB (59) and HTML 385 KiB (1). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 107.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
3 elements hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails 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.
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.
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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 10 images in the HTML carry an alt attribute.
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 8 failed. 1 more 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.
Structured data has 1 problem
Structured data found (ItemList and WebSite) but with 1 problem, for example “WebSite: missing name”.
No social preview image
No Open Graph image, 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.
11 internal links, 0 external
The homepage links to 11 pages on gandhi.com.mx and 0 external pages.
5 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Librerías Gandhi es la puerta a tu imaginación y a un mundo lleno de posibilidades: busca y compra libros, sagas, novel…”.
Title: 44 characters
Your title is a healthy 44 characters: “Librerías Gandhi | Librería online en México”.
Canonical URL set
The canonical URL is https://www.gandhi.com.mx/.
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.gandhi.com.mx/sitemap.xml.
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.
No llms.txt
There is no https://www.gandhi.com.mx/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.
1 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.
Other pages
3 pages share a title
/, https://www.gandhi.com.mx/terror and https://www.gandhi.com.mx/rincon-de-oportunidades all use the title “Librerías Gandhi | Librería online en México”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages share a meta description
https://www.gandhi.com.mx/gandhi-selecto, https://www.gandhi.com.mx/terror, https://www.gandhi.com.mx/mas-leidos, https://www.gandhi.com.mx/libros-de-arte, https://www.gandhi.com.mx/tienda-kobo and https://www.gandhi.com.mx/harry-potter and 2 others use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.gandhi.com.mx/libros/ediciones-gandhi, whose canonical is https://www.gandhi.com.mx/ediciones-gandhi. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
8 pages without an H1
https://www.gandhi.com.mx/gandhi-selecto, https://www.gandhi.com.mx/terror, https://www.gandhi.com.mx/mas-leidos, https://www.gandhi.com.mx/novedades, https://www.gandhi.com.mx/libros-de-arte and https://www.gandhi.com.mx/tienda-kobo and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
8 pages with very little text
https://www.gandhi.com.mx/gandhi-selecto, https://www.gandhi.com.mx/terror, https://www.gandhi.com.mx/mas-leidos, https://www.gandhi.com.mx/novedades, https://www.gandhi.com.mx/libros-de-arte and https://www.gandhi.com.mx/harry-potter and 2 others have 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.
6 pages slow to respond
https://www.gandhi.com.mx/gandhi-selecto, https://www.gandhi.com.mx/mas-leidos, https://www.gandhi.com.mx/novedades, https://www.gandhi.com.mx/libros-de-arte, https://www.gandhi.com.mx/accesorios/juegos-y-juguetes and https://www.gandhi.com.mx/rincon-de-oportunidades took over 3 s to send their HTML from our server.
10 internal pages checked
We fetched 10 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 10 pages we checked loaded without an error.
Every page has a meta description
All 10 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 10 pages that loaded have a <title>.
Best practices
14 small tap targets
14 of 29 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'register')”.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 63 words
The homepage has only about 63 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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.
21 cookies set on arrival
21Opening the homepage sets 21 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.
35 other companies contacted
Loading the homepage contacts 35 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 gandhi.com.mx, 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
Company
- Headquarters
- Mexico City
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 49 issues on gandhi.com.mx, including 24 speed issues, 3 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.