4.8 sec in total
1.1 sec
3.4 sec
268 ms
Click here to check amazing Getafe content for Spain. Otherwise, check out these important facts you probably never knew about getafe.es
Sitio oficial del Ayuntamiento de Getafe. Sede electrónica, noticias, agenda, canal de vídeos, gestión electrónica de incidencias, planes de gobierno y mucho más...
Visit getafe.esWe analyzed Getafe.es page load time and found that the first response time was 1.1 sec and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
getafe.es performance score
name
value
score
weighting
Value9.3 s
0/100
10%
Value11.5 s
0/100
25%
Value14.3 s
2/100
10%
Value60 ms
100/100
30%
Value0.127
83/100
15%
Value12.6 s
14/100
10%
1102 ms
180 ms
168 ms
175 ms
171 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 88% of them (94 requests) were addressed to the original Getafe.es, 3% (3 requests) were made to Getafe--es.accesible.inclusite.com and 3% (3 requests) were made to Accesible.inclusite.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Getafe.es.
Page size can be reduced by 855.4 kB (37%)
2.3 MB
1.5 MB
In fact, the total size of Getafe.es main page is 2.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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 63.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. This page needs HTML code to be minified as it can gain 17.1 kB, which is 22% 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 63.5 kB or 83% of the original size.
Potential reduce by 139.2 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. Getafe images are well optimized though.
Potential reduce by 398.6 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 398.6 kB or 67% of the original size.
Potential reduce by 254.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. Getafe.es needs all CSS files to be minified and compressed as it can save up to 254.1 kB or 78% of the original size.
Number of requests can be reduced by 48 (46%)
104
56
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Getafe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
getafe.es
1102 ms
bootstrap.min.css
180 ms
font-awesome.min.css
168 ms
style.css
175 ms
custom_styles.css
171 ms
jquery.min.js
72 ms
bootstrap.min.js
172 ms
ultimahora.js
177 ms
jScrollPane.js
252 ms
mousewheel.js
252 ms
menu.js
252 ms
jquery.min.js
44 ms
dashicons.min.css
338 ms
wunderground.css
276 ms
flick.css
276 ms
getafe.es
474 ms
estilos.css
332 ms
styles.css
334 ms
jquery.fancybox.css
343 ms
postratings-css.css
349 ms
pagenavi-css.css
414 ms
shortcodes.css
418 ms
shortcodes_responsive.css
423 ms
addtoany.min.css
427 ms
9a43c5d9133ec61553f2117752874a29.css
434 ms
jquery.js
583 ms
jquery-migrate.min.js
502 ms
core.min.js
504 ms
widget.min.js
511 ms
position.min.js
520 ms
menu.min.js
553 ms
autocomplete.min.js
604 ms
widget.min.js
610 ms
scrollTo.js
609 ms
jquery.form.min.js
610 ms
mailchimp.js
634 ms
datepicker.js
671 ms
principal.js
668 ms
jquery.fancybox.js
675 ms
jquery.easing.js
523 ms
jquery.riva.slider.pro.js
559 ms
scripts.js
561 ms
postratings-js.js
600 ms
wp-embed.min.js
601 ms
wp-emoji-release.min.js
534 ms
ga.js
39 ms
body-bg.png
506 ms
icon_search.png
506 ms
ico-facebook.png
508 ms
ico-twitter.png
509 ms
ico-google.png
509 ms
ico-flickr.png
510 ms
ico-issuu.png
512 ms
logo.jpg
516 ms
bg-topmenu.png
512 ms
bg-cabecera-ultimahora.png
514 ms
logo-xs.png
512 ms
timthumb.php
518 ms
timthumb.php
544 ms
timthumb.php
543 ms
timthumb.php
516 ms
timthumb.php
644 ms
timthumb.php
543 ms
timthumb.php
558 ms
timthumb.php
569 ms
timthumb.php
680 ms
timthumb.php
685 ms
timthumb.php
694 ms
timthumb.php
724 ms
timthumb.php
654 ms
ayto_2_150.jpg
730 ms
getafe-ayuntamiento-20150310-010.jpg
739 ms
20151017_mercado_ayto002.jpg
765 ms
banner-farmacias.png
766 ms
banner-newsletter.png
779 ms
banner-directoriomunicipal.png
804 ms
banner-boletindigital.png
789 ms
boton-sede-electronica-es.png
811 ms
fontawesome-webfont.woff
911 ms
page.js
28 ms
__utm.gif
432 ms
piwik.js
445 ms
frameworks_initializer.js
745 ms
boton2.png
750 ms
boton3.png
766 ms
collect
58 ms
boton-seguimiento-incidencias.png
391 ms
footer-logo-ayuntamientogetafe.png
396 ms
footer-logo-peq-1.png
408 ms
footer-logo-peq-2.png
433 ms
footer-logo-peq-3.png
452 ms
footer-logo-peq-4.png
468 ms
circle_default.gif
474 ms
pause.png
487 ms
next.png
510 ms
prev.png
513 ms
timthumb.php
533 ms
bg-areasdegobierno-titular.png
543 ms
bg-areasdegobierno-social.png
549 ms
bg-areasdegobierno-economia.png
561 ms
bg-areasdegobierno-urbanismo.png
560 ms
rating_over.gif
569 ms
logo_inclusite.png
74 ms
inclusite_multisite_config_iframe.html
172 ms
pestania.png
86 ms
frameworks_libraries.js
241 ms
texts.js
207 ms
getafe.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.
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
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.
getafe.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Registers an unload listener
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
getafe.es SEO score
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 doesn't use 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 Getafe.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 Getafe.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.
getafe.es
Open Graph description is not detected on the main page of Getafe. 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: