Tools & Wizards About Us
twitter-lib.jp screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

twitter-lib.jp

twitter使い方徹底ガイド

Page Load Speed

4.1 sec in total

First Response

582 ms

Resources Loaded

3.2 sec

Page Rendered

276 ms

twitter-lib.jp screenshot

About Website

Welcome to twitter-lib.jp homepage info - get ready to check Twitter Lib best content for Japan right away, or after learning these important things about twitter-lib.jp

老若男女、個人・法人問わず、 幅広く利用されているTwitter。 リアルタイムで気軽につぶやける という使い方がウケ、 根強い人気を誇っています。 基本的な使い方はモチロンですが、 最新情報やTwitterにまつわるエピソード、 これは面白い！というネタなどを 発信していく予定です

Visit twitter-lib.jp

Key Findings

We analyzed Twitter-lib.jp page load time and found that the first response time was 582 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

twitter-lib.jp performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value3,410 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.055

98/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

Network Requests Diagram

twitter-lib.jp

582 ms

common.css.pagespeed.ce.m0FC3aptKn.css

192 ms

layout.css.pagespeed.ce.GMAtOn-Tgb.css

347 ms

design.css.pagespeed.ce.TUNLdIe2Xs.css

367 ms

mobile.css.pagespeed.ce.T4-rKo9ccm.css

371 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 54% of them (30 requests) were addressed to the original Twitter-lib.jp, 5% (3 requests) were made to S.gravatar.com and 4% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Sns-lib.com.

Page Optimization Overview & Recommendations

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

Content Size

576.4 kB

After Optimization

218.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Twitter-lib.jp main page is 576.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. 50% of websites need less resources to load. Javascripts take 329.6 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 34.3 kB

  • Original 47.1 kB
  • After minification 45.3 kB
  • After compression 12.8 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 34.3 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 412 B

  • Original 53.1 kB
  • After minification 52.7 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. Twitter Lib images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 201.5 kB

  • Original 329.6 kB
  • After minification 329.5 kB
  • After compression 128.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 201.5 kB or 61% of the original size.

CSS Optimization

-83%

Potential reduce by 121.5 kB

  • Original 146.7 kB
  • After minification 123.2 kB
  • After compression 25.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. Twitter-lib.jp needs all CSS files to be minified and compressed as it can save up to 121.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (78%)

Requests Now

55

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

twitter-lib.jp

twitter-lib.jp

582 ms

common.css.pagespeed.ce.m0FC3aptKn.css

common.css.pagespeed.ce.m0FC3aptKn.css

192 ms

layout.css.pagespeed.ce.GMAtOn-Tgb.css

layout.css.pagespeed.ce.GMAtOn-Tgb.css

347 ms

design.css.pagespeed.ce.TUNLdIe2Xs.css

design.css.pagespeed.ce.TUNLdIe2Xs.css

367 ms

mobile.css.pagespeed.ce.T4-rKo9ccm.css

mobile.css.pagespeed.ce.T4-rKo9ccm.css

371 ms

mobile_layout.css.pagespeed.ce.lbLFKRh61u.css

mobile_layout.css.pagespeed.ce.lbLFKRh61u.css

372 ms

advanced.css.pagespeed.ce.kVMePCUZ4U.css

advanced.css.pagespeed.ce.kVMePCUZ4U.css

380 ms

jquery.js.pagespeed.jm.bThpIvFEiG.js

jquery.js.pagespeed.jm.bThpIvFEiG.js

572 ms

styles.css,qver=4.3.pagespeed.ce._rvaR2jS-i.css

styles.css,qver=4.3.pagespeed.ce._rvaR2jS-i.css

613 ms

screen.min.css,qver=1509.pagespeed.ce.w2pUIxA01D.css

screen.min.css,qver=1509.pagespeed.ce.w2pUIxA01D.css

546 ms

wpp.css,qver=3.3.1.pagespeed.ce.qH-xCxR6hY.css

wpp.css,qver=3.3.1.pagespeed.ce.qH-xCxR6hY.css

551 ms

jetpack.css,qver=3.7.2.pagespeed.ce.AXHN_isHpx.css

jetpack.css,qver=3.7.2.pagespeed.ce.AXHN_isHpx.css

