9.4 sec in total
2.2 sec
6.7 sec
582 ms
Visit imer.gob.mx now to see the best up-to-date IMER content for Mexico and also check out these interesting facts you probably never knew about imer.gob.mx
Instituto Mexicano de la Radio
Visit imer.gob.mxWe analyzed Imer.gob.mx page load time and found that the first response time was 2.2 sec and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
imer.gob.mx performance score
name
value
score
weighting
Value22.5 s
0/100
10%
Value41.1 s
0/100
25%
Value56.3 s
0/100
10%
Value40,150 ms
0/100
30%
Value0.215
58/100
15%
Value86.8 s
0/100
10%
2164 ms
61 ms
37 ms
37 ms
38 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Imer.gob.mx, 11% (11 requests) were made to Maps.googleapis.com and 4% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Imer.mx.
Page size can be reduced by 3.6 MB (56%)
6.4 MB
2.8 MB
In fact, the total size of Imer.gob.mx main page is 6.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 105.4 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 105.4 kB or 78% of the original size.
Potential reduce by 90.0 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. IMER images are well optimized though.
Potential reduce by 1.1 MB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.1 MB or 71% of the original size.
Potential reduce by 2.3 MB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Imer.gob.mx needs all CSS files to be minified and compressed as it can save up to 2.3 MB or 89% of the original size.
Number of requests can be reduced by 59 (66%)
89
30
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IMER. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
www.imer.mx
2164 ms
wp-emoji-release.min.js
61 ms
wild-googlemap-css-frontend.css
37 ms
page-list.css
37 ms
styles.css
38 ms
tp_twitter_plugin.css
39 ms
css
57 ms
wpgform.css
61 ms
js_composer.min.css
318 ms
css
81 ms
main.min.css
162 ms
font-awesome.min.css
75 ms
fontello.min.css
69 ms
custom-89629bfe92.css
249 ms
media-89629bfe92.css
100 ms
style.css
84 ms
ubermenu.min.css
111 ms
cleanwhite.css
124 ms
font-awesome.min.css
147 ms
Defaults.css
226 ms
ultimate.min.css
377 ms
genericons.css
361 ms
jetpack.css
362 ms
wpss-pkg.min.css
368 ms
jquery.js
370 ms
jquery-migrate.min.js
366 ms
js
127 ms
wild-googlemap-js.js
365 ms
wild-googlemap-js-frontend.js
365 ms
above-the-fold.min.js
365 ms
ultimate.min.js
411 ms
wpss-pkg.min.js
409 ms
external-tracking.min.js
408 ms
default_style.css
28 ms
photon.js
24 ms
jquery.form.min.js
24 ms
scripts.js
23 ms
devicepx-jetpack.js
7 ms
gprofiles.js
85 ms
wpgroho.js
40 ms
main.min.js
101 ms
js
55 ms
ubermenu.min.js
61 ms
wp-embed.min.js
40 ms
js_composer_front.min.js
61 ms
e-201611.js
17 ms
analytics.js
195 ms
logo_IMER-transp-601_blanco.png
172 ms
embed
2181 ms
afr.php
1791 ms
imerlogoverde_footer_blanco.png
225 ms
ban_arcpualc_01.jpg
234 ms
pst_mcrSte_ErnestoDelaPena.jpg
2039 ms
mainimer_ban_inai.jpg
233 ms
portaltransparencia_banner_rect.jpg
235 ms
sisiinfomex_banner_rect.jpg
234 ms
ban_transp_foc_mainimer1.jpg
236 ms
ban_prog_inst_imer_logros_2015.jpg
237 ms
ban_parametria.gif
238 ms
logo_sep_main31.jpg
239 ms
EfemeridesSonoras.jpg
2209 ms
FonotecaHistorica2.jpg
2213 ms
all.js
147 ms
linkid.js
129 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
138 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
141 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
1617 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
1614 ms
fontello.woff
1623 ms
fontawesome-webfont.woff
1616 ms
fontawesome-webfont.woff
1938 ms
Defaults.svg
2112 ms
Defaults.woff
1967 ms
widgets.js
1938 ms
hovercard.css
1268 ms
services.css
1276 ms
ajax-loader.gif
351 ms
EfemeridesSonoras-150x150.jpg
346 ms
FonotecaHistorica2-150x150.jpg
353 ms
lg.php
323 ms
collect
291 ms
g.gif
367 ms
js
364 ms
init_embed.js
588 ms
btn_mainimer_ar.jpg
414 ms
642 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
665 ms
xd_arbiter.php
296 ms
xd_arbiter.php
389 ms
common.js
418 ms
map.js
418 ms
google4.png
288 ms
overlay.js
286 ms
util.js
430 ms
onion.js
428 ms
search_impl.js
283 ms
StaticMapService.GetMapImage
409 ms
stats.js
83 ms
openhand_8_8.cur
64 ms
imer.gob.mx accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
imer.gob.mx best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
imer.gob.mx SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imer.gob.mx can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Imer.gob.mx main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
imer.gob.mx
Open Graph data is detected on the main page of IMER. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: