Tools & Wizards About Us

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

twilog.org

Twitterのつぶやきをブログ形式で保存 - Twilog (ツイログ)

Page Load Speed

4.4 sec in total

First Response

556 ms

Resources Loaded

3.6 sec

Page Rendered

210 ms

About Website

Visit twilog.org now to see the best up-to-date Twilog content for Japan and also check out these interesting facts you probably never knew about twilog.org

TwilogはTwitterのツイートをブログ形式で保存するサービスです。過去のツイートを簡単に見返すことができます。

Visit twilog.org

Key Findings

We analyzed Twilog.org page load time and found that the first response time was 556 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

twilog.org performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value1,110 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.3 s

24/100

10%

Network Requests Diagram

twilog.org

556 ms

twilog.togetter.com

695 ms

wilog.087e422e9b7d9cc4e7f9.css

1078 ms

js

63 ms

cRn6IXVv_normal.jpg

222 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Twilog.org, 68% (30 requests) were made to Pbs.twimg.com and 14% (6 requests) were made to S.togetter.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source S.togetter.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 28.3 kB (5%)

Content Size

569.5 kB

After Optimization

541.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Twilog.org main page is 569.5 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. 25% of websites need less resources to load. Javascripts take 336.6 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 23.8 kB

  • Original 31.8 kB
  • After minification 25.1 kB
  • After compression 8.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 6.7 kB, which is 21% 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 23.8 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 4.5 kB

  • Original 190.8 kB
  • After minification 186.3 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. Twilog images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 336.6 kB
  • After minification 336.6 kB
  • After compression 336.6 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

-0%

Potential reduce by 25 B

  • Original 10.3 kB
  • After minification 10.3 kB
  • After compression 10.2 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. Twilog.org has all CSS files already compressed.

Requests Breakdown

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

Requests Now

42

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

twilog.org accessibility score

65

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

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

twilog.org best practices score

83

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

twilog.org SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Twilog.org can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Twilog.org 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

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