Tools & Wizards About Us
yakukan.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

yakukan.jp

【公式】屋久島観光協会 世界自然遺産「屋久島」の観光・旅行情報サイト Yakushima Japan Tourism

Page Load Speed

66.1 sec in total

First Response

5.1 sec

Resources Loaded

60.5 sec

Page Rendered

439 ms

yakukan.jp screenshot

About Website

Welcome to yakukan.jp homepage info - get ready to check Yakukan best content for Japan right away, or after learning these important things about yakukan.jp

日本で初めて世界自然遺産に登録された屋久島を旅しよう。屋久島観光協会公式サイトでは、観光、グルメ、宿泊などのスポット情報、人気の縄文杉トレッキングをはじめ、登山、ダイビング、カヤックなどの各種体験・ツアー情報、屋久島への行き方、島内交通など、屋久島旅行のお役立ち情報を満載。あなたの屋久島旅行の計画にお役立てください。

Visit yakukan.jp

Key Findings

We analyzed Yakukan.jp page load time and found that the first response time was 5.1 sec and then it took 61 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 33 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

yakukan.jp performance score

0

Network Requests Diagram

yakukan.jp

5134 ms

slider.css

1558 ms

style.css

19792 ms

style_0.css

5657 ms

thickbox.css

15773 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 54% of them (52 requests) were addressed to the original Yakukan.jp, 20% (19 requests) were made to Static.xx.fbcdn.net and 14% (13 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Yakukan.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 161.0 kB (31%)

Content Size

512.3 kB

After Optimization

351.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yakukan.jp main page is 512.3 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. 60% of websites need less resources to load. Images take 291.2 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 26.1 kB

  • Original 35.1 kB
  • After minification 30.3 kB
  • After compression 9.0 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 4.8 kB, which is 14% 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 26.1 kB or 74% of the original size.

Image Optimization

-0%

Potential reduce by 534 B

  • Original 291.2 kB
  • After minification 290.7 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. Yakukan images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 60.3 kB

  • Original 95.5 kB
  • After minification 72.9 kB
  • After compression 35.3 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 60.3 kB or 63% of the original size.

CSS Optimization

-82%

Potential reduce by 74.1 kB

  • Original 90.4 kB
  • After minification 73.0 kB
  • After compression 16.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. Yakukan.jp needs all CSS files to be minified and compressed as it can save up to 74.1 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

61

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yakukan. 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 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

yakukan.jp

yakukan.jp

5134 ms

slider.css

slider.css

1558 ms

style.css

style.css

19792 ms

style_0.css

style_0.css

5657 ms

thickbox.css

thickbox.css

15773 ms

cal.css

cal.css

19791 ms

jquery.js

jquery.js

19791 ms

thickbox.js

thickbox.js

13730 ms

fg.menu.js

fg.menu.js

19790 ms

fontfloat.js

fontfloat.js

14459 ms

top.css

top.css

15394 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

17392 ms

jsapi

jsapi

30 ms

jquery.cookie.js

jquery.cookie.js

19604 ms

default.css

default.css

17040 ms

nivo-slider.css

nivo-slider.css

17263 ms

cal.js

cal.js

19473 ms

fg.menu.css

fg.menu.css

19063 ms

ui.core.css

ui.core.css

14913 ms

ui.theme.css

ui.theme.css

20136 ms

font-awesome.min.css

font-awesome.min.css

19110 ms

analytics.js

analytics.js

55 ms

logo.gif

logo.gif

2274 ms

font.gif

font.gif

397 ms

df.gif

df.gif

15992 ms

zf.gif

zf.gif

3772 ms

top_img.jpg

top_img.jpg

19973 ms

top_img2.jpg

top_img2.jpg

19973 ms

top_img3.jpg

top_img3.jpg

19971 ms

top_img4.jpg

top_img4.jpg

19970 ms

top_img5.jpg

top_img5.jpg

19971 ms

top_img6.jpg

top_img6.jpg

19970 ms

top_img7.jpg

top_img7.jpg

19970 ms

top_img8.jpg

top_img8.jpg

19969 ms

top_img9.jpg

top_img9.jpg

19968 ms

top_img10.jpg

top_img10.jpg

19965 ms

syakunage_img.jpg

syakunage_img.jpg

19964 ms

orion_yakushima_yellow.jpg

orion_yakushima_yellow.jpg

19964 ms

jal.png

jal.png

19963 ms

yakushima220-30.jpg

yakushima220-30.jpg

19964 ms

kaiinn.png

kaiinn.png

19962 ms

bannerad.png

bannerad.png

19961 ms

recruit.png

recruit.png

19959 ms

donation.png

donation.png

19958 ms

capinnovation3.jpg

capinnovation3.jpg

19955 ms

anboshinjiyama.jpg

anboshinjiyama.jpg

19955 ms

shimaitoko.jpg

shimaitoko.jpg

19956 ms

yamazuki2.png

yamazuki2.png

19956 ms

yakushimabito.png

yakushimabito.png

19956 ms

aquastyle.jpg

aquastyle.jpg

19956 ms

220_80.gif

220_80.gif

19954 ms

sdk.js

sdk.js

113 ms

collect

collect

260 ms

loading.gif

loading.gif

19836 ms

264 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

20383 ms

xd_arbiter.php

xd_arbiter.php

127 ms

xd_arbiter.php

xd_arbiter.php

138 ms

page.php

page.php

198 ms

82F_t5lLrzg.css

82F_t5lLrzg.css

50 ms

PKZMFIxHiFI.css

PKZMFIxHiFI.css

59 ms

D2ZmywQcH_r.css

D2ZmywQcH_r.css

70 ms

_ckaNY0tjun.css

_ckaNY0tjun.css

101 ms

SRSW8M763HA.js

SRSW8M763HA.js

100 ms

ldIMPsSoKmy.js

ldIMPsSoKmy.js

100 ms

y97Ig99UVTs.js

y97Ig99UVTs.js

80 ms

KHAtULXOQuz.js

KHAtULXOQuz.js

79 ms

W4NL_XloU4d.js

W4NL_XloU4d.js

74 ms

eACiSk3I2K6.js

eACiSk3I2K6.js

357 ms

FOagnU9QnXq.js

FOagnU9QnXq.js

93 ms

rR4Qw0p7TFQ.js

rR4Qw0p7TFQ.js

374 ms

ULtnh-HfQSw.js

ULtnh-HfQSw.js

371 ms

6IFzBT9uHU-.js

6IFzBT9uHU-.js

372 ms

12047108_408345842709233_3540107767256016447_n.jpg

12047108_408345842709233_3540107767256016447_n.jpg

364 ms

12924573_468605943349889_7720577409533592395_n.jpg

12924573_468605943349889_7720577409533592395_n.jpg

330 ms

12938178_467915666752250_8533117840009802572_n.jpg

12938178_467915666752250_8533117840009802572_n.jpg

332 ms

12928255_467918473418636_7541626027675780837_n.jpg

12928255_467918473418636_7541626027675780837_n.jpg

330 ms

12920365_467505300126620_8245448387252323425_n.jpg

12920365_467505300126620_8245448387252323425_n.jpg

349 ms

934125_466800993530384_3766376046159996834_n.jpg

934125_466800993530384_3766376046159996834_n.jpg

348 ms

12924443_466801103530373_2105272902703411480_n.jpg

12924443_466801103530373_2105272902703411480_n.jpg

329 ms

12801638_466801123530371_4314760344895486335_n.jpg

12801638_466801123530371_4314760344895486335_n.jpg

340 ms

12961740_466801143530369_4243385698619544580_n.jpg

12961740_466801143530369_4243385698619544580_n.jpg

332 ms

12472364_464370450440105_2147071174517108727_n.jpg

12472364_464370450440105_2147071174517108727_n.jpg

347 ms

943817_464370477106769_4335846703303044385_n.jpg

943817_464370477106769_4335846703303044385_n.jpg

338 ms

12923217_464370533773430_608763176365073934_n.jpg

12923217_464370533773430_608763176365073934_n.jpg

339 ms

12718027_464370577106759_5197422791197496393_n.jpg

12718027_464370577106759_5197422791197496393_n.jpg

359 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

302 ms

1JLnMyDN79z.png

1JLnMyDN79z.png

294 ms

gm-8CYVMZ_l.png

gm-8CYVMZ_l.png

300 ms

VXcANLwwL5J.js

VXcANLwwL5J.js

18 ms

i8XO-4kv8i7.js

i8XO-4kv8i7.js

18 ms

75 ms

fontawesome-webfont.ttf

fontawesome-webfont.ttf

13068 ms

81 ms

61 ms

65 ms

SEO Factors

yakukan.jp SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yakukan.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Yakukan.jp 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

yakukan.jp

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