Tools & Wizards About Us
talltweets.com screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 95

    SEO

    Google-friendlier than
    91% of websites

talltweets.com

Coming Soon

Page Load Speed

1.6 sec in total

First Response

485 ms

Resources Loaded

961 ms

Page Rendered

123 ms

talltweets.com screenshot

About Website

Click here to check amazing Talltweets content for United States. Otherwise, check out these important facts you probably never knew about talltweets.com

Use Tall Tweets to write longer tweets that have more than 140 characters. You can compose both tweetshots (tweet screenshots) and tweetstorms (numbered tweets) and it works on your desktop or mobile ...

Visit talltweets.com

Key Findings

We analyzed Talltweets.com page load time and found that the first response time was 485 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

talltweets.com performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

47/100

25%

SI (Speed Index)

Value3.4 s

89/100

10%

TBT (Total Blocking Time)

Value2,190 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value13.0 s

12/100

10%

Network Requests Diagram

talltweets.com

485 ms

medium-editor.js

76 ms

medium-editor.min.css

98 ms

bootstrap.min.css

98 ms

html2canvas.min.js

101 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 9% of them (2 requests) were addressed to the original Talltweets.com, 26% (6 requests) were made to Platform.twitter.com and 22% (5 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (485 ms) belongs to the original domain Talltweets.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 100.2 kB (62%)

Content Size

160.4 kB

After Optimization

60.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Talltweets.com main page is 160.4 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. 30% of websites need less resources to load. Javascripts take 89.9 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 18.6 kB

  • Original 26.0 kB
  • After minification 25.8 kB
  • After compression 7.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. 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 18.6 kB or 71% of the original size.

Image Optimization

-15%

Potential reduce by 2.1 kB

  • Original 14.5 kB
  • After minification 12.4 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. Obviously, Talltweets needs image optimization as it can save up to 2.1 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-63%

Potential reduce by 56.6 kB

  • Original 89.9 kB
  • After minification 89.9 kB
  • After compression 33.3 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 56.6 kB or 63% of the original size.

CSS Optimization

-76%

Potential reduce by 22.9 kB

  • Original 29.9 kB
  • After minification 29.9 kB
  • After compression 7.0 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. Talltweets.com needs all CSS files to be minified and compressed as it can save up to 22.9 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (60%)

Requests Now

20

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Talltweets. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

talltweets.com

talltweets.com

485 ms

medium-editor.js

medium-editor.js

76 ms

medium-editor.min.css

medium-editor.min.css

98 ms

bootstrap.min.css

bootstrap.min.css

98 ms

html2canvas.min.js

html2canvas.min.js

101 ms

font-awesome.min.css

font-awesome.min.css

103 ms

css

css

44 ms

widgets.js

widgets.js

180 ms

analytics.js

analytics.js

31 ms

tall-tweets.png

tall-tweets.png

262 ms

sign-in.png

sign-in.png

68 ms

WgTPAq6J1u0Fg5nXLMPTA.js

WgTPAq6J1u0Fg5nXLMPTA.js

8 ms

collect

collect

25 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

26 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

36 ms

tweet.04d20138f67ab41d6b4af6cc583926d9.js

tweet.04d20138f67ab41d6b4af6cc583926d9.js

30 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

71 ms

syndication

syndication

95 ms

tweets.json

tweets.json

112 ms

tweet_button.6a78875565a912489e9aef879c881358.en.html

tweet_button.6a78875565a912489e9aef879c881358.en.html

71 ms

track.js

track.js

156 ms

tweet.7edb5b7c103e282bacfdf7055ee51cce.light.ltr.css

tweet.7edb5b7c103e282bacfdf7055ee51cce.light.ltr.css

30 ms

tweet.7edb5b7c103e282bacfdf7055ee51cce.light.ltr.css

tweet.7edb5b7c103e282bacfdf7055ee51cce.light.ltr.css

61 ms

Accessibility Review

talltweets.com accessibility score

88

Accessibility Issues

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

talltweets.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

talltweets.com SEO score

95

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Talltweets.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Talltweets.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

talltweets.com

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