Access ootaya99.com. 太田屋酒店｜オンラインショップ

ootaya99.com screenshot

30

Performance

Renders faster than
50% of other websites
67

Accessibility

Visual factors better than
that of 32% of websites
67

Best Practices

More advanced features
available than in
24% of websites
90

SEO

Google-friendlier than
68% of websites

First Response

1.4 sec

Resources Loaded

19 sec

Page Rendered

891 ms

ootaya99.com screenshot

About Website

Welcome to ootaya99.com homepage info - get ready to check Ootaya 99 best content right away, or after learning these important things about ootaya99.com

太田屋酒店は九十九里町にて自然派ワインや千葉の地酒・焼酎、クラフトビールを販売。

Visit ootaya99.com

Key Findings

We analyzed Ootaya99.com page load time and found that the first response time was 1.4 sec and then it took 19.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value640 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0.345

32/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

ootaya99.com

1418 ms

colormekit.css

561 ms

colormekit-responsive.css

719 ms

index.css

22 ms

top.css

27 ms

Our browser made a total of 332 requests to load all elements on the main page. We found that 3% of them (11 requests) were addressed to the original Ootaya99.com, 87% (288 requests) were made to Img21.shop-pro.jp and 7% (22 requests) were made to Img.shop-pro.jp. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Img21.shop-pro.jp.

Content Size

6.4 MB

After Optimization

5.1 MB

In fact, the total size of Ootaya99.com main page is 6.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.4 MB which makes up the majority of the site volume.

HTML Optimization

-96%

Potential reduce by 858.0 kB

Original 889.8 kB
After minification 295.5 kB
After compression 31.8 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 594.3 kB, which is 67% 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 858.0 kB or 96% of the original size.

Image Optimization

-6%

Potential reduce by 347.6 kB

Original 5.4 MB
After minification 5.0 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. Ootaya 99 images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 7.0 kB

Original 67.2 kB
After minification 66.4 kB
After compression 60.2 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

-78%

Potential reduce by 55.4 kB

Original 71.0 kB
After minification 58.0 kB
After compression 15.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. Ootaya99.com needs all CSS files to be minified and compressed as it can save up to 55.4 kB or 78% of the original size.

Requests Now

331

After Optimization

301

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

[aria-*] attributes do not match their roles

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

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 items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

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

Serves images with low resolution

Low

Detected JavaScript libraries

Search Engine Optimization Advices

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

High

Links are not crawlable

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

EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ootaya99.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 Ootaya99.com main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

ootaya99.com

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