Tools & Wizards About Us
fujiyamasan.com screenshot

Report Summary

  • 86

    Performance

    Renders faster than
    89% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

fujiyamasan.com

富士山観光情報 FUJIYAMA JAPAN | 静岡県・山梨県・富士山周辺観光情報　Fujiyama Sightseeing Information

Page Load Speed

23.6 sec in total

First Response

62 ms

Resources Loaded

23 sec

Page Rendered

543 ms

fujiyamasan.com screenshot

About Website

Visit fujiyamasan.com now to see the best up-to-date FUJIYAMA San content for Japan and also check out these interesting facts you probably never knew about fujiyamasan.com

コンテンツ 静岡県、山梨県、富士山周辺の観光情報サイト - 観光施設、大自然・景勝地、道の駅、温泉・銭湯、グルメ、観光イベント、交通事情、宿泊、富士山 観光 静岡県 朝霧フィールドドッグスガーデン / いでぼく / エスパルスドリームプラザ

Visit fujiyamasan.com

Key Findings

We analyzed Fujiyamasan.com page load time and found that the first response time was 62 ms and then it took 23.5 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.

Performance Metrics

fujiyamasan.com performance score

86

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

83/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.8 s

97/100

10%

Network Requests Diagram

fujiyamasan.com

62 ms

fujiyamasan.com

1585 ms

fontawesome-webfont.woff

1532 ms

icomoon.woff

1051 ms

fuji-gcecf4d971_1280.jpg

1793 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that all of those requests were addressed to Fujiyamasan.com and no external sources were called. The less responsive or slowest element that took the longest time to load (19.7 sec) belongs to the original domain Fujiyamasan.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 617.1 kB (61%)

Content Size

1.0 MB

After Optimization

392.4 kB

  • HTML
  • Images

In fact, the total size of Fujiyamasan.com main page is 1.0 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. HTML takes 722.3 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 617.1 kB

  • Original 722.3 kB
  • After minification 722.3 kB
  • After compression 105.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 617.1 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 287.2 kB
  • After minification 287.2 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. FUJIYAMA San images are well optimized though.

Requests Breakdown

We found no issues to fix!

Requests Now

9

After Optimization

9

  • Images

The browser has sent 9 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FUJIYAMA San. According to our analytics all requests are already optimized.

Network Requests Diagram

fujiyamasan.com

fujiyamasan.com

62 ms

fujiyamasan.com

fujiyamasan.com

1585 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1532 ms

icomoon.woff

icomoon.woff

1051 ms

fuji-gcecf4d971_1280.jpg

fuji-gcecf4d971_1280.jpg

1793 ms

a0007_000172-120x68.jpg

a0007_000172-120x68.jpg

787 ms

4848204446_2b7fdf98f4_m.jpg

4848204446_2b7fdf98f4_m.jpg

19747 ms

9474602545_cdbeb8de6b_o-120x68.jpg

9474602545_cdbeb8de6b_o-120x68.jpg

1511 ms

racingpalace.jpg

racingpalace.jpg

1043 ms

hakushuu01.jpg

hakushuu01.jpg

1753 ms

%E7%99%BD%E7%B3%B8%E3%81%AE%E6%BB%9D-120x68.jpg

%E7%99%BD%E7%B3%B8%E3%81%AE%E6%BB%9D-120x68.jpg

1566 ms

ojiragawa1.jpg

ojiragawa1.jpg

2304 ms

2372570_s-120x68.jpg

2372570_s-120x68.jpg

2321 ms

4848655836_781757a80f_m.jpg

4848655836_781757a80f_m.jpg

2583 ms

Accessibility Review

fujiyamasan.com accessibility score

98

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

fujiyamasan.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

fujiyamasan.com SEO score

100

Search Engine Optimization Advices

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

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 Fujiyamasan.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 Fujiyamasan.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

fujiyamasan.com

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