Website review, no card needed

esri.mx logo

esri.mx website review

Visit site (opens in a new tab)Reviewed 31 October 202639 issues · 78 checks

This review found 39 issues worth fixing on esri.mx, 18 of them high impact, across 78 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
4.3 s2.6 sMay 9Oct 243.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.0 s
May 16, 20264.1 s
May 23, 20263.9 s
May 30, 20263.9 s
Jun 6, 20263.6 s
Jun 13, 20263.4 s
Jun 20, 20263.6 s
Jun 27, 20263.6 s
Jul 4, 20264.0 s
Jul 11, 20263.4 s
Jul 18, 20263.3 s
Jul 25, 20262.8 s
Aug 1, 20263.0 s
Aug 8, 20263.2 s
Aug 15, 20263.4 s
Aug 22, 20263.7 s
Aug 29, 20263.7 s
Sep 5, 20263.5 s
Sep 12, 20263.4 s
Sep 19, 20263.2 s
Sep 26, 20263.1 s
Oct 3, 20263.1 s
Oct 10, 20263.1 s
Oct 17, 20263.2 s
Oct 24, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
170 ms124 msAug 1Oct 17156 ms
Show as table
DateReal-visitor tap response (INP)
Aug 1, 2026129 ms
Aug 8, 2026132 ms
Aug 15, 2026147 ms
Aug 22, 2026143 ms
Aug 29, 2026165 ms
Sep 5, 2026161 ms
Sep 12, 2026162 ms
Sep 19, 2026165 ms
Sep 26, 2026159 ms
Oct 3, 2026158 ms
Oct 10, 2026155 ms
Oct 17, 2026156 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 esri.mx (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. esri.mx at 0.4 s0.4 s
  2. esri.mx at 0.8 s0.8 s
  3. esri.mx at 1.2 s1.2 s
  4. esri.mx at 1.6 s1.6 s
  5. esri.mx at 2.0 s2.0 s
  6. esri.mx at 2.4 s2.4 s
  7. esri.mx at 2.8 s2.8 s
  8. esri.mx at 3.2 s3.2 s

Speed

12 to fix47
  • Use efficient cache lifetimes

    8.3 s · 7.1 MB

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

  • Improve image delivery

    4.0 s · 6.6 MB

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

  • Reduce unused JavaScript

    5.6 s · 902 KiB

    About 902 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.6 s faster on a phone.

  • Render-blocking requests

    4.0 s

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

  • Reduce unused CSS

    1.3 s · 174 KiB

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

  • Mobile performance score: 47

    47/100

    Your mobile performance score is 47. 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 (YouTube, Facebook and Adobe Tag Manager and others), adding 1.9 MB and 1.2 s of main-thread time.

  • YouTube adds 519 ms

    519 ms

    YouTube costs a phone 519 ms of main-thread work and 980 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.

  • Minify JavaScript

    450 ms · 65 KiB

    65 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    400 ms · 37 KiB

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

  • Main-thread work: 2.6 s

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

  • esri.com adds 137 ms

    137 ms

    esri.com costs a phone 137 ms of main-thread work and 299 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.

  • 10 long tasks on the main thread

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

  • Minify CSS

    150 ms · 4 KiB

    4 KiB could be saved by minifying CSS.

  • Font display

    50 ms

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

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

    2 ms

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

Core Web Vitals

9 to fix50
  • 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 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.

  • First Contentful Paint: 9.2 s

    9.2 s

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

  • Largest Contentful Paint: 32.3 s

    32.3 s

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

  • Time to Interactive: 33.3 s

    33.3 s

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

  • Speed Index: 11.3 s

    11.3 s

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user TTFB: 910 ms

    910 ms

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

  • Total Blocking Time: 372 ms

    372 ms

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

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

    +19%

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

3 checks passed
  • Real-user CLS: 0.00

    0.00

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

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

    -20%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.0 s to 3.3 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 fix25
  • Page weight: 9.2 MB in 121 requests

    9.2 MB

    Your homepage downloads 9.2 MB in 121 requests on a phone: images 7.0 MB (23), scripts 1.8 MB (47) and stylesheets 168 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 1.5 MB together. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    956 KiB

    3 images are downloaded at several times the size a phone draws them, for example sigsa-card-01.jpg at 2,100 px wide, shown at 326 px. Resized copies would save about 956 KiB.

  • 5 images in older formats

    5 images (2.7 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.

  • About 2.6 g of CO₂ per visit

    2.61 g

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

2 to fixGoogle 10098
  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 14 images in the HTML carry an alt attribute.

  • 44 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: 44 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10093
  • Title is long (130 characters)

    Your title is 130 characters, so Google will cut it off around 60: “Esri MX: Software de representación cartográfica (SIG), Inteligencia de Ubicación, Busine…”.

  • 13 internal links, 7 external

    The homepage links to 13 pages on esri.mx and 7 external pages.

7 checks passed
  • Meta description: 130 characters

    Your meta description is 130 characters: “Esri MX: Software de representación cartográfica (SIG), Inteligencia de Ubicación, Business Analytics, SIG + AI, Gemelo…”.

  • One H1 headline

    Your main headline reads: “Impulsa tus ventas y atrae más clientes con Inteligencia de Ubicación”.

  • Canonical URL set

    The canonical URL is https://www.esri.mx/es-mx/home.

  • Structured data in place

    Structured data found: BreadcrumbList.

  • 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.esri.mx/sitemap-sites.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.esri.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 (603 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.esri.mx/es-mx/acerca-de-esrimx has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.esri.mx/es-mx/industries/telecommunications/segments/planificacion-e-ingenieria has no <h1> headline, so visitors and search engines get no clear main topic.

  • 12 internal pages checked

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

5 checks passed
  • Linked pages load

    All 12 pages we checked loaded without an error.

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

Best practices

2 to fixGoogle 7391
  • 9 third-party cookies

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “_console is not defined”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix20
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 304 words of copy

    The homepage carries about 304 words of visible text.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 10 cookies set on arrival

    10

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

  • 31 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
Esri

Hiring

Hiring
493 open roles
Teams
PS Services Delivery Domestic (88), Product Development (51), Industry Solutions (36), Local/State/Provincial Govt. (25)
Job board
greenhouse

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 esri.mx, including 21 speed issues, 1 SEO issue 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

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