Tools & Wizards About Us
nakayamakyoko.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

nakayamakyoko.net

中山恭子 - 公式ホームページ

Page Load Speed

8.1 sec in total

First Response

1.4 sec

Resources Loaded

6.4 sec

Page Rendered

319 ms

nakayamakyoko.net screenshot

About Website

Click here to check amazing Nakayamakyoko content for Japan. Otherwise, check out these important facts you probably never knew about nakayamakyoko.net

参議院議員中山恭子の公式サイトです。

Visit nakayamakyoko.net

Key Findings

We analyzed Nakayamakyoko.net page load time and found that the first response time was 1.4 sec and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

nakayamakyoko.net performance score

0

Network Requests Diagram

nakayamakyoko.net

1432 ms

xoops.css

364 ms

styleMAC.css

401 ms

tdt.js

619 ms

style.css

393 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 63% of them (44 requests) were addressed to the original Nakayamakyoko.net, 14% (10 requests) were made to Static.xx.fbcdn.net and 4% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Nakayamakyoko.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 65.9 kB (16%)

Content Size

417.7 kB

After Optimization

351.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nakayamakyoko.net main page is 417.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. 35% of websites need less resources to load. Images take 317.2 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 28.3 kB

  • Original 38.2 kB
  • After minification 35.7 kB
  • After compression 9.9 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 28.3 kB or 74% of the original size.

Image Optimization

-5%

Potential reduce by 15.0 kB

  • Original 317.2 kB
  • After minification 302.2 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. Nakayamakyoko images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 13.7 kB

  • Original 51.3 kB
  • After minification 46.9 kB
  • After compression 37.7 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 13.7 kB or 27% of the original size.

CSS Optimization

-81%

Potential reduce by 8.9 kB

  • Original 10.9 kB
  • After minification 9.1 kB
  • After compression 2.1 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. Nakayamakyoko.net needs all CSS files to be minified and compressed as it can save up to 8.9 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (48%)

Requests Now

61

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nakayamakyoko.net

nakayamakyoko.net

1432 ms

xoops.css

xoops.css

364 ms

styleMAC.css

styleMAC.css

401 ms

tdt.js

tdt.js

619 ms

style.css

style.css

393 ms

jsapi

jsapi

22 ms

jquery-ui.css

jquery-ui.css

21 ms

xoops.js

xoops.js

815 ms

gs_image_130-66_ja.js

gs_image_130-66_ja.js

15 ms

style.css

style.css

523 ms

15 ms

jquery.min.js

jquery.min.js

17 ms

jquery-ui.min.js

jquery-ui.min.js

34 ms

default+en.I.js

default+en.I.js

4 ms

bg.gif

bg.gif

226 ms

sdk.js

sdk.js

275 ms

gs_noscript_130-66_ja.gif

gs_noscript_130-66_ja.gif

58 ms

head_01.gif

head_01.gif

361 ms

head_02.gif

head_02.gif

565 ms

head_03.gif

head_03.gif

375 ms

txt_cg.gif

txt_cg.gif

406 ms

larger.gif

larger.gif

397 ms

default.gif

default.gif

522 ms

small.gif

small.gif

743 ms

g_menu_01.gif

g_menu_01.gif

791 ms

g_menu_02.gif

g_menu_02.gif

790 ms

g_menu_03.gif

g_menu_03.gif

813 ms

g_menu_04.gif

g_menu_04.gif

935 ms

g_menu_05.gif

g_menu_05.gif

952 ms

g_menu_06.gif

g_menu_06.gif

1317 ms

g_menu_07.gif

g_menu_07.gif

1322 ms

head_04.gif

head_04.gif

1168 ms

middle.gif

middle.gif

1184 ms

top_img.jpg

top_img.jpg

2503 ms

head_05.gif

head_05.gif

1341 ms

title_bar.gif

title_bar.gif

1717 ms

spacer.gif

spacer.gif

1569 ms

banner_06.jpg

banner_06.jpg

1985 ms

banner_01.jpg

banner_01.jpg

1813 ms

banner_02.jpg

banner_02.jpg

2106 ms

banner_03.jpg

banner_03.jpg

2313 ms

banner_04.jpg

banner_04.jpg

2374 ms

banner_05.jpg

banner_05.jpg

2349 ms

hiidurukuniyori.jpg

hiidurukuniyori.jpg

2975 ms

foot_00.gif

foot_00.gif

2502 ms

foot.gif

foot.gif

3034 ms

siteSeal.do

siteSeal.do

641 ms

124 ms

xd_arbiter.php

xd_arbiter.php

220 ms

xd_arbiter.php

xd_arbiter.php

423 ms

siteSealImage.do

siteSealImage.do

371 ms

g_menu_01_o.gif

g_menu_01_o.gif

352 ms

g_menu_02_o.gif

g_menu_02_o.gif

364 ms

g_menu_03_o.gif

g_menu_03_o.gif

371 ms

g_menu_04_o.gif

g_menu_04_o.gif

373 ms

g_menu_05_o.gif

g_menu_05_o.gif

395 ms

g_menu_06_o.gif

g_menu_06_o.gif

451 ms

g_menu_07_o.gif

g_menu_07_o.gif

724 ms

like_box.php

like_box.php

108 ms

hQThvcX2PmE.css

hQThvcX2PmE.css

281 ms

t3u7Vo4PVNb.css

t3u7Vo4PVNb.css

351 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

485 ms

ehA1CqzHyzE.js

ehA1CqzHyzE.js

619 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

484 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

503 ms

67542_509386325777994_1748632650_n.jpg

67542_509386325777994_1748632650_n.jpg

281 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

72 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

72 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

68 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

136 ms

SEO Factors

nakayamakyoko.net 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 Nakayamakyoko.net 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 Nakayamakyoko.net 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

nakayamakyoko.net

Open Graph description is not detected on the main page of Nakayamakyoko. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: