Tools & Wizards About Us
fujisan-3776.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

fujisan-3776.jp

世界遺産 富士山｜富士山世界文化遺産登録推進両県合同会議

Page Load Speed

11.9 sec in total

First Response

1.5 sec

Resources Loaded

10 sec

Page Rendered

452 ms

fujisan-3776.jp screenshot

About Website

Click here to check amazing Fujisan 3776 content for Japan. Otherwise, check out these important facts you probably never knew about fujisan-3776.jp

世界文化遺産富士山の顕著な普遍的価値や保全の取り組み、各種調査結果や各会議の会議資料などを紹介しています。

Visit fujisan-3776.jp

Key Findings

We analyzed Fujisan-3776.jp page load time and found that the first response time was 1.5 sec and then it took 10.5 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

fujisan-3776.jp performance score

0

Network Requests Diagram

fujisan-3776.jp

1462 ms

default.css

1164 ms

shared.css

1770 ms

edit.css

1556 ms

jquery.js

1249 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 97% of them (61 requests) were addressed to the original Fujisan-3776.jp, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.2 sec) belongs to the original domain Fujisan-3776.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 275.9 kB (22%)

Content Size

1.3 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fujisan-3776.jp main page is 1.3 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. 20% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 8.6 kB

  • Original 12.0 kB
  • After minification 11.8 kB
  • After compression 3.4 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 8.6 kB or 72% of the original size.

Image Optimization

-14%

Potential reduce by 154.5 kB

  • Original 1.1 MB
  • After minification 937.1 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, Fujisan 3776 needs image optimization as it can save up to 154.5 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-59%

Potential reduce by 85.9 kB

  • Original 145.2 kB
  • After minification 138.6 kB
  • After compression 59.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 85.9 kB or 59% of the original size.

CSS Optimization

-86%

Potential reduce by 26.9 kB

  • Original 31.4 kB
  • After minification 20.9 kB
  • After compression 4.5 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. Fujisan-3776.jp needs all CSS files to be minified and compressed as it can save up to 26.9 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (35%)

Requests Now

62

After Optimization

40

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fujisan-3776.jp

fujisan-3776.jp

1462 ms

default.css

default.css

1164 ms

shared.css

shared.css

1770 ms

edit.css

edit.css

1556 ms

jquery.js

jquery.js

1249 ms

gd.js

gd.js

2581 ms

setting_head.js

setting_head.js

2170 ms

ga.js

ga.js

1359 ms

setting_body.js

setting_body.js

1457 ms

easing.js

easing.js

1550 ms

timers.js

timers.js

1462 ms

gallery.js

gallery.js

1751 ms

setting_onload.js

setting_onload.js

1670 ms

ga.js

ga.js

15 ms

hlogo_top.png

hlogo_top.png

418 ms

hnavi_ja.png

hnavi_ja.png

199 ms

hnavi_en.png

hnavi_en.png

202 ms

hnavi_fr.png

hnavi_fr.png

213 ms

hnavi_zh-CN.png

hnavi_zh-CN.png

202 ms

hnavi_zh-TW.png

hnavi_zh-TW.png

210 ms

hnavi_ko.png

hnavi_ko.png

396 ms

gallery_btn.gif

gallery_btn.gif

402 ms

image01.jpg

image01.jpg

4695 ms

image02.jpg

image02.jpg

5936 ms

image03.jpg

image03.jpg

3262 ms

image04.jpg

image04.jpg

6162 ms

image05.jpg

image05.jpg

2487 ms

topics_ttl.png

topics_ttl.png

624 ms

topics_list.png

topics_list.png

833 ms

rss_btn.png

rss_btn.png

1042 ms

position_map.png

position_map.png

1705 ms

banner_intro.png

banner_intro.png

2124 ms

live_shizuoka_bnr.gif

live_shizuoka_bnr.gif

2332 ms

live_yamanashi_bnr.gif

live_yamanashi_bnr.gif

2542 ms

mtfuji_bnr.gif

mtfuji_bnr.gif

2686 ms

mtfuji_facebook_bnr.gif

mtfuji_facebook_bnr.gif

2750 ms

3776fuji_bnr.gif

3776fuji_bnr.gif

2887 ms

fnavi_sitemap.png

fnavi_sitemap.png

2959 ms

fnavi_links.png

fnavi_links.png

3086 ms

jimu_yamanashi.gif

jimu_yamanashi.gif

3167 ms

jimu_shizuoka.gif

jimu_shizuoka.gif

3287 ms

wrapper_bg.png

wrapper_bg.png

3580 ms

gallery_bg.png

gallery_bg.png

3465 ms

gnavi_top_bg.png

gnavi_top_bg.png

3483 ms

gnavi_top.png

gnavi_top.png

4954 ms

box_txt_bg.png

box_txt_bg.png

3683 ms

topics_bg.png

topics_bg.png

3787 ms

topics_cnt_bg.png

topics_cnt_bg.png

3884 ms

list_icon.gif

list_icon.gif

3996 ms

position_bg.png

position_bg.png

4083 ms

__utm.gif

__utm.gif

13 ms

fnavi_bg.png

fnavi_bg.png

4019 ms

address_bg.gif

address_bg.gif

4095 ms

onavi_1_off.gif

onavi_1_off.gif

4223 ms

onavi_1_on.gif

onavi_1_on.gif

4288 ms

onavi_2_off.gif

onavi_2_off.gif

4422 ms

onavi_2_on.gif

onavi_2_on.gif

4302 ms

onavi_3_off.gif

onavi_3_off.gif

4442 ms

onavi_3_on.gif

onavi_3_on.gif

4478 ms

onavi_4_off.gif

onavi_4_off.gif

4273 ms

onavi_4_on.gif

onavi_4_on.gif

4217 ms

onavi_5_off.gif

onavi_5_off.gif

4052 ms

onavi_5_on.gif

onavi_5_on.gif

3394 ms

SEO Factors

fujisan-3776.jp 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 Fujisan-3776.jp 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 Fujisan-3776.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

fujisan-3776.jp

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