Report Summary

  • 81

    Performance

    Renders faster than
    87% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

nanamori.jp

道の駅 ななもり清見

Page Load Speed

2.4 sec in total

First Response

421 ms

Resources Loaded

1.7 sec

Page Rendered

278 ms

nanamori.jp screenshot

About Website

Click here to check amazing Nanamori content. Otherwise, check out these important facts you probably never knew about nanamori.jp

飛騨高山観光の中継点、道の駅ななもり清見のホームページです。飛騨高山に一番近い道の駅。飛騨牛がうまいお食事処レストラン味彩七杜など、ぜひお立ち寄り下さい。

Visit nanamori.jp

Key Findings

We analyzed Nanamori.jp page load time and found that the first response time was 421 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

nanamori.jp performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.071

96/100

15%

TTI (Time to Interactive)

Value3.2 s

94/100

10%

Network Requests Diagram

nanamori.jp

421 ms

common.css

161 ms

index.css

306 ms

script.js

319 ms

htmlview.cgi

339 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 89% of them (25 requests) were addressed to the original Nanamori.jp, 7% (2 requests) were made to Google-analytics.com and 4% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (955 ms) belongs to the original domain Nanamori.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 41.4 kB (11%)

Content Size

362.0 kB

After Optimization

320.5 kB

In fact, the total size of Nanamori.jp main page is 362.0 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 295.9 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 5.1 kB

  • Original 7.3 kB
  • After minification 5.7 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 1.6 kB, which is 22% 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 5.1 kB or 70% of the original size.

Image Optimization

-0%

Potential reduce by 13 B

  • Original 295.9 kB
  • After minification 295.9 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. Nanamori images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 33.4 kB

  • Original 55.0 kB
  • After minification 54.2 kB
  • After compression 21.5 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 33.4 kB or 61% of the original size.

CSS Optimization

-76%

Potential reduce by 2.9 kB

  • Original 3.8 kB
  • After minification 2.2 kB
  • After compression 921 B

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. Nanamori.jp needs all CSS files to be minified and compressed as it can save up to 2.9 kB or 76% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

27

After Optimization

27

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

Accessibility Review

nanamori.jp accessibility score

72

Accessibility Issues

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

Best Practices

nanamori.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

nanamori.jp SEO score

69

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nanamori.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 Nanamori.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

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