Tools & Wizards About Us
tokyo.thepage.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

tokyo.thepage.jp

THE PAGE 東京　|　あなたの街の気になるニュース

Page Load Speed

10.4 sec in total

First Response

592 ms

Resources Loaded

8.2 sec

Page Rendered

1.6 sec

tokyo.thepage.jp screenshot

About Website

Visit tokyo.thepage.jp now to see the best up-to-date Tokyo THE PAGE content for Japan and also check out these interesting facts you probably never knew about tokyo.thepage.jp

気になる世の中の動きや社会問題を、わかりやすく解説するニュースサイト。ニュースの理解を助ける図解や写真、オピニオンや議論まとめも。

Visit tokyo.thepage.jp

Key Findings

We analyzed Tokyo.thepage.jp page load time and found that the first response time was 592 ms and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

tokyo.thepage.jp performance score

0

Network Requests Diagram

tokyo.thepage.jp

592 ms

1082 ms

top-20140507.css

1311 ms

branches-20140507.css

1143 ms

all-20140507.min.js

2016 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Tokyo.thepage.jp, 31% (13 requests) were made to S.yimg.jp and 24% (10 requests) were made to Wordleaf.c.yimg.jp. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Wordleaf.c.yimg.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 443.5 kB (52%)

Content Size

848.7 kB

After Optimization

405.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tokyo.thepage.jp main page is 848.7 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. 15% of websites need less resources to load. Javascripts take 482.3 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 45.7 kB

  • Original 57.5 kB
  • After minification 46.2 kB
  • After compression 11.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. This page needs HTML code to be minified as it can gain 11.2 kB, which is 20% 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 45.7 kB or 79% of the original size.

Image Optimization

-13%

Potential reduce by 32.1 kB

  • Original 254.1 kB
  • After minification 222.0 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, Tokyo THE PAGE needs image optimization as it can save up to 32.1 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 320.1 kB

  • Original 482.3 kB
  • After minification 481.5 kB
  • After compression 162.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 320.1 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 45.5 kB

  • Original 54.8 kB
  • After minification 54.3 kB
  • After compression 9.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. Tokyo.thepage.jp needs all CSS files to be minified and compressed as it can save up to 45.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (82%)

Requests Now

39

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tokyo.thepage.jp

tokyo.thepage.jp

592 ms

1082 ms

top-20140507.css

top-20140507.css

1311 ms

branches-20140507.css

branches-20140507.css

1143 ms

all-20140507.min.js

all-20140507.min.js

2016 ms

pcore-1.0.1.min.js

pcore-1.0.1.min.js

1194 ms

platform.js

platform.js

357 ms

main-b8533eda075ae798e0f347d838e11a60.js

main-b8533eda075ae798e0f347d838e11a60.js

936 ms

yads-async.js

yads-async.js

1619 ms

yads.js

yads.js

1700 ms

rapidjp-1.0.0.js

rapidjp-1.0.0.js

1631 ms

clear_620x270.png

clear_620x270.png

199 ms

gtm.js

gtm.js

183 ms

20160325-00000007-wordleaf-08beb272b666029841636adb7a58b70f0.jpg

20160325-00000007-wordleaf-08beb272b666029841636adb7a58b70f0.jpg

2254 ms

branch_logo.png

branch_logo.png

303 ms

sprites-s2d0f0bc149.png

sprites-s2d0f0bc149.png

1256 ms

branch_cover_bg.png

branch_cover_bg.png

287 ms

tag

tag

984 ms

analytics.js

analytics.js

56 ms

collect

collect

33 ms

collect

collect

86 ms

yads-iframe.html

yads-iframe.html

270 ms

20160322-00000008-wordleaf-0bf07e36f1d52ed71c997be3dc76c9480.jpg

20160322-00000008-wordleaf-0bf07e36f1d52ed71c997be3dc76c9480.jpg

931 ms

20160320-00000003-wordleafv-0eb0c03f1f9e831b70c75d0c8a30f956d.jpg

20160320-00000003-wordleafv-0eb0c03f1f9e831b70c75d0c8a30f956d.jpg

945 ms

20160320-00000002-wordleafv-060197f0319a95329f229d7cb525fbd29.jpg

20160320-00000002-wordleafv-060197f0319a95329f229d7cb525fbd29.jpg

948 ms

20160320-00000001-wordleafv-00c80e704e80c3441c7de25a3b097622b.jpg

20160320-00000001-wordleafv-00c80e704e80c3441c7de25a3b097622b.jpg

1153 ms

20160222-00000003-wordleaf-04d14223ad1c5ee4f89b8cc60484f6bff.jpg

20160222-00000003-wordleaf-04d14223ad1c5ee4f89b8cc60484f6bff.jpg

949 ms

sprite_ico_cloud.png

sprite_ico_cloud.png

204 ms

sprite_ico_rain.png

sprite_ico_rain.png

392 ms

n

n

1242 ms

tag

tag

790 ms

oi

oi

1035 ms

rapidworker-1.2-968d6ea67f7b8577ee1c6b5f6deae357.js

rapidworker-1.2-968d6ea67f7b8577ee1c6b5f6deae357.js

881 ms

fbevents.js

fbevents.js

286 ms

collect

collect

128 ms

20160324-00000002-wordleafv-08b91ee06ae586edc898fb182bcb1097c.jpg

20160324-00000002-wordleafv-08b91ee06ae586edc898fb182bcb1097c.jpg

700 ms

20160323-00000005-wordleafv-01917a4187e192b66a3eb70aa7accdcdd.jpg

20160323-00000005-wordleafv-01917a4187e192b66a3eb70aa7accdcdd.jpg

479 ms

20160323-00000004-wordleafv-0ca6677b733443c9a407ea577c77f4142.jpg

20160323-00000004-wordleafv-0ca6677b733443c9a407ea577c77f4142.jpg

478 ms

20160323-00000002-wordleafv-057642ceef8707d566195503814e4e67f.jpg

20160323-00000002-wordleafv-057642ceef8707d566195503814e4e67f.jpg

666 ms

295 ms

collect

collect

30 ms

L300_250.jpg

L300_250.jpg

1057 ms

SEO Factors

tokyo.thepage.jp SEO score

0

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 Tokyo.thepage.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 Tokyo.thepage.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

tokyo.thepage.jp

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