Tools & Wizards About Us
stories.twitter.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

stories.twitter.com

About Twitter | Our company and priorities

Page Load Speed

2.9 sec in total

First Response

97 ms

Resources Loaded

985 ms

Page Rendered

1.8 sec

stories.twitter.com screenshot

About Website

Visit stories.twitter.com now to see the best up-to-date Stories Twitter content for United States and also check out these interesting facts you probably never knew about stories.twitter.com

We serve the public conversation. Learn more about Twitter the company, and how we ensure people have a free and safe place to talk.

Visit stories.twitter.com

Key Findings

We analyzed Stories.twitter.com page load time and found that the first response time was 97 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

stories.twitter.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

62/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value900 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.228

55/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

stories.twitter.com

97 ms

issue2.css

28 ms

jquery.min.js

30 ms

pulltweet.js

58 ms

widgets.js

57 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 86% of them (56 requests) were addressed to the original Stories.twitter.com, 8% (5 requests) were made to Platform.twitter.com and 3% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (692 ms) belongs to the original domain Stories.twitter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (7%)

Content Size

16.1 MB

After Optimization

14.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stories.twitter.com main page is 16.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 16.0 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 16.4 kB

  • Original 20.9 kB
  • After minification 15.9 kB
  • After compression 4.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 5.0 kB, which is 24% 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 16.4 kB or 78% of the original size.

Image Optimization

-7%

Potential reduce by 1.1 MB

  • Original 16.0 MB
  • After minification 14.9 MB

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. Stories Twitter images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 279 B

  • Original 17.7 kB
  • After minification 17.6 kB
  • After compression 17.4 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

-87%

Potential reduce by 21.5 kB

  • Original 24.8 kB
  • After minification 19.0 kB
  • After compression 3.3 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. Stories.twitter.com needs all CSS files to be minified and compressed as it can save up to 21.5 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

63

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stories Twitter. 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

stories.twitter.com

stories.twitter.com

97 ms

issue2.css

issue2.css

28 ms

jquery.min.js

jquery.min.js

30 ms

pulltweet.js

pulltweet.js

58 ms

widgets.js

widgets.js

57 ms

ga.js

ga.js

84 ms

TwitterStories.json

TwitterStories.json

232 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

20 ms

background2.png

background2.png

107 ms

stories_large_en.png

stories_large_en.png

107 ms

dream.png

dream.png

285 ms

white80.png

white80.png

114 ms

eyes_ears.png

eyes_ears.png

288 ms

japan_rescue.png

japan_rescue.png

277 ms

get_a_job.png

get_a_job.png

297 ms

london_langs.png

london_langs.png

308 ms

trickortweet.png

trickortweet.png

692 ms

corn.png

corn.png

351 ms

everest.png

everest.png

352 ms

lostlang.png

lostlang.png

347 ms

wordnik.png

wordnik.png

351 ms

pedal_adam.png

pedal_adam.png

362 ms

carjack.png

carjack.png

397 ms

hello_giggles.png

hello_giggles.png

389 ms

musical_tweets.png

musical_tweets.png

377 ms

lauren_lane.png

lauren_lane.png

389 ms

arijit_guha.png

arijit_guha.png

401 ms

francis_kariuki.png

francis_kariuki.png

422 ms

steve_berry.png

steve_berry.png

412 ms

huseyin_cakir.png

huseyin_cakir.png

419 ms

food52.png

food52.png

422 ms

public_health.png

public_health.png

468 ms

myra_mcentire.png

myra_mcentire.png

462 ms

jerry_rizzo.png

jerry_rizzo.png

469 ms

mark_hayward.png

mark_hayward.png

471 ms

brian_stelter.png

brian_stelter.png

465 ms

2_wael_ghonim.png

2_wael_ghonim.png

487 ms

2_sohaib_athar.png

2_sohaib_athar.png

495 ms

2_kevin_durant.png

2_kevin_durant.png

495 ms

2_london_cleanup.png

2_london_cleanup.png

497 ms

2_daniel_morales.png

2_daniel_morales.png

497 ms

2_japan_quake.png

2_japan_quake.png

531 ms

2_julia_probst.png

2_julia_probst.png

533 ms

2_stefanie_gordon.png

2_stefanie_gordon.png

533 ms

__utm.gif

__utm.gif

98 ms

2_okan_bayulgen.png

2_okan_bayulgen.png

437 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

44 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

76 ms

2_peter_shankman.png

2_peter_shankman.png

431 ms

background.png

background.png

449 ms

1_aaron_durand.png

1_aaron_durand.png

290 ms

1_roger_ebert.png

1_roger_ebert.png

284 ms

1_chad_ochocinco.png

1_chad_ochocinco.png

279 ms

1_maureen_evans.png

1_maureen_evans.png

269 ms

1_willy_mutunga.png

1_willy_mutunga.png

281 ms

1_queen_rania.png

1_queen_rania.png

239 ms

1_burberry.png

1_burberry.png

237 ms

1_rebecca_chiao.png

1_rebecca_chiao.png

235 ms

1_ravi_pina.png

1_ravi_pina.png

236 ms

1_mike_massimino.png

1_mike_massimino.png

266 ms

1_yoshieimaru.png

1_yoshieimaru.png

247 ms

1_mark_slavonia.png

1_mark_slavonia.png

223 ms

1_bullet_skan.png

1_bullet_skan.png

222 ms

1_chris_strouth.png

1_chris_strouth.png

222 ms

jot.html

jot.html

4 ms

Accessibility Review

stories.twitter.com accessibility score

98

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

stories.twitter.com best practices score

75

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

stories.twitter.com 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

Document doesn't have a valid hreflang

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 Stories.twitter.com 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 Stories.twitter.com 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

stories.twitter.com

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