690 ms in total
33 ms
585 ms
72 ms
Click here to check amazing Datos content for Mexico. Otherwise, check out these important facts you probably never knew about datos.gob.mx
Visualiza las base de datos abiertas del Gobierno de México
Visit datos.gob.mxWe analyzed Datos.gob.mx page load time and found that the first response time was 33 ms and then it took 657 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
datos.gob.mx performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value10.1 s
0/100
25%
Value30.3 s
0/100
10%
Value1,200 ms
20/100
30%
Value0.166
71/100
15%
Value12.6 s
14/100
10%
33 ms
135 ms
21 ms
124 ms
12 ms
Our browser made a total of 15 requests to load all elements on the main page. We found that 40% of them (6 requests) were addressed to the original Datos.gob.mx, 33% (5 requests) were made to Cdn.datos.gob.mx and 7% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (307 ms) belongs to the original domain Datos.gob.mx.
Page size can be reduced by 132.2 kB (32%)
418.5 kB
286.3 kB
In fact, the total size of Datos.gob.mx main page is 418.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 381.1 kB which makes up the majority of the site volume.
Potential reduce by 3.5 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 3.5 kB or 55% of the original size.
Potential reduce by 128.5 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 128.5 kB or 34% of the original size.
Potential reduce by 115 B
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. Datos.gob.mx has all CSS files already compressed.
Number of requests can be reduced by 9 (64%)
14
5
The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Datos. 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 4 to 1 for CSS and as a result speed up the page load time.
datos.gob.mx
33 ms
main.css
135 ms
sec-style.css
21 ms
webcomponents-lite.min.js
124 ms
vendor.css
12 ms
d052ee8
25 ms
vendor.js
307 ms
jquery-ui-datepicker.min.js
189 ms
require.js
214 ms
css
32 ms
analytics.js
26 ms
EYBK8-KMMQ2-JTWM7-W2TTL-89Y2Y
59 ms
config.json
113 ms
dgm-navbar.html
36 ms
dgm-footer.html
16 ms
datos.gob.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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
datos.gob.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
datos.gob.mx SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
![]()
N/A
![]()
N/A
UTF8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Datos.gob.mx can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Datos.gob.mx main page’s claimed encoding is utf8. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
datos.gob.mx
Open Graph description is not detected on the main page of Datos. 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: