4.5 sec in total
1.3 sec
2.8 sec
438 ms
Welcome to storiadoc.com homepage info - get ready to check Storia Doc best content right away, or after learning these important things about storiadoc.com
Su StoriaDoc trovate i documentari prodotti da La Storia In Rete. Una grande scelta di argomenti per chi ha la passione della storia e dei suoi personaggi.
Visit storiadoc.comWe analyzed Storiadoc.com page load time and found that the first response time was 1.3 sec and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
storiadoc.com performance score
name
value
score
weighting
Value2.7 s
58/100
10%
Value8.5 s
1/100
25%
Value6.3 s
41/100
10%
Value310 ms
77/100
30%
Value0.185
66/100
15%
Value10.0 s
26/100
10%
1309 ms
198 ms
199 ms
515 ms
202 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 67% of them (63 requests) were addressed to the original Storiadoc.com, 22% (21 requests) were made to Static.xx.fbcdn.net and 2% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Storiadoc.com.
Page size can be reduced by 177.4 kB (18%)
1.0 MB
828.1 kB
In fact, the total size of Storiadoc.com main page is 1.0 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. 80% 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 818.6 kB which makes up the majority of the site volume.
Potential reduce by 59.0 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 59.0 kB or 80% of the original size.
Potential reduce by 107.4 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, Storia Doc needs image optimization as it can save up to 107.4 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 6.4 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. This website has mostly compressed JavaScripts.
Potential reduce by 4.5 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. Storiadoc.com needs all CSS files to be minified and compressed as it can save up to 4.5 kB or 21% of the original size.
Number of requests can be reduced by 41 (46%)
89
48
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Storia Doc. 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 10 to 1 for CSS and as a result speed up the page load time.
storiadoc.com
1309 ms
wp-emoji-release.min.js
198 ms
styles.css
199 ms
cookie-law-info-public.css
515 ms
cookie-law-info-gdpr.css
202 ms
pagenavi-css.css
201 ms
css
16 ms
style.css
297 ms
responsive.css
296 ms
jquery.js
406 ms
jquery-migrate.min.js
303 ms
cookie-law-info-public.js
393 ms
jwplayer.js
106 ms
modernizr.min.js
396 ms
jquery.plugins.min.js
404 ms
scripts.js
101 ms
imagesloaded.min.js
109 ms
masonry.min.js
110 ms
jquery.masonry.min.js
121 ms
jquery.fitvids.js
122 ms
theme.js
207 ms
comment-reply.min.js
214 ms
wp-embed.min.js
214 ms
fsb.js
222 ms
jquery.jcarousel.js
224 ms
addthis_widget.js
16 ms
red_white.png
18 ms
bg-pattern.png
119 ms
storiadoc-logo-5.png
141 ms
s.png
147 ms
bg-pattern-nav.png
146 ms
nav-sep.png
170 ms
bg-pattern-black.png
171 ms
loading-bert.gif
307 ms
Volto-tridimensionale-640x360.jpg
529 ms
icon-play-64.png
376 ms
Diari-Mussolini-640x360.jpg
533 ms
Molteni-Signora-di-Monza-ridotta.jpg
372 ms
galileo_-_4-640x360.jpg
373 ms
dante-640x360.jpg
1108 ms
Santa-Rita-de-Casiacapa.jpg
575 ms
caravaggio-la-vera-storia-640x360.jpg
577 ms
danae-Tiziano-640x360.jpg
763 ms
Volto-tridimensionale-160x90.jpg
723 ms
icon-play-24.png
631 ms
Diari-Mussolini-160x90.jpg
677 ms
Molteni-Signora-di-Monza-ridotta-160x90.jpg
678 ms
galileo_-_4-160x90.jpg
729 ms
dante-160x90.jpg
778 ms
Santa-Rita-de-Casiacapa-160x90.jpg
780 ms
caravaggio-la-vera-storia-160x90.jpg
820 ms
danae-Tiziano-160x90.jpg
828 ms
bg-grad.png
861 ms
section-shadow.png
978 ms
galileo-telescope1-320x180.png
982 ms
icon-play-32.png
921 ms
stats.png
925 ms
savonarola-320x180.jpg
944 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
17 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
28 ms
page.php
125 ms
submit.shutterstock.com
99 ms
primavera-dettaglio-320x180.jpg
1169 ms
Santa-Rita-de-Casiacapa-320x180.jpg
975 ms
celestino-V-320x180.jpg
1103 ms
Vespasiano-Gonzaga-320x180.jpg
1022 ms
come-funziona.png
970 ms
iaacfebe.gif
1099 ms
banner-dvd-mussolini-300x38.gif
1044 ms
s2.png
1043 ms
social.png
1156 ms
lAoLamSrylq.css
28 ms
8R6ZAHuGts7.css
25 ms
lvDq5oJaRpV.css
30 ms
nDOmhvCeUjd.js
35 ms
2o-XRyr-n9k.js
33 ms
8ZrPme2EwKH.js
26 ms
5IFVSw5iabs.js
32 ms
p55HfXW__mM.js
33 ms
oGNFfuRupM0.js
33 ms
Hg3bckQWXeS.js
69 ms
1g8n8BHlVpv.js
81 ms
kCgk__hWT3L.js
68 ms
O6ztBnt32yw.js
95 ms
4DjEjIssQLw.js
79 ms
bU_NPlOAs12.js
67 ms
u7L7xDrlXEl.js
104 ms
HzxD9aAXSyD.js
106 ms
369660974_693631122781464_59216866764875784_n.jpg
37 ms
301715227_446251400852772_6954248634574867783_n.jpg
31 ms
kCwDvxe1QsQ.js
10 ms
6MX5XQNo-F7.js
16 ms
J5o5gBJIZ-_.js
9 ms
UXtr_j2Fwe-.png
8 ms
storiadoc.com 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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.
storiadoc.com 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
Browser errors were logged to the console
storiadoc.com 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
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
EN
IT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Storiadoc.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Italian language. Our system also found out that Storiadoc.com 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.
storiadoc.com
Open Graph data is detected on the main page of Storia Doc. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: