Website review, no card needed

casamyers.com.mx logo

casamyers.com.mx website review

Visit site (opens in a new tab)Reviewed 24 October 202647 issues · 93 checks

This review found 47 issues worth fixing on casamyers.com.mx, 22 of them high impact, across 93 checks. The most urgent: render-blocking requests. 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
5.7 s4.8 sMay 2Oct 175.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20265.1 s
May 9, 20265.2 s
May 16, 20265.1 s
May 23, 20265.0 s
May 30, 20265.0 s
Jun 6, 20264.9 s
Jun 13, 20264.9 s
Jun 20, 20264.9 s
Jun 27, 20264.9 s
Jul 4, 20265.0 s
Jul 11, 20265.1 s
Jul 18, 20265.2 s
Jul 25, 20265.4 s
Aug 1, 20265.5 s
Aug 8, 20265.5 s
Aug 15, 20265.5 s
Aug 22, 20265.6 s
Aug 29, 20265.5 s
Sep 5, 20265.5 s
Sep 12, 20265.5 s
Sep 19, 20265.4 s
Sep 26, 20265.5 s
Oct 3, 20265.5 s
Oct 10, 20265.4 s
Oct 17, 20265.3 s
Real-visitor tap response (INP)75th percentile, phones
453 ms297 msMay 2Oct 17329 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026435 ms
May 9, 2026435 ms
May 16, 2026431 ms
May 23, 2026415 ms
May 30, 2026406 ms
Jun 6, 2026398 ms
Jun 13, 2026390 ms
Jun 20, 2026392 ms
Jun 27, 2026386 ms
Jul 4, 2026375 ms
Jul 11, 2026357 ms
Jul 18, 2026347 ms
Jul 25, 2026344 ms
Aug 1, 2026345 ms
Aug 8, 2026350 ms
Aug 15, 2026345 ms
Aug 22, 2026336 ms
Aug 29, 2026322 ms
Sep 5, 2026318 ms
Sep 12, 2026315 ms
Sep 19, 2026321 ms
Sep 26, 2026326 ms
Oct 3, 2026321 ms
Oct 10, 2026329 ms
Oct 17, 2026329 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 casamyers.com.mx (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. casamyers.com.mx at 0.7 s0.7 s
  2. casamyers.com.mx at 1.3 s1.3 s
  3. casamyers.com.mx at 2.0 s2.0 s
  4. casamyers.com.mx at 2.6 s2.6 s
  5. casamyers.com.mx at 3.3 s3.3 s
  6. casamyers.com.mx at 3.9 s3.9 s
  7. casamyers.com.mx at 4.6 s4.6 s
  8. casamyers.com.mx at 5.3 s5.3 s

Speed

14 to fix35
  • Render-blocking requests

    4.3 s

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

  • 13,734 HTML elements

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

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 6.8 s

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

  • Reduce unused JavaScript

    900 ms · 1.5 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and respond.io and others), adding 2.5 MB and 1.1 s of main-thread time.

  • Reduce unused CSS

    900 ms · 243 KiB

    About 243 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • 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

    725 ms

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

  • Google CDN adds 432 ms

    432 ms

    Google CDN costs a phone 432 ms of main-thread work and 1.5 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 359 ms

    359 ms

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

  • Use efficient cache lifetimes

    383 KiB

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

  • 20 long tasks on the main thread

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

  • Server response: 825 ms

    825 ms

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

  • Improve image delivery

    152 KiB

    5 images could be 152 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 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.

Core Web Vitals

11 to fix33
  • 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: 4.1 s

    4.1 s

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

  • Real-user FCP: 3.9 s

    3.9 s

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

  • Real-user TTFB: 2.9 s

    2.9 s

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

  • Largest Contentful Paint: 9.5 s

    9.5 s

    Your largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “CATEGORÍAS DESTACADAS”.

  • Time to Interactive: 34.9 s

    34.9 s

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

  • First Contentful Paint: 5.3 s

    5.3 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

  • Speed Index: 7.8 s

    7.8 s

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

  • Real-user INP: 377 ms

    377 ms

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

  • 5 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

3 checks passed
  • Real-user CLS: 0.03

    0.03

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

  • Tap response (INP) got 24% faster for real visitors

    -24%

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

  • Cumulative Layout Shift: 0.003

    0.003

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

Images and page weight

2 to fix60
  • Page weight: 6.8 MB in 241 requests

    6.8 MB

    Your homepage downloads 6.8 MB in 241 requests on a phone: scripts 2.7 MB (55), images 1.6 MB (110) and other files 1.3 MB (46). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    103 KiB

    1 image is downloaded at several times the size a phone draws it, for example big_banner_navidad_copia_3.webp at 2,100 px wide, shown at 300 px. Resized copies would save about 103 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (164 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.9 g of CO₂ per visit

    1.94 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

10 to fixGoogle 7186
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 15 text elements with low contrast

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

  • Orphan list items

    Some list items are not inside a list.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 7 form fields without a label

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

  • 2 links without text

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

  • Alternative text of images should not be repeated as text (11 elements)

    Alternative text of images should not be repeated as text: 11 elements on the page fail this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 130 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 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9278
  • 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.

  • No social preview image

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

  • 1 link crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 2,325 internal links, 6 external

    The homepage links to 2,325 pages on casamyers.com.mx and 6 external pages.

4 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “En Casa Myers, encuentra todo lo que necesitas para tus proyectos de construcción, reparación y mantenimiento con envío…”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Casa Myers | Ferreteros desde 1921| Tienda en línea”.

  • 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.casamyers.com.mx/media/sitemap/casa_myers.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.casamyers.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 (5,916 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 15 pages without an H1

    https://www.casamyers.com.mx/abrasivos, https://www.casamyers.com.mx/abrasivos/accesorios-de-corte, https://www.casamyers.com.mx/abrasivos/accesorios-de-corte/adaptador, https://www.casamyers.com.mx/abrasivos/accesorios-de-corte/arbol-morse, https://www.casamyers.com.mx/abrasivos/accesorios-de-corte/liquido-para-corte and https://www.casamyers.com.mx/abrasivos/brocas and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://www.casamyers.com.mx/abrasivos/accesorios-de-corte, https://www.casamyers.com.mx/abrasivos/accesorios-de-corte/arbol-morse and https://www.casamyers.com.mx/abrasivos/brocas/madera took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

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

Best practices

2 to fixGoogle 8591
  • 99 distorted images

    99 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “The source list for the Content Security Policy directive 'form-action' contains an invalid source: '*-gateway.masterca…”.

  • 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 (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

    163 of 168 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • 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,421 words of copy

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Button Call”.

  • 1 call to action

    The homepage has 1 call to action, for example “Button Call”.

  • 39 short forms

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

  • Social proof on the page

    Social proof on the homepage: 6 customer or partner logos and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google 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.

  • 19 cookies set on arrival

    19

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

  • 26 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on casamyers.com.mx, including 25 speed issues and 5 SEO issues. 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