Tools & Wizards About Us
dyog.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

dyog.jp

dyogBlog

Page Load Speed

6.7 sec in total

First Response

949 ms

Resources Loaded

4.7 sec

Page Rendered

1.1 sec

dyog.jp screenshot

About Website

Visit dyog.jp now to see the best up-to-date Dyog content for Japan and also check out these interesting facts you probably never knew about dyog.jp

dyogを使うと、アウトドアギアのリストを作って共有することができます。キャンプ、ハイキング、バックパッキングなどに使うことができます。

Visit dyog.jp

Key Findings

We analyzed Dyog.jp page load time and found that the first response time was 949 ms and then it took 5.8 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

dyog.jp performance score

0

Network Requests Diagram

dyog.jp

949 ms

all.css

350 ms

all.js

923 ms

plusone.js

62 ms

bookmark_button.js

373 ms

Our browser made a total of 131 requests to load all elements on the main page. We found that 60% of them (79 requests) were addressed to the original Dyog.jp, 9% (12 requests) were made to Static.xx.fbcdn.net and 6% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Dyog.jp.

Page Optimization Overview & Recommendations

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

Content Size

1.2 MB

After Optimization

663.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 136.2 kB

  • Original 169.3 kB
  • After minification 161.9 kB
  • After compression 33.2 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 136.2 kB or 80% of the original size.

Image Optimization

-5%

Potential reduce by 25.3 kB

  • Original 538.9 kB
  • After minification 513.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. Dyog images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 318.8 kB

  • Original 427.4 kB
  • After minification 341.8 kB
  • After compression 108.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 318.8 kB or 75% of the original size.

CSS Optimization

-83%

Potential reduce by 38.3 kB

  • Original 46.2 kB
  • After minification 29.7 kB
  • After compression 7.8 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. Dyog.jp needs all CSS files to be minified and compressed as it can save up to 38.3 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

129

After Optimization

91

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dyog.jp

dyog.jp

949 ms

all.css

all.css

350 ms

all.js

all.js

923 ms

plusone.js

plusone.js

62 ms

bookmark_button.js

bookmark_button.js

373 ms

all.js

all.js

164 ms

ga.js

ga.js

113 ms

delay=5

delay=5

239 ms

41V8PIlwG4L._SL75_.jpg

41V8PIlwG4L._SL75_.jpg

90 ms

button-only.gif

button-only.gif

183 ms

delay=5

delay=5

255 ms

bg-new.png

bg-new.png

1137 ms

logo.png

logo.png

401 ms

twitter_signin_01.png

twitter_signin_01.png

182 ms

bg-spacer.gif

bg-spacer.gif

400 ms

dyog_pack.png

dyog_pack.png

754 ms

feature.png

feature.png

642 ms

%E3%82%B3%E3%83%BC%E3%83%92%E3%83%BC%E3%83%BB%E3%81%8A%E8%8C%B6.png

%E3%82%B3%E3%83%BC%E3%83%92%E3%83%BC%E3%83%BB%E3%81%8A%E8%8C%B6.png

401 ms

feature.png

feature.png

641 ms

%E3%83%95%E3%82%A1%E3%83%BC%E3%82%B9%E3%83%88%E3%82%A8%E3%82%A4%E3%83%89.png

%E3%83%95%E3%82%A1%E3%83%BC%E3%82%B9%E3%83%88%E3%82%A8%E3%82%A4%E3%83%89.png

642 ms

sanpo2.png

sanpo2.png

644 ms

Kawaemoon.png

Kawaemoon.png

765 ms

wadatchi.png

wadatchi.png

768 ms

nasiadm.png

nasiadm.png

768 ms

hinoharuto.png

hinoharuto.png

771 ms

en.png

en.png

922 ms

jp.png

jp.png

947 ms

thumb.png

thumb.png

949 ms

thumb.png

thumb.png

952 ms

thumb.png

thumb.png

962 ms

thumb.png

thumb.png

1103 ms

thumb.png

thumb.png

1130 ms

thumb.png

thumb.png

1133 ms

thumb.png

thumb.png

1135 ms

thumb.png

thumb.png

1148 ms

thumb.png

thumb.png

1284 ms

thumb.png

thumb.png

1366 ms

thumb.png

thumb.png

1365 ms

thumb.png

thumb.png

1366 ms

medium.png

medium.png

1367 ms

warashibechota.png

warashibechota.png

1367 ms

medium.png

medium.png

1475 ms

hwgytn.png

hwgytn.png

1478 ms

takeo710.png

takeo710.png

1489 ms

t_407.png

t_407.png

1498 ms

mon6_hime.png

mon6_hime.png

1519 ms

51ULFB5MRiL._SL75_.jpg

