Tools & Wizards About Us
matsuge-dartsdiary.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

matsuge-dartsdiary.com

ダーツ初心者からの上達への道　～ダーツの総合情報サイト～

Page Load Speed

16.2 sec in total

First Response

1.4 sec

Resources Loaded

14.2 sec

Page Rendered

649 ms

matsuge-dartsdiary.com screenshot

About Website

Welcome to matsuge-dartsdiary.com homepage info - get ready to check Matsuge Dartsdiary best content for Japan right away, or after learning these important things about matsuge-dartsdiary.com

飲みダーツもガチダーツもやる、両刀使いの私が、日々の出来事や自分が学んだことを綴っていく日記です。

Visit matsuge-dartsdiary.com

Key Findings

We analyzed Matsuge-dartsdiary.com page load time and found that the first response time was 1.4 sec and then it took 14.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

matsuge-dartsdiary.com performance score

0

Network Requests Diagram

www.matsuge-dartsdiary.com

1359 ms

style.css

334 ms

jsapi

17 ms

rollover.js

354 ms

styles.css

363 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 59% of them (55 requests) were addressed to the original Matsuge-dartsdiary.com, 5% (5 requests) were made to Platform.twitter.com and 3% (3 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Matsuge-dartsdiary.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 382.5 kB (32%)

Content Size

1.2 MB

After Optimization

797.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Matsuge-dartsdiary.com 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. 45% of websites need less resources to load. Images take 901.8 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 36.0 kB

  • Original 46.0 kB
  • After minification 43.8 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 36.0 kB or 78% of the original size.

Image Optimization

-22%

Potential reduce by 197.8 kB

  • Original 901.8 kB
  • After minification 704.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, Matsuge Dartsdiary needs image optimization as it can save up to 197.8 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-54%

Potential reduce by 85.5 kB

  • Original 157.1 kB
  • After minification 154.3 kB
  • After compression 71.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 85.5 kB or 54% of the original size.

CSS Optimization

-85%

Potential reduce by 63.2 kB

  • Original 74.6 kB
  • After minification 58.2 kB
  • After compression 11.4 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. Matsuge-dartsdiary.com needs all CSS files to be minified and compressed as it can save up to 63.2 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (45%)

Requests Now

91

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.matsuge-dartsdiary.com

www.matsuge-dartsdiary.com

1359 ms

style.css

style.css

334 ms

jsapi

jsapi

17 ms

rollover.js

rollover.js

354 ms

styles.css

styles.css

363 ms

jquery.js

jquery.js

1302 ms

common.css

common.css

166 ms

wordpress.css

wordpress.css

198 ms

cool-greeng12.css

cool-greeng12.css

606 ms

clearfix.css

clearfix.css

331 ms

print.css

print.css

339 ms

advanced.css

advanced.css

697 ms

scs

scs

605 ms

jquery.form.min.js

jquery.form.min.js

558 ms

scripts.js

scripts.js

492 ms

2nd_gets.php

2nd_gets.php

324 ms

index.js

index.js

346 ms

jquery.min.js

jquery.min.js

27 ms

ga.js

ga.js

67 ms

entry.gif

entry.gif

315 ms

add_icon_mini_08.gif

add_icon_mini_08.gif

523 ms

clip_16_16_w.gif

clip_16_16_w.gif

552 ms

ybm16.gif

ybm16.gif

1438 ms

darts88_31.gif

darts88_31.gif

553 ms

br_c_1220_1.gif

br_c_1220_1.gif

381 ms

valid-xhtml10.gif

valid-xhtml10.gif

65 ms

wcag1A.gif

wcag1A.gif

64 ms

bg2.jpg

bg2.jpg

542 ms

bg-contents-h3.gif

bg-contents-h3.gif

181 ms

1-topmenu.png

1-topmenu.png

541 ms

2-topmenu.png

2-topmenu.png

380 ms

3-topmenu.png

3-topmenu.png

389 ms

4-topmenu.png

4-topmenu.png

400 ms

5-topmenu.png

5-topmenu.png

709 ms

6-topmenu1.png

6-topmenu1.png

739 ms

9-topmenu.png

9-topmenu.png

1339 ms

7-topmenu.png

7-topmenu.png

1096 ms

8-topmenu.png

8-topmenu.png

855 ms

bg-contents-h2.gif

bg-contents-h2.gif

675 ms

icon-color01.gif

icon-color01.gif

853 ms

icon-color02.gif

icon-color02.gif

902 ms

icon-color03.gif

icon-color03.gif

938 ms

icon-color04.gif

icon-color04.gif

1022 ms

icon-color05.gif

icon-color05.gif

1026 ms

IMG_1546_thumb.jpg

IMG_1546_thumb.jpg

1276 ms

2013-05-27_002445_thumb.png

2013-05-27_002445_thumb.png

1843 ms

2013-05-18_013301_thumb.png

2013-05-18_013301_thumb.png

1537 ms

2013-04-28_153930_thumb.png

2013-04-28_153930_thumb.png

1695 ms

2013-04-14_221505_thumb.png

2013-04-14_221505_thumb.png

1791 ms

address-image3.png

address-image3.png

2325 ms

btn-search_off.gif

btn-search_off.gif

1522 ms

btn-pagetop_off.gif

btn-pagetop_off.gif

1708 ms

logo3.png

logo3.png

2249 ms

top-image2.jpg

top-image2.jpg

1859 ms

541 ms

__utm.gif

__utm.gif

34 ms

315 ms

bg-sidebar.gif

bg-sidebar.gif

1811 ms

bg-sidebar-top.gif

bg-sidebar-top.gif

1883 ms

bg-sidebar-h3.png

bg-sidebar-h3.png

1940 ms

collect

collect

62 ms

b.php

b.php

369 ms

00002.gif

00002.gif

8 ms

icon-sidenavi01.png

icon-sidenavi01.png

1553 ms

icon-arrow.png

icon-arrow.png

1608 ms

widgets.js

widgets.js

16 ms

bg-footer.jpg

bg-footer.jpg

2001 ms

icon-access.png

icon-access.png

1715 ms

icon-footernavi.png

icon-footernavi.png

1701 ms

bg-prnavi.jpg

bg-prnavi.jpg

1778 ms

bg-topimage.gif

bg-topimage.gif

1867 ms

bg-topmenu.gif

bg-topmenu.gif

1855 ms

bg-topmenu-list.gif

bg-topmenu-list.gif

1887 ms

bg-header.gif

bg-header.gif

1921 ms

bg-navi.gif

bg-navi.gif

2249 ms

bg-navilist.gif

bg-navilist.gif

1988 ms

i2i.gif

i2i.gif

309 ms

2014081231385.gif

2014081231385.gif

296 ms

illegal.gif

illegal.gif

296 ms

uh.js

uh.js

529 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

22 ms

syndication

syndication

91 ms

270479669755789312

270479669755789312

190 ms

proxy.jpg

proxy.jpg

72 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css

6 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css

8 ms

b3b03cd114d12ae83822b306eb9be2e3_normal.png

b3b03cd114d12ae83822b306eb9be2e3_normal.png

46 ms

BDHzaCFCIAEyaWN.jpg:small

BDHzaCFCIAEyaWN.jpg:small

341 ms

BC3Gaa5CAAABAy_.jpg:small

BC3Gaa5CAAABAy_.jpg:small

305 ms

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

42 ms

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

98 ms

proxy.jpg

proxy.jpg

33 ms

jot.html

jot.html

2 ms

SEO Factors

matsuge-dartsdiary.com 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 Matsuge-dartsdiary.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 Matsuge-dartsdiary.com 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

matsuge-dartsdiary.com

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