5 sec in total
549 ms
4 sec
484 ms
Visit whatastory.in now to see the best up-to-date What A Story content for India and also check out these interesting facts you probably never knew about whatastory.in
Elevate your brand with What a Story's top-notch video production services. Custom videos, affordable pricing, and premium support.
Visit whatastory.inWe analyzed Whatastory.in page load time and found that the first response time was 549 ms 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.
whatastory.in performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value7.1 s
6/100
25%
Value7.7 s
24/100
10%
Value1,270 ms
19/100
30%
Value0.099
90/100
15%
Value13.3 s
12/100
10%
549 ms
1328 ms
562 ms
1150 ms
740 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 65% of them (26 requests) were addressed to the original Whatastory.in, 20% (8 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Whatastory.in.
Page size can be reduced by 857.2 kB (58%)
1.5 MB
629.9 kB
In fact, the total size of Whatastory.in main page is 1.5 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. Javascripts take 800.5 kB which makes up the majority of the site volume.
Potential reduce by 8.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 2.0 kB, which is 18% 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 8.5 kB or 76% of the original size.
Potential reduce by 15.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. What A Story images are well optimized though.
Potential reduce by 611.1 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 611.1 kB or 76% of the original size.
Potential reduce by 222.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. Whatastory.in needs all CSS files to be minified and compressed as it can save up to 222.1 kB or 87% of the original size.
Number of requests can be reduced by 16 (55%)
29
13
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of What A Story. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
whatastory.in
549 ms
bootstrap.css
1328 ms
fonts.css
562 ms
plugins-common.css
1150 ms
owl.carousel.css
740 ms
owl.theme.css
737 ms
intro08.css
738 ms
main.css
1029 ms
less-compiled.css
989 ms
main-bg.css
990 ms
main-responsive.css
1474 ms
main-retina.css
1240 ms
css
25 ms
plugins.js
3071 ms
navmenu-init.js
1263 ms
equalheights-init.js
1389 ms
main.js
1521 ms
analytics.js
42 ms
menu.jpg
752 ms
logo.png
263 ms
01.jpg
486 ms
02.jpg
716 ms
03.jpg
1275 ms
04.jpg
1493 ms
01.png
733 ms
02.png
951 ms
03.png
974 ms
04.png
1004 ms
BjAYBlHtW3CJxDcjzrnZCJ0EAVxt0G0biEntp43Qt6E.ttf
22 ms
AIed271kqQlcIRSOnQH0yZ_TkvowlIOtbR7ePgFOpF4.ttf
23 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
20 ms
IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf
21 ms
-_Ctzj9b56b8RgXW8FAriS3USBnSvpkopQaUR-2r7iU.ttf
23 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
20 ms
JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf
21 ms
PKCRbVvRfd5n7BTjtGiFZC3USBnSvpkopQaUR-2r7iU.ttf
22 ms
collect
22 ms
collect
61 ms
ga-audiences
55 ms
default
211 ms
whatastory.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
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
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.
whatastory.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Missing source maps for large first-party JavaScript
whatastory.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Whatastory.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 Whatastory.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.
whatastory.in
Open Graph description is not detected on the main page of What A Story. 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: