Tools & Wizards About Us
torihei.co.jp screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    66% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

torihei.co.jp

上州御用 鳥めし本舗　登利平

Page Load Speed

7.6 sec in total

First Response

863 ms

Resources Loaded

6.3 sec

Page Rendered

474 ms

torihei.co.jp screenshot

About Website

Click here to check amazing Torihei content for Japan. Otherwise, check out these important facts you probably never knew about torihei.co.jp

創業以来四十有余年。先達より受け継がれた伝統の味に研鑽に研鑽。究極の味を求めて真摯な努力を日夜重ねております。群馬・埼玉に33店舗、オンラインお弁当注文も。宴会、法事や慰労会にもご利用いただけます。

Visit torihei.co.jp

Key Findings

We analyzed Torihei.co.jp page load time and found that the first response time was 863 ms and then it took 6.8 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

torihei.co.jp performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value35.9 s

0/100

25%

SI (Speed Index)

Value15.4 s

1/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

www.torihei.co.jp

863 ms

ga.js

11 ms

pagenavi-css.css

179 ms

default.min.css

352 ms

jquery.js

882 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 96% of them (48 requests) were addressed to the original Torihei.co.jp, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Torihei.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 518.0 kB (13%)

Content Size

3.9 MB

After Optimization

3.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Torihei.co.jp main page is 3.9 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. 50% of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 7.4 kB

  • Original 10.6 kB
  • After minification 9.9 kB
  • After compression 3.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. 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 7.4 kB or 69% of the original size.

Image Optimization

-8%

Potential reduce by 272.2 kB

  • Original 3.6 MB
  • After minification 3.3 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. Torihei images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 128.9 kB

  • Original 217.4 kB
  • After minification 217.2 kB
  • After compression 88.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 128.9 kB or 59% of the original size.

CSS Optimization

-87%

Potential reduce by 109.5 kB

  • Original 126.0 kB
  • After minification 100.1 kB
  • After compression 16.4 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. Torihei.co.jp needs all CSS files to be minified and compressed as it can save up to 109.5 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (33%)

Requests Now

49

After Optimization

33

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.torihei.co.jp

www.torihei.co.jp

863 ms

ga.js

ga.js

11 ms

pagenavi-css.css

pagenavi-css.css

179 ms

default.min.css

default.min.css

352 ms

jquery.js

jquery.js

882 ms

jquery-migrate.min.js

jquery-migrate.min.js

353 ms

style.css

style.css

553 ms

jquery.sidr.dark.css

jquery.sidr.dark.css

369 ms

sub.css

sub.css

964 ms

home.css

home.css

698 ms

jquery.js

jquery.js

1057 ms

scroll.js

scroll.js

551 ms

jquery.sidr.min.js

jquery.sidr.min.js

736 ms

__utm.gif

__utm.gif

14 ms

bg_header.png

bg_header.png

881 ms

logo_header.png

logo_header.png

187 ms

bg_btn_header02.png

bg_btn_header02.png

177 ms

bg_btn_header02_on.png

bg_btn_header02_on.png

178 ms

bg_btn_header01.png

bg_btn_header01.png

194 ms

bg_btn_header01_on.png

bg_btn_header01_on.png

186 ms

btn_toggle.png

btn_toggle.png

352 ms

bg_nav.png

bg_nav.png

353 ms

bg_nav_cell.png

bg_nav_cell.png

373 ms

ikiaji.png

ikiaji.png

737 ms

toriheiinfo01.png

toriheiinfo01.png

385 ms

toriheiinfo02.png

toriheiinfo02.png

528 ms

toriheiinfo03.png

toriheiinfo03.png

529 ms

bnr_top_order.png

bnr_top_order.png

1106 ms

bnr_specialstore.png

bnr_specialstore.png

769 ms

bnr_order.png

bnr_order.png

880 ms

bnr_shoplist.png

bnr_shoplist.png

879 ms

img_top-party01.png

img_top-party01.png

919 ms

img_top-party02.png

img_top-party02.png

961 ms

img_top-party03.png

img_top-party03.png

1050 ms

bnr_footer02.png

bnr_footer02.png

1055 ms

bnr_footer03.png

bnr_footer03.png

1407 ms

bnr_footer04.png

bnr_footer04.png

1102 ms

bnr_footer05.png

bnr_footer05.png

1152 ms

logo_footer.png

logo_footer.png

1225 ms

torihei_top_img.png

torihei_top_img.png

2577 ms

bg_wrapper03.png

bg_wrapper03.png

1222 ms

bg_wrapper02.png

bg_wrapper02.png

1224 ms

bg_wrapper.png

bg_wrapper.png

3209 ms

logo_mini.png

logo_mini.png

1335 ms

bg_toriheiinfo.png

bg_toriheiinfo.png

1590 ms

bg_column-full01.png

bg_column-full01.png

1407 ms

bg_column-full02.png

bg_column-full02.png

1511 ms

icon_up.png

icon_up.png

1517 ms

bg_footer02.png

bg_footer02.png

1775 ms

bg_footer01.png

bg_footer01.png

1685 ms

Accessibility Review

torihei.co.jp accessibility score

100

Accessibility Issues

Best Practices

torihei.co.jp 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

torihei.co.jp SEO score

91

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

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

    N/A

  • Encoding

    UTF-8

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

torihei.co.jp

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