Tools & Wizards About Us
dewazakura.co.jp screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

dewazakura.co.jp

出羽桜酒造株式会社 | 山形から日本酒を世界へ

Page Load Speed

6.3 sec in total

First Response

509 ms

Resources Loaded

5.4 sec

Page Rendered

345 ms

dewazakura.co.jp screenshot

About Website

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

明治創業以来、手造りにこだわって酒造りを続けています。全国新酒鑑評会12年連続金賞、世界一の称号「チャンピオン・サケ」に二度輝くなど国内外で高く評価されています。

Visit dewazakura.co.jp

Key Findings

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

Performance Metrics

dewazakura.co.jp performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.323

35/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

dewazakura.co.jp

509 ms

dewazakura.co.jp

687 ms

www.dewazakura.co.jp

859 ms

bootstrap.css

357 ms

font-awesome.min.css

548 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 90% of them (55 requests) were addressed to the original Dewazakura.co.jp, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Dewazakura.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 337.3 kB (6%)

Content Size

5.7 MB

After Optimization

5.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 28.9 kB

  • Original 34.4 kB
  • After minification 29.6 kB
  • After compression 5.5 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 4.9 kB, which is 14% 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 28.9 kB or 84% of the original size.

Image Optimization

-6%

Potential reduce by 304.6 kB

  • Original 5.5 MB
  • After minification 5.2 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. Dewazakura images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 247 B

  • Original 126.1 kB
  • After minification 126.1 kB
  • After compression 125.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. This website has mostly compressed JavaScripts.

CSS Optimization

-10%

Potential reduce by 3.5 kB

  • Original 36.3 kB
  • After minification 36.3 kB
  • After compression 32.8 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. Dewazakura.co.jp has all CSS files already compressed.

Requests Breakdown

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

Requests Now

52

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dewazakura.co.jp

dewazakura.co.jp

509 ms

dewazakura.co.jp

dewazakura.co.jp

687 ms

www.dewazakura.co.jp

www.dewazakura.co.jp

859 ms

bootstrap.css

bootstrap.css

357 ms

font-awesome.min.css

font-awesome.min.css

548 ms

slider-pro.css

slider-pro.css

685 ms

slick.css

slick.css

692 ms

slick-theme.css

slick-theme.css

694 ms

style.css

style.css

700 ms

jquery.min.js

jquery.min.js

20 ms

jquery.js

jquery.js

929 ms

bootstrap.min.js

bootstrap.min.js

797 ms

jquery.sliderPro.min.js

jquery.sliderPro.min.js

1036 ms

slick.min.js

slick.min.js

878 ms

analytics.js

analytics.js

95 ms

hd-bg01.png

hd-bg01.png

199 ms

hd-logo01.png

hd-logo01.png

198 ms

hd-english01.png

hd-english01.png

265 ms

slide-cover01.png

slide-cover01.png

390 ms

slide01.png

slide01.png

1059 ms

slide-txt01.png

slide-txt01.png

391 ms

slide02.png

slide02.png

758 ms

slide03.png

slide03.png

953 ms

slide04.png

slide04.png

1001 ms

slide05.png

slide05.png

1198 ms

slide06.png

slide06.png

1072 ms

slide07.png

slide07.png

970 ms

slide08.png

slide08.png

1308 ms

slide09.png

slide09.png

1168 ms

slide10.png

slide10.png

1674 ms

arrow01.png

arrow01.png

1247 ms

prize-img01-06x.png

prize-img01-06x.png

1448 ms

prize-img02.png

prize-img02.png

1370 ms

prize-img03.png

prize-img03.png

1713 ms

prize-img04.png

prize-img04.png

1612 ms

prize-img05-20.png

prize-img05-20.png

1510 ms

top-bnr06.png

top-bnr06.png

1578 ms

top-bnr05.png

top-bnr05.png

1657 ms

top-bnr02.png

top-bnr02.png

1702 ms

top-bnr04.png

top-bnr04.png

1776 ms

bg01.png

bg01.png

1803 ms

yukimegami48-thum.png

yukimegami48-thum.png

1877 ms

ouka-thum.png

ouka-thum.png

1864 ms

sato-thum.png

sato-thum.png

1897 ms

sansan2-thum.png

sansan2-thum.png

2067 ms

ichiro-thum.png

ichiro-thum.png

1974 ms

kare-thum.png

kare-thum.png

1919 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1968 ms

collect

collect

13 ms

collect

collect

64 ms

js

js

66 ms

ft-bg02.png

ft-bg02.png

1914 ms

ga-audiences

ga-audiences

116 ms

ft-logo01.png

ft-logo01.png

1886 ms

openhand.cur

openhand.cur

1781 ms

sake-arrow01.png

sake-arrow01.png

1810 ms

sake-arrow02.png

sake-arrow02.png

1859 ms

slick.woff

slick.woff

1865 ms

ajax-loader.gif

ajax-loader.gif

1878 ms

slick.ttf

slick.ttf

190 ms

slick.svg

slick.svg

183 ms

Accessibility Review

dewazakura.co.jp accessibility score

88

Accessibility Issues

ARIA

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.

Impact

Issue

High

ARIA input fields do not have accessible names

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Tables and lists

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

Impact

Issue

High

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

Best Practices

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

SEO Factors

dewazakura.co.jp SEO score

90

Search Engine Optimization Advices

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

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

dewazakura.co.jp

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