16.7 sec in total
5.2 sec
11 sec
435 ms
Visit dpz.es now to see the best up-to-date Dpz content for Spain and also check out these interesting facts you probably never knew about dpz.es
Página oficial de la Diputación Provincial de Zaragoza.
Visit dpz.esWe analyzed Dpz.es page load time and found that the first response time was 5.2 sec and then it took 11.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
dpz.es performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value8.5 s
2/100
25%
Value11.6 s
4/100
10%
Value90 ms
99/100
30%
Value0.002
100/100
15%
Value7.3 s
50/100
10%
5240 ms
2566 ms
134 ms
379 ms
250 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 90% of them (84 requests) were addressed to the original Dpz.es, 5% (5 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain Dpz.es.
Page size can be reduced by 157.5 kB (13%)
1.2 MB
1.1 MB
In fact, the total size of Dpz.es main page is 1.2 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. 40% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 46.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 17.6 kB, which is 32% 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 46.6 kB or 86% of the original size.
Potential reduce by 11.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. Dpz images are well optimized though.
Potential reduce by 98.8 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 98.8 kB or 66% of the original size.
Potential reduce by 907 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. Dpz.es needs all CSS files to be minified and compressed as it can save up to 907 B or 71% of the original size.
Number of requests can be reduced by 43 (50%)
86
43
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dpz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
dpz.es
5240 ms
www.dpz.es
2566 ms
reset.css
134 ms
base.css
379 ms
public.css
250 ms
collective.js.jqueryui.custom.min.css
389 ms
columns.css
272 ms
authoring.css
256 ms
portlets.css
263 ms
controlpanel.css
384 ms
forms.css
504 ms
discussion.css
507 ms
tinymce.css
506 ms
++resource++collective.js.colorpicker.css
508 ms
TTGoogleMapStyle.css
530 ms
easynewsletter.css
533 ms
jquery.autocomplete.css
624 ms
contenttree.css
623 ms
++resource++plone.app.jquerytools.dateinput.css
621 ms
fullcalendar.css
624 ms
solgema_contextualcontentmenu.css
662 ms
popoll.css
664 ms
style.css
740 ms
normalize.css
740 ms
swipebox.min.css
742 ms
jquery.bxslider.css
742 ms
foundation.min.css
1255 ms
main.css
1038 ms
ploneCustom.css
870 ms
resourceplone.app.jquery-cachekey-f3fbf24d109198a7a71eb0b262817b2f.js
1339 ms
collective.js.jqueryui.custom.min-cachekey-c974bcc583a1f2be747bfb7f8c1ce4a1.js
1477 ms
resourcecollective.js.colorpicker.jseye-cachekey-61c8c7792488b1b980ce864c790d4b3d.js
979 ms
resourceplone.formwidget.autocompletejquery.autocomplete.min-cachekey-66b83550e9ae83ac7d2bfd8972f85760.js
1378 ms
jquery.autocomplete.js
1221 ms
css
24 ms
resourceplonetheme.dpz.javascriptscustom-dpz-cachekey-22895a10eecdb7913e4fd4860dfbc56e.js
1160 ms
foundation.min.js
1421 ms
responsiveslides.min.js
1139 ms
analytics.js
112 ms
bg.png
135 ms
fb.png
120 ms
tw.png
123 ms
lupa.png
124 ms
logo.png
135 ms
image
485 ms
izq.png
248 ms
der.png
246 ms
rss.png
248 ms
image_large
397 ms
image_large
509 ms
image_large
385 ms
image_large
503 ms
mas.png
365 ms
image_preview
622 ms
image_preview
521 ms
image_preview
535 ms
image_preview
615 ms
image_preview
635 ms
image_preview
641 ms
image_preview
652 ms
image_preview
674 ms
04a5247b-bf0f-468f-9dba-5f258e08e7ad.png
747 ms
8fbb0416-c836-45b7-9556-206458b8b6ab.png
757 ms
dfc9e910-d6c6-4631-a456-01ad3f98f561.png
771 ms
e5f3c26b-6b18-4cb5-a005-02fe5ce7a215.png
769 ms
2038e845-0fc9-494e-9e9e-8384d9d4b586.png
779 ms
image
805 ms
image
874 ms
image
883 ms
image
895 ms
image
896 ms
image
903 ms
image
937 ms
image
1000 ms
update.js
20 ms
image
1040 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
35 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
63 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
64 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
64 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
64 ms
collect
14 ms
image
912 ms
image
906 ms
image
916 ms
image
941 ms
image
971 ms
image
913 ms
logotrans.png
908 ms
spinner.gif
914 ms
image
968 ms
print.css
135 ms
fullcalendar.print.css
127 ms
dpz.es 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
Links do not have a discernible name
dpz.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
dpz.es SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dpz.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it does not match the claimed English language. Our system also found out that Dpz.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.
dpz.es
Open Graph description is not detected on the main page of Dpz. 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: