Tools & Wizards About Us
tebaichi.jp screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

tebaichi.jp

【公式】てば壱 ｜ 富山の手羽先居酒屋

Page Load Speed

8.7 sec in total

First Response

1.1 sec

Resources Loaded

7.3 sec

Page Rendered

284 ms

tebaichi.jp screenshot

About Website

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

富山県内に展開する手羽先居酒屋。各店、手羽先の唐揚げをキラーコンテンツに、串揚げやもつ鍋、焼肉、炭火鶏肉料理などなど、お店ごとに特色を出したサブメニューも取り揃え、地元密着型で老若男女、幅広い層のお客様にご愛顧頂いております。

Visit tebaichi.jp

Key Findings

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

tebaichi.jp performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value15.1 s

0/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.169

70/100

15%

TTI (Time to Interactive)

Value11.9 s

17/100

10%

Network Requests Diagram

www.tebaichi.jp

1149 ms

css

25 ms

style.css

328 ms

jquery.js

498 ms

jquery-migrate.min.js

335 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 67% of them (44 requests) were addressed to the original Tebaichi.jp, 8% (5 requests) were made to Platform.twitter.com and 5% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Tebaichi.jp.

Page Optimization Overview & Recommendations

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

Content Size

2.5 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tebaichi.jp main page is 2.5 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 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 30.5 kB

  • Original 38.5 kB
  • After minification 37.5 kB
  • After compression 8.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 30.5 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 101.7 kB

  • Original 2.2 MB
  • After minification 2.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. Tebaichi images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 88.1 kB

  • Original 147.9 kB
  • After minification 138.9 kB
  • After compression 59.7 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 88.1 kB or 60% of the original size.

CSS Optimization

-84%

Potential reduce by 66.0 kB

  • Original 78.7 kB
  • After minification 68.0 kB
  • After compression 12.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. Tebaichi.jp needs all CSS files to be minified and compressed as it can save up to 66.0 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

63

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tebaichi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 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.tebaichi.jp

www.tebaichi.jp

1149 ms

css

css

25 ms

style.css

style.css

328 ms

jquery.js

jquery.js

498 ms

jquery-migrate.min.js

jquery-migrate.min.js

335 ms

mplus_webfonts.css

mplus_webfonts.css

843 ms

unslider.min.js

unslider.min.js

334 ms

jquery.event.move.js

jquery.event.move.js

338 ms

jquery.event.swipe.js

jquery.event.swipe.js

334 ms

harvey.min.js

harvey.min.js

646 ms

theme.js

theme.js

661 ms

mplus_webfonts.css

mplus_webfonts.css

780 ms

solid.png

solid.png

1016 ms

header-title-shop2.png

header-title-shop2.png

679 ms

header-banner05.jpg

header-banner05.jpg

833 ms

logo-tebaichi.png

logo-tebaichi.png

176 ms

header-banner20.jpg

header-banner20.jpg

938 ms

tebaichi_nomura_5th-150x150.jpg

tebaichi_nomura_5th-150x150.jpg

509 ms

icon-new.png

icon-new.png

346 ms

tebaichi-haru2016-150x150.jpg

tebaichi-haru2016-150x150.jpg

509 ms

tebaichi-haru2016-150x150.jpg

tebaichi-haru2016-150x150.jpg

704 ms

tebaichi-haru2016-150x150.jpg

tebaichi-haru2016-150x150.jpg

848 ms

tebaichi-haru2016-150x150.jpg

tebaichi-haru2016-150x150.jpg

995 ms

tebaichi-haru2016-150x150.jpg

tebaichi-haru2016-150x150.jpg

1000 ms

tebaichi-haru2016-150x150.jpg

tebaichi-haru2016-150x150.jpg

1235 ms

tebaichi-haru2016-150x150.jpg

tebaichi-haru2016-150x150.jpg

1338 ms

tebaichi-haru2016-150x150.jpg

tebaichi-haru2016-150x150.jpg

1473 ms

kawari-teba-150x150.jpg

kawari-teba-150x150.jpg

1321 ms

kawari-teba-150x150.jpg

kawari-teba-150x150.jpg

1342 ms

kawari-teba-150x150.jpg

kawari-teba-150x150.jpg

1350 ms

kawari-teba-150x150.jpg

kawari-teba-150x150.jpg

1578 ms

kawari-teba-150x150.jpg

kawari-teba-150x150.jpg

1661 ms

2e7ff0d1081e00ff7c24a9a18bf771eb-150x150.jpg

2e7ff0d1081e00ff7c24a9a18bf771eb-150x150.jpg

1854 ms

beeline-150x150.jpg

beeline-150x150.jpg

1683 ms

fe6ca4aed35c0ba57ad271f3f17321f4-150x150.jpg

fe6ca4aed35c0ba57ad271f3f17321f4-150x150.jpg

1700 ms

tebasaki500000-150x150.jpg

tebasaki500000-150x150.jpg

2004 ms

kamiiino4th-150x150.jpg

kamiiino4th-150x150.jpg

2038 ms

teba-boushinnenkai15-16-150x150.jpg

teba-boushinnenkai15-16-150x150.jpg

2189 ms

banner-kamiiino.png

banner-kamiiino.png

2757 ms

banner-yamamuro.png

banner-yamamuro.png

2686 ms

banner-toyamaekimae.png

banner-toyamaekimae.png

2898 ms

banner-fuchu.png

banner-fuchu.png

3112 ms

banner-nomura.png

banner-nomura.png

2980 ms

banner-naimen.png

banner-naimen.png

3184 ms

banner-kizu.png

banner-kizu.png

3613 ms

banner-kosugi.png

banner-kosugi.png

3721 ms

banner-taipei.png

banner-taipei.png

3829 ms

widgets.js

widgets.js

78 ms

ga.js

ga.js

5 ms

__utm.gif

__utm.gif

15 ms

all.js

all.js

167 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

150 ms

61 ms

102 ms

xd_arbiter.php

xd_arbiter.php

146 ms

xd_arbiter.php

xd_arbiter.php

266 ms

syndication

syndication

121 ms

317083312537604096

317083312537604096

208 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

29 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

62 ms

a2870a778e79bafbb7e4764091c5fa7a_normal.png

a2870a778e79bafbb7e4764091c5fa7a_normal.png

262 ms

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

35 ms

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

45 ms

link_v1_e64f66f5650df987d97cc5f00c4cb5987f367028.svg

link_v1_e64f66f5650df987d97cc5f00c4cb5987f367028.svg

13 ms

jot.html

jot.html

30 ms

ping

ping

41 ms

Accessibility Review

tebaichi.jp accessibility score

82

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

Best Practices

tebaichi.jp 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

High

Page has valid source maps

SEO Factors

tebaichi.jp SEO score

75

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

Page is blocked from indexing

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

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

tebaichi.jp

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