4.9 sec in total
922 ms
3.5 sec
461 ms
Welcome to stori.in homepage info - get ready to check Stori best content for India right away, or after learning these important things about stori.in
Visit stori.inWe analyzed Stori.in page load time and found that the first response time was 922 ms and then it took 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.
stori.in performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value6.7 s
7/100
25%
Value16.4 s
0/100
10%
Value160 ms
94/100
30%
Value0.001
100/100
15%
Value8.2 s
41/100
10%
922 ms
113 ms
183 ms
185 ms
189 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 43% of them (29 requests) were addressed to the original Stori.in, 25% (17 requests) were made to Stori.in.managewebsiteportal.com and 6% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Stori.in.managewebsiteportal.com.
Page size can be reduced by 1.0 MB (15%)
6.6 MB
5.6 MB
In fact, the total size of Stori.in main page is 6.6 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. 65% of websites need less resources to load. Images take 5.3 MB which makes up the majority of the site volume.
Potential reduce by 24.5 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 3.5 kB, which is 11% 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 24.5 kB or 79% of the original size.
Potential reduce by 83.3 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. Stori images are well optimized though.
Potential reduce by 609.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 609.2 kB or 69% of the original size.
Potential reduce by 286.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. Stori.in needs all CSS files to be minified and compressed as it can save up to 286.2 kB or 83% of the original size.
Number of requests can be reduced by 35 (54%)
65
30
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 12 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
stori.in
922 ms
base.css
113 ms
ckeditor.css
183 ms
blackboard.css
185 ms
prettyPhoto.css
189 ms
superfish.css
194 ms
video-js.css
195 ms
slicebox.css
202 ms
nivo-slider.css
350 ms
justifiedGallery.min.css
351 ms
animation.css
357 ms
ui-dialog.css
354 ms
jquery-jvectormap-2.0.2.css
355 ms
lightbox.css
354 ms
bootstrap.css
436 ms
style.css
500 ms
bootstrap.min.css
26 ms
font-awesome.min.css
19 ms
jquery_modified.js
531 ms
jquery.ui.js
620 ms
i18n.js
437 ms
en.js
441 ms
asterion.js
884 ms
jquery-1.7.min.js
34 ms
jquery.min.js
7 ms
bootstrap.min.js
20 ms
css
27 ms
tweed_marle-562x336.jpg
511 ms
close.png
92 ms
loading.gif
93 ms
prev.png
93 ms
next.png
94 ms
sdk.js
165 ms
200;86;8d0ed76e7ebc6b03d82e6147508bbe0394bb2193.png
227 ms
230;61;1fca44b094ec32095365b2fbc8d2e4c114eeaf7c.png
323 ms
200;88;f39ac45433533d2b18073e75a45d38dc125f67c9.png
262 ms
wave2.png
176 ms
stori-small-%281%29.png
327 ms
trends-3.jpg
840 ms
trends-4.jpg
1213 ms
trends-2.jpg
980 ms
stori-logo.jpg
589 ms
redflame-p.jpg
533 ms
dagerfly-p-%281%29.jpg
834 ms
quote-2.jpg
663 ms
quote-1.jpg
894 ms
Look-book-01.jpg
967 ms
Look-book-02.jpg
1145 ms
Look-book-04.jpg
1074 ms
Look-book-03.jpg
1303 ms
Stori_Catalogue_03.jpg
1523 ms
Stori_Catalogue_09.jpg
1553 ms
Stori_Catalogue_14.jpg
1630 ms
widgets.js
86 ms
WhvNfO27lzODDhoAPcYEXQ.ttf
6 ms
glyphicons-halflings-regular.woff
8 ms
timeline.5d8406ab2e764a871ed41bd9aa0b693f.js
138 ms
119 ms
xd_arbiter.php
135 ms
xd_arbiter.php
263 ms
syndication
86 ms
682174482467786753
172 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
30 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
56 ms
gmBgqJMe_normal.jpg
191 ms
Cdl4NzNWIAAr6ly.jpg:small
227 ms
Cdl4NuxW8AIlVu_.jpg:small
191 ms
jot
22 ms
stori.in accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
stori.in 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
stori.in SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stori.in can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Stori.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.
stori.in
Open Graph description is not detected on the main page of Stori. 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: