Access kingeshop.jp. KING e-SHOP

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value530 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value1.009

2/100

15%

TTI (Time to Interactive)

Value18.7 s

3/100

10%

kingeshop.jp

489 ms

default.aspx

1112 ms

style.css

303 ms

core.css

302 ms

skin.css

309 ms

Our browser made a total of 129 requests to load all elements on the main page. We found that 94% of them (121 requests) were addressed to the original Kingeshop.jp, 3% (4 requests) were made to Google-analytics.com and 1% (1 request) were made to Harpoon3.userdive.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Kingeshop.jp.

Content Size

1.6 MB

After Optimization

1.0 MB

In fact, the total size of Kingeshop.jp main page is 1.6 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. 25% of websites need less resources to load. Images take 943.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 32.8 kB

Original 41.8 kB
After minification 36.9 kB
After compression 9.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 4.9 kB, which is 12% 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 32.8 kB or 78% of the original size.

Image Optimization

-11%

Potential reduce by 103.9 kB

Original 943.6 kB
After minification 839.7 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, KING E SHOP needs image optimization as it can save up to 103.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 282.0 kB

Original 434.0 kB
After minification 422.6 kB
After compression 152.1 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 282.0 kB or 65% of the original size.

CSS Optimization

-85%

Potential reduce by 123.1 kB

Original 145.0 kB
After minification 98.8 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. Kingeshop.jp needs all CSS files to be minified and compressed as it can save up to 123.1 kB or 85% of the original size.

Requests Now

127

After Optimization

The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of KING E SHOP. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 20 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 toggle fields do not have accessible names

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 semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

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

SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kingeshop.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 Kingeshop.jp main page’s claimed encoding is shift_jis. 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

kingeshop.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

KING e-SHOP

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

kingeshop.jp

default.aspx

style.css

core.css

skin.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

kingeshop.jp

default.aspx

style.css

core.css

skin.css

smartRollover.js

jquery.js

itemheight.js

common.js

swfobject.js

topics_tab.css

goods_cartlist.js

jquery-ui.js

goods_ajax_cart.js

reset.css

s_lmr.css

common.css

sidebox.css

category.css

goods.css

order.css

customer.css

etc.css

quickorder.css

userreview.css

dropframe.css

user.css

freepage.css

kage.css

jquery-ui-1.8.5.custom.css

body-bg.png

UDTracker.js

analytics.js

logo.png

arrow-top-nav.png

arrow-hover-top-nav.png

circle-welcome.gif

cart.aspx

home-btm-off.png

login-btm-off.png

register-btm-off.png

howto-btm-off.png

magazine-btm-off.png