Tools & Wizards About Us
thepage.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

thepage.jp

THE PAGE（ザ・ページ）　|　気になるニュースをわかりやすく

Page Load Speed

5.7 sec in total

First Response

584 ms

Resources Loaded

4.7 sec

Page Rendered

423 ms

thepage.jp screenshot

About Website

Welcome to thepage.jp homepage info - get ready to check THE PAGE best content for Japan right away, or after learning these important things about thepage.jp

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

Visit thepage.jp

Key Findings

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

Performance Metrics

thepage.jp performance score

0

Network Requests Diagram

thepage.jp

584 ms

top-20140507.css

570 ms

all-20140507.min.js

1120 ms

pcore-1.0.1.min.js

583 ms

platform.js

63 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 7% of them (3 requests) were addressed to the original Thepage.jp, 31% (13 requests) were made to Wordleaf.c.yimg.jp and 19% (8 requests) were made to I.yimg.jp. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Wordleaf.c.yimg.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 635.6 kB (53%)

Content Size

1.2 MB

After Optimization

559.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 46.9 kB

  • Original 59.7 kB
  • After minification 47.7 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. This page needs HTML code to be minified as it can gain 12.0 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 46.9 kB or 78% of the original size.

Image Optimization

-10%

Potential reduce by 32.8 kB

  • Original 326.8 kB
  • After minification 294.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. THE PAGE images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 510.8 kB

  • Original 754.3 kB
  • After minification 753.5 kB
  • After compression 243.5 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 510.8 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 45.1 kB

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

Requests Breakdown

Number of requests can be reduced by 21 (53%)

Requests Now

40

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

thepage.jp

thepage.jp

584 ms

top-20140507.css

top-20140507.css

570 ms

all-20140507.min.js

all-20140507.min.js

1120 ms

pcore-1.0.1.min.js

pcore-1.0.1.min.js

583 ms

platform.js

platform.js

63 ms

main-a380a93c5a96cdd9f645f82e2002919a.js

main-a380a93c5a96cdd9f645f82e2002919a.js

488 ms

yads-async.js

yads-async.js

493 ms

yads.js

yads.js

526 ms

rapidjp-1.0.0.js

rapidjp-1.0.0.js

783 ms

clear_620x270.png

clear_620x270.png

190 ms

gtm.js

gtm.js

28 ms

20160301-00000005-wordleaf-05f1f0718722ab99680267ad19299e6b9.jpg

20160301-00000005-wordleaf-05f1f0718722ab99680267ad19299e6b9.jpg

1559 ms

sprites-s2d0f0bc149.png

sprites-s2d0f0bc149.png

551 ms

yads_vimps-1.4.1.js

yads_vimps-1.4.1.js

194 ms

tag

tag

574 ms

analytics.js

analytics.js

5 ms

collect

collect

2 ms

collect

collect

50 ms

yads-iframe.html

yads-iframe.html

189 ms

20160301-00000001-wordleafs-0f43b48e4380aebcae56b1056bd2d8d8f.jpg

20160301-00000001-wordleafs-0f43b48e4380aebcae56b1056bd2d8d8f.jpg

806 ms

20160229-00000003-wordleafs-0056efa5247ff4da323d5571cecae93eb.jpg

20160229-00000003-wordleafs-0056efa5247ff4da323d5571cecae93eb.jpg

804 ms

20160229-00000007-wordleaf-0f4e48bda740453d7c3ad6e0de4ed74b9.jpg

20160229-00000007-wordleaf-0f4e48bda740453d7c3ad6e0de4ed74b9.jpg

684 ms

20160229-00000002-wordleafs-0a36652b0657aba0ebc44d7e92fbe5ded.jpg

20160229-00000002-wordleafs-0a36652b0657aba0ebc44d7e92fbe5ded.jpg

696 ms

20160229-00000001-wordleafv-041dc5ea45b7ccd03572c5cb411077e3f.jpg

20160229-00000001-wordleafv-041dc5ea45b7ccd03572c5cb411077e3f.jpg

930 ms

n

n

1059 ms

tag

tag

377 ms

oi

oi

412 ms

L300_250.jpg

L300_250.jpg

1387 ms

b

b

565 ms

rapidworker-1.2-968d6ea67f7b8577ee1c6b5f6deae357.js

rapidworker-1.2-968d6ea67f7b8577ee1c6b5f6deae357.js

483 ms

acaad569fd5bc2.js

acaad569fd5bc2.js

41 ms

collect

collect

17 ms

20160229-00000009-wordleaf-04eeca8c515ba8531eea15e261350db79.jpg

20160229-00000009-wordleaf-04eeca8c515ba8531eea15e261350db79.jpg

156 ms

20160229-00000010-wordleaf-04ccd5c5a6c6cd2ae295d0200bfcb7b54.jpg

20160229-00000010-wordleaf-04ccd5c5a6c6cd2ae295d0200bfcb7b54.jpg

181 ms

20160226-00000005-wordleaf-02d02fa16b7fa8477943867ce137ef619.jpg

20160226-00000005-wordleaf-02d02fa16b7fa8477943867ce137ef619.jpg

198 ms

20160226-00000009-wordleaf-0cff34e53e57727cd949023732720e1ef.jpg

20160226-00000009-wordleaf-0cff34e53e57727cd949023732720e1ef.jpg

157 ms

20160301-00000001-wordleafv-0f202a1a4e9f590152f2275c0f3fe507f.jpg

20160301-00000001-wordleafv-0f202a1a4e9f590152f2275c0f3fe507f.jpg

311 ms

20160301-00000001-wordleaf-02cadc448f466120e9f5504192b891436.jpg

20160301-00000001-wordleaf-02cadc448f466120e9f5504192b891436.jpg

172 ms

20160229-00000015-wordleaf-05d4e595fa52cf861a0e4a6c0be090f1b.jpg

20160229-00000015-wordleaf-05d4e595fa52cf861a0e4a6c0be090f1b.jpg

299 ms

collect

collect

39 ms

fbevents.js

fbevents.js

16 ms

96 ms

SEO Factors

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 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 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

thepage.jp

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