560 ms

jquery.js,qver=1.11.3.pagespeed.jm.zixJPNMRNN.js

jquery.js,qver=1.11.3.pagespeed.jm.zixJPNMRNN.js

763 ms

jquery-migrate.min.js,qver=1.2.1.pagespeed.jm.mhpNjdU8Wl.js

jquery-migrate.min.js,qver=1.2.1.pagespeed.jm.mhpNjdU8Wl.js

729 ms

loader.js

loader.js

124 ms

vertical-m.css,qversion=3.5.4.pagespeed.ce.ostx54xlK8.css

vertical-m.css,qversion=3.5.4.pagespeed.ce.ostx54xlK8.css

735 ms

twitter-lib.jp

twitter-lib.jp

742 ms

goodAd.js

goodAd.js

869 ms

066746008

066746008

619 ms

sh.adingo.jp

sh.adingo.jp

332 ms

socialButton.js

socialButton.js

752 ms

jquery.form.min.js,qver=3.51.0-2014.06.20.pagespeed.jm.RVBOol6lkO.js

jquery.form.min.js,qver=3.51.0-2014.06.20.pagespeed.jm.RVBOol6lkO.js

752 ms

scripts.js,qver=4.3.pagespeed.jm.AQ2a9_TgU5.js

scripts.js,qver=4.3.pagespeed.jm.AQ2a9_TgU5.js

903 ms

front.min.js,qver=1509.pagespeed.ce.-Y1QEmx-I-.js

front.min.js,qver=1509.pagespeed.ce.-Y1QEmx-I-.js

917 ms

devicepx-jetpack.js

devicepx-jetpack.js

70 ms

gprofiles.js

gprofiles.js

69 ms

e-201609.js

e-201609.js

7 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

327 ms

analytics.js

analytics.js

58 ms

415-5-1.bmp

415-5-1.bmp

1859 ms

230x230x150-featured-230x230.jpg.pagespeed.ic.gHINCHTyc7.jpg

230x230x150-featured-230x230.jpg.pagespeed.ic.gHINCHTyc7.jpg

190 ms

230x230x1308-featured-230x230.jpg.pagespeed.ic.vSOk95UjRZ.jpg

230x230x1308-featured-230x230.jpg.pagespeed.ic.vSOk95UjRZ.jpg

192 ms

230x230x396-featured-230x230.jpg.pagespeed.ic.tM23AnIKbr.jpg

230x230x396-featured-230x230.jpg.pagespeed.ic.tM23AnIKbr.jpg

343 ms

230x230x1552-featured-230x230.jpg.pagespeed.ic.kUgN7O8MMw.jpg

230x230x1552-featured-230x230.jpg.pagespeed.ic.kUgN7O8MMw.jpg

301 ms

230x230x942-featured-230x230.jpg.pagespeed.ic.7Aw_u1E-yn.jpg

230x230x942-featured-230x230.jpg.pagespeed.ic.7Aw_u1E-yn.jpg

318 ms

bg-sub-h3.png

bg-sub-h3.png

316 ms

icon-arrow_r.png

icon-arrow_r.png

366 ms

collect

collect

18 ms

Zen

Zen

336 ms

encount

encount

531 ms

print.css.pagespeed.ce.w3Bu_wD1_o.css

print.css.pagespeed.ce.w3Bu_wD1_o.css

192 ms

1.13.17

1.13.17

355 ms

i.adingo.jp

i.adingo.jp

314 ms

bg-pagetop.png

bg-pagetop.png

194 ms

i.adingo.jp

i.adingo.jp

354 ms

g.gif

g.gif

56 ms

widgets.js

widgets.js

26 ms

plusone.js

plusone.js

114 ms

all.js

all.js

54 ms

hovercard.css

hovercard.css

82 ms

services.css

services.css

82 ms

68 ms

xd_arbiter.php

xd_arbiter.php

47 ms

xd_arbiter.php

xd_arbiter.php

81 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

45 ms

sync

sync

185 ms

Accessibility Review

twitter-lib.jp accessibility score

68

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

twitter-lib.jp best practices score

58

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

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

twitter-lib.jp SEO score

98

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Twitter-lib.jp 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 Twitter-lib.jp 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

twitter-lib.jp

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