2.3 sec in total
115 ms
1.8 sec
388 ms
Click here to check amazing Fmm content for Mexico. Otherwise, check out these important facts you probably never knew about fmm.org.mx
Federación Mexicana de Motociclismo
Visit fmm.org.mxWe analyzed Fmm.org.mx page load time and found that the first response time was 115 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
fmm.org.mx performance score
name
value
score
weighting
Value3.5 s
33/100
10%
Value8.9 s
1/100
25%
Value5.6 s
52/100
10%
Value160 ms
93/100
30%
Value0.053
98/100
15%
Value8.7 s
36/100
10%
115 ms
71 ms
528 ms
93 ms
116 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 75% of them (53 requests) were addressed to the original Fmm.org.mx, 11% (8 requests) were made to I3.ytimg.com and 3% (2 requests) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (712 ms) belongs to the original domain Fmm.org.mx.
Page size can be reduced by 831.8 kB (32%)
2.6 MB
1.8 MB
In fact, the total size of Fmm.org.mx main page is 2.6 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. 45% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 47.1 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 47.1 kB or 83% of the original size.
Potential reduce by 97.8 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. Fmm images are well optimized though.
Potential reduce by 467.8 kB
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 467.8 kB or 69% of the original size.
Potential reduce by 219.0 kB
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. Fmm.org.mx needs all CSS files to be minified and compressed as it can save up to 219.0 kB or 83% of the original size.
Number of requests can be reduced by 27 (45%)
60
33
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fmm. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
fmm.org.mx
115 ms
new
71 ms
528 ms
jquery.min.js
93 ms
jquery-ui.min.js
116 ms
style.css
72 ms
style.css
74 ms
mootools-core.js
247 ms
core.js
80 ms
caption.js
80 ms
mootools-more.js
384 ms
contentslider.js
110 ms
jquery1.5-sot.min.js
317 ms
jquery.easing.1.3.js
146 ms
jquery.mousewheel.min.js
144 ms
jquery.mCustomScrollbar.js
210 ms
440 ms
joomla.css
215 ms
template_css.css
281 ms
layout.css
290 ms
scroll_to_top.css
311 ms
menu_accordion.css
353 ms
jquery.hjt.accmenu.js
360 ms
menu_drop_down.css
439 ms
jquery.hjt.nav.js
440 ms
tinynav.min.js
441 ms
responsive_menu.js
440 ms
scroll_to_top.js
418 ms
da0TabnLdVE
156 ms
default.jpg
137 ms
banner_fmm_new.jpg
368 ms
016_velocidad_amozoc_posterm.jpg
661 ms
016_mx_mazatlan_poster-conv.png
367 ms
banner_afiliados014-2.jpg
134 ms
b_90_90_16185078_94_016_fim_la_competition.jpg
139 ms
016_fim_la_competition.jpg
278 ms
top_right2.png
164 ms
top_left2.png
166 ms
top2.png
274 ms
left2.png
275 ms
right2.png
300 ms
016_gpleonb_50_30.png
313 ms
bottom_right2.png
364 ms
bottom_left2.png
377 ms
bottom_center2.png
405 ms
016_velocidad_amozoc_50_30.jpg
409 ms
0_logo_cnv_para_nota_50_30.jpg
407 ms
9_nalmx_almanza_50_30.png
412 ms
logo_cnmx-sx_m_50_30.jpg
445 ms
mcs_btnUp.png
470 ms
mcs_btnDown.png
474 ms
foto_pantalla_sitio_011m.jpg
650 ms
banner_wada.jpg
518 ms
logo_elcierre012m-2.png
584 ms
015_banner_calendario.png
712 ms
015_banner_calendario_sx-mx.png
706 ms
default.jpg
46 ms
default.jpg
45 ms
default.jpg
46 ms
default.jpg
55 ms
default.jpg
47 ms
default.jpg
120 ms
default.jpg
121 ms
1J3ZBWI
79 ms
top.png
468 ms
www-embed-player-vflfNyN_r.css
42 ms
www-embed-player.js
66 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
59 ms
ad_status.js
104 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
96 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
98 ms
fmm.org.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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
fmm.org.mx best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
fmm.org.mx SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Fmm.org.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 Fmm.org.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.
fmm.org.mx
Open Graph description is not detected on the main page of Fmm. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: