Tools & Wizards About Us
oshino.jp screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

oshino.jp

忍野八海 - 山中湖観光情報

Page Load Speed

6.5 sec in total

First Response

753 ms

Resources Loaded

5 sec

Page Rendered

702 ms

oshino.jp screenshot

About Website

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

山中湖の最新の観光情報を提供するサイト「山中湖観光情報」。民宿やペンション、ホテルなどの宿探しから紅富士の湯や石割の湯の温泉ガイド、ブラックバス釣りやわかさぎ釣り等のフィッシング情報、ダイヤモンド富士情報、山中湖で行われる最新のイベント情報、山中湖の駐車場や公衆トイレマップ、人気の富士山のフォトギャラリーや富士山の無料壁紙等。その他ハイキング等のアウトドア情報、白鳥情報や紅葉情報、桜の開花情報、富...

Visit oshino.jp

Key Findings

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

oshino.jp performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value220 ms

88/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value6.7 s

56/100

10%

Network Requests Diagram

oshino.jp

753 ms

8lakes_top.php

2051 ms

js

68 ms

jquery.min.js

25 ms

reset.css

433 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Oshino.jp, 88% (23 requests) were made to Yamanakako.info and 4% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Yamanakako.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 107.1 kB (10%)

Content Size

1.0 MB

After Optimization

917.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oshino.jp 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. Images take 928.6 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 17.2 kB

  • Original 23.3 kB
  • After minification 19.9 kB
  • After compression 6.1 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.4 kB, which is 15% 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 17.2 kB or 74% of the original size.

Image Optimization

-6%

Potential reduce by 57.5 kB

  • Original 928.6 kB
  • After minification 871.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. Oshino images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 1.5 kB

  • Original 35.4 kB
  • After minification 34.7 kB
  • After compression 33.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-84%

Potential reduce by 30.9 kB

  • Original 36.9 kB
  • After minification 28.4 kB
  • After compression 6.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. Oshino.jp needs all CSS files to be minified and compressed as it can save up to 30.9 kB or 84% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

24

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oshino.jp

oshino.jp

753 ms

8lakes_top.php

8lakes_top.php

2051 ms

js

js

68 ms

jquery.min.js

jquery.min.js

25 ms

reset.css

reset.css

433 ms

yamanakako_common_res.css

yamanakako_common_res.css

1073 ms

yamanakako_sisetsu_res.css

yamanakako_sisetsu_res.css

651 ms

logo.png

logo.png

832 ms

2.png

2.png

627 ms

4.png

4.png

646 ms

1.png

1.png

649 ms

menu-24.png

menu-24.png

834 ms

hakkai_top.jpg

hakkai_top.jpg

1925 ms

deguchi_ike.jpg

deguchi_ike.jpg

1509 ms

okama_ike.jpg

okama_ike.jpg

1515 ms

sokonashi_ike.jpg

sokonashi_ike.jpg

1265 ms

tyoshi_ike.jpg

tyoshi_ike.jpg

1698 ms

waku_ike.jpg

waku_ike.jpg

1885 ms

nigori_ike.jpg

nigori_ike.jpg

1700 ms

kagami_ike.jpg

kagami_ike.jpg

1939 ms

classie.js

classie.js

1557 ms

syobu_ike.jpg

syobu_ike.jpg

1957 ms

hakkaimap.gif

hakkaimap.gif

1960 ms

reijyo.jpg

reijyo.jpg

2207 ms

arrowtop.png

arrowtop.png

1923 ms

background_common.gif

background_common.gif

1103 ms

Accessibility Review

oshino.jp accessibility score

70

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Best Practices

oshino.jp best practices score

67

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

SEO Factors

oshino.jp SEO score

92

Search Engine Optimization Advices

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

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

    N/A

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oshino.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Oshino.jp main page’s claimed encoding is euc-jp. 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

oshino.jp

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