Website review, no card needed
imef.org.mx website review
Visit site (opens in a new tab)Reviewed 3 November 202643 issues · 90 checks
This review found 43 issues worth fixing on imef.org.mx, 19 of them high impact, across 90 checks. The most urgent: use efficient cache lifetimes. 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
65DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 5.1 s |
| May 23, 2026 | 5.3 s |
| May 30, 2026 | 5.4 s |
| Jun 6, 2026 | 5.2 s |
| Jun 13, 2026 | 5.1 s |
| Jun 20, 2026 | 5.0 s |
| Jun 27, 2026 | 5.0 s |
| Jul 4, 2026 | 5.3 s |
| Jul 11, 2026 | 5.2 s |
| Jul 18, 2026 | 5.3 s |
| Jul 25, 2026 | 5.4 s |
| Aug 1, 2026 | 5.4 s |
| Aug 8, 2026 | 6.0 s |
| Aug 15, 2026 | 5.4 s |
| Aug 22, 2026 | 5.5 s |
| Aug 29, 2026 | 5.4 s |
| Sep 5, 2026 | 5.5 s |
| Sep 12, 2026 | 5.5 s |
| Sep 19, 2026 | 5.2 s |
| Sep 26, 2026 | 5.2 s |
| Oct 3, 2026 | 4.9 s |
| Oct 10, 2026 | 5.5 s |
| Oct 17, 2026 | 5.5 s |
| Oct 24, 2026 | 5.5 s |
| Oct 31, 2026 | 5.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 156 ms |
| May 23, 2026 | 154 ms |
| May 30, 2026 | 163 ms |
| Jun 6, 2026 | 149 ms |
| Jun 13, 2026 | 147 ms |
| Jun 20, 2026 | 140 ms |
| Jun 27, 2026 | 135 ms |
| Jul 4, 2026 | 145 ms |
| Jul 11, 2026 | 145 ms |
| Jul 18, 2026 | 137 ms |
| Jul 25, 2026 | 154 ms |
| Aug 1, 2026 | 167 ms |
| Aug 8, 2026 | 162 ms |
| Aug 15, 2026 | 177 ms |
| Aug 22, 2026 | 159 ms |
| Aug 29, 2026 | 156 ms |
| Sep 5, 2026 | 158 ms |
| Sep 12, 2026 | 158 ms |
| Sep 19, 2026 | 169 ms |
| Sep 26, 2026 | 173 ms |
| Oct 3, 2026 | 185 ms |
| Oct 10, 2026 | 196 ms |
| Oct 17, 2026 | 196 ms |
| Oct 24, 2026 | 188 ms |
| Oct 31, 2026 | 170 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.4 s
2.7 s
4.1 s
5.5 s
6.8 s
8.2 s
9.6 s
10.9 s
Speed
Use efficient cache lifetimes
31.5 s · 6.4 MB149 files are served with short cache lifetimes, so returning visitors download them again (6.4 MB).
Reduce unused JavaScript
20.8 s · 2.9 MBAbout 2.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 20.8 s faster on a phone.
Reduce unused CSS
10.6 s · 1.9 MBAbout 1.9 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 10.6 s faster on a phone.
Render-blocking requests
11.4 s53 files block the first paint until they finish downloading. Deferring or inlining them could save about 11.4 s.
Improve image delivery
1.5 s · 1,005 KiB7 images could be 1,005 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.
Mobile performance score: 45
45/100Your mobile performance score is 45. 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, Google Tag Manager and Facebook and others), adding 3.4 MB and 1.4 s of main-thread time.
YouTube adds 738 ms
738 msYouTube costs a phone 738 ms of main-thread work and 2.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.
Legacy JavaScript
550 ms · 69 KiBPolyfills for old browsers add 69 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 550 ms faster on a phone.
Google Tag Manager adds 341 ms
341 msGoogle Tag Manager costs a phone 341 ms of main-thread work and 883 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.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,613 HTML elements
The page has 1,613 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 219 ms. During a long task the page ignores taps.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Minify CSS
140 ms · 30 KiB30 KiB could be saved by minifying CSS.
Document request latency
166 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
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: 112 ms
112 msYour server sent the HTML in 112 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 LCP: 7.3 s
7.3 sReal visitors wait 7.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.5 s
4.5 sReal visitors see the first content after 4.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.3 s
2.3 sReal visitors wait 2.3 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 13.7 s
13.7 sThe first text or image appears after 13.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 56.2 s
56.2 sYour largest element takes 56.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Instituto Mexicano de Ejecutivos de Finanzas El círculo que…”.
Speed Index: 28.4 s
28.4 sVisually, the page fills in at 28.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 56.5 s
56.5 sThe page becomes fully interactive after 56.5 s. Good is under 3.8 s.
Real-user INP: 204 ms
204 msReal visitors wait 204 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 369 ms
369 msScripts block taps and scrolling for 369 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 156 ms to 170 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.1 s to 5.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.071
0.071The layout barely moves while loading (CLS 0.071, good is under 0.1).
Images and page weight
Page weight: 9.8 MB in 199 requests
9.8 MBYour homepage downloads 9.8 MB in 199 requests on a phone: scripts 5.0 MB (70), stylesheets 2.1 MB (66) and images 1.7 MB (32). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
BANNERS-SITIO-WEB-convencion-imef-1-768x236.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
4 images in older formats
4 images (405 KiB) 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.8 g of CO₂ per visit
2.78 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.78 g of CO₂e: 333.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Interactive controls must not be nested (2 elements)
Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.
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.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
13 links without text
13 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 43 images in the HTML carry an alt attribute.
46 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: 46 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“Bienvenidos al Instituto Mexicanode Ejecutivos de…”, “Instituto Mexicano de Ejecutivos de Finanzas” and “NUESTRA MISIÓN”). One clear main headline is easier for people and search engines.
132 internal links, 42 external
The homepage links to 132 pages on imef.org.mx and 42 external pages.
7 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “Bienvenidos al Instituto Mexicano de Ejecutivos de Finanzas, el círculo que reúne a líderes y altos directivos de las m…”.
Title: 51 characters
Your title is a healthy 51 characters: “Instituto Mexicano de Ejecutivos de Finanzas - IMEF”.
Canonical URL set
The canonical URL is https://www.imef.org.mx/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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.imef.org.mx/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.imef.org.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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Other pages
5 pages share a meta description
https://www.imef.org.mx/acerca-del-imef and https://www.imef.org.mx/convocatorias use the same meta description. A description written for each page earns more clicks.
14 pages without an H1
https://www.imef.org.mx/acerca-del-imef, https://www.imef.org.mx/consejo-directivo-del-imef, https://www.imef.org.mx/comites-tecnicos-del-imef, https://www.imef.org.mx/convenios-para-socios-del-imef, https://www.imef.org.mx/centro-de-certificacion-y-desarrollo and https://www.imef.org.mx/codigo-de-conducta-imef and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://www.imef.org.mx/centro-de-certificacion-y-desarrollo and https://www.imef.org.mx/codigo-de-conducta-imef took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 49 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
6 small tap targets
6 of 26 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”.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
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.
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.
Only about 66 words
The homepage has only about 66 words of visible text; thin pages give Google and first-time buyers little to go on.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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.
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and LinkedIn Insight.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight 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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
17 other companies contacted
Loading the homepage contacts 17 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 imef.org.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
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- netcup GmbH
Company
- Founded
- 1961
- Headquarters
- Mexico City
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on imef.org.mx, including 23 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.