Website review, no card needed

sadm.gob.mx logo

sadm.gob.mx website review

Visit site (opens in a new tab)Reviewed 4 November 202648 issues · 85 checks

This review found 48 issues worth fixing on sadm.gob.mx, 19 of them high impact, across 85 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
5.0 s2.9 sMay 16Oct 313.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.4 s
May 23, 20264.7 s
May 30, 20264.7 s
Jun 6, 20264.4 s
Jun 13, 20263.9 s
Jun 20, 20263.9 s
Jun 27, 20263.6 s
Jul 11, 20263.5 s
Jul 18, 20263.5 s
Jul 25, 20263.3 s
Aug 1, 20263.9 s
Aug 8, 20263.6 s
Aug 15, 20263.3 s
Aug 22, 20263.9 s
Aug 29, 20263.7 s
Sep 5, 20263.5 s
Sep 12, 20263.5 s
Sep 19, 20263.3 s
Sep 26, 20263.5 s
Oct 3, 20263.8 s
Oct 10, 20263.6 s
Oct 17, 20263.5 s
Oct 24, 20263.1 s
Oct 31, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
237 ms148 msMay 16Oct 31178 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026220 ms
May 23, 2026227 ms
May 30, 2026197 ms
Jun 6, 2026203 ms
Jun 13, 2026216 ms
Jun 20, 2026203 ms
Jun 27, 2026216 ms
Jul 4, 2026182 ms
Jul 11, 2026182 ms
Jul 18, 2026177 ms
Jul 25, 2026182 ms
Aug 1, 2026191 ms
Aug 8, 2026175 ms
Aug 15, 2026158 ms
Aug 22, 2026162 ms
Aug 29, 2026162 ms
Sep 5, 2026161 ms
Sep 12, 2026167 ms
Sep 19, 2026159 ms
Sep 26, 2026162 ms
Oct 3, 2026178 ms
Oct 10, 2026175 ms
Oct 17, 2026182 ms
Oct 24, 2026179 ms
Oct 31, 2026178 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 sadm.gob.mx (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sadm.gob.mx at 0.4 s0.4 s
  2. sadm.gob.mx at 0.9 s0.9 s
  3. sadm.gob.mx at 1.3 s1.3 s
  4. sadm.gob.mx at 1.8 s1.8 s
  5. sadm.gob.mx at 2.2 s2.2 s
  6. sadm.gob.mx at 2.7 s2.7 s
  7. sadm.gob.mx at 3.1 s3.1 s
  8. sadm.gob.mx at 3.5 s3.5 s

Speed

6 to fix59
  • Use efficient cache lifetimes

    16.6 s · 54.6 MB

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

  • Improve image delivery

    7.3 s · 2.9 MB

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

  • Render-blocking requests

    2.8 s

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

  • Mobile performance score: 59

    59/100

    Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    450 ms · 108 KiB

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

  • Main-thread work: 2.1 s

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Google CDN and Cloudflare and others), adding 340 KiB and 123 ms of main-thread time.

  • Minify CSS

    150 ms · 5 KiB

    5 KiB could be saved by minifying CSS.

  • 6 long tasks on the main thread

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

  • Legacy JavaScript

    100 ms · 10 KiB

    Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

  • Reduce unused CSS

    56 KiB

    About 56 KiB of CSS is downloaded but never applied on this page.

  • 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: 145 ms

    145 ms

    Your server sent the HTML in 145 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix67
  • 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.0 s

    4.0 s

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

  • Real-user FCP: 4.1 s

    4.1 s

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

  • Largest Contentful Paint: 29.5 s

    29.5 s

    Your largest element takes 29.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Conoce Más”.

  • Time to Interactive: 29.7 s

    29.7 s

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

  • Speed Index: 6.3 s

    6.3 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Total Blocking Time: 270 ms

    270 ms

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

  • 10 images without width and height

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

6 checks passed
  • Real-user INP: 188 ms

    188 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user TTFB: 564 ms

    564 ms

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

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

    -20%

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

  • Largest content (LCP) got 31% faster for real visitors

    -31%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix43
  • Page weight: 80.7 MB in 54 requests

    80.7 MB

    Your homepage downloads 80.7 MB in 54 requests on a phone: images 80.1 MB (32), scripts 375 KiB (10) and fonts 152 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 6 images in older formats

    6 images (1.1 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.

  • 5 images below the first screen load straight away

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

  • 1 image far larger than shown

    233 KiB

    1 image is downloaded at several times the size a phone draws it, for example 5b6b5f504c3819038b156e33_logo_sadm.png at 5,071 px wide, shown at 220 px. Resized copies would save about 233 KiB.

  • About 22.9 g of CO₂ per visit

    22.86 g

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

Accessibility

10 to fixGoogle 7585
  • Invalid ARIA attributes

    11 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (14 elements)

    All page content should be contained by landmarks: 14 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.

  • 21 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

1 checks passed
  • 38 automated accessibility rules passed

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

SEO

6 to fixGoogle 8379
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “Invitación abierta a Contratistas y Proveedores d…”). One clear main headline is easier for people and search engines.

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

  • No XML sitemap

    No XML sitemap at https://sadm.gob.mx/sitemap.xml, so Google discovers your pages only by following links.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 86 internal links, 39 external

    The homepage links to 86 pages on sadm.gob.mx and 39 external pages.

3 checks passed
  • Meta description: 144 characters

    Your meta description is 144 characters: “Servicios de agua y drenaje, agua, drenaje, saneamiento, calidad del agua, cuidado del agua, contratos, clic en línea, …”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “Servicios de Agua y Drenaje de Monterrey I.P.D.”.

  • robots.txt in place

    robots.txt is in place.

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://sadm.gob.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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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 (789 words), so crawlers that don't run JavaScript still read it.

Other pages

6 to fix43
  • 1 linked page is broken

    Your homepage links to https://sadm.gob.mx/services, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 page without a title

    https://sadm.gob.mx/CFDI4 has no <title>, so Google invents the link text in results.

  • 2 pages share a title

    / and https://sadm.gob.mx/SADM/index.jsp all use the title “Servicios de Agua y Drenaje de Monterrey I.P.D.”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://sadm.gob.mx/AyD_Aclaraciones and https://sadm.gob.mx/CFDI4 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://sadm.gob.mx/SADM/index.jsp and https://sadm.gob.mx/SADM/Prensa.jsp use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://sadm.gob.mx/AyD_Aclaraciones and https://sadm.gob.mx/CFDI4 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://sadm.gob.mx/CFDI4 has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 5 internal pages checked

    We fetched 5 pages linked from your homepage and read each the way a search engine does.

2 checks passed
  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

1 to fixGoogle 9693
  • 13 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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: 4 customer or partner logos. 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 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 656 words of copy

    The homepage carries about 656 words of visible text.

2 checks passed
  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 3 cookies set on arrival

    3

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

  • 8 other companies contacted

    Loading the homepage contacts 8 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 sadm.gob.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
Webflow
Framework
jQuery
Analytics
Google Analytics
Hosting
Cloudflare

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 sadm.gob.mx, including 15 speed issues, 6 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