4.3 sec in total
275 ms
3.7 sec
358 ms
Click here to check amazing Insp content for Mexico. Otherwise, check out these important facts you probably never knew about insp.mx
Portal del Instituto Nacional de Salud Pública
Visit insp.mxWe analyzed Insp.mx page load time and found that the first response time was 275 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
insp.mx performance score
name
value
score
weighting
Value18.5 s
0/100
10%
Value26.5 s
0/100
25%
Value20.8 s
0/100
10%
Value530 ms
56/100
30%
Value0.089
92/100
15%
Value34.6 s
0/100
10%
275 ms
1439 ms
42 ms
657 ms
377 ms
Our browser made a total of 27 requests to load all elements on the main page. We found that 37% of them (10 requests) were addressed to the original Insp.mx, 30% (8 requests) were made to Fonts.gstatic.com and 11% (3 requests) were made to Framework-gb.cdn.gob.mx. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Insp.mx.
Page size can be reduced by 2.8 MB (57%)
4.9 MB
2.1 MB
In fact, the total size of Insp.mx main page is 4.9 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. 60% of websites need less resources to load. Javascripts take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 276.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 276.1 kB or 83% of the original size.
Potential reduce by 124.1 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. Insp images are well optimized though.
Potential reduce by 2.2 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 2.2 MB or 72% of the original size.
Potential reduce by 209.1 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. Insp.mx needs all CSS files to be minified and compressed as it can save up to 209.1 kB or 97% of the original size.
Number of requests can be reduced by 11 (65%)
17
6
The browser has sent 17 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Insp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
insp.mx
275 ms
www.insp.mx
1439 ms
css2
42 ms
app.css
657 ms
insp-icons.css
377 ms
jquery.fancybox.min.css
42 ms
gobmx-accesibilidad.min.css
43 ms
font-awesome.min.css
34 ms
a23eb34ca6.js
84 ms
jquery-3.6.0.min.js
25 ms
manifest.js
278 ms
vendor.js
1050 ms
app.js
765 ms
js
56 ms
gobmx-accesibilidad.min.js
15 ms
logoheader.svg
92 ms
insp.png
116 ms
logo_salud.png
199 ms
contact_information.png
1140 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZg.ttf
37 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fMZg.ttf
49 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfMZg.ttf
65 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYMZg.ttf
72 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYMZg.ttf
70 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhLsWUBw.ttf
64 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhHMWUBw.ttf
63 ms
jizOREVItHgc8qDIbSTKq4XkRg8T88bjFuXOnduhcMWUBw.ttf
70 ms
insp.mx accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
insp.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
Missing source maps for large first-party JavaScript
insp.mx SEO score
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 Insp.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 Insp.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.
insp.mx
Open Graph description is not detected on the main page of Insp. 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: