5.9 sec in total
1.5 sec
3.8 sec
586 ms
Visit datastori.es now to see the best up-to-date Data Stori content for United States and also check out these interesting facts you probably never knew about datastori.es
Latest episodes Show full episode archive News Show more news Classics Show full episode archive
Visit datastori.esWe analyzed Datastori.es page load time and found that the first response time was 1.5 sec and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
datastori.es performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value19.9 s
0/100
25%
Value11.7 s
4/100
10%
Value150 ms
95/100
30%
Value0.192
64/100
15%
Value13.1 s
12/100
10%
1456 ms
302 ms
209 ms
207 ms
211 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 69% of them (45 requests) were addressed to the original Datastori.es, 8% (5 requests) were made to Cdn.podlove.org and 5% (3 requests) were made to S.gravatar.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Datastori.es.
Page size can be reduced by 1.1 MB (29%)
4.0 MB
2.8 MB
In fact, the total size of Datastori.es main page is 4.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. 60% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 41.2 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 9.4 kB, which is 19% 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 41.2 kB or 83% of the original size.
Potential reduce by 523.5 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, Data Stori needs image optimization as it can save up to 523.5 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 320.9 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 320.9 kB or 67% of the original size.
Potential reduce by 258.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. Datastori.es needs all CSS files to be minified and compressed as it can save up to 258.1 kB or 83% of the original size.
Number of requests can be reduced by 34 (58%)
59
25
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Data Stori. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
datastori.es
1456 ms
wp-emoji-release.min.js
302 ms
frontend.css
209 ms
admin-font.css
207 ms
library.css
211 ms
public.css
215 ms
magnific-popup.css
297 ms
font-awesome.min.css
414 ms
style.css
606 ms
jetpack.css
528 ms
podlove-web-player.css
536 ms
jquery.js
601 ms
jquery-migrate.min.js
398 ms
frontend.js
505 ms
jquery.magnific-popup.min.js
630 ms
jquery.cookie.js
628 ms
public.js
632 ms
hashchange.min.js
643 ms
podlove-web-player.js
918 ms
datastori.es
1121 ms
app.js
680 ms
wp-tiles.css
546 ms
devicepx-jetpack.js
7 ms
gprofiles.js
58 ms
wpgroho.js
559 ms
global.min.js
560 ms
dynamic-stylesheet.js
567 ms
wp-embed.min.js
650 ms
wp-tiles.min.js
663 ms
font-awesome.css
42 ms
ga.js
13 ms
load.js
13 ms
about_headshot@2x.png
83 ms
seeing-data-logo.png
106 ms
print3-663x1024.png
764 ms
hadley.jpg
559 ms
Untitled.png
988 ms
daniel-pearson-domestic-data-streamers.jpg
109 ms
max-roser.png
611 ms
amanda-cox-695x1024.jpg
559 ms
jen-christiansen.jpeg
557 ms
offenhuber1.jpg
559 ms
munzner-2014-headshot-909x1024.jpg
881 ms
Paolo.jpeg
736 ms
jer-thorp-1-300x169.jpeg
609 ms
datastories-fun-storytelling-1024x507.png
1510 ms
kate2.jpg
733 ms
loader.js
73 ms
__utm.gif
13 ms
data-stories-logo-on-transparent.png
746 ms
fontawesome-webfont.woff
845 ms
fontawesome-webfont.woff
3 ms
header-bg.png
1259 ms
hovercard.css
73 ms
services.css
73 ms
app.css
82 ms
button.html
164 ms
css
54 ms
icon-small.png
82 ms
icon-big.png
216 ms
data-stories_400x400.png
200 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
16 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
18 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
21 ms
print.css
114 ms
datastori.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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
datastori.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
datastori.es 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Datastori.es can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Datastori.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.
datastori.es
Open Graph data is detected on the main page of Data Stori. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: