Tools & Wizards About Us
kawakamian.com screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

kawakamian.com

川上庵｜蕎麦・そば（軽井沢・青山・麻布十番）

Page Load Speed

8.5 sec in total

First Response

1.1 sec

Resources Loaded

7.3 sec

Page Rendered

86 ms

kawakamian.com screenshot

About Website

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

蕎麦（そば）『川上庵』公式サイト。軽井沢、青山（表参道）、麻布（麻布十番）の蕎麦（そば）・和食ダイニング。ランチ、コースもあります。

Visit kawakamian.com

Key Findings

We analyzed Kawakamian.com page load time and found that the first response time was 1.1 sec and then it took 7.4 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

kawakamian.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

21/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value380 ms

69/100

30%

CLS (Cumulative Layout Shift)

Value0.169

70/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

kawakamian.com

1068 ms

top.css

499 ms

jquery.min.js

6 ms

jquery.ticker.js

674 ms

scrollsmoothly.js

352 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 75% of them (54 requests) were addressed to the original Kawakamian.com, 11% (8 requests) were made to Apis.google.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Kawakamian.com.

Page Optimization Overview & Recommendations

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

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kawakamian.com main page is 1.2 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. 45% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 32.9 kB

  • Original 37.9 kB
  • After minification 37.0 kB
  • After compression 5.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. 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 32.9 kB or 87% of the original size.

Image Optimization

-4%

Potential reduce by 43.4 kB

  • Original 1.1 MB
  • After minification 1.1 MB

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. Kawakamian images are well optimized though.

JavaScript Optimization

-29%

Potential reduce by 23.9 kB

  • Original 82.3 kB
  • After minification 73.0 kB
  • After compression 58.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 23.9 kB or 29% of the original size.

CSS Optimization

-83%

Potential reduce by 20.8 kB

  • Original 25.1 kB
  • After minification 21.0 kB
  • After compression 4.3 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. Kawakamian.com needs all CSS files to be minified and compressed as it can save up to 20.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (18%)

Requests Now

71

After Optimization

58

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kawakamian.com

kawakamian.com

1068 ms

top.css

top.css

499 ms

jquery.min.js

jquery.min.js

6 ms

jquery.ticker.js

jquery.ticker.js

674 ms

scrollsmoothly.js

scrollsmoothly.js

352 ms

common.css

common.css

711 ms

ga.js

ga.js

13 ms

img_opening.gif

img_opening.gif

174 ms

img_top01_1.jpg

img_top01_1.jpg

469 ms

img_top01_2.jpg

img_top01_2.jpg

471 ms

img_top01_3.jpg

img_top01_3.jpg

504 ms

img_top01_4.jpg

img_top01_4.jpg

502 ms

img_top01_5.jpg

img_top01_5.jpg

500 ms

img_top01_6.jpg

img_top01_6.jpg

660 ms

img_top01_7.jpg

img_top01_7.jpg

1094 ms

img_top01_on.png

img_top01_on.png

799 ms

img_top02_1.jpg

img_top02_1.jpg

1135 ms

img_top02_2.jpg

img_top02_2.jpg

1349 ms

img_top02_3.jpg

img_top02_3.jpg

1221 ms

img_top03_1_off.jpg

img_top03_1_off.jpg

1275 ms

img_top03_2.jpg

img_top03_2.jpg

1572 ms

img_top03_3.jpg

img_top03_3.jpg

1765 ms

img_top03_4.jpg

img_top03_4.jpg

1789 ms

img_top03_5.jpg

img_top03_5.jpg

1889 ms

img_top03_on.png

img_top03_on.png

1604 ms

img_top04_1.jpg

img_top04_1.jpg

2227 ms

img_top04_2.jpg

img_top04_2.jpg

2183 ms

img_top04_3.jpg

img_top04_3.jpg

2511 ms

img_top04_4.jpg

img_top04_4.jpg

2648 ms

img_top04_5.jpg

img_top04_5.jpg

2611 ms

img_top04_6.jpg

img_top04_6.jpg

2720 ms

img_top04_7.jpg

img_top04_7.jpg

2947 ms

img_top04_on.png

img_top04_on.png

2556 ms

img_top05_1.jpg

img_top05_1.jpg

3336 ms

img_top05_2.jpg

img_top05_2.jpg

3217 ms

img_top05_3.jpg

img_top05_3.jpg

3426 ms

img_top05_4.jpg

img_top05_4.jpg

3411 ms

img_top05_on.png

img_top05_on.png

3034 ms

img_top06_1.jpg

img_top06_1.jpg

3619 ms

img_top06_2.jpg

img_top06_2.jpg

3693 ms

img_top06_3.jpg

img_top06_3.jpg

4049 ms

img_top06_4.jpg

img_top06_4.jpg

4220 ms

all.js

all.js

273 ms

img_top06_5.jpg

img_top06_5.jpg

4181 ms

plusone.js

plusone.js

72 ms

__utm.gif

__utm.gif

21 ms

widgets.js

widgets.js

165 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

8 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

18 ms

fastbutton

fastbutton

77 ms

postmessageRelay

postmessageRelay

30 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

28 ms

rpc:shindig_random.js

rpc:shindig_random.js

36 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

18 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

18 ms

img_top06_on.png

img_top06_on.png

3610 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

7 ms

23 ms

xd_arbiter.php

xd_arbiter.php

215 ms

xd_arbiter.php

xd_arbiter.php

423 ms

img_top07_1.jpg

img_top07_1.jpg

3776 ms

img_top07_2.jpg

img_top07_2.jpg

4004 ms

img_top07_3.jpg

img_top07_3.jpg

3957 ms

img_top08_1.jpg

img_top08_1.jpg

4390 ms

img_top08_2.jpg

img_top08_2.jpg

4514 ms

img_top08_3.jpg

img_top08_3.jpg

4226 ms

img_top09_1.jpg

img_top09_1.jpg

4107 ms

img_top09_2.jpg

img_top09_2.jpg

3983 ms

img_top09_3.jpg

img_top09_3.jpg

3994 ms

img_top09_4.jpg

img_top09_4.jpg

4283 ms

img_top09_on.png

img_top09_on.png

3927 ms

btn_backtotop.png

btn_backtotop.png

3911 ms

Accessibility Review

kawakamian.com accessibility score

58

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

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

kawakamian.com 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

High

Browser errors were logged to the console

SEO Factors

kawakamian.com SEO score

82

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

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

High

Tap targets are not sized appropriately

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

kawakamian.com

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