7 sec in total
1.4 sec
3.9 sec
1.8 sec
Visit datastories.in now to see the best up-to-date Data Stories content and also check out these interesting facts you probably never knew about datastories.in
Visit datastories.inWe analyzed Datastories.in page load time and found that the first response time was 1.4 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
datastories.in performance score
name
value
score
weighting
Value2.3 s
76/100
10%
Value2.3 s
94/100
25%
Value5.0 s
63/100
10%
Value390 ms
68/100
30%
Value0.002
100/100
15%
Value5.5 s
70/100
10%
1362 ms
244 ms
242 ms
301 ms
165 ms
Our browser made a total of 29 requests to load all elements on the main page. We found that 62% of them (18 requests) were addressed to the original Datastories.in, 7% (2 requests) were made to Google-analytics.com and 7% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Datastories.in.
Page size can be reduced by 140.8 kB (33%)
421.8 kB
281.0 kB
In fact, the total size of Datastories.in main page is 421.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 328.4 kB which makes up the majority of the site volume.
Potential reduce by 15.8 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 15.8 kB or 63% of the original size.
Potential reduce by 85.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 Stories needs image optimization as it can save up to 85.5 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 28.2 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 28.2 kB or 53% of the original size.
Potential reduce by 11.2 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. Datastories.in needs all CSS files to be minified and compressed as it can save up to 11.2 kB or 78% of the original size.
Number of requests can be reduced by 13 (57%)
23
10
The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Data Stories. 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 5 to 1 for CSS and as a result speed up the page load time.
datastories.in
1362 ms
style.css
244 ms
style.css
242 ms
widgets.js
301 ms
webfont.js
165 ms
ga.js
497 ms
plusone.js
382 ms
bg.png
167 ms
wealth.html
180 ms
Rplot.png
272 ms
parset-nss2012.html
261 ms
up.png
725 ms
564 ms
ofl-normal.css
227 ms
ofl-italic.css
244 ms
d3.v3.min.js
308 ms
whv2_001.js
121 ms
d3.parsets.css
90 ms
d3.v3.min.js
275 ms
d3.parsets.js
1364 ms
OFLGoudyStM-Italic-webfont.woff
261 ms
OFLGoudyStM-webfont.woff
328 ms
cb=gapi.loaded_0
54 ms
fac3.csv
1167 ms
visit.gif
140 ms
__utm.gif
89 ms
work2012.csv
231 ms
visit.gif
76 ms
34f44a27ef6cbea3749f49c47950d87b
502 ms
datastories.in 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
Image elements do not have [alt] attributes
datastories.in 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
Browser errors were logged to the console
datastories.in 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Datastories.in 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 Datastories.in 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.
datastories.in
Open Graph description is not detected on the main page of Data Stories. 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: