Website review, no card needed
izabc.com.mx website review
Visit site (opens in a new tab)Reviewed 4 November 202642 issues · 77 checks
This review found 42 issues worth fixing on izabc.com.mx, 16 of them high impact, across 77 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
69D- #101,728 of 118,362 reviewed websitesbeats 12%
- #61,738 of 67,243 online storesbeats 7%
- #2,196 of 2,712 WooCommerce storesbeats 16%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.1 s |
| May 23, 2026 | 3.1 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 2.8 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 2.8 s |
| Oct 31, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 243 ms |
| May 23, 2026 | 212 ms |
| May 30, 2026 | 209 ms |
| Jun 6, 2026 | 201 ms |
| Jun 13, 2026 | 178 ms |
| Jun 20, 2026 | 175 ms |
| Jun 27, 2026 | 168 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 174 ms |
| Jul 18, 2026 | 174 ms |
| Jul 25, 2026 | 181 ms |
| Aug 1, 2026 | 178 ms |
| Aug 8, 2026 | 187 ms |
| Aug 15, 2026 | 194 ms |
| Aug 22, 2026 | 191 ms |
| Aug 29, 2026 | 207 ms |
| Sep 5, 2026 | 202 ms |
| Sep 12, 2026 | 205 ms |
| Sep 19, 2026 | 214 ms |
| Sep 26, 2026 | 202 ms |
| Oct 3, 2026 | 211 ms |
| Oct 10, 2026 | 198 ms |
| Oct 17, 2026 | 191 ms |
| Oct 24, 2026 | 194 ms |
| Oct 31, 2026 | 194 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
Speed
Render-blocking requests
1.6 s38 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 40
40/100Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.9 s
A phone's processor spends 6.9 s on main-thread work while loading, 4.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 (Google Tag Manager, typeform.com and hsappstatic.net and others), adding 3.4 MB and 3.5 s of main-thread time.
Improve image delivery
1.4 MB14 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
150 ms · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
200 ms · 878 KiB43 files are served with short cache lifetimes, so returning visitors download them again (878 KiB).
Google Tag Manager adds 913 ms
913 msGoogle Tag Manager costs a phone 913 ms of main-thread work and 1.0 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.
typeform.com adds 681 ms
681 mstypeform.com costs a phone 681 ms of main-thread work and 769 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.
hsappstatic.net adds 613 ms
613 mshsappstatic.net costs a phone 613 ms of main-thread work and 372 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.
Facebook adds 517 ms
517 msFacebook costs a phone 517 ms of main-thread work and 505 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 531 ms. During a long task the page ignores taps.
Reduce unused CSS
320 ms · 95 KiBAbout 95 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 320 ms faster on a phone.
Hubspot adds 316 ms
316 msHubspot costs a phone 316 ms of main-thread work and 413 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need.
Minify JavaScript
11 KiB11 KiB could be saved by minifying JavaScript.
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: 50 ms
50 msYour server sent the HTML in 50 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 TTFB: 2.0 s
2.0 sReal visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 38.5 s
38.5 sThe page becomes fully interactive after 38.5 s. Good is under 3.8 s.
Speed Index: 12.1 s
12.1 sVisually, the page fills in at 12.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.5 s
4.5 sThe first text or image appears after 4.5 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.4 s
1.4 sScripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 4.5 s
4.5 sYour largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Explora las soluciones que tenemos en IZA Business Centers …”. Most of its time is element render delay (2.5 s).
Real-user LCP: 3.8 s
3.8 sReal visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.9 s
2.9 sReal visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.
21 images without width and height
21 images have no width and height attributes, so the layout jumps as each one loads.
5 checks passed
Real-user INP: 186 ms
186 msReal visitors wait 186 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 243 ms to 194 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.1 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 7.3 MB in 211 requests
7.3 MBYour homepage downloads 7.3 MB in 211 requests on a phone: scripts 3.5 MB (83), images 3.2 MB (41) and fonts 294 KiB (8). Under 2 MB keeps phones on slow connections fast.
20 images in older formats
20 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.
12 images below the first screen load straight away
12 images further down the page (1.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
8 images far larger than shown
226 KiB8 images are downloaded at several times the size a phone draws them, for example mejorar-tall-image.jpg at 1,280 px wide, shown at 390 px. Resized copies would save about 226 KiB.
About 2.1 g of CO₂ per visit
2.08 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.08 g of CO₂e: 249.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
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.
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.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 23 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 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 3 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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://izabc.com.mx/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at izabc.com.mx/robots.txt, the first file search crawlers ask for.
89 internal links, 11 external
The homepage links to 89 pages on izabc.com.mx and 11 external pages.
5 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “Encuentra tu espacio de trabajo ideal en México. Renta oficinas amuebladas y equipadas, salas de juntas y coworking fle…”.
One H1 headline
Your main headline reads: “Explora las soluciones que tenemos en IZA Business Centers para impulsar el éxito de tu empresa.”.
Title: 58 characters
Your title is a healthy 58 characters: “IZA Business Centers | Renta tu oficina y cowork en México”.
Canonical URL set
The canonical URL is https://izabc.com.mx/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, WebPage and WebSite.
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://izabc.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.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (755 words), so crawlers that don't run JavaScript still read it.
Other pages
15 linked pages are broken
Your homepage links to https://izabc.com.mx/nosotros, https://izabc.com.mx/soluciones, https://izabc.com.mx/private-office, https://izabc.com.mx/soluciones/full-time-office, https://izabc.com.mx/soluciones/think-tank and https://izabc.com.mx/iza-office-club and 9 others, which answer with an error. Visitors hit a dead end and search engines drop them.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 30 found) and read each the way a search engine does.
Best practices
4 third-party cookies
4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were 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”).
2 checks passed
Tap targets are thumb-sized
18 of 18 tappable elements near the top are at least 24 px.
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.
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 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 702 words of copy
The homepage carries about 702 words of visible text.
2 checks passed
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Hotjar and HubSpot.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
20 cookies set on arrival
20Opening the homepage sets 20 cookies (measured from a US location before any click).
37 other companies contacted
Loading the homepage contacts 37 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) loads with the page.
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 izabc.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
- Hosting
- Google Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on izabc.com.mx, including 24 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.