Website review, no card needed
extendedsuites.com.mx website review
Visit site (opens in a new tab)Reviewed 25 October 202640 issues · 87 checks
This review found 40 issues worth fixing on extendedsuites.com.mx, 21 of them high impact, across 87 checks. The most urgent: render-blocking requests. 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
61DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 4.1 s |
| May 9, 2026 | 4.0 s |
| May 16, 2026 | 4.0 s |
| May 23, 2026 | 4.1 s |
| May 30, 2026 | 4.4 s |
| Jun 6, 2026 | 4.6 s |
| Jun 13, 2026 | 4.7 s |
| Jun 20, 2026 | 4.8 s |
| Jun 27, 2026 | 4.9 s |
| Jul 4, 2026 | 4.9 s |
| Jul 11, 2026 | 4.8 s |
| Jul 18, 2026 | 4.6 s |
| Jul 25, 2026 | 4.6 s |
| Aug 1, 2026 | 4.3 s |
| Aug 8, 2026 | 3.9 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 2.8 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.1 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 3.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 183 ms |
| May 9, 2026 | 180 ms |
| May 16, 2026 | 187 ms |
| May 23, 2026 | 187 ms |
| May 30, 2026 | 189 ms |
| Jun 6, 2026 | 193 ms |
| Jun 13, 2026 | 188 ms |
| Jun 20, 2026 | 190 ms |
| Jun 27, 2026 | 187 ms |
| Jul 4, 2026 | 189 ms |
| Jul 11, 2026 | 193 ms |
| Jul 18, 2026 | 193 ms |
| Jul 25, 2026 | 190 ms |
| Aug 1, 2026 | 187 ms |
| Aug 8, 2026 | 188 ms |
| Aug 15, 2026 | 187 ms |
| Aug 22, 2026 | 189 ms |
| Aug 29, 2026 | 190 ms |
| Sep 5, 2026 | 187 ms |
| Sep 12, 2026 | 187 ms |
| Sep 19, 2026 | 188 ms |
| Sep 26, 2026 | 190 ms |
| Oct 3, 2026 | 202 ms |
| Oct 10, 2026 | 201 ms |
| Oct 17, 2026 | 204 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
How it loaded on a phone
1.0 s
1.9 s
2.9 s
3.9 s
4.9 s
5.8 s
6.8 s
7.8 s
Speed
Render-blocking requests
3.8 s47 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.8 s.
Reduce unused JavaScript
1.4 s · 1.9 MBAbout 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Improve image delivery
1.1 s · 2.1 MB17 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Use efficient cache lifetimes
1.4 s · 450 KiB89 files are served with short cache lifetimes, so returning visitors download them again (450 KiB).
Google Tag Manager adds 1.5 s
1.5 sGoogle Tag Manager costs a phone 1.5 s of main-thread work and 2.1 MB 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: 8
8/100Your mobile performance score is 8 (desktop: 38). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.0 s
A phone's processor spends 6.0 s on main-thread work while loading, 3.5 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, YouTube and mirai.com and others), adding 9.0 MB and 2.4 s of main-thread time.
mirai.com adds 325 ms
325 msmirai.com costs a phone 325 ms of main-thread work and 5.6 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.
YouTube adds 393 ms
393 msYouTube costs a phone 393 ms of main-thread work and 993 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.
2,182 HTML elements
The page has 2,182 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 145 KiBAbout 145 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 209 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 24 KiBPolyfills for old browsers add 24 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Phones get a much slower page than desktops
Desktop scores 38 but mobile only 8. A gap that wide usually means heavy scripts and images that hit phones hardest.
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 CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 9 ms
9 msYour server sent the HTML in 9 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.72
0.72For real visitors the layout shifts by 0.72 (75th percentile). Good is under 0.1.
First Contentful Paint: 7.8 s
7.8 sThe first text or image appears after 7.8 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 14.1 s
14.1 sYour largest element takes 14.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “pop MONTERREY”.
Time to Interactive: 40.6 s
40.6 sThe page becomes fully interactive after 40.6 s. Good is under 3.8 s.
Speed Index: 12.3 s
12.3 sVisually, the page fills in at 12.3 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.784
0.784The layout shifts by 0.784 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 183 ms to 204 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 166 ms
166 msReal visitors wait 166 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 766 ms
766 msReal visitors wait 766 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.1 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 9.9 MB in 226 requests
9.9 MBYour homepage downloads 9.9 MB in 226 requests on a phone: images 5.0 MB (42), scripts 3.9 MB (76) and fonts 532 KiB (7). Under 2 MB keeps phones on slow connections fast.
About 2.8 g of CO₂ per visit
2.80 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.80 g of CO₂e: 336.2 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
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
17 links without text
17 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 91 images in the HTML carry an alt attribute.
49 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: 49 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Structured data has 1 problem
Structured data found (BreadcrumbList, FAQPage, ImageObject and WebPage) but with 1 problem, for example “ld+json block 3 is not valid JSON (Unexpected non-whitespace character after JSON at position 1)”.
13 links with vague text
13 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
180 internal links, 14 external
The homepage links to 180 pages on extendedsuites.com.mx and 14 external pages.
6 checks passed
Meta description: 137 characters
Your meta description is 137 characters: “Extended Suites es la cadena de hoteles líder en estancias de larga duración en México. Descubre nuestros hoteles y des…”.
Title: 49 characters
Your title is a healthy 49 characters: “Extended Suites | Hoteles en México - Web oficial”.
Canonical URL set
The canonical URL is https://www.extendedsuites.com.mx/.
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.extendedsuites.com.mx/sitemap_index.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://www.extendedsuites.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 (2,063 words), so crawlers that don't run JavaScript still read it.
Other pages
11 pages share a title
https://www.extendedsuites.com.mx/hotel-extended-suites-queretaro-juriquilla/ofertas/extended-days-3bhol3, https://www.extendedsuites.com.mx/hotel-extended-suites-chihuahua-la-juventud/ofertas/extended-days-0b2y91, https://www.extendedsuites.com.mx/hotel-extended-suites-ciudad-juarez-consulado/ofertas/extended-days-2b2yb3, https://www.extendedsuites.com.mx/hotel-extended-suites-ciudad-del-carmen-aeropuerto/ofertas/extended-days-1b2ya2, https://www.extendedsuites.com.mx/hotel-extended-suites-coatzacoalcos-forum/ofertas/extended-days-3b2yc4 and https://www.extendedsuites.com.mx/hotel-extended-suites-merida-siglo-xxi/ofertas/extended-days-4b2yd0 and 5 others all use the title “Extended Days | Extended Suites”. Search engines can't tell which page to show for a search, so each competes with the others.
10 pages share a meta description
https://www.extendedsuites.com.mx/hotel-extended-suites-queretaro-juriquilla/ofertas/extended-days-3bhol3, https://www.extendedsuites.com.mx/hotel-extended-suites-chihuahua-la-juventud/ofertas/extended-days-0b2y91, https://www.extendedsuites.com.mx/hotel-extended-suites-ciudad-juarez-consulado/ofertas/extended-days-2b2yb3, https://www.extendedsuites.com.mx/hotel-extended-suites-ciudad-del-carmen-aeropuerto/ofertas/extended-days-1b2ya2, https://www.extendedsuites.com.mx/hotel-extended-suites-coatzacoalcos-forum/ofertas/extended-days-3b2yc4 and https://www.extendedsuites.com.mx/hotel-extended-suites-merida-siglo-xxi/ofertas/extended-days-4b2yd0 and 4 others use the same meta description. A description written for each page earns more clicks.
12 pages without an H1
https://www.extendedsuites.com.mx/en, https://www.extendedsuites.com.mx/hotel-extended-suites-queretaro-juriquilla/ofertas/extended-days-3bhol3, https://www.extendedsuites.com.mx/hotel-extended-suites-chihuahua-la-juventud/ofertas/extended-days-0b2y91, https://www.extendedsuites.com.mx/hotel-extended-suites-ciudad-juarez-consulado/ofertas/extended-days-2b2yb3, https://www.extendedsuites.com.mx/hotel-extended-suites-ciudad-del-carmen-aeropuerto/ofertas/extended-days-1b2ya2 and https://www.extendedsuites.com.mx/hotel-extended-suites-coatzacoalcos-forum/ofertas/extended-days-3b2yc4 and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://www.extendedsuites.com.mx/hotel-extended-suites-mexicali-catavina/ofertas/extended-days-5b2ye1 and https://www.extendedsuites.com.mx/hotel-extended-suites-tijuana-macroplaza/ofertas/extended-days-3b2yj1 took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 38 found) and read each the way a search engine does.
5 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.
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
21 small tap targets
21 of 68 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.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 747 words of copy
The homepage carries about 747 words of visible text.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Call Center”.
Direct contact links
Visitors can reach you directly: 2 phone links and 5 email links.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Ads (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.
1 cookie set on arrival
1Opening the homepage sets 1 cookie, 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.
14 other companies contacted
Loading the homepage contacts 14 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 extendedsuites.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
- jQuery
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on extendedsuites.com.mx, including 20 speed issues, 3 SEO issues and 3 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.