Tools & Wizards About Us
kimiko-date.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

kimiko-date.com

伊達公子 公式サイト - Kimiko Date｜THE TENNIS DAILY

Page Load Speed

10.5 sec in total

First Response

453 ms

Resources Loaded

9.9 sec

Page Rendered

177 ms

kimiko-date.com screenshot

About Website

Click here to check amazing Kimiko Date content for Japan. Otherwise, check out these important facts you probably never knew about kimiko-date.com

テニスを愛するすべての人々へ。テニスを「知る」「読む」「観る」「調べる」「楽しむ」そして、テニスに「参加する」。あなたがのぞむ テニスがここに詰まっています。プロテニスプレーヤー伊達公子のオフィシャルサイト。

Visit kimiko-date.com

Key Findings

We analyzed Kimiko-date.com page load time and found that the first response time was 453 ms and then it took 10.1 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

kimiko-date.com performance score

0

Network Requests Diagram

kimiko-date.com

453 ms

kimiko-date.thetennisdaily.jp

6419 ms

reset_html5.css

531 ms

common.css

528 ms

top.css

534 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Kimiko-date.com, 80% (51 requests) were made to Kimiko-date.thetennisdaily.jp and 11% (7 requests) were made to Thetennisdaily.jp. The less responsive or slowest element that took the longest time to load (6.4 sec) relates to the external source Kimiko-date.thetennisdaily.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 163.4 kB (15%)

Content Size

1.1 MB

After Optimization

924.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kimiko-date.com main page is 1.1 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. 30% of websites need less resources to load. Images take 916.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 18.3 kB

  • Original 23.1 kB
  • After minification 22.2 kB
  • After compression 4.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 18.3 kB or 79% of the original size.

Image Optimization

-8%

Potential reduce by 68.8 kB

  • Original 916.2 kB
  • After minification 847.3 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. Kimiko Date images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 55.8 kB

  • Original 122.0 kB
  • After minification 121.3 kB
  • After compression 66.2 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 55.8 kB or 46% of the original size.

CSS Optimization

-78%

Potential reduce by 20.5 kB

  • Original 26.4 kB
  • After minification 19.0 kB
  • After compression 5.9 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. Kimiko-date.com needs all CSS files to be minified and compressed as it can save up to 20.5 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (27%)

Requests Now

60

After Optimization

44

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kimiko-date.com

kimiko-date.com

453 ms

kimiko-date.thetennisdaily.jp

kimiko-date.thetennisdaily.jp

6419 ms

reset_html5.css

reset_html5.css

531 ms

common.css

common.css

528 ms

top.css

top.css

534 ms

skippr.css

skippr.css

368 ms

jquery.min.js

jquery.min.js

30 ms

skippr.min.js

skippr.min.js

925 ms

common.js

common.js

552 ms

xmlrequest.js

xmlrequest.js

704 ms

jquery.min.js

jquery.min.js

11 ms

common_header.css

common_header.css

524 ms

btn_hshare.png

btn_hshare.png

366 ms

logo.gif

logo.gif

737 ms

logo_date.png

logo_date.png

195 ms

navi01_on.png

navi01_on.png

190 ms

navi02_off.png

navi02_off.png

184 ms

navi03_off.png

navi03_off.png

182 ms

navi04_off.png

navi04_off.png

182 ms

navi04_sub1_off.png

navi04_sub1_off.png

195 ms

navi04_sub2_off.png

navi04_sub2_off.png

378 ms

navi05_off.png

navi05_off.png

377 ms

navi06_off.png

navi06_off.png

356 ms

navi07_off.png

navi07_off.png

378 ms

navi08_off.png

navi08_off.png

380 ms

navi08_sub1_off.png

navi08_sub1_off.png

395 ms

navi08_sub2_off.png

navi08_sub2_off.png

548 ms

navi_jp_on.png

navi_jp_on.png

549 ms

navi_en_off.png

navi_en_off.png

560 ms

logo_date_sp.png

logo_date_sp.png

567 ms

btn_menu_sp.png

btn_menu_sp.png

565 ms

ttl_blog.png

ttl_blog.png

757 ms

btn_more01.gif

btn_more01.gif

701 ms

ttl_news.png

ttl_news.png

720 ms

ttl_ranking.png

ttl_ranking.png

901 ms

txt_single.png

txt_single.png

753 ms

1.png

1.png

754 ms

9.png

9.png

873 ms

8.png

8.png

897 ms

txt_doubles.png

txt_doubles.png

937 ms

0.png

0.png

942 ms

bnr_news.jpg

bnr_news.jpg

1119 ms

bnr_video.jpg

bnr_video.jpg

1386 ms

bnr_books.jpg

bnr_books.jpg

1418 ms

bnr_facebook.jpg

bnr_facebook.jpg

1247 ms

btn_pagetop.gif

btn_pagetop.gif

1120 ms

btn_sponsor.png

btn_sponsor.png

1128 ms

banner-tbc_off.png

banner-tbc_off.png

1303 ms

banner-iyo_off.png

banner-iyo_off.png

1326 ms

banner-yonex_off.png

banner-yonex_off.png

1312 ms

banner-adidas_off.png

banner-adidas_off.png

1254 ms

bg_header.jpg

bg_header.jpg

174 ms

h_menu.gif

h_menu.gif

189 ms

bg_menu.jpg

bg_menu.jpg

349 ms

m_menu00.gif

m_menu00.gif

545 ms

img_main01.jpg

img_main01.jpg

1511 ms

img_main02.jpg

img_main02.jpg

1537 ms

img_main03.jpg

img_main03.jpg

1731 ms

bg_topcontent.png

bg_topcontent.png

1040 ms

analytics.js

analytics.js

16 ms

yql

yql

1102 ms

collect

collect

11 ms

common_sp.css

common_sp.css

192 ms

top_sp.css

top_sp.css

189 ms

SEO Factors

kimiko-date.com SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kimiko-date.com 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 Kimiko-date.com main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

kimiko-date.com

Open Graph description is not detected on the main page of Kimiko Date. 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: