20.6 sec in total
8.7 sec
11.6 sec
248 ms
Welcome to datos.gob.es homepage info - get ready to check Datos best content for Spain right away, or after learning these important things about datos.gob.es
Datos abiertos del Gobierno de España para la apertura de la información pública y desarrollo de servicios avanzados basados en datos. Es promovida por el Ministerio de Asuntos Económicos y Transforma...
Visit datos.gob.esWe analyzed Datos.gob.es page load time and found that the first response time was 8.7 sec and then it took 11.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
datos.gob.es performance score
name
value
score
weighting
Value6.0 s
3/100
10%
Value14.4 s
0/100
25%
Value9.5 s
11/100
10%
Value800 ms
36/100
30%
Value0.184
66/100
15%
Value13.3 s
12/100
10%
8675 ms
38 ms
205 ms
304 ms
203 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 77% of them (106 requests) were addressed to the original Datos.gob.es, 3% (4 requests) were made to Static.licdn.com and 3% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (8.7 sec) belongs to the original domain Datos.gob.es.
Page size can be reduced by 727.9 kB (54%)
1.4 MB
627.7 kB
In fact, the total size of Datos.gob.es main page is 1.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. 60% of websites need less resources to load. Images take 472.9 kB which makes up the majority of the site volume.
Potential reduce by 44.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 44.4 kB or 77% of the original size.
Potential reduce by 66.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. Obviously, Datos needs image optimization as it can save up to 66.1 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 304.3 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 304.3 kB or 66% of the original size.
Potential reduce by 313.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. Datos.gob.es needs all CSS files to be minified and compressed as it can save up to 313.1 kB or 86% of the original size.
Number of requests can be reduced by 89 (70%)
128
39
The browser has sent 128 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 17 to 1 for JavaScripts and from 47 to 1 for CSS and as a result speed up the page load time.
datos.gob.es
8675 ms
css
38 ms
jMyCarousel.css
205 ms
system.base.css
304 ms
system.menus.css
203 ms
system.messages.css
221 ms
system.theme.css
328 ms
jquery.ui.core.css
301 ms
jquery.ui.theme.css
432 ms
jquery.ui.autocomplete.css
302 ms
simplenews.css
329 ms
comment.css
408 ms
date.css
409 ms
datepicker.1.7.css
411 ms
field.css
437 ms
logintoboggan.css
438 ms
node.css
507 ms
search.css
540 ms
user.css
509 ms
views.css
550 ms
ckeditor.css
542 ms
ctools.css
545 ms
eu_cookie_compliance.css
596 ms
panels.css
594 ms
rate.css
620 ms
classic.css
639 ms
video.css
641 ms
style.css
882 ms
html-reset.css
690 ms
wireframes.css
688 ms
layout-fixed.css
721 ms
page-backgrounds.css
749 ms
tabs.css
749 ms
pages.css
794 ms
blocks.css
795 ms
navigation.css
830 ms
views-styles.css
861 ms
jquery.min.js
29 ms
in.js
10 ms
nodes.css
690 ms
comments.css
725 ms
forms.css
723 ms
fields.css
739 ms
styles.css
1358 ms
print.css
700 ms
chosen.css
730 ms
js_xAPl0qIk9eowy_iS9tNkCWXLUVoat94SQT48UBCFkyQ.js
901 ms
js_fDyuIEGrEBqCopqPxfNZo3fOcNiTp5Sr0AKIgjl2qcw.js
700 ms
js_uF4vZIO1-52Jf2ElKIehO8h5ykFaP9bgQPmZY03Dd5Y.js
660 ms
js_yCwTCFbqiELTXW4WD8z_XOw386DLUxubUwJYvtkAPpQ.js
703 ms
js_MQtAJ7ZhvhgkuAoDzQgp4JH7I4IpQ0SlJY0mpx6fXgY.js
724 ms
chosen.js
855 ms
zice.custom.js
733 ms
jquery.tweet.js
900 ms
jMyCarousel.js
836 ms
datosgob.min.js
764 ms
domtab.js
791 ms
js_Dpwj9_jdZx11LB9vWakYPT-NglBvlNPbjDg8kKHykyQ.js
830 ms
piwik.js
453 ms
secureAnonymousFramework
82 ms
page_gl.png
321 ms
sheet_b.png
132 ms
sheet_t.png
130 ms
sheet.png
129 ms
header.jpg
148 ms
logo.png
146 ms
minicon_twitter.png
301 ms
minicon_linkedin.png
301 ms
slideshare2.png
344 ms
Flickr.png
609 ms
youtube_dg.png
506 ms
llave.PNG
342 ms
aportav2.jpg
650 ms
catalogov2.jpg
508 ms
iodcv4.jpg
869 ms
bannerv2.jpg
866 ms
young_europeans_0.jpg
633 ms
mobility4all.png
645 ms
tendencias_europeas.png
716 ms
european_data_portal.png
748 ms
opendata_charter.png
805 ms
bde.png
757 ms
banner-pie-1.jpg
839 ms
banner-pie-2.jpg
971 ms
banner-pie-3.jpg
944 ms
banner-pie-5.jpg
875 ms
LOGO_APORA_NEW_v02.jpg
1051 ms
bg_input.png
936 ms
search.png
942 ms
bg_menu.jpg
970 ms
menuicon_1-hover.png
1025 ms
menuicon_2.png
1043 ms
menu_sep.png
1045 ms
menuicon_3.png
1059 ms
menuicon_4.png
1086 ms
menuicon_5.png
1126 ms
widgets.js
153 ms
XreLooTt3EU7pik51LvgPw.ttf
32 ms
menuicon_6.png
1048 ms
menuicon_7.png
1053 ms
ga.js
92 ms
icon-breadcrumb.gif
1042 ms
seppath.png
1057 ms
all.js
232 ms
bullet.png
1014 ms
xdrpc.html
83 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
164 ms
__utm.gif
33 ms
bg_menu-ver-mas.jpg
966 ms
bigicon_twitter.png
975 ms
bigicon_linkedin.png
968 ms
profile
114 ms
bg_news.png
942 ms
mail.png
988 ms
css
83 ms
anonymoususerspace
51 ms
js
90 ms
css
88 ms
js
80 ms
150 ms
syndication
154 ms
552739293220069377
228 ms
piwik.php
290 ms
xd_arbiter.php
164 ms
xd_arbiter.php
332 ms
bg_menu-newsletter.jpg
849 ms
rssicon.png
862 ms
134ac07.png
83 ms
bg_footer.jpg
778 ms
line_footer.png
769 ms
ui-bg_flat_75_ffffff_40x100.png
756 ms
25b6.png
22 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
33 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
102 ms
1eyki5331eknvf679qmq_normal.jpeg
69 ms
jot
35 ms
ping
41 ms
datos.gob.es accessibility score
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
datos.gob.es 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
datos.gob.es 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 Datos.gob.es 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 Datos.gob.es 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.
datos.gob.es
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: