7 sec in total
352 ms
6.2 sec
444 ms
Click here to check amazing Zaragoza content. Otherwise, check out these important facts you probably never knew about zaragoza.mobi
La Sede Electrónica del Ayuntamiento de Zaragoza, creada por el Ayuntamiento de la ciudad en 1994 es una vía de comunicación con los ciudadanos, donde se puede obtener información integral, actualiza
Visit zaragoza.mobiWe analyzed Zaragoza.mobi page load time and found that the first response time was 352 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
zaragoza.mobi performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value10.6 s
0/100
25%
Value18.1 s
0/100
10%
Value7,070 ms
0/100
30%
Value0.017
100/100
15%
Value38.4 s
0/100
10%
352 ms
555 ms
238 ms
31 ms
32 ms
Our browser made a total of 240 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Zaragoza.mobi, 43% (102 requests) were made to Zaragoza.es and 26% (63 requests) were made to Idezar.zaragoza.es. The less responsive or slowest element that took the longest time to load (937 ms) relates to the external source Zaragoza.es.
Page size can be reduced by 921.5 kB (15%)
6.3 MB
5.4 MB
In fact, the total size of Zaragoza.mobi main page is 6.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.3 MB which makes up the majority of the site volume.
Potential reduce by 101.6 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 32.9 kB, which is 28% 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 101.6 kB or 87% of the original size.
Potential reduce by 469.0 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. Zaragoza images are well optimized though.
Potential reduce by 260.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 260.3 kB or 39% of the original size.
Potential reduce by 90.6 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. Zaragoza.mobi needs all CSS files to be minified and compressed as it can save up to 90.6 kB or 43% of the original size.
Number of requests can be reduced by 119 (61%)
195
76
The browser has sent 195 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zaragoza. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 89 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
zaragoza.mobi
352 ms
www.zaragoza.es
555 ms
238 ms
ReadSpeaker.Styles-Button.css
31 ms
webReader.js
32 ms
main-sede.min.css
339 ms
main-sede-pendientes.css
325 ms
all.min.css
143 ms
main-sede.min.css
533 ms
main.mt.min.css
562 ms
homeMapa.js
454 ms
jquery-1.11.3.min.js
499 ms
bootstrap.js
498 ms
main-sede.js
350 ms
smooth-scroll.js
498 ms
debounce.js
551 ms
collapse-to-tab.js
558 ms
logo_escudo.png
140 ms
lse.jpg
152 ms
WhatsApp%20Image%202022-09-14%20at%202.51.21%20PM.jpeg
345 ms
plenoayuntamiento2.jpg
272 ms
volveremos.jpg
139 ms
web-Atencion_Telefonica-ZGZ-320x480.jpg
366 ms
cartel-a3_creactivamiz.jpg
452 ms
Cartel_PACCZ.png
342 ms
flyer-ayudas-concertada-22-23.png
685 ms
Destacado-AGENDAURBANA.jpg
442 ms
cartel-cheque-familia.jpg
439 ms
8dc65b29_fb38_4eaa_a099_0caf40810883.jpeg
447 ms
blues.png
691 ms
foto_3.jpg
554 ms
whatsapp_image_2022_09_29_at_7.43.39_pm1.jpeg
656 ms
11.png
565 ms
icono_polen.png
565 ms
icono_aire.png
671 ms
icono_facebook.png
685 ms
icono_twitter.png
684 ms
icono_youtube.png
761 ms
icono_flickr.png
778 ms
icono_blog.png
787 ms
icono_accesibilidad.png
783 ms
agenda2.png
788 ms
empleo2.png
789 ms
Licitacion2.png
873 ms
Equipamientos2
888 ms
tablonEdictos2.png
891 ms
turismo2
898 ms
logo.png
906 ms
datos_abiertos.png
853 ms
callejero.png
922 ms
transparencia.png
937 ms
cita3.png
937 ms
index.html
914 ms
quejas_sugerencias2.png
895 ms
fa-solid-900.woff
50 ms
fa-regular-400.woff
70 ms
analytics.js
119 ms
collect
30 ms
bootstrap.min.css
94 ms
container.css
125 ms
jquery-3.3.1.slim.min.js
107 ms
popper.min.js
62 ms
bootstrap.min.js
110 ms
GeorefServlet.js
193 ms
engine.js
194 ms
GUI.js
192 ms
all.css
288 ms
container-facade.js
186 ms
messages-fallback.js
186 ms
container-facade-fallback.js
257 ms
container-gui.js
251 ms
container-gui-fallback.js
247 ms
TuCiudad.png
152 ms
bus.png
149 ms
tranvia_2.png
150 ms
bus_rural.png
176 ms
icono_localizacion_dispositivo.png
184 ms
address_bar.png
189 ms
viewer.html
180 ms
estilosmapa.css
120 ms
css
66 ms
genericProperties.js
120 ms
OpenLayers.js
170 ms
localFacade.js
136 ms
IDEZarOL.js
119 ms
web_style.css
116 ms
messagesProperties_ES.js
117 ms
esteticaGeneralProperties.js
113 ms
toolButtonProperties.js
367 ms
mapProperties.js
370 ms
wmsProperties.js
370 ms
esteticaProperties.js
371 ms
legendProperties.js
371 ms
vectorialLayerProperties.js
372 ms
ajax-loader_128.gif
496 ms
zoomInCentered.png
489 ms
zoomOutCentered.png
488 ms
style.css
467 ms
GeorefServlet.js
199 ms
dojo.xd.js
195 ms
tree_config.css
183 ms
tree_functions.js
183 ms
tree_config.js
181 ms
ajax-loader.gif
153 ms
botonArbolCapas.png
151 ms
WMSTileCache
567 ms
WMSTileCache
597 ms
WMSTileCache
595 ms
WMSTileCache
597 ms
WMSTileCache
598 ms
WMSTileCache
589 ms
WMSTileCache
646 ms
WMSTileCache
663 ms
WMSTileCache
664 ms
WMSTileCache
666 ms
WMSTileCache
667 ms
WMSTileCache
670 ms
WMSTileCache
726 ms
WMSTileCache
739 ms
WMSTileCache
738 ms
WMSTileCache
744 ms
WMSTileCache
745 ms
WMSTileCache
749 ms
WMSTileCache
804 ms
WMSTileCache
814 ms
WMSTileCache
814 ms
WMSTileCache
821 ms
WMSTileCache
823 ms
AccordionContainer.xd.js
111 ms
ContentPane.xd.js
117 ms
ItemFileReadStore.xd.js
121 ms
Tree.xd.js
116 ms
_Container.xd.js
15 ms
_Templated.xd.js
17 ms
_CssStateMixin.xd.js
73 ms
StackContainer.xd.js
75 ms
AccordionPane.xd.js
74 ms
_Widget.xd.js
118 ms
_ContentPaneResizeMixin.xd.js
120 ms
string.xd.js
120 ms
html.xd.js
116 ms
loading.xd.js
123 ms
fx.xd.js
119 ms
DeferredList.xd.js
121 ms
_Contained.xd.js
121 ms
cookie.xd.js
122 ms
TreeStoreModel.xd.js
268 ms
ForestStoreModel.xd.js
268 ms
_dndSelector.xd.js
379 ms
filter.xd.js
132 ms
simpleFetch.xd.js
346 ms
stamp.xd.js
133 ms
parser.xd.js
130 ms
cache.xd.js
229 ms
_LayoutWidget.xd.js
222 ms
common.xd.js
224 ms
StackController.xd.js
221 ms
_WidgetBase.xd.js
132 ms
_base.xd.js
135 ms
Toggler.xd.js
127 ms
regexp.xd.js
113 ms
blank.gif
240 ms
WMSTileCache
381 ms
WMSTileCache
438 ms
WMSTileCache
443 ms
WMSTileCache
442 ms
WMSTileCache
453 ms
WMSTileCache
455 ms
WMSTileCache
460 ms
WMSTileCache
517 ms
ToggleButton.xd.js
27 ms
manager.xd.js
414 ms
Stateful.xd.js
24 ms
focus.xd.js
26 ms
place.xd.js
27 ms
popup.xd.js
95 ms
scroll.xd.js
29 ms
sniff.xd.js
64 ms
typematic.xd.js
29 ms
wai.xd.js
42 ms
window.xd.js
57 ms
wms
629 ms
Button.xd.js
36 ms
window.xd.js
357 ms
AdapterRegistry.xd.js
40 ms
_FormWidget.xd.js
75 ms
_HasDropDown.xd.js
20 ms
uacss.xd.js
19 ms
wms
568 ms
sorter.xd.js
24 ms
wms
557 ms
wms
480 ms
wms
569 ms
wms
627 ms
wms
639 ms
common.xd.js
13 ms
_dndContainer.xd.js
142 ms
wms
648 ms
wms
555 ms
wms
641 ms
wms
663 ms
wms
709 ms
wms
721 ms
wms
674 ms
wms
635 ms
wms
647 ms
wms
669 ms
wms
712 ms
Container.xd.js
111 ms
wms
705 ms
wms
662 ms
wms
662 ms
wms
665 ms
wms
675 ms
wms
710 ms
wms
710 ms
wms
662 ms
wms
670 ms
wms
672 ms
wms
761 ms
wms
716 ms
wms
710 ms
wms
663 ms
blank.gif
83 ms
tree_corner_up.gif
117 ms
tree_corner_down.gif
114 ms
load.gif
110 ms
accordion.png
114 ms
on.png
114 ms
commonHighlight.png
112 ms
afecciones.png
152 ms
expand.png
221 ms
off.png
222 ms
botonArbolCapas.png
222 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
17 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
21 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
25 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
30 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
31 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
33 ms
zaragoza.mobi 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.
zaragoza.mobi best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
zaragoza.mobi 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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zaragoza.mobi 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 Zaragoza.mobi 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.
zaragoza.mobi
Open Graph description is not detected on the main page of Zaragoza. 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: