Tools & Wizards About Us
fujiginkei.jp screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

fujiginkei.jp

富士河口湖温泉郷 湖楽 | おんやど 富士吟景 | トップページ

Page Load Speed

9.7 sec in total

First Response

793 ms

Resources Loaded

8.6 sec

Page Rendered

327 ms

fujiginkei.jp screenshot

About Website

Click here to check amazing Fujiginkei content for Taiwan. Otherwise, check out these important facts you probably never knew about fujiginkei.jp

富士河口湖温泉郷 湖楽 おんやど 富士吟景は、富士山を一望出来る最高のロケーションが自慢です。温泉、客室からも迫力満点の富士山の大パノラマが広がります。

Visit fujiginkei.jp

Key Findings

We analyzed Fujiginkei.jp page load time and found that the first response time was 793 ms and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

fujiginkei.jp performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value540 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0.223

56/100

15%

TTI (Time to Interactive)

Value5.7 s

68/100

10%

Network Requests Diagram

fujiginkei.jp

793 ms

import.css

324 ms

index.css

495 ms

search.js

331 ms

jquery.js

835 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 95% of them (57 requests) were addressed to the original Fujiginkei.jp, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to 489pro.com. The less responsive or slowest element that took the longest time to load (6.6 sec) belongs to the original domain Fujiginkei.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.6 kB (16%)

Content Size

600.1 kB

After Optimization

504.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 15.0 kB

  • Original 19.8 kB
  • After minification 16.4 kB
  • After compression 4.8 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 3.5 kB, which is 18% 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 15.0 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 9.1 kB

  • Original 467.8 kB
  • After minification 458.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. Fujiginkei images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 55.0 kB

  • Original 93.0 kB
  • After minification 84.8 kB
  • After compression 38.0 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 55.0 kB or 59% of the original size.

CSS Optimization

-84%

Potential reduce by 16.5 kB

  • Original 19.5 kB
  • After minification 12.3 kB
  • After compression 3.0 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. Fujiginkei.jp needs all CSS files to be minified and compressed as it can save up to 16.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (17%)

Requests Now

59

After Optimization

49

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fujiginkei.jp

fujiginkei.jp

793 ms

import.css

import.css

324 ms

index.css

index.css

495 ms

search.js

search.js

331 ms

jquery.js

jquery.js

835 ms

yuga.js

yuga.js

709 ms

js_library.js

js_library.js

691 ms

jquerypngfix.js

jquerypngfix.js

834 ms

swf.js

swf.js

680 ms

default.css

default.css

534 ms

common.css

common.css

1014 ms

print.css

print.css

718 ms

reservation_ken.gif

reservation_ken.gif

1514 ms

a_ilst198.gif

a_ilst198.gif

553 ms

bg_header.gif

bg_header.gif

809 ms

img_logo.png

img_logo.png

1000 ms

bn_renew.gif

bn_renew.gif

485 ms

japanican_en.gif

japanican_en.gif

332 ms

japanican_kr.gif

japanican_kr.gif

371 ms

japanican_tc.gif

japanican_tc.gif

387 ms

japanican_sc.gif

japanican_sc.gif

685 ms

bn_htel.gif

bn_htel.gif

725 ms

menu_hnav.gif

menu_hnav.gif

1068 ms

bn_rin.jpg

bn_rin.jpg

1204 ms

new.jpg

new.jpg

2838 ms

bn_hujimi.jpg

bn_hujimi.jpg

1465 ms

bn_reihou.jpg

bn_reihou.jpg

1630 ms

img_13_2_20140301175726.jpg

img_13_2_20140301175726.jpg

1486 ms

img_9_2_20130704140048.jpg

img_9_2_20130704140048.jpg

1583 ms

img_8_2_20130704135906.jpg

img_8_2_20130704135906.jpg

1700 ms

bt_search.gif

bt_search.gif

1793 ms

bt_plan.png

bt_plan.png

1833 ms

img_contact.gif

img_contact.gif

2093 ms

img_mobile.gif

img_mobile.gif

2348 ms

bt_mobile.gif

bt_mobile.gif

2193 ms

bn_blog.jpg

bn_blog.jpg

2447 ms

weather.png

weather.png

2382 ms

img_flogo.png

img_flogo.png

2636 ms

bg_gmenu.gif

bg_gmenu.gif

3051 ms

menu_gmenu.gif

menu_gmenu.gif

3242 ms

planpop.png

planpop.png

3425 ms

img_roompop.png

img_roompop.png

3491 ms

img_hotspapop.png

img_hotspapop.png

3728 ms

img_diningpop.png

img_diningpop.png

3821 ms

img_welcomepop.png

img_welcomepop.png

4072 ms

img_coursepop.png

img_coursepop.png

4291 ms

bg_contents.gif

bg_contents.gif

6556 ms

bg_contents_wrap.gif

bg_contents_wrap.gif

4211 ms

bg_hujisan.png

bg_hujisan.png

4247 ms

bg_topbn.gif

bg_topbn.gif

4311 ms

ga.js

ga.js

7 ms

__utm.gif

__utm.gif

16 ms

st_plan.gif

st_plan.gif

4284 ms

icon_line_plan.gif

icon_line_plan.gif

4208 ms

st_no1.gif

st_no1.gif

4283 ms

st_no2.gif

st_no2.gif

4192 ms

st_no3.gif

st_no3.gif

4016 ms

st_news.gif

st_news.gif

4217 ms

bg_search.gif

bg_search.gif

4473 ms

bg_footer.gif

bg_footer.gif

5483 ms

Accessibility Review

fujiginkei.jp accessibility score

83

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

ARIA toggle fields do not have accessible names

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

fujiginkei.jp best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

fujiginkei.jp SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

fujiginkei.jp

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