Website review, no card needed

juguetron.mx logo

juguetron.mx website review

Visit site (opens in a new tab)Reviewed 30 October 202645 issues · 82 checks

This review found 45 issues worth fixing on juguetron.mx, 16 of them high impact, across 82 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.9 s2.9 sMay 9Oct 243.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.8 s
May 16, 20263.8 s
May 23, 20263.7 s
May 30, 20263.6 s
Jun 6, 20263.7 s
Jun 13, 20263.7 s
Jun 20, 20263.6 s
Jun 27, 20263.4 s
Jul 4, 20263.3 s
Jul 11, 20263.1 s
Jul 18, 20263.0 s
Jul 25, 20263.0 s
Aug 1, 20263.0 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20263.0 s
Aug 29, 20263.0 s
Sep 5, 20263.1 s
Sep 12, 20263.1 s
Sep 19, 20263.1 s
Sep 26, 20263.2 s
Oct 3, 20263.1 s
Oct 10, 20263.1 s
Oct 17, 20263.1 s
Oct 24, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
428 ms192 msMay 9Oct 24219 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026401 ms
May 16, 2026388 ms
May 23, 2026369 ms
May 30, 2026355 ms
Jun 6, 2026362 ms
Jun 13, 2026364 ms
Jun 20, 2026354 ms
Jun 27, 2026351 ms
Jul 4, 2026347 ms
Jul 11, 2026323 ms
Jul 18, 2026296 ms
Jul 25, 2026268 ms
Aug 1, 2026238 ms
Aug 8, 2026228 ms
Aug 15, 2026230 ms
Aug 22, 2026230 ms
Aug 29, 2026229 ms
Sep 5, 2026231 ms
Sep 12, 2026231 ms
Sep 19, 2026229 ms
Sep 26, 2026227 ms
Oct 3, 2026227 ms
Oct 10, 2026225 ms
Oct 17, 2026223 ms
Oct 24, 2026219 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

Full-page screenshot of juguetron.mx (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. juguetron.mx at 0.8 s0.8 s
  2. juguetron.mx at 1.6 s1.6 s
  3. juguetron.mx at 2.4 s2.4 s
  4. juguetron.mx at 3.2 s3.2 s
  5. juguetron.mx at 4.0 s4.0 s
  6. juguetron.mx at 4.9 s4.9 s
  7. juguetron.mx at 5.7 s5.7 s
  8. juguetron.mx at 6.5 s6.5 s

Speed

13 to fix36
  • Use efficient cache lifetimes

    2.8 s · 394 KiB

    15 files are served with short cache lifetimes, so returning visitors download them again (394 KiB).

  • Reduce unused JavaScript

    2.3 s · 472 KiB

    About 472 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

  • Mobile performance score: 36

    36/100

    Your mobile performance score is 36. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.3 s

    A phone's processor spends 4.3 s on main-thread work while loading, 2.8 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, adray.ai and vtexassets.com and others), adding 2.0 MB and 2.5 s of main-thread time.

  • Reduce unused CSS

    750 ms · 100 KiB

    About 100 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Google Tag Manager adds 733 ms

    733 ms

    Google Tag Manager costs a phone 733 ms of main-thread work and 363 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.

  • vtexassets.com adds 616 ms

    616 ms

    vtexassets.com costs a phone 616 ms of main-thread work and 1.2 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.

  • adray.ai adds 648 ms

    648 ms

    adray.ai costs a phone 648 ms of main-thread work and 94 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.

  • 11 long tasks on the main thread

    11 long tasks block the main thread while loading, the longest for 645 ms. During a long task the page ignores taps.

  • Improve image delivery

    450 ms · 91 KiB

    2 images could be 91 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Facebook adds 284 ms

    284 ms

    Facebook costs a phone 284 ms of main-thread work and 282 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.

  • Render-blocking requests

    300 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

  • Legacy JavaScript

    250 ms · 49 KiB

    Polyfills for old browsers add 49 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

  • Minify JavaScript

    150 ms · 13 KiB

    13 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.

1 checks passed
  • Server response: 21 ms

    21 ms

    Your server sent the HTML in 21 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix67
  • 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.46

    0.46

    For real visitors the layout shifts by 0.46 (75th percentile). Good is under 0.1.

  • Largest Contentful Paint: 13.8 s

    13.8 s

    Your largest element takes 13.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 14.6 s

    14.6 s

    The page becomes fully interactive after 14.6 s. Good is under 3.8 s.

  • Total Blocking Time: 1.7 s

    1.7 s

    Scripts block taps and scrolling for 1.7 s in total while the page loads. Good is under 200 ms.

  • Speed Index: 7.9 s

    7.9 s

    Visually, the page fills in at 7.9 s (Speed Index). Good is under 3.4 s.

  • Real-user FCP: 2.0 s

    2.0 s

    Real visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.2 s

    1.2 s

    Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 2.8 s

    2.8 s

    The first text or image appears after 2.8 s on a phone. Good is under 1.8 s.

5 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

    Real visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 186 ms

    186 ms

    Real visitors wait 186 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 44% faster for real visitors

    -44%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 401 ms to 219 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 19% faster for real visitors

    -19%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.8 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix81
  • Page weight: 2.1 MB in 114 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 114 requests on a phone: scripts 1.5 MB (43), images 206 KiB (14) and fonts 161 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    9976a137-5ffd-4149-aa39-c8aba0753191___74102f3fbc9511a1ecc9c 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).

  • About 0.6 g of CO₂ per visit

    0.58 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.58 g of CO₂e: 70.1 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

6 to fixGoogle 8890
  • 6 tap targets too small

    6 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.

  • 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 (5 elements)

    All page content should be contained by landmarks: 5 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.

  • 5 links without text

    5 visible links have no text or label, so screen readers cannot say where they go.

2 checks passed
  • Every image has alt text

    All 27 images in the HTML carry an alt attribute.

  • 38 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: 38 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10081
  • Title is short (9 characters)

    Your title is only 9 characters: “Juguetron”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (195 characters)

    Your meta description is 195 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (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.

  • 43 internal links, 0 external

    The homepage links to 43 pages on juguetron.mx and 0 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Juguetron | Juguetes, Juegos y Regalos con Envío a Todo México”.

  • Canonical URL set

    The canonical URL is https://www.juguetron.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.juguetron.mx/sitemap.xml.

AI search readiness

1 to fix83
  • 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.

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.

  • llms.txt published

    The site publishes https://www.juguetron.mx/llms.txt (2 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix88
  • 2 linked pages hidden from search

    https://www.juguetron.mx/landing-lego and https://www.juguetron.mx/188 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages without an H1

    https://www.juguetron.mx/collectors-landing and https://www.juguetron.mx/landing-lego have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.juguetron.mx/collectors-landing 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.

  • 5 pages slow to respond

    https://www.juguetron.mx/al-aire-libre, https://www.juguetron.mx/juguetes-para-bebes, https://www.juguetron.mx/preescolar, https://www.juguetron.mx/creatividad-y-arte and https://www.juguetron.mx/figuras-de-accion took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 40 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 9 small tap targets

    9 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Warning: No Pinterest tag ID is defined. ”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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 31 words

    The homepage has only about 31 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, Meta Pixel and TikTok Pixel.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel (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

    21

    Opening 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.

  • 22 other companies contacted

    Loading the homepage contacts 22 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 juguetron.mx, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
React
Analytics
Google Tag Manager
Hosting
Comunicaciones de Mexico, S.A. de C.V.

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on juguetron.mx, including 22 speed issues, 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25