51ULFB5MRiL._SL75_.jpg

81 ms

515resvhm7L._SL75_.jpg

515resvhm7L._SL75_.jpg

77 ms

41Mjg-bMbgL._SL160_.jpg

41Mjg-bMbgL._SL160_.jpg

78 ms

41ItD9CY24L._SL160_.jpg

41ItD9CY24L._SL160_.jpg

79 ms

cinuxjp.png

cinuxjp.png

1457 ms

__utm.gif

__utm.gif

16 ms

gen_fU.png

gen_fU.png

1484 ms

yssm184.png

yssm184.png

1259 ms

kazecco_.png

kazecco_.png

1276 ms

tweet_button.html

tweet_button.html

24 ms

atstgm.png

atstgm.png

1268 ms

jot

jot

202 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

67 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

65 ms

fastbutton

fastbutton

162 ms

244 ms

227 ms

xd_arbiter.php

xd_arbiter.php

183 ms

xd_arbiter.php

xd_arbiter.php

332 ms

turedure_camp.png

turedure_camp.png

1072 ms

sei_bold.png

sei_bold.png

1084 ms

windabeam.png

windabeam.png

1187 ms

mitsutanaka3.png

mitsutanaka3.png

1202 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

99 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

100 ms

postmessageRelay

postmessageRelay

87 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

48 ms

gonatmark.png

gonatmark.png

1104 ms

kucch.png

kucch.png

1108 ms

contrail0913.png

contrail0913.png

1129 ms

kimatsu.png

kimatsu.png

1144 ms

timetriper.png

timetriper.png

1231 ms

reset.css

reset.css

17 ms

entry-button.css

entry-button.css

25 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

31 ms

rpc:shindig_random.js

rpc:shindig_random.js

34 ms

like.php

like.php

126 ms

button-counter.gif

button-counter.gif

20 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

13 ms

like_box.php

like_box.php

165 ms

yasuyo_sting.png

yasuyo_sting.png

1103 ms

wy1X4hBW7e7.js

wy1X4hBW7e7.js

309 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

262 ms

kim_tack.png

kim_tack.png

1088 ms

djsawacamp.png

djsawacamp.png

1106 ms

koji_murao.png

koji_murao.png

1130 ms

notechg.png

notechg.png

1134 ms

SwWqNEM2GQB.css

SwWqNEM2GQB.css

188 ms

qfDTH5pB6Ut.css

qfDTH5pB6Ut.css

189 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

230 ms

ehA1CqzHyzE.js

ehA1CqzHyzE.js

269 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

222 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

226 ms

brutus_misc.png

brutus_misc.png

1072 ms

yos44162001.png

yos44162001.png

1076 ms

ushimas.png

ushimas.png

1084 ms

juqcho_jp.png

juqcho_jp.png

1106 ms

Kawaemoon.png

Kawaemoon.png

1130 ms

northmanstyle.png

northmanstyle.png

1134 ms

sanpo2.png

sanpo2.png

1063 ms

189301_176787442368048_6102987_n.jpg

189301_176787442368048_6102987_n.jpg

352 ms

1382017_10151976542486178_2064649846_n.jpg

1382017_10151976542486178_2064649846_n.jpg

451 ms

163529_464789473597023_1261601901_n.jpg

163529_464789473597023_1261601901_n.jpg

472 ms

10354686_10150004552801856_220367501106153455_n.jpg

10354686_10150004552801856_220367501106153455_n.jpg

470 ms

319986_137055183055146_2321753_n.jpg

319986_137055183055146_2321753_n.jpg

515 ms

308518_1581875912138538_8433678695259151312_n.jpg

308518_1581875912138538_8433678695259151312_n.jpg

475 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

53 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

51 ms

taorhashi.png

taorhashi.png

1022 ms

sashimi399.png

sashimi399.png

1028 ms

dirtnp.png

dirtnp.png

1055 ms

so_ooo.png

so_ooo.png

1084 ms

key317.png

key317.png

1100 ms

HAN_LTZ.png

HAN_LTZ.png

1043 ms

yamatoasukakun.png

yamatoasukakun.png

1089 ms

arzac_.png

arzac_.png

1084 ms

akkyal.png

akkyal.png

1106 ms

ma_tomacha3.png

ma_tomacha3.png

1116 ms

amazon_logo.png

amazon_logo.png

1122 ms

rss_icon.png

rss_icon.png

1039 ms

brand-banner-dyog-2.png

brand-banner-dyog-2.png

1273 ms

loading.gif

loading.gif

1084 ms

closelabel.gif

closelabel.gif

1106 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

46 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

81 ms

SEO Factors

dyog.jp SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dyog.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Dyog.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

dyog.jp

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