Website review, no card needed

distritomax.com logo

distritomax.com website review

Visit site (opens in a new tab)Reviewed 5 November 202653 issues · 93 checks

This review found 53 issues worth fixing on distritomax.com, 19 of them high impact, across 93 checks. The most urgent: main-thread work: 11.1 s. 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
2.2 s1.9 sMay 16Oct 311.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.0 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20262.0 s
Oct 31, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
305 ms263 msMay 16Oct 31271 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026275 ms
May 23, 2026273 ms
May 30, 2026282 ms
Jun 6, 2026288 ms
Jun 13, 2026296 ms
Jun 20, 2026299 ms
Jun 27, 2026300 ms
Jul 4, 2026299 ms
Jul 11, 2026294 ms
Jul 18, 2026289 ms
Jul 25, 2026280 ms
Aug 1, 2026278 ms
Aug 8, 2026272 ms
Aug 15, 2026271 ms
Aug 22, 2026271 ms
Aug 29, 2026268 ms
Sep 5, 2026273 ms
Sep 12, 2026274 ms
Sep 19, 2026277 ms
Sep 26, 2026280 ms
Oct 3, 2026279 ms
Oct 10, 2026278 ms
Oct 17, 2026276 ms
Oct 24, 2026272 ms
Oct 31, 2026271 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 distritomax.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. distritomax.com at 1.0 s1.0 s
  2. distritomax.com at 2.0 s2.0 s
  3. distritomax.com at 3.1 s3.1 s
  4. distritomax.com at 4.1 s4.1 s
  5. distritomax.com at 5.1 s5.1 s
  6. distritomax.com at 6.1 s6.1 s
  7. distritomax.com at 7.2 s7.2 s
  8. distritomax.com at 8.2 s8.2 s

Speed

14 to fix39
  • Main-thread work: 11.1 s

    A phone's processor spends 11.1 s on main-thread work while loading, 5.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Render-blocking requests

    1.0 s

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.

  • Mobile performance score: 39

    39/100

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

  • 4,077 HTML elements

    The page has 4,077 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, Signyfyd and onrender.com and others), adding 2.8 MB and 3.1 s of main-thread time.

  • Reduce unused JavaScript

    900 ms · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Google Tag Manager adds 959 ms

    959 ms

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

  • Reduce unused CSS

    750 ms · 224 KiB

    About 224 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.

  • Signyfyd adds 901 ms

    901 ms

    Signyfyd costs a phone 901 ms of main-thread work and 260 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.

  • 20 long tasks on the main thread

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

  • Use efficient cache lifetimes

    150 ms · 568 KiB

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

  • onrender.com adds 367 ms

    367 ms

    onrender.com costs a phone 367 ms of main-thread work and 42 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.

  • ZenDesk adds 216 ms

    216 ms

    ZenDesk costs a phone 216 ms of main-thread work and 431 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.

  • Stamped.io adds 167 ms

    167 ms

    Stamped.io costs a phone 167 ms of main-thread work and 569 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.

  • Improve image delivery

    250 ms · 106 KiB

    3 images could be 106 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.

  • Legacy JavaScript

    90 KiB

    Polyfills for old browsers add 90 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    21 KiB

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

  • 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: 16 ms

    16 ms

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

Core Web Vitals

9 to fix0
  • 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: 32.3 s

    32.3 s

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

  • Speed Index: 11.9 s

    11.9 s

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

  • Total Blocking Time: 2.5 s

    2.5 s

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

  • Largest Contentful Paint: 6.4 s

    6.4 s

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

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 285 ms

    285 ms

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

  • Real-user CLS: 0.16

    0.16

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

  • 2 images without width and height

    2 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -1%

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

  • Largest content (LCP) held steady for real visitors

    -7%

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

4 checks passed
  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 714 ms

    714 ms

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.016

    0.016

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

Images and page weight

2 to fix60
  • Page weight: 5.2 MB in 299 requests

    5.2 MB

    Your homepage downloads 5.2 MB in 299 requests on a phone: scripts 3.1 MB (112), other files 932 KiB (141) and images 555 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    251 KiB

    2 images are downloaded at several times the size a phone draws them, for example 66552_9247995986094.png at 700 px wide, shown at 50 px. Resized copies would save about 251 KiB.

  • 2 images in older formats

    2 images (263 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 1.5 g of CO₂ per visit

    1.47 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.47 g of CO₂e: 176.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

11 to fixGoogle 7086
  • Invalid ARIA attributes

    2 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

  • 11 tap targets too small

    11 tap targets are too small or too close together to hit reliably with a finger.

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

  • Hidden but focusable

    3 elements hidden from screen readers can still receive keyboard focus.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • All page content should be contained by landmarks (57 elements)

    All page content should be contained by landmarks: 57 elements on the page fail 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.

  • 12 links without text

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

  • Elements use prohibited ARIA attributes

    Elements use prohibited ARIA attributes (1 element).

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 9 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8577
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Tienda en línea de juguetes y muñecos coleccionables — Distrito Max”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 4 links crawlers can't follow

    4 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 447 internal links, 2 external

    The homepage links to 447 pages on distritomax.com and 2 external pages.

5 checks passed
  • Meta description: 94 characters

    Your meta description is 94 characters: “Tienda en línea de juguetes y todo tipo de coleccionables. Juguetería con envíos a todo México”.

  • Canonical URL set

    The canonical URL is https://www.distritomax.com/.

  • Structured data in place

    Structured data found: WebSite.

  • 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.distritomax.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.distritomax.com/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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,404 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 2 pages without a meta description

    https://www.distritomax.com/collections/todo and https://www.distritomax.com/collections/lo-mas-chingon have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://www.distritomax.com/collections/todo, https://www.distritomax.com/collections/ultimas-piezas, https://www.distritomax.com/collections/preventa, https://www.distritomax.com/collections/descuento and https://www.distritomax.com/collections/lo-mas-chingon have no <h1> headline, so visitors and search engines get no clear main topic.

  • 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

    5 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • Every page has a title

    All 5 pages that loaded have a <title>.

Best practices

3 to fixGoogle 5885
  • 22 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix42
  • 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: 26 testimonial or review blocks. 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 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 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 1,560 words of copy

    The homepage carries about 1,560 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

1 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 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.

  • 45 other companies contacted

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

Apps on your store

Your storefront loads 11 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Elevar Conversion Tracking · Kor Order Limit Quantity · Boost Ai Search Filter · Klaviyo Email Marketing Sms · Minmaxify Order Limits · Purchase Limit · amazonaws.com · signifyd.com · cloudfront.net · lay-buys.com · onrender.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Naucalpan

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 53 issues on distritomax.com, including 23 speed issues, 5 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