Tools & Wizards About Us
inayasu.com screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

inayasu.com

ファミリーレストラン【稲安】 寿司 宴会 定食 ランチ おいしい和食 栃木 上都賀郡 西方町 金崎 東武日光線のファミレス

Page Load Speed

8 sec in total

First Response

1.4 sec

Resources Loaded

6.1 sec

Page Rendered

496 ms

inayasu.com screenshot

About Website

Click here to check amazing Inayasu content. Otherwise, check out these important facts you probably never knew about inayasu.com

栃木県の東武日光線沿いの東武金崎にある寿司、定食、割烹、宴会のファミリーレストラン「 稲安 」和食、寿司、ラーメン、丼物、定食から法事、学校、役所などの宴会まで幅広くご利用頂ける、和風ファミリーレストランです。ボリューム満点でおいしい料理、マグロ、トンカツ、お寿司、出前も承ります。

Visit inayasu.com

Key Findings

We analyzed Inayasu.com page load time and found that the first response time was 1.4 sec and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

inayasu.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value16.2 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.283

43/100

15%

TTI (Time to Interactive)

Value4.3 s

85/100

10%

Network Requests Diagram

inayasu.com

1429 ms

jquery.min.js

24 ms

smoothscroll.js

178 ms

ofi.min.js

356 ms

option.js

517 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 99% of them (76 requests) were addressed to the original Inayasu.com, 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Inayasu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 87.2 kB (3%)

Content Size

3.4 MB

After Optimization

3.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inayasu.com main page is 3.4 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 3.2 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 15.3 kB

  • Original 20.9 kB
  • After minification 20.2 kB
  • After compression 5.6 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 15.3 kB or 73% of the original size.

Image Optimization

-2%

Potential reduce by 55.3 kB

  • Original 3.2 MB
  • After minification 3.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. Inayasu images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 9.5 kB

  • Original 98.4 kB
  • After minification 98.0 kB
  • After compression 88.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

-24%

Potential reduce by 7.1 kB

  • Original 29.3 kB
  • After minification 29.3 kB
  • After compression 22.2 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. Inayasu.com needs all CSS files to be minified and compressed as it can save up to 7.1 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (41%)

Requests Now

76

After Optimization

45

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

inayasu.com

inayasu.com

1429 ms

jquery.min.js

jquery.min.js

24 ms

smoothscroll.js

smoothscroll.js

178 ms

ofi.min.js

ofi.min.js

356 ms

option.js

option.js

517 ms

style.css

style.css

519 ms

colorbox.css

colorbox.css

570 ms

style.min.css

style.min.css

541 ms

styles.css

styles.css

532 ms

jquery.js

jquery.js

710 ms

jquery-migrate.min.js

jquery-migrate.min.js

689 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

692 ms

jquery-colorbox-wrapper-min.js

jquery-colorbox-wrapper-min.js

712 ms

scripts.js

scripts.js

723 ms

wp-embed.min.js

wp-embed.min.js

746 ms

style_pc.css

style_pc.css

344 ms

style_smp.css

style_smp.css

348 ms

top.css

top.css

372 ms

blog.css

blog.css

373 ms

contact.css

contact.css

385 ms

enkai.css

enkai.css

406 ms

kodawari.css

kodawari.css

516 ms

menu.css

menu.css

520 ms

recruit.css

recruit.css

548 ms

shop.css

shop.css

551 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

178 ms

bg_head.jpg

bg_head.jpg

181 ms

sns_ico1.png

sns_ico1.png

176 ms

sns_ico2.png

sns_ico2.png

173 ms

sns_ico3.png

sns_ico3.png

179 ms

logo.png

logo.png

178 ms

menu_line.png

menu_line.png

337 ms

menu1.png

menu1.png

346 ms

menu2.png

menu2.png

519 ms

menu3.png

menu3.png

355 ms

menu4.png

menu4.png

356 ms

menu5.png

menu5.png

357 ms

menu6.png

menu6.png

514 ms

bg_wood.jpg

bg_wood.jpg

1551 ms

main_tel.png

main_tel.png

709 ms

main.png

main.png

1422 ms

main_smp.png

main_smp.png

1425 ms

bg_lunch.png

bg_lunch.png

691 ms

IMG_8344-300x225.jpeg

IMG_8344-300x225.jpeg

864 ms

bt1.png

bt1.png

1220 ms

title_news_bg_left.png

title_news_bg_left.png

886 ms

title_news_bg_right.png

title_news_bg_right.png

1038 ms

bt2.png

bt2.png

1241 ms

kodawaribn.jpg

kodawaribn.jpg

1730 ms

title_bg_top.png

title_bg_top.png

1397 ms

title_bg_bottom.png

title_bg_bottom.png

1419 ms

menu_photo1.png

menu_photo1.png

1576 ms

menu_photo2.png

menu_photo2.png

1598 ms

menu_photo3.png

menu_photo3.png

1605 ms

bg_enkai.jpg

bg_enkai.jpg

1606 ms

enkai_ico.png

enkai_ico.png

1722 ms

enkai_photo3.jpg

enkai_photo3.jpg

1753 ms

enkai_photo2.jpg

enkai_photo2.jpg

1776 ms

enkai_photo1.jpg

enkai_photo1.jpg

1782 ms

bg_shop.png

bg_shop.png

1784 ms

foot_img1.png

foot_img1.png

1760 ms

foot_photo1.jpg

foot_photo1.jpg

1747 ms

foot_logo.png

foot_logo.png

1759 ms

foot_tel.png

foot_tel.png

1781 ms

foot_takuhai.png

foot_takuhai.png

1786 ms

foot_photo2.jpg

foot_photo2.jpg

1787 ms

foot_menu_ico1.png

foot_menu_ico1.png

1891 ms

foot_menu_ico2.png

foot_menu_ico2.png

1746 ms

foot_ico1.png

foot_ico1.png

1764 ms

foot_menu_ico3.png

foot_menu_ico3.png

1781 ms

foot_menu_ico4.png

foot_menu_ico4.png

1786 ms

foot_menu_ico5.png

foot_menu_ico5.png

1787 ms

foot_ico2.png

foot_ico2.png

1729 ms

foot_ico3.png

foot_ico3.png

1738 ms

foot_ico4.png

foot_ico4.png

1595 ms

foot_ico5.png

foot_ico5.png

1602 ms

bt_pagetop.png

bt_pagetop.png

1455 ms

Accessibility Review

inayasu.com accessibility score

73

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

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

Links do not have a discernible name

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

inayasu.com best practices score

75

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

inayasu.com SEO score

92

Search Engine Optimization Advices

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

inayasu.com

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