Tools & Wizards About Us
aichi.thepage.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

aichi.thepage.jp

THE PAGE 愛知　|　あなたの街の気になるニュース

Page Load Speed

8.6 sec in total

First Response

524 ms

Resources Loaded

7.6 sec

Page Rendered

479 ms

aichi.thepage.jp screenshot

About Website

Click here to check amazing Aichi THE PAGE content for Japan. Otherwise, check out these important facts you probably never knew about aichi.thepage.jp

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

Visit aichi.thepage.jp

Key Findings

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

Performance Metrics

aichi.thepage.jp performance score

0

Network Requests Diagram

aichi.thepage.jp

524 ms

994 ms

top-20140507.css

1043 ms

branches-20140507.css

1005 ms

all-20140507.min.js

2000 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Aichi.thepage.jp, 29% (12 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 sec) relates to the external source S.yimg.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 439.1 kB (44%)

Content Size

998.7 kB

After Optimization

559.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 43.6 kB

  • Original 54.3 kB
  • After minification 43.6 kB
  • After compression 10.7 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 10.8 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 43.6 kB or 80% of the original size.

Image Optimization

-7%

Potential reduce by 29.8 kB

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

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. Aichi.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 23 (61%)

Requests Now

38

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aichi 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

aichi.thepage.jp

aichi.thepage.jp

524 ms

994 ms

top-20140507.css

top-20140507.css

1043 ms

branches-20140507.css

branches-20140507.css

1005 ms

all-20140507.min.js

all-20140507.min.js

2000 ms

pcore-1.0.1.min.js

pcore-1.0.1.min.js

1005 ms

platform.js

platform.js

85 ms

main-b8533eda075ae798e0f347d838e11a60.js

main-b8533eda075ae798e0f347d838e11a60.js

803 ms

yads-async.js

yads-async.js

1242 ms

yads.js

yads.js

1300 ms

rapidjp-1.0.0.js

rapidjp-1.0.0.js

1413 ms

clear_620x270.png

clear_620x270.png

205 ms

gtm.js

gtm.js

71 ms

20160325-00000002-wordleaf-0c0d9fde729c01bc06b4da69a428eb7cd.jpg

20160325-00000002-wordleaf-0c0d9fde729c01bc06b4da69a428eb7cd.jpg

1947 ms

branch_logo.png

branch_logo.png

183 ms

sprites-s2d0f0bc149.png

sprites-s2d0f0bc149.png

405 ms

branch_cover_bg.png

branch_cover_bg.png

209 ms

tag

tag

1431 ms

analytics.js

analytics.js

19 ms

collect

collect

3 ms

collect

collect

55 ms

yads-iframe.html

yads-iframe.html

209 ms

sprite_ico_sun.png

sprite_ico_sun.png

345 ms

20160307-00000009-wordleaf-06aba6180e1fadc58031437a5e11a3ee8.jpg

20160307-00000009-wordleaf-06aba6180e1fadc58031437a5e11a3ee8.jpg

809 ms

20160307-00000004-wordleafv-020f9afac391359322838d30e6b8efa40.jpg

20160307-00000004-wordleafv-020f9afac391359322838d30e6b8efa40.jpg

835 ms

20160303-00000016-wordleaf-0dd994cc4fa3a605243904a848bb095a5.jpg

20160303-00000016-wordleaf-0dd994cc4fa3a605243904a848bb095a5.jpg

879 ms

20160301-00000002-wordleaf-083287d938e7ff15e8350d8b411ed3950.jpg

20160301-00000002-wordleaf-083287d938e7ff15e8350d8b411ed3950.jpg

868 ms

20160325-00000003-wordleaf-017340c8052c6069f7782203e403c29c5.jpg

20160325-00000003-wordleaf-017340c8052c6069f7782203e403c29c5.jpg

1080 ms

n

n

1350 ms

tag

tag

815 ms

oi

oi

770 ms

rapidworker-1.2-968d6ea67f7b8577ee1c6b5f6deae357.js

rapidworker-1.2-968d6ea67f7b8577ee1c6b5f6deae357.js

668 ms

fbevents.js

fbevents.js

41 ms

collect

collect

18 ms

20160322-00000001-wordleafv-088d950586f36c8b0bf32f57b911b2e12.jpg

20160322-00000001-wordleafv-088d950586f36c8b0bf32f57b911b2e12.jpg

206 ms

20160317-00000009-wordleaf-067f1529839649b1e1c4c3150e16c2460.jpg

20160317-00000009-wordleaf-067f1529839649b1e1c4c3150e16c2460.jpg

158 ms

20160311-00000006-wordleaf-0244f341bf95657bed5b1ea5f3911f39b.jpg

20160311-00000006-wordleaf-0244f341bf95657bed5b1ea5f3911f39b.jpg

421 ms

20160309-00000002-wordleaf-0e28ba000bb4fc49fd0cec54d0350627f.jpg

20160309-00000002-wordleaf-0e28ba000bb4fc49fd0cec54d0350627f.jpg

315 ms

collect

collect

18 ms

19 ms

L300_250.jpg

L300_250.jpg

800 ms

SEO Factors

aichi.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 Aichi.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 Aichi.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

aichi.thepage.jp

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