Tools & Wizards About Us
yossix.co.jp screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    54% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

yossix.co.jp

株式会社ヨシックスホールディングス | 本格職人握り寿司居酒屋「や台ずし」、全品280円(税込308円)の安い居酒屋「ニパチ」、お好み焼き・鉄板焼居酒屋「や台や」、手羽先唐揚、鮮魚刺身と鶏黒炭焼「せんと」、串カツ居酒屋「これや」などの居酒屋チェーン「や台やグループ」を展開する株式会社ヨシックスホール...

Page Load Speed

3.5 sec in total

First Response

646 ms

Resources Loaded

2.6 sec

Page Rendered

259 ms

yossix.co.jp screenshot

About Website

Welcome to yossix.co.jp homepage info - get ready to check Yossix best content for Japan right away, or after learning these important things about yossix.co.jp

本格職人握り寿司居酒屋「や台ずし」、全品280円(税込308円)安い居酒屋「ニパチ」、お好み焼き・鉄板焼居酒屋「や台や」、手羽先唐揚、鮮魚刺身と鶏黒炭焼「せんと」、串カツ居酒屋「これや」などの居酒屋チェーン「や台やグループ」を展開しています。

Visit yossix.co.jp

Key Findings

We analyzed Yossix.co.jp page load time and found that the first response time was 646 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

yossix.co.jp performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value10.4 s

0/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value530 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.669

8/100

15%

TTI (Time to Interactive)

Value11.7 s

18/100

10%

Network Requests Diagram

yossix.co.jp

646 ms

base.css

179 ms

common.css

334 ms

top.css

349 ms

font-awesome.css

342 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 58% of them (49 requests) were addressed to the original Yossix.co.jp, 7% (6 requests) were made to Apis.google.com and 6% (5 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Yossix.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 246.0 kB (29%)

Content Size

846.2 kB

After Optimization

600.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yossix.co.jp main page is 846.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Javascripts take 562.3 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 55.7 kB

  • Original 71.7 kB
  • After minification 68.3 kB
  • After compression 16.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 55.7 kB or 78% of the original size.

Image Optimization

-21%

Potential reduce by 38.4 kB

  • Original 185.6 kB
  • After minification 147.2 kB

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. Obviously, Yossix needs image optimization as it can save up to 38.4 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-26%

Potential reduce by 147.3 kB

  • Original 562.3 kB
  • After minification 562.3 kB
  • After compression 414.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 147.3 kB or 26% of the original size.

CSS Optimization

-17%

Potential reduce by 4.5 kB

  • Original 26.5 kB
  • After minification 26.5 kB
  • After compression 22.0 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. Yossix.co.jp needs all CSS files to be minified and compressed as it can save up to 4.5 kB or 17% of the original size.

Requests Breakdown

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

Requests Now

79

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yossix.co.jp

yossix.co.jp

646 ms

base.css

base.css

179 ms

common.css

common.css

334 ms

top.css

top.css

349 ms

font-awesome.css

font-awesome.css

342 ms

jquery.bxslider.css

jquery.bxslider.css

343 ms

loader.min.js

loader.min.js

170 ms

platform.js

platform.js

21 ms

jquery-2.1.1.min.js

jquery-2.1.1.min.js

592 ms

jquery.tmpl.min.js

jquery.tmpl.min.js

399 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

590 ms

script-ps.js

script-ps.js

590 ms

jquery.lsknow.js

jquery.lsknow.js

606 ms

nav.js

nav.js

606 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

591 ms

analytics.js

analytics.js

49 ms

header-message.png

header-message.png

531 ms

logo.png

logo.png

609 ms

tataizushi.jpg

tataizushi.jpg

760 ms

obon-2024.gif

obon-2024.gif

405 ms

takeout.gif

takeout.gif

610 ms

twitter.gif

twitter.gif

416 ms

anniv-40th.gif

anniv-40th.gif

609 ms

jobs.gif

jobs.gif

760 ms

yataizushi.gif

yataizushi.gif

707 ms

nipachi.gif

nipachi.gif

768 ms

nipachi-02.gif

nipachi-02.gif

762 ms

yataiya.gif

yataiya.gif

769 ms

sento.gif

sento.gif

878 ms

koreya.gif

koreya.gif

927 ms

teppan.gif

teppan.gif

932 ms

tamahagane.gif

tamahagane.gif

927 ms

itadaki.gif

itadaki.gif

941 ms

hanahana.gif

hanahana.gif

940 ms

rikunavi.gif

rikunavi.gif

1055 ms

line.png

line.png

1099 ms

twitter.png

twitter.png

1093 ms

instagram.png

instagram.png

1105 ms

facebook.png

facebook.png

1109 ms

blog.png

blog.png

1120 ms

movie.gif

movie.gif

1237 ms

ma-cloud.jpg

ma-cloud.jpg

1259 ms

ir-info.gif

ir-info.gif

1265 ms

preferential-treatment.gif

preferential-treatment.gif

1279 ms

zaidan.gif

zaidan.gif

1241 ms

zaidan-yoshioka.gif

zaidan-yoshioka.gif

1240 ms

widgets.js

widgets.js

19 ms

collect

collect

199 ms

collect

collect

168 ms

sdk.js

sdk.js

210 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

157 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

201 ms

fastbutton

fastbutton

197 ms

cse.js

cse.js

188 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1360 ms

mail.png

mail.png

1193 ms

bg-h2-information.jpg

bg-h2-information.jpg

1185 ms

bg-h2-newshop.jpg

bg-h2-newshop.jpg

1205 ms

share

share

278 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

88 ms

bg-h2-campaign.jpg

bg-h2-campaign.jpg

1189 ms

js

js

151 ms

ya_orange.png

ya_orange.png

1189 ms

cse.js

cse.js

108 ms

sdk.js

sdk.js

48 ms

postmessageRelay

postmessageRelay

225 ms

settings

settings

264 ms

developers.google.com

developers.google.com

271 ms

cse_element__ja.js

cse_element__ja.js

132 ms

default+ja.css

default+ja.css

177 ms

default.css

default.css

180 ms

3636781319-postmessagerelay.js

3636781319-postmessagerelay.js

78 ms

rpc:shindig_random.js

rpc:shindig_random.js

51 ms

widget.1.23.2.0.css

widget.1.23.2.0.css

156 ms

button.1.23.2.0.js

button.1.23.2.0.js

172 ms

sentry.1.23.2.0.js

sentry.1.23.2.0.js

174 ms

async-ads.js

async-ads.js

55 ms

branding.png

branding.png

33 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

8 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

25 ms

embeds

embeds

42 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

21 ms

torimochi.js

torimochi.js

24 ms

line_v3@3x.png

line_v3@3x.png

15 ms

Accessibility Review

yossix.co.jp accessibility score

74

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

<frame> or <iframe> elements do not have a title

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

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

High

Page has valid source maps

SEO Factors

yossix.co.jp SEO score

100

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 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 Yossix.co.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 Yossix.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

yossix.co.jp

Open Graph data is detected on the main page of Yossix. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: