Website review, no card needed
adrian.com.mx website review
Visit site (opens in a new tab)Reviewed 7 November 202635 issues · 80 checks
This review found 35 issues worth fixing on adrian.com.mx, 8 of them high impact, across 80 checks. The most urgent: improve image delivery. 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
76C- #72,106 of 118,024 reviewed websitesbeats 34%
- #46,539 of 67,072 online storesbeats 26%
- #457 of 884 BigCommerce storesbeats 43%
Closest competitors among BigCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Sep 19, 2026 | 155 ms |
| Sep 26, 2026 | 158 ms |
| Oct 3, 2026 | 164 ms |
| Oct 10, 2026 | 147 ms |
| Oct 17, 2026 | 128 ms |
| Oct 24, 2026 | 110 ms |
| Oct 31, 2026 | 103 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
Speed
Improve image delivery
1.4 s · 395 KiB14 images could be 395 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Render-blocking requests
1.1 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 97 KiBAbout 97 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Bigcommerce, jQuery CDN and Cloudflare CDN and others), adding 1.5 MB and 350 ms of main-thread time.
Reduce unused CSS
450 ms · 50 KiBAbout 50 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Bigcommerce adds 295 ms
295 msBigcommerce costs a phone 295 ms of main-thread work and 1.3 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.
Use efficient cache lifetimes
300 ms · 32 KiB8 files are served with short cache lifetimes, so returning visitors download them again (32 KiB).
Legacy JavaScript
150 ms · 15 KiBPolyfills for old browsers add 15 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 87 ms. During a long task the page ignores taps.
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 JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 403 ms of it running JavaScript. That is comfortably low.
Server response: 12 ms
12 msYour server sent the HTML in 12 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.37
0.37For real visitors the layout shifts by 0.37 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 8.2 s
8.2 sYour largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Shop now”.
Time to Interactive: 8.2 s
8.2 sThe page becomes fully interactive after 8.2 s. Good is under 3.8 s.
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.
Real-user INP: 98 ms
98 msReal visitors wait 98 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 540 ms
540 msReal visitors wait 540 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 32% faster for real visitors
-32%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 155 ms to 103 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 82 ms
82 msScripts block the page for only 82 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
3 images far larger than shown
219 KiB3 images are downloaded at several times the size a phone draws them, for example WhatsApp_Image_2025-04-22_at_7.32.56_PM_-_13__13383.17455388 at 853 px wide, shown at 159 px. Resized copies would save about 219 KiB.
4 images in older formats
4 images (344 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.
3 images below the first screen load straight away
3 images further down the page (78 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.4 g of CO₂ per visit
0.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.44 g of CO₂e: 52.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.6 MB in 75 requests
1.6 MBYour homepage downloads 1.6 MB in 75 requests on a phone: images 1.0 MB (37), scripts 314 KiB (16) and fonts 68 KiB (2). That is a lean page.
Accessibility
14 text elements with low contrast
14 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 (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 9 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (19 characters)
Your title is only 19 characters: “Adrian Tenis y Ropa”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (66 characters)
Your meta description is only 66 characters: “Tienda de Calzado y Ropa con precios accesibles en Colima, Colima.”. 70 to 160 characters is enough to sell the click.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://adrian.com.mx/sitemap.xml, so Google discovers your pages only by following links.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
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.
74 internal links, 9 external
The homepage links to 74 pages on adrian.com.mx and 9 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://adrian.com.mx/.
robots.txt in place
robots.txt is in place.
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://adrian.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.
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 (304 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://adrian.com.mx/hombre/ropa/chamarras has no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://adrian.com.mx/hombre, https://adrian.com.mx/hombre/lo-nuevo, https://adrian.com.mx/hombre/ropa, https://adrian.com.mx/hombre/ropa/chamarras, https://adrian.com.mx/hombre/ropa/playeras and https://adrian.com.mx/hombre/ropa/pantalones and 7 others 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 54 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 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 14 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://bigc-zoom-magnifier.hubifyapps.com/bc_cs/custom.css' from origin 'https://adrian.c…”.
2 checks passed
Tap targets are thumb-sized
42 of 52 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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: a star rating. 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 454 words of copy
The homepage carries about 454 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop now”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Privacy and tracking
11 cookies set on arrival
11Opening the homepage sets 11 cookies, 1 of them by other companies (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.
13 other companies contacted
Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 adrian.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
- Framework
- jQuery
- E-commerce
- BigCommerce
- Hosting
- Bigcommerce Inc.
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on adrian.com.mx, including 15 speed issues, 7 SEO issues 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.