Access drinx.jp. DRINX｜KIRIN（キリン）公式オンラインショップ

drinx.jp screenshot

6

Performance

Renders faster than
21% of other websites
62

Accessibility

Visual factors better than
that of 28% of websites
75

Best Practices

More advanced features
available than in
36% of websites
97

SEO

Google-friendlier than
91% of websites

First Response

493 ms

Resources Loaded

8.1 sec

Page Rendered

509 ms

drinx.jp screenshot

About Website

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

KIRIN（キリン）オンラインショップ DRINX（ドリンクス）はキリンが運営するお酒（ビール・ウイスキー・ワイン）の公式通販サイトです。最新の特集やイベント情報も続々お届けします。限定商品やギフト商品多数。5,500円以上で送料無料。

Visit drinx.jp

Key Findings

We analyzed Drinx.jp page load time and found that the first response time was 493 ms and then it took 8.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.

name

value

score

weighting

FCP (First Contentful Paint)

Value10.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.6 s

0/100

25%

SI (Speed Index)

Value22.6 s

0/100

10%

TBT (Total Blocking Time)

Value2,500 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.343

32/100

15%

TTI (Time to Interactive)

Value28.5 s

0/100

10%

drinx.jp

493 ms

www.drinx.jp

849 ms

reset.css

312 ms

layout.css

310 ms

parts.css

307 ms

Our browser made a total of 173 requests to load all elements on the main page. We found that 69% of them (119 requests) were addressed to the original Drinx.jp, 3% (6 requests) were made to Cast-cs-j.adtdp.com and 2% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Drinx.jp.

Content Size

289.8 kB

After Optimization

85.3 kB

In fact, the total size of Drinx.jp main page is 289.8 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. 50% of websites need less resources to load. Javascripts take 195.6 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 82.1 kB

Original 94.1 kB
After minification 80.4 kB
After compression 12.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. This page needs HTML code to be minified as it can gain 13.8 kB, which is 15% 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 82.1 kB or 87% of the original size.

JavaScript Optimization

-63%

Potential reduce by 122.4 kB

Original 195.6 kB
After minification 179.4 kB
After compression 73.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 122.4 kB or 63% of the original size.

Requests Now

162

After Optimization

82

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

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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 keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Drinx.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Drinx.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

drinx.jp

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