6.3 sec in total
566 ms
5.1 sec
688 ms
Visit katasekk.co.jp now to see the best up-to-date Katasekk content for Japan and also check out these interesting facts you probably never knew about katasekk.co.jp
化粧品卸売商社・カタセ株式会社は、海外売れ筋人気ブランドコスメ・香水・ヘルス&ビューティグッズ等を世界中より輸入卸売。入手しにくい国内ブランド化粧品、サロン専売品ヘアケア商材など 5,000アイテムを在庫し当日出荷に対応。世界中・日本中のネットワーク、長年のノウハウを活かし、海外市場向け輸出にも力を入れております。
Visit katasekk.co.jpWe analyzed Katasekk.co.jp page load time and found that the first response time was 566 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
katasekk.co.jp performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value18.0 s
0/100
25%
Value11.0 s
6/100
10%
Value80 ms
99/100
30%
Value0.007
100/100
15%
Value23.1 s
1/100
10%
566 ms
1085 ms
353 ms
506 ms
685 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 72% of them (59 requests) were addressed to the original Katasekk.co.jp, 13% (11 requests) were made to Fonts.gstatic.com and 6% (5 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Katasekk.co.jp.
Page size can be reduced by 1.9 MB (21%)
9.0 MB
7.2 MB
In fact, the total size of Katasekk.co.jp main page is 9.0 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 8.7 MB which makes up the majority of the site volume.
Potential reduce by 59.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 19.1 kB, which is 26% 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 59.0 kB or 81% of the original size.
Potential reduce by 1.7 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. Obviously, Katasekk needs image optimization as it can save up to 1.7 MB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 41.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 41.2 kB or 33% of the original size.
Potential reduce by 80.9 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. Katasekk.co.jp needs all CSS files to be minified and compressed as it can save up to 80.9 kB or 81% of the original size.
Number of requests can be reduced by 25 (37%)
67
42
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Katasekk. 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 12 to 1 for CSS and as a result speed up the page load time.
katasekk.co.jp
566 ms
katasekk.co.jp
1085 ms
viewport.js
353 ms
reset.css
506 ms
base.css
685 ms
top.css
699 ms
media.css
528 ms
font-awesome.min.css
840 ms
slick.css
705 ms
slick-theme.css
855 ms
jquery-3.3.1.js
14 ms
jquery.min.js
17 ms
common.js
742 ms
slick.min.js
812 ms
jsapi
21 ms
access.js
989 ms
loader.js
19 ms
css
25 ms
notosansjapanese.css
41 ms
notosansjp.css
45 ms
notosanssc.css
44 ms
cwtexming.css
48 ms
analytics.js
128 ms
logo.png
169 ms
h_ico_mail.png
348 ms
1535502908-173300_1.jpg
393 ms
1535502915-757413_1.jpg
1109 ms
1535502899-938376_1.jpg
1010 ms
1686296911-732013_1.jpg
1357 ms
bnr_allbrand.png
1045 ms
bnr_privatebrand.png
908 ms
sec03_photo01.png
919 ms
sec03_photo02.png
1082 ms
sec03_photo03.png
1268 ms
sec03_photo04.png
1186 ms
sec03_photo05.png
1570 ms
sec03_photo06.png
1254 ms
sec03_photo07.png
1283 ms
sec03_photo08.png
1363 ms
sec03_photo09.png
1427 ms
ico_search.png
1442 ms
1641540039-080843_1.png
1462 ms
1599720541-412744_1.jpg
1525 ms
1542585082-816692_1.jpg
1540 ms
1571192296-472935_1.jpg
1599 ms
1541052393-052214_1.png
1961 ms
1536208534-485614_1.png
1641 ms
1583983311-189747_1.jpg
1694 ms
1536629537-151020_1.png
1720 ms
1545374820-194918_1.png
1924 ms
sec04_concept_bg.png
2113 ms
sec04_brand_bg.png
1819 ms
sec06_photo01.png
1867 ms
sec06_ttl.png
1896 ms
gotop.png
1994 ms
f_logo.png
2038 ms
f_ico_twitter.png
2022 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35zS1g.ttf
115 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj35zS1g.ttf
126 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFE8j35zS1g.ttf
169 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEj35zS1g.ttf
181 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEi35zS1g.ttf
181 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFM8k35zS1g.ttf
181 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk35zS1g.ttf
180 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFJEk35zS1g.ttf
181 ms
-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFLgk35zS1g.ttf
179 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_DjQbMZhKg.ttf
183 ms
Qw3PZQNVED7rKGKxtqIqX5E-AVSJrOCfjY46_GbQbMZhKg.ttf
183 ms
f_ico_facebook.png
2045 ms
f_ico_instagram.png
2012 ms
collect
60 ms
btn_arrow.png
2003 ms
sec01_bg.png
1865 ms
sec02_bg.png
1867 ms
sec03_bg.png
1552 ms
arrow_white.png
1367 ms
arrow_black.png
1301 ms
sec05_bg.png
1479 ms
arrow_slider.png
1298 ms
f_ico_mail.png
1329 ms
ajax-loader.gif
1272 ms
slick.woff
177 ms
katasekk.co.jp accessibility score
ARIA
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.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
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
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
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>).
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.
katasekk.co.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
katasekk.co.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 Katasekk.co.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 Katasekk.co.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.
katasekk.co.jp
Open Graph description is not detected on the main page of Katasekk. 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: