Tools & Wizards About Us
hakone-iori.jp screenshot

Report Summary

  • 75

    Performance

    Renders faster than
    83% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

hakone-iori.jp

箱根でそば打ちができる蕎麦屋［箱根乃庵］

Page Load Speed

3.7 sec in total

First Response

747 ms

Resources Loaded

2.7 sec

Page Rendered

314 ms

hakone-iori.jp screenshot

About Website

Visit hakone-iori.jp now to see the best up-to-date Hakone Iori content and also check out these interesting facts you probably never knew about hakone-iori.jp

神奈川県箱根(入生田)・香川に展開している手打ちそば屋、箱根乃庵です。そば打ち体験も行なっておりますので、ご自分で打った蕎麦もお召し上がりいただけます。そばは最高級蕎麦粉を使用し、挽きたて、打ち立て、茹で立てのそばにこだわり、おいしい天ぷらや季節の和え物と一緒にご提供しております。近くにお越しの際はぜひお越しください。

Visit hakone-iori.jp

Key Findings

We analyzed Hakone-iori.jp page load time and found that the first response time was 747 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

hakone-iori.jp performance score

75

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

34/100

25%

SI (Speed Index)

Value4.5 s

72/100

10%

TBT (Total Blocking Time)

Value140 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.0 s

88/100

10%

Network Requests Diagram

hakone-iori.jp

747 ms

import.css

341 ms

jquery.js

843 ms

tab.js

345 ms

heightLine.js

354 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 95% of them (39 requests) were addressed to the original Hakone-iori.jp, 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Hakone-iori.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 86.2 kB (12%)

Content Size

701.8 kB

After Optimization

615.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-74%

Potential reduce by 5.5 kB

  • Original 7.5 kB
  • After minification 6.1 kB
  • After compression 2.0 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.4 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 5.5 kB or 74% of the original size.

Image Optimization

-1%

Potential reduce by 6.8 kB

  • Original 575.4 kB
  • After minification 568.6 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. Hakone Iori images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 48.5 kB

  • Original 87.8 kB
  • After minification 82.5 kB
  • After compression 39.4 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 48.5 kB or 55% of the original size.

CSS Optimization

-82%

Potential reduce by 25.4 kB

  • Original 31.2 kB
  • After minification 19.7 kB
  • After compression 5.7 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. Hakone-iori.jp needs all CSS files to be minified and compressed as it can save up to 25.4 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

39

After Optimization

29

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hakone-iori.jp

hakone-iori.jp

747 ms

import.css

import.css

341 ms

jquery.js

jquery.js

843 ms

tab.js

tab.js

345 ms

heightLine.js

heightLine.js

354 ms

yuga.js

yuga.js

532 ms

reset.css

reset.css

187 ms

base.css

base.css

506 ms

nav.css

nav.css

179 ms

custom.css

custom.css

364 ms

top.css

top.css

350 ms

cal.css

cal.css

371 ms

jquery.lightbox-0.5.css

jquery.lightbox-0.5.css

371 ms

ga.js

ga.js

49 ms

bg.jpg

bg.jpg

371 ms

head_bg.jpg

head_bg.jpg

174 ms

logo.jpg

logo.jpg

179 ms

tel.jpg

tel.jpg

338 ms

main_img.jpg

main_img.jpg

879 ms

gnav_bg.jpg

gnav_bg.jpg

170 ms

gnav_01.jpg

gnav_01.jpg

338 ms

gnav_02.jpg

gnav_02.jpg

344 ms

gnav_03.jpg

gnav_03.jpg

355 ms

gnav_05.jpg

gnav_05.jpg

506 ms

gnav_06.jpg

gnav_06.jpg

506 ms

bnr_01.jpg

bnr_01.jpg

686 ms

bnr_03.jpg

bnr_03.jpg

707 ms

btn_bg.jpg

btn_bg.jpg

1108 ms

btn_01.jpg

btn_01.jpg

672 ms

btn_03.jpg

btn_03.jpg

673 ms

foot_bg.jpg

foot_bg.jpg

841 ms

gnav_01_o.jpg

gnav_01_o.jpg

856 ms

gnav_02_o.jpg

gnav_02_o.jpg

858 ms

gnav_03_o.jpg

gnav_03_o.jpg

885 ms

gnav_05_o.jpg

gnav_05_o.jpg

1010 ms

gnav_06_o.jpg

gnav_06_o.jpg

1024 ms

bnr_01_o.jpg

bnr_01_o.jpg

1030 ms

bnr_03_o.jpg

bnr_03_o.jpg

1051 ms

btn_01_o.jpg

btn_01_o.jpg

1063 ms

btn_03_o.jpg

btn_03_o.jpg

1177 ms

__utm.gif

__utm.gif

16 ms

Accessibility Review

hakone-iori.jp accessibility score

93

Accessibility Issues

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

Best Practices

hakone-iori.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

hakone-iori.jp SEO score

75

Search Engine Optimization Advices

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 Hakone-iori.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 Hakone-iori.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

hakone-iori.jp

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