3.6 sec in total
339 ms
2.7 sec
483 ms
Visit kobako.com now to see the best up-to-date KOBAKO content and also check out these interesting facts you probably never knew about kobako.com
貝印のビューティーツールブランド「KOBAKO」(コバコ)の公式ブランドサイト。商品・イベントの情報、店舗情報、ツールの使い方などをご紹介しております。
Visit kobako.comWe analyzed Kobako.com page load time and found that the first response time was 339 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
kobako.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value47.1 s
0/100
25%
Value16.2 s
0/100
10%
Value670 ms
44/100
30%
Value0.694
7/100
15%
Value34.2 s
0/100
10%
339 ms
575 ms
24 ms
296 ms
301 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 81% of them (34 requests) were addressed to the original Kobako.com, 7% (3 requests) were made to Analytics.fs-bdash.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Kobako.com.
Page size can be reduced by 144.1 kB (13%)
1.1 MB
993.5 kB
In fact, the total size of Kobako.com main page is 1.1 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 926.7 kB which makes up the majority of the site volume.
Potential reduce by 17.4 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 5.4 kB, which is 24% 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 17.4 kB or 77% of the original size.
Potential reduce by 11.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. KOBAKO images are well optimized though.
Potential reduce by 92.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 92.2 kB or 58% of the original size.
Potential reduce by 22.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. Kobako.com needs all CSS files to be minified and compressed as it can save up to 22.8 kB or 80% of the original size.
Number of requests can be reduced by 18 (45%)
40
22
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of KOBAKO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
kobako.com
339 ms
www.kobako.com
575 ms
css
24 ms
base.css
296 ms
common.css
301 ms
jquery-1.2.6.min.js
596 ms
common.js
302 ms
top.css
300 ms
top.js
305 ms
bd-UJEQG2-1.js
333 ms
urchin.js
307 ms
bdash.js
873 ms
logo_g.png
151 ms
btn_close.png
153 ms
icon-bag.png
160 ms
icon_fb.jpg
154 ms
logo_b.png
155 ms
icon_bag.png
156 ms
icon_kobako.png
297 ms
btn_menu.png
304 ms
top_main01.jpg
899 ms
top_panel01.png
304 ms
top_panel04.png
750 ms
top_panel02.jpg
616 ms
top_panel04.jpg
738 ms
top_panel03_sp.jpg
751 ms
top_panel05.jpg
896 ms
top_panel04_sp.jpg
922 ms
top_panel08.png
891 ms
top_panel05_sp.jpg
898 ms
top_panel06.png
1066 ms
top_panel06_sp.png
1188 ms
top_panel07.png
1049 ms
top_panel07_sp.jpg
1341 ms
top_kobako_concept.png
1047 ms
top_btn_concept.png
1073 ms
ga.js
24 ms
bi.js
523 ms
__utm.gif
1121 ms
__utm.gif
14 ms
334 ms
create
156 ms
kobako.com 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
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
kobako.com 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
kobako.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Kobako.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 Kobako.com 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.
kobako.com
Open Graph data is detected on the main page of KOBAKO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: