Tools & Wizards About Us
whatastory.in screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

whatastory.in

What a Story: SaaS Product Videos, Explainer Videos, Corporate Videos

Page Load Speed

3.5 sec in total

First Response

67 ms

Resources Loaded

1.7 sec

Page Rendered

1.7 sec

whatastory.in screenshot

About Website

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.in

Key Findings

We analyzed Whatastory.in page load time and found that the first response time was 67 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

whatastory.in performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value1,530 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.089

92/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

whatastory.in

67 ms

whatastory.agency

23 ms

whatastory.agency

46 ms

css

54 ms

style.min.css

732 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Whatastory.in, 52% (13 requests) were made to Whatastory.agency and 8% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Whatastory.agency.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.9 kB (41%)

Content Size

236.0 kB

After Optimization

140.1 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Whatastory.in main page is 236.0 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. 35% of websites need less resources to load. HTML takes 107.4 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 87.4 kB

  • Original 107.4 kB
  • After minification 105.5 kB
  • After compression 20.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 87.4 kB or 81% of the original size.

JavaScript Optimization

-8%

Potential reduce by 8.2 kB

  • Original 107.4 kB
  • After minification 107.4 kB
  • After compression 99.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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 294 B

  • Original 21.2 kB
  • After minification 21.2 kB
  • After compression 20.9 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 17 (81%)

Requests Now

21

After Optimization

4

  • Images
  • JavaScript
  • CSS

The browser has sent 21 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 13 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

whatastory.in

whatastory.in

67 ms

whatastory.agency

whatastory.agency

23 ms

whatastory.agency

whatastory.agency

46 ms

css

css

54 ms

style.min.css

style.min.css

732 ms

oxygen.css

oxygen.css

800 ms

lity.min.css

lity.min.css

40 ms

jquery.min.js

jquery.min.js

775 ms

js

js

84 ms

7160570.js

7160570.js

77 ms

whatastory.agency

whatastory.agency

42 ms

aos.css

aos.css

774 ms

lazysizes.min.js

lazysizes.min.js

37 ms

lity.js

lity.js

994 ms

custom.js

custom.js

779 ms

aos.js

aos.js

1461 ms

gtm.js

gtm.js

188 ms

lined-bg.svg

lined-bg.svg

743 ms

cursor.svg

cursor.svg

753 ms

fb.js

fb.js

177 ms

banner.js

banner.js

177 ms

7160570.js

7160570.js

260 ms

font

font

57 ms

iframe_api

iframe_api

87 ms

www-widgetapi.js

www-widgetapi.js

4 ms

Accessibility Review

whatastory.in accessibility score

65

Accessibility Issues

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

whatastory.in best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

whatastory.in SEO score

84

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

whatastory.in

Open Graph data is detected on the main page of What A Story. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: