Access jizake.com. 佐野屋 JIZAKE.COM｜日本酒・地酒　通販

jizake.com screenshot

13

Performance

Renders faster than
25% of other websites
77

Accessibility

Visual factors better than
that of 44% of websites
58

Best Practices

More advanced features
available than in
20% of websites
82

SEO

Google-friendlier than
44% of websites

First Response

520 ms

Resources Loaded

13.6 sec

Page Rendered

1.1 sec

jizake.com screenshot

About Website

Click here to check amazing JIZAKE content for Singapore. Otherwise, check out these important facts you probably never knew about jizake.com

日本酒のネット通販20年以上。年間発送数5万件以上の実績。獺祭・梵・作・雨後の月・羽根屋といった人気銘柄を始め、豊富なラインナップ。あなたの好みのお酒が見つかる！

Visit jizake.com

Key Findings

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

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value18.1 s

0/100

10%

TBT (Total Blocking Time)

Value4,590 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.172

70/100

15%

TTI (Time to Interactive)

Value39.3 s

0/100

10%

jizake.com

520 ms

jizake.com

1196 ms

www.jizake.com

1658 ms

fs_style.css

876 ms

fs_theme.css

882 ms

Our browser made a total of 154 requests to load all elements on the main page. We found that 4% of them (6 requests) were addressed to the original Jizake.com, 75% (116 requests) were made to Sanoya.itembox.design and 8% (13 requests) were made to Happywine.itembox.design. The less responsive or slowest element that took the longest time to load (4 sec) relates to the external source Sanoya.itembox.design.

Content Size

2.7 MB

After Optimization

2.4 MB

In fact, the total size of Jizake.com main page is 2.7 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. 65% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 210.3 kB

Original 234.4 kB
After minification 184.0 kB
After compression 24.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 50.4 kB, which is 22% 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 210.3 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 1.4 kB

Original 2.1 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. JIZAKE images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 36.9 kB

Original 259.5 kB
After minification 259.5 kB
After compression 222.6 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 36.9 kB or 14% of the original size.

CSS Optimization

-13%

Potential reduce by 10.9 kB

Original 87.4 kB
After minification 87.4 kB
After compression 76.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. Jizake.com needs all CSS files to be minified and compressed as it can save up to 10.9 kB or 13% of the original size.

Requests Now

137

After Optimization

117

The browser has sent 137 CSS, Javascripts, AJAX and image requests in order to completely render the main page of JIZAKE. 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 8 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

button, link, and menuitem elements do not have accessible names.

High

ARIA input fields do not have accessible names

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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

jizake.com

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