4.3 sec in total
785 ms
3.4 sec
121 ms
Visit m.principal.com.mx now to see the best up-to-date M Principal content for Mexico and also check out these interesting facts you probably never knew about m.principal.com.mx
Visit m.principal.com.mxWe analyzed M.principal.com.mx page load time and found that the first response time was 785 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
m.principal.com.mx performance score
785 ms
212 ms
516 ms
536 ms
217 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original M.principal.com.mx, 8% (4 requests) were made to Chat.principal.com.mx and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Principal.com.mx.
Page size can be reduced by 962.5 kB (73%)
1.3 MB
356.0 kB
In fact, the total size of M.principal.com.mx main page is 1.3 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. 20% of websites need less resources to load. Javascripts take 717.7 kB which makes up the majority of the site volume.
Potential reduce by 111.2 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. This page needs HTML code to be minified as it can gain 53.1 kB, which is 43% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 111.2 kB or 90% of the original size.
Potential reduce by 10.6 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. Obviously, M Principal needs image optimization as it can save up to 10.6 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 484.7 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 484.7 kB or 68% of the original size.
Potential reduce by 356.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. M.principal.com.mx needs all CSS files to be minified and compressed as it can save up to 356.0 kB or 84% of the original size.
Number of requests can be reduced by 36 (73%)
49
13
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M Principal. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
handle404.html
785 ms
jquery-ui-1.10.3.custom.min.css
212 ms
screenbootstrap.css
516 ms
screen.css
536 ms
principalfg.css
217 ms
jquery-1.10.2.min.js
630 ms
bootstrap.min.js
434 ms
jquery.prettyPhoto.closebtnup.js
419 ms
holder.min.js
423 ms
sgshare-facebook.js
546 ms
jquery.validate-1.13.1.min.js
651 ms
sglogin.min.js
545 ms
hover-dropdown.min.js
618 ms
sg-menu-responsive.js
653 ms
equal-height-boxes.js
653 ms
btn-collapse-template-row.js
654 ms
outdatedbrowser.min.js
823 ms
theme.js
832 ms
responsive-overlay-header.js
742 ms
jquery-ui-1.10.3.Datepicker.js
957 ms
jquery.ui.datepicker-es.js
750 ms
icheck.js
854 ms
webform-confirmationemail.js
848 ms
tinymce.min.js
1180 ms
iniciar-template-hidden.js
931 ms
_analytics.js
938 ms
webtrends.load.js
955 ms
subfields.js
967 ms
analytics.js
23 ms
webtrends.min.js
213 ms
logo_principal_2.png_1254337366.png
217 ms
icono-custom-phone-22x22.png
217 ms
icono-custom-envelope-22x22.png
218 ms
icono-custom-location-22x22.png
219 ms
iconos_quejas-22x22.png
112 ms
UEAP-6.png
219 ms
captcha.jsp
345 ms
sdk.js
83 ms
collect
30 ms
fontawesome-webfont.woff
472 ms
ChatLink.ashx
537 ms
Scroll.gif
346 ms
146 ms
xd_arbiter.php
87 ms
xd_arbiter.php
144 ms
wtid.js
117 ms
dcs.gif
112 ms
print.css
321 ms
ChatLink.ashx
105 ms
CHAT_a_100.jpg
504 ms
CHAT_c_100.jpg
499 ms
m.principal.com.mx SEO score
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise M.principal.com.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 M.principal.com.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.
m.principal.com.mx
Open Graph description is not detected on the main page of M Principal. 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: