Tools & Wizards About Us
ootoya.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

ootoya.com

大戸屋

Page Load Speed

5.3 sec in total

First Response

543 ms

Resources Loaded

4.4 sec

Page Rendered

326 ms

ootoya.com screenshot

About Website

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

素材と店内調理にこだわる、定食の「大戸屋ごはん処」を展開。“そうそう、これこれ”って、思わず嬉しくなる味。家庭の食卓にある献立をイメージした、そんな毎日食べたくなる、くらしの基本になるごはんを大戸屋は丁寧に作ります。

Visit ootoya.com

Key Findings

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

Performance Metrics

ootoya.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value25.3 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value2,070 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value17.8 s

4/100

10%

Network Requests Diagram

ootoya.com

543 ms

www.ootoya.com

1252 ms

gtm.js

52 ms

normalize.css

871 ms

common.css

1260 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 82% of them (72 requests) were addressed to the original Ootoya.com, 8% (7 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Ootoya.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 43.2 kB (2%)

Content Size

2.6 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ootoya.com main page is 2.6 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. Only a small number of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 20.5 kB

  • Original 25.6 kB
  • After minification 19.3 kB
  • After compression 5.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 6.3 kB, which is 25% 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 20.5 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 20.4 kB

  • Original 2.4 MB
  • After minification 2.4 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. Ootoya images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 445 B

  • Original 164.2 kB
  • After minification 164.2 kB
  • After compression 163.8 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

-16%

Potential reduce by 1.8 kB

  • Original 11.3 kB
  • After minification 11.3 kB
  • After compression 9.5 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. Ootoya.com needs all CSS files to be minified and compressed as it can save up to 1.8 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (30%)

Requests Now

79

After Optimization

55

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ootoya.com

ootoya.com

543 ms

www.ootoya.com

www.ootoya.com

1252 ms

gtm.js

gtm.js

52 ms

normalize.css

normalize.css

871 ms

common.css

common.css

1260 ms

style.css

style.css

1053 ms

logo.png

logo.png

34 ms

nav_01.svg

nav_01.svg

882 ms

nav_02.svg

nav_02.svg

868 ms

btn_menu_close_off.png

btn_menu_close_off.png

187 ms

map_search_ttl.png

map_search_ttl.png

324 ms

btn_search_dis.png

btn_search_dis.png

326 ms

icon_map_off.png

icon_map_off.png

326 ms

nav_03.png

nav_03.png

327 ms

btn_menu_open.png

btn_menu_open.png

328 ms

btn_parttime.jpg

btn_parttime.jpg

327 ms

btn_fulltime.jpg

btn_fulltime.jpg

328 ms

icon_sns01.png

icon_sns01.png

329 ms

icon_sns05.png

icon_sns05.png

330 ms

icon_sns03.png

icon_sns03.png

329 ms

icon_sns04.png

icon_sns04.png

349 ms

icon_attention.svg

icon_attention.svg

353 ms

js

js

69 ms

analytics.js

analytics.js

18 ms

destination

destination

62 ms

collect

collect

148 ms

libs_top.js

libs_top.js

2408 ms

base.js

base.js

1648 ms

top.js

top.js

1647 ms

2404_haru_1500x844.jpg

2404_haru_1500x844.jpg

706 ms

2404_cm__1500x844.jpg

2404_cm__1500x844.jpg

712 ms

3cec7349bbc9c031f6fecb85edb232c4c975dc1f.jpg

3cec7349bbc9c031f6fecb85edb232c4c975dc1f.jpg

717 ms

part_time_off.png

part_time_off.png

728 ms

full_time_off.png

full_time_off.png

732 ms

btn_x.png

btn_x.png

737 ms

btn_youtube.png

btn_youtube.png

740 ms

btn_insta.png

btn_insta.png

1647 ms

btn_fb.png

btn_fb.png

872 ms

page_top.png

page_top.png

877 ms

f_logo.png

f_logo.png

882 ms

f_contact.png

f_contact.png

886 ms

f_facebook.png

f_facebook.png

890 ms

f_x.png

f_x.png

894 ms

f_instagram.png

f_instagram.png

898 ms

f_youtube.png

f_youtube.png

763 ms

collect

collect

41 ms

notosansjapanese.css

notosansjapanese.css

37 ms

head_border.png

head_border.png

154 ms

bg.png

bg.png

154 ms

main_border_01.png

main_border_01.png

893 ms

maincap.png

maincap.png

154 ms

icon_caption.png

icon_caption.png

155 ms

main_border_02.png

main_border_02.png

155 ms

border_dotted.png

border_dotted.png

155 ms

bnr_Appli.jpg

bnr_Appli.jpg

156 ms

bnr_small09.jpg

bnr_small09.jpg

157 ms

bnr_small01.jpg

bnr_small01.jpg

157 ms

bnr_eGift.jpg

bnr_eGift.jpg

157 ms

bnr_Mutenka.jpg

bnr_Mutenka.jpg

158 ms

bnr_SDGs.jpg

bnr_SDGs.jpg

159 ms

bnr_Syokuiku.jpg

bnr_Syokuiku.jpg

159 ms

bnr_Foreign.jpg

bnr_Foreign.jpg

160 ms

bnr_Recipe.jpg

bnr_Recipe.jpg

161 ms

bnr_passport.jpg

bnr_passport.jpg

161 ms

bnr_small07.jpg

bnr_small07.jpg

162 ms

bnr_soba.jpg

bnr_soba.jpg

163 ms

part_time.jpg

part_time.jpg

163 ms

full_time.jpg

full_time.jpg

164 ms

icon_fc.png

icon_fc.png

165 ms

icon_store.png

icon_store.png

165 ms

icon_blank.png

icon_blank.png

165 ms

logo_company.png

logo_company.png

194 ms

NotoSansJP-Regular.woff

NotoSansJP-Regular.woff

52 ms

NotoSansJP-Medium.woff

NotoSansJP-Medium.woff

177 ms

NotoSansJP-DemiLight.woff

NotoSansJP-DemiLight.woff

225 ms

NotoSansJP-Light.woff

NotoSansJP-Light.woff

228 ms

NotoSansJP-Thin.woff

NotoSansJP-Thin.woff

334 ms

NotoSansJP-Bold.woff

NotoSansJP-Bold.woff

229 ms

NotoSansJP-Black.woff

NotoSansJP-Black.woff

232 ms

icomoon.ttf

icomoon.ttf

839 ms

collect

collect

30 ms

slide_prev_off.png

slide_prev_off.png

16 ms

slide_next_off.png

slide_next_off.png

109 ms

btn_menu_close_on.png

btn_menu_close_on.png

5 ms

icon_map_on.png

icon_map_on.png

7 ms

part_time_on.png

part_time_on.png

6 ms

full_time_on.png

full_time_on.png

5 ms

js

js

40 ms

Accessibility Review

ootoya.com accessibility score

96

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

Links do not have a discernible name

Best Practices

ootoya.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ootoya.com SEO score

71

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

High

robots.txt is not valid

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

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

ootoya.com

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