Website review, no card needed
abasteo.mx website review
Visit site (opens in a new tab)Reviewed 18 October 202648 issues · 77 checks
This review found 48 issues worth fixing on abasteo.mx, 20 of them high impact, across 77 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
58FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 4.2 s |
| May 2, 2026 | 4.1 s |
| May 9, 2026 | 4.1 s |
| May 16, 2026 | 4.1 s |
| May 23, 2026 | 4.1 s |
| May 30, 2026 | 4.1 s |
| Jun 6, 2026 | 4.1 s |
| Jun 13, 2026 | 4.1 s |
| Jun 20, 2026 | 4.2 s |
| Jun 27, 2026 | 4.3 s |
| Jul 4, 2026 | 4.3 s |
| Jul 11, 2026 | 4.3 s |
| Jul 18, 2026 | 4.3 s |
| Jul 25, 2026 | 4.3 s |
| Aug 1, 2026 | 4.2 s |
| Aug 8, 2026 | 4.0 s |
| Aug 15, 2026 | 3.9 s |
| Aug 22, 2026 | 3.8 s |
| Aug 29, 2026 | 3.7 s |
| Sep 5, 2026 | 3.7 s |
| Sep 12, 2026 | 3.7 s |
| Sep 19, 2026 | 3.7 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 203 ms |
| May 2, 2026 | 196 ms |
| May 9, 2026 | 198 ms |
| May 16, 2026 | 197 ms |
| May 23, 2026 | 196 ms |
| May 30, 2026 | 203 ms |
| Jun 6, 2026 | 203 ms |
| Jun 13, 2026 | 204 ms |
| Jun 20, 2026 | 214 ms |
| Jun 27, 2026 | 217 ms |
| Jul 4, 2026 | 224 ms |
| Jul 11, 2026 | 230 ms |
| Jul 18, 2026 | 228 ms |
| Jul 25, 2026 | 226 ms |
| Aug 1, 2026 | 225 ms |
| Aug 8, 2026 | 219 ms |
| Aug 15, 2026 | 217 ms |
| Aug 22, 2026 | 214 ms |
| Aug 29, 2026 | 212 ms |
| Sep 5, 2026 | 212 ms |
| Sep 12, 2026 | 218 ms |
| Sep 19, 2026 | 225 ms |
| Sep 26, 2026 | 227 ms |
| Oct 3, 2026 | 235 ms |
| Oct 10, 2026 | 248 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
Use efficient cache lifetimes
6.5 s · 2.3 MB81 files are served with short cache lifetimes, so returning visitors download them again (2.3 MB).
Render-blocking requests
5.3 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.3 s.
Reduce unused JavaScript
3.6 s · 625 KiBAbout 625 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.
Improve image delivery
2.8 s · 676 KiB30 images could be 676 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.8 s faster on a phone.
Mobile performance score: 38
38/100Your mobile performance score is 38 (desktop: 46). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Cloudflare CDN and Facebook and others), adding 1.1 MB and 941 ms of main-thread time.
Google Tag Manager adds 404 ms
404 msGoogle Tag Manager costs a phone 404 ms of main-thread work and 531 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.
Reduce unused CSS
310 ms · 41 KiBAbout 41 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 ms faster on a phone.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 243 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need. 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.
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: 2 ms
2 msYour server sent the HTML in 2 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.31
0.31For real visitors the layout shifts by 0.31 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 22.0 s
22.0 sYour largest element takes 22.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “hb Apple Builder Jul 26”.
Time to Interactive: 22.1 s
22.1 sThe page becomes fully interactive after 22.1 s. Good is under 3.8 s.
First Contentful Paint: 6.7 s
6.7 sThe first text or image appears after 6.7 s on a phone. Good is under 1.8 s.
Speed Index: 9.3 s
9.3 sVisually, the page fills in at 9.3 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.9 s
3.9 sReal visitors wait 3.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.
Tap response (INP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 203 ms to 248 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.9 s
2.9 sReal visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 480 ms
480 msScripts block taps and scrolling for 480 ms in total while the page loads. Good is under 200 ms.
27 images without width and height
27 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.154
0.154The layout shifts by 0.154 while loading, so content jumps under the reader's thumb. Good is under 0.1.
1 checks passed
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 4.2 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 4.8 MB in 140 requests
4.8 MBYour homepage downloads 4.8 MB in 140 requests on a phone: images 2.6 MB (67), scripts 1.6 MB (32) and fonts 339 KiB (3). Under 2 MB keeps phones on slow connections fast.
19 images in older formats
19 images (2.0 MB) 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.
4 images below the first screen load straight away
4 images further down the page (358 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.37 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.37 g of CO₂e: 164.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
126 text elements with low contrast
126 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
19 tap targets too small
19 tap targets are too small or too close together to hit reliably with a finger.
Interactive controls must not be nested (2 elements)
Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (114 elements)
All page content should be contained by landmarks: 114 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.
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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 1 image 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
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is long (193 characters)
Your meta description is 193 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 2 problems
Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: url points at a different host (https://www.cyberpuerta.mx/)”.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
5 checks passed
Title: 60 characters
Your title is a healthy 60 characters: “Abasteo.mx - Proveedor Moderno de TI para Empresas en México”.
Canonical URL set
The canonical URL is https://www.abasteo.mx/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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.abasteo.mx/export/google/sitemap-mx.xml.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 899 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
llms.txt published
The site publishes https://www.abasteo.mx/llms.txt (9 KiB, 0 links), a plain-text guide to the site for AI tools.
Best practices
1 broken image
1 image failed to load on a phone, for example https://jwjvyq.abasteo.mx/g/uids?pld=bDUBs_Bd4sEeid3O2ugHTR0RftV7mKyfmfCEOyrz3eVFS935rtaExBxjQVkfvrtuV9VxNK61pNWDt_xOmyOWbDOJhOcO_B-JTboV9JgmS4ErVkAK0KRGKbZaPfDSOed96OiOXFYvxwDkfHPQG4d2EqHxxs7LYY8uWDt.
85 small tap targets
85 of 172 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 899 words of copy
The homepage carries about 899 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 2 mores (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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
30 other companies contacted
Loading the homepage contacts 30 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 abasteo.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
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on abasteo.mx, including 23 speed issues, 5 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.