Website review, no card needed
aplazo.mx website review
Visit site (opens in a new tab)Reviewed 23 October 202639 issues · 67 checks
This review found 39 issues worth fixing on aplazo.mx, 20 of them high impact, across 67 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
53FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 5.2 s |
| May 9, 2026 | 5.2 s |
| May 16, 2026 | 5.2 s |
| May 23, 2026 | 5.0 s |
| May 30, 2026 | 5.0 s |
| Jun 6, 2026 | 5.0 s |
| Jun 13, 2026 | 5.0 s |
| Jun 20, 2026 | 5.0 s |
| Jun 27, 2026 | 5.0 s |
| Jul 4, 2026 | 4.9 s |
| Jul 11, 2026 | 4.8 s |
| Jul 18, 2026 | 4.8 s |
| Jul 25, 2026 | 4.7 s |
| Aug 1, 2026 | 4.7 s |
| Aug 8, 2026 | 4.7 s |
| Aug 15, 2026 | 4.7 s |
| Aug 22, 2026 | 4.7 s |
| Aug 29, 2026 | 4.8 s |
| Sep 5, 2026 | 4.8 s |
| Sep 12, 2026 | 4.8 s |
| Sep 19, 2026 | 4.7 s |
| Sep 26, 2026 | 4.6 s |
| Oct 3, 2026 | 4.5 s |
| Oct 10, 2026 | 4.4 s |
| Oct 17, 2026 | 4.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 204 ms |
| May 9, 2026 | 207 ms |
| May 16, 2026 | 209 ms |
| May 23, 2026 | 210 ms |
| May 30, 2026 | 204 ms |
| Jun 6, 2026 | 202 ms |
| Jun 13, 2026 | 200 ms |
| Jun 20, 2026 | 195 ms |
| Jun 27, 2026 | 196 ms |
| Jul 4, 2026 | 194 ms |
| Jul 11, 2026 | 192 ms |
| Jul 18, 2026 | 193 ms |
| Jul 25, 2026 | 195 ms |
| Aug 1, 2026 | 195 ms |
| Aug 8, 2026 | 195 ms |
| Aug 15, 2026 | 195 ms |
| Aug 22, 2026 | 195 ms |
| Aug 29, 2026 | 196 ms |
| Sep 5, 2026 | 198 ms |
| Sep 12, 2026 | 199 ms |
| Sep 19, 2026 | 200 ms |
| Sep 26, 2026 | 202 ms |
| Oct 3, 2026 | 202 ms |
| Oct 10, 2026 | 203 ms |
| Oct 17, 2026 | 202 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
4.2 s · 824 KiB27 files are served with short cache lifetimes, so returning visitors download them again (824 KiB).
Reduce unused JavaScript
3.2 s · 735 KiBAbout 735 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.2 s faster on a phone.
Google Tag Manager adds 1.2 s
1.2 sGoogle Tag Manager costs a phone 1.2 s of main-thread work and 908 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 31
31/100Your mobile performance score is 31 (desktop: 32). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.4 s
A phone's processor spends 4.4 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, Facebook and TikTok and others), adding 1.4 MB and 1.6 s of main-thread time.
Legacy JavaScript
550 ms · 48 KiBPolyfills for old browsers add 48 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 550 ms faster on a phone.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 452 ms. During a long task the page ignores taps.
Render-blocking requests
150 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Improve image delivery
47 KiB3 images could be 47 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
11 KiB11 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: 1 ms
1 msYour server sent the HTML in 1 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.94
0.94For real visitors the layout shifts by 0.94 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 17.0 s
17.0 sYour largest element takes 17.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “null”.
Time to Interactive: 20.3 s
20.3 sThe page becomes fully interactive after 20.3 s. Good is under 3.8 s.
First Contentful Paint: 5.9 s
5.9 sThe first text or image appears after 5.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
Speed Index: 8.9 s
8.9 sVisually, the page fills in at 8.9 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 215 ms
215 msReal visitors wait 215 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
3 images without width and height
3 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-17, real Chrome visitors' tap response (inp) went from 204 ms to 202 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user TTFB: 275 ms
275 msReal visitors wait 275 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 5.2 s to 4.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.8 MB in 130 requests
2.8 MBYour homepage downloads 2.8 MB in 130 requests on a phone: scripts 1.8 MB (35), other files 338 KiB (63) and fonts 311 KiB (4). Under 2 MB keeps phones on slow connections fast.
About 0.8 g of CO₂ per visit
0.78 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.78 g of CO₂e: 93.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
9 buttons without a name
9 buttons have no accessible name, so screen readers announce just “button”.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
1 checks passed
31 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 34 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No page title
Your page has no <title>, so Google has to invent the blue link in search results.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
3 checks passed
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 http://www.aplazo.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://aplazo.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.
Best practices
14 small tap targets
14 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “ERROR TypeError: Cannot read properties of undefined (reading 'nativeElement')”.
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 78 words
The homepage has only about 78 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 Hotjar.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight and 4 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.
20 cookies set on arrival
20Opening the homepage sets 20 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.
36 other companies contacted
Loading the homepage contacts 36 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 aplazo.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 | Hotjar
- Hosting
- AWS
Hiring
- Hiring
- 12 open roles
- Teams
- Engineering (5), Product (2), Commercial (1), Finance (1)
- Job board
- ashby
- Careers page
- aplazo.mx/careers (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on aplazo.mx, including 19 speed issues, 6 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.