Website review, no card needed

alvamex.com.mx logo

alvamex.com.mx website review

Visit site (opens in a new tab)Reviewed 19 October 202651 issues · 92 checks

This review found 51 issues worth fixing on alvamex.com.mx, 23 of them high impact, across 92 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
7.6 s2.9 sMay 2Oct 176.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.9 s
May 9, 20263.6 s
May 16, 20263.4 s
May 23, 20263.8 s
May 30, 20264.4 s
Jun 6, 20264.7 s
Jun 13, 20264.8 s
Jun 20, 20264.9 s
Jun 27, 20264.7 s
Jul 4, 20264.7 s
Jul 11, 20264.7 s
Jul 18, 20264.6 s
Jul 25, 20265.1 s
Aug 1, 20266.6 s
Aug 8, 20266.7 s
Aug 15, 20266.7 s
Aug 22, 20266.3 s
Aug 29, 20266.3 s
Sep 5, 20266.5 s
Sep 12, 20266.7 s
Sep 19, 20267.0 s
Sep 26, 20266.2 s
Oct 3, 20266.3 s
Oct 10, 20266.4 s
Oct 17, 20266.3 s
Real-visitor tap response (INP)75th percentile, phones
256 ms144 msMay 2Oct 17243 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026166 ms
May 9, 2026161 ms
May 16, 2026158 ms
May 23, 2026157 ms
May 30, 2026160 ms
Jun 6, 2026159 ms
Jun 13, 2026163 ms
Jun 20, 2026173 ms
Jun 27, 2026174 ms
Jul 4, 2026180 ms
Jul 11, 2026188 ms
Jul 18, 2026186 ms
Jul 25, 2026191 ms
Aug 1, 2026196 ms
Aug 8, 2026198 ms
Aug 15, 2026202 ms
Aug 22, 2026207 ms
Aug 29, 2026217 ms
Sep 5, 2026230 ms
Sep 12, 2026239 ms
Sep 19, 2026240 ms
Sep 26, 2026234 ms
Oct 3, 2026237 ms
Oct 10, 2026238 ms
Oct 17, 2026243 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 alvamex.com.mx (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alvamex.com.mx at 1.9 s1.9 s
  2. alvamex.com.mx at 3.7 s3.7 s
  3. alvamex.com.mx at 5.6 s5.6 s
  4. alvamex.com.mx at 7.5 s7.5 s
  5. alvamex.com.mx at 9.3 s9.3 s
  6. alvamex.com.mx at 11.2 s11.2 s
  7. alvamex.com.mx at 13.0 s13.0 s
  8. alvamex.com.mx at 14.9 s14.9 s

Speed

14 to fix38
  • Use efficient cache lifetimes

    13.8 s · 5.4 MB

    262 files are served with short cache lifetimes, so returning visitors download them again (5.4 MB).

  • Reduce unused JavaScript

    10.8 s · 2.1 MB

    About 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.8 s faster on a phone.

  • Improve image delivery

    2.6 s · 1.2 MB

    7 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.

  • Render-blocking requests

    2.5 s

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

  • Reduce unused CSS

    1.1 s · 216 KiB

    About 216 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 38

    38/100

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

  • Main-thread work: 5.6 s

    A phone's processor spends 5.6 s on main-thread work while loading, 2.0 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 (YouTube, Google Tag Manager and Facebook and others), adding 2.0 MB and 745 ms of main-thread time.

  • Document request latency

    750 ms

    The HTML itself could arrive about 750 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    729 ms

    Reduce initial server response time. Google estimates savings of 729 ms on a phone.

  • YouTube adds 322 ms

    322 ms

    YouTube costs a phone 322 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.

  • Google Tag Manager adds 273 ms

    273 ms

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

  • 1,713 HTML elements

    The page has 1,713 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Server response: 829 ms

    829 ms

    Your server takes 829 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 14 long tasks on the main thread

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

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Legacy JavaScript

    23 KiB

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

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

    5 KiB could be saved by minifying JavaScript.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

Core Web Vitals

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

  • Real-user LCP: 8.0 s

    8.0 s

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

  • Real-user FCP: 3.3 s

    3.3 s

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

  • Real-user TTFB: 2.6 s

    2.6 s

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

  • Largest Contentful Paint: 42.7 s

    42.7 s

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

  • Speed Index: 25.0 s

    25.0 s

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

  • Time to Interactive: 44.9 s

    44.9 s

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

  • First Contentful Paint: 4.1 s

    4.1 s

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

  • Total Blocking Time: 802 ms

    802 ms

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

  • Real-user INP: 227 ms

    227 ms

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

  • Real-user CLS: 0.17

    0.17

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

  • Tap response (INP) got 47% slower for real visitors

    +47%

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

  • Largest content (LCP) got 69% slower for real visitors

    +69%

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

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix50
  • Page weight: 9.4 MB in 342 requests

    9.4 MB

    Your homepage downloads 9.4 MB in 342 requests on a phone: images 4.6 MB (57), scripts 4.0 MB (135) and stylesheets 336 KiB (102). Under 2 MB keeps phones on slow connections fast.

  • 8 images in older formats

    8 images (1.5 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 far larger than shown

    403 KiB

    4 images are downloaded at several times the size a phone draws them, for example PROHS4200.jpg at 700 px wide, shown at 175 px. Resized copies would save about 403 KiB.

  • About 2.7 g of CO₂ per visit

    2.65 g

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

8 to fixGoogle 8490
  • 10 text elements with low contrast

    10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 54 images without alt text

    54 images have no alt text, which hurts accessibility and image search.

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 15 form fields without a label

    15 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h5, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • Meta description is long (463 characters)

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 145 internal links, 28 external

    The homepage links to 145 pages on alvamex.com.mx and 28 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Encuentra la sucursal más cercana a ti”.

  • Title: 39 characters

    Your title is a healthy 39 characters: “Alvamex Pinturas - Dale color a tu vida”.

  • Canonical URL set

    The canonical URL is https://www.alvamex.com.mx/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

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

AI search readiness

100
4 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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.alvamex.com.mx/llms.txt (80 KiB, 410 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.alvamex.com.mx/blog has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.alvamex.com.mx/contactanos has no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://www.alvamex.com.mx/distribuidor, https://www.alvamex.com.mx/contactanos, https://www.alvamex.com.mx/nosotros and https://www.alvamex.com.mx/blog took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 41 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    4 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 4 pages that loaded have a <title>.

Best practices

4 to fixGoogle 7370
  • 2 broken images

    2 images failed to load on a phone, for example https://www.alvamex.com.mx/.

  • 19 small tap targets

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

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.

  • 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

4 to fix57
  • 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: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 187 words

    The homepage has only about 187 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 12 cookies set on arrival

    12

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

  • 17 other companies contacted

    Loading the homepage contacts 17 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 alvamex.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

CMS
WordPress
Framework
React
E-commerce
WooCommerce
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 51 issues on alvamex.com.mx, including 27 speed issues, 2 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

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