5.5 sec in total
886 ms
4.3 sec
336 ms
Visit kempa.jp now to see the best up-to-date Kempa content and also check out these interesting facts you probably never knew about kempa.jp
Kempa(ケンパ)は海外スポーツ用品専門ショップのmelisまで。人気のKempa(ケンパ)を日本国内では入手困難なものなど豊富に取り揃えております。
Visit kempa.jpWe analyzed Kempa.jp page load time and found that the first response time was 886 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
kempa.jp performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value6.3 s
10/100
25%
Value13.9 s
1/100
10%
Value650 ms
46/100
30%
Value0.069
96/100
15%
Value12.1 s
16/100
10%
886 ms
347 ms
385 ms
587 ms
403 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 55% of them (38 requests) were addressed to the original Kempa.jp, 29% (20 requests) were made to Static.xx.fbcdn.net and 10% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Kempa.jp.
Page size can be reduced by 149.2 kB (12%)
1.2 MB
1.1 MB
In fact, the total size of Kempa.jp main page is 1.2 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. 60% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 13.2 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 3.0 kB, which is 17% 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 13.2 kB or 74% of the original size.
Potential reduce by 14.9 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. Kempa images are well optimized though.
Potential reduce by 97.5 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 97.5 kB or 64% of the original size.
Potential reduce by 23.6 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. Kempa.jp needs all CSS files to be minified and compressed as it can save up to 23.6 kB or 80% of the original size.
Number of requests can be reduced by 40 (59%)
68
28
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kempa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
kempa.jp
886 ms
reset.css
347 ms
layout.css
385 ms
style.css
587 ms
ex.css
403 ms
maxheight.js
407 ms
jquery-1.4.2.min.js
904 ms
jquery.faded.js
723 ms
jquery.jqtransform.js
758 ms
script.js
785 ms
rollover.js
826 ms
svwp_style.css
960 ms
jquery.slideViewerPro.1.0.js
1089 ms
jquery.timers-1.2.js
1105 ms
zoombox.css
1157 ms
zoombox.js
1358 ms
css
24 ms
catarog.png
893 ms
tryon.png
895 ms
kempa_body.jpg
1598 ms
logo.png
348 ms
space.png
360 ms
main_vidual_bg.jpg
386 ms
04.jpg
1184 ms
02.jpg
1227 ms
05.jpg
1526 ms
intro_lead.png
891 ms
png.png
894 ms
btn-topics-list.png
1098 ms
title-img-fb.png
1108 ms
marker.gif
1422 ms
kempa-logo.png
1489 ms
hrt-img.png
1580 ms
line-ver.gif
1633 ms
arrow_top.png
1789 ms
ga.js
12 ms
svwloader.gif
1825 ms
__utm.gif
12 ms
likebox.php
490 ms
IWXAbM4pe57.css
33 ms
whsuYM0JyRK.css
44 ms
mJ3scex-8ho.css
40 ms
eXhc6OJ3pgj.css
48 ms
yYGNrWyPiTw.css
56 ms
q68gy-v_YMF.js
56 ms
FJmpeSpHpjS.js
89 ms
0wM5s1Khldu.js
89 ms
1bNoFZUdlYZ.js
100 ms
njO1TPvGzoR.js
101 ms
1QuX41zDRrx.js
104 ms
Oagsvfb4VWi.js
103 ms
LTv6ZK-5zxz.js
107 ms
1FCa-btixu2.js
102 ms
11921694_967866923236388_7207150310724033968_n.png
112 ms
1796464_689848484371568_1481735561_n.png
83 ms
12289478_1007810159242064_7163913584406952457_n.png
31 ms
11921694_967866923236388_7207150310724033968_n.png
33 ms
11752438_967854879904259_1072408990485141637_n.png
25 ms
11188198_909733009065270_6448734403638613327_n.jpg
80 ms
11156412_902627633093651_251568955745074596_n.png
170 ms
wL6VQj7Ab77.png
15 ms
s7jcwEQH7Sx.png
13 ms
QDwYpIaRyfG.png
13 ms
K00K-UgnsKu.png
12 ms
I6-MnjEovm5.js
2 ms
pQrUxxo5oQp.js
4 ms
thumb_04.jpg
186 ms
thumb_02.jpg
169 ms
thumb_05.jpg
182 ms
kempa.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
kempa.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
kempa.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kempa.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 Kempa.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.
kempa.jp
Open Graph description is not detected on the main page of Kempa. 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: