Tools & Wizards About Us
story.tel screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

story.tel

Storytel - Audiobooks on your iPhone or Android mobile. We have thousands of audiobook titles covering all genres.

Page Load Speed

1.5 sec in total

First Response

247 ms

Resources Loaded

1.1 sec

Page Rendered

136 ms

story.tel screenshot

About Website

Visit story.tel now to see the best up-to-date Story content and also check out these interesting facts you probably never knew about story.tel

Audiobooks on your iPhone or Android mobile. We have thousands of audiobook titles covering all genres. Listen to a book when you're out jogging, cutting the grass or during the commute to work.

Visit story.tel

Key Findings

We analyzed Story.tel page load time and found that the first response time was 247 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

story.tel performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

84/100

25%

SI (Speed Index)

Value1.8 s

100/100

10%

TBT (Total Blocking Time)

Value2,510 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value12.3 s

15/100

10%

Network Requests Diagram

www.storytel.com

247 ms

main.css

48 ms

countryPickerLandingPage.css

45 ms

analyticsHelper.js

141 ms

uc.js

22 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Story.tel, 9% (1 request) were made to Consent.cookiebot.com and 9% (1 request) were made to Static.cloudflareinsights.com. The less responsive or slowest element that took the longest time to load (627 ms) relates to the external source Sgtm.storytel.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 115.6 kB (39%)

Content Size

293.3 kB

After Optimization

177.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Story.tel main page is 293.3 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. Only 10% of websites need less resources to load. Images take 135.4 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 18.9 kB

  • Original 24.9 kB
  • After minification 22.0 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 2.8 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 18.9 kB or 76% of the original size.

Image Optimization

-7%

Potential reduce by 9.8 kB

  • Original 135.4 kB
  • After minification 125.6 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. Story images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 87.0 kB

  • Original 133.1 kB
  • After minification 133.1 kB
  • After compression 46.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 87.0 kB or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (40%)

Requests Now

10

After Optimization

6

  • Images
  • JavaScript
  • CSS

The browser has sent 10 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 5 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

www.storytel.com

www.storytel.com

247 ms

main.css

main.css

48 ms

countryPickerLandingPage.css

countryPickerLandingPage.css

45 ms

analyticsHelper.js

analyticsHelper.js

141 ms

uc.js

uc.js

22 ms

v84a3a4012de94ce1a686ba8c167c359c1696973893317

v84a3a4012de94ce1a686ba8c167c359c1696973893317

52 ms

flags32.css

flags32.css

33 ms

gtm.js

gtm.js

627 ms

pattern_medium_salmon.png

pattern_medium_salmon.png

125 ms

analytics.js

analytics.js

25 ms

flags32.png

flags32.png

45 ms

Accessibility Review

story.tel accessibility score

97

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

story.tel best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

story.tel SEO score

100

Search Engine Optimization Advices

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

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 Story.tel 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 Story.tel 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

story.tel

Open Graph description is not detected on the main page of 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: