2 sec in total
242 ms
1.5 sec
264 ms
Visit cosme-i.jp now to see the best up-to-date COSME I content for Japan and also check out these interesting facts you probably never knew about cosme-i.jp
原料、OEM、パッケージ、研究機器、販促製品など、化粧品の研究・企画開発に必要なあらゆる製品が一堂に出展する専門展。国内外から多数の化粧品メーカーが来場、化粧品開発に関する相談・打合せが活発に行われる国際商談展です。
Visit cosme-i.jpWe analyzed Cosme-i.jp page load time and found that the first response time was 242 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
cosme-i.jp performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value24.1 s
0/100
25%
Value12.2 s
3/100
10%
Value1,780 ms
10/100
30%
Value0.414
24/100
15%
Value23.0 s
1/100
10%
242 ms
22 ms
37 ms
35 ms
24 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 85% of them (80 requests) were addressed to the original Cosme-i.jp, 4% (4 requests) were made to Google-analytics.com and 3% (3 requests) were made to Ad.doubleclick.net. The less responsive or slowest element that took the longest time to load (593 ms) relates to the external source B92.yahoo.co.jp.
Page size can be reduced by 518.0 kB (29%)
1.8 MB
1.3 MB
In fact, the total size of Cosme-i.jp main page is 1.8 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. 55% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 69.3 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 14.4 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 69.3 kB or 74% of the original size.
Potential reduce by 32.1 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. COSME I images are well optimized though.
Potential reduce by 320.3 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 320.3 kB or 63% of the original size.
Potential reduce by 96.3 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. Cosme-i.jp needs all CSS files to be minified and compressed as it can save up to 96.3 kB or 85% of the original size.
Number of requests can be reduced by 56 (61%)
92
36
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of COSME I. 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 33 to 1 for CSS and as a result speed up the page load time.
www.cosme-i.jp
242 ms
html5shiv.js
22 ms
Reset.css
37 ms
module-bootstrap_templated.css
35 ms
Core_v2_templated.css
24 ms
homepage_templated.css
50 ms
autocomplete_templated.css
41 ms
jquery-ui.css
57 ms
icon_up.css
47 ms
custom.css
69 ms
extra.css
62 ms
color-ci_new_ja.css
76 ms
color-ci_new_en.css
78 ms
overwrite_ja.css
83 ms
overwrite_en.css
75 ms
CI_01_ja.css
87 ms
cosme_tech_ja.css
93 ms
cosme_tech_en.css
107 ms
rollover-Nav_01.css
96 ms
R211-Shared-CI.css
113 ms
relx-logo2.css
111 ms
jpcustom.css
103 ms
NovaJs.x.js
145 ms
conversion.js
21 ms
s_retargeting.js
593 ms
nivo_slider.css
137 ms
;Title=;kw=CEO_book;language=ja;sz=214x74;ord=299960949
29 ms
;Title=;kw=reed_top53;language=ja;sz=212x74;ord=299960949
31 ms
;Title=;kw=yokosojapan-jp%20and%20yokosojapan-en;language=ja;sz=104x74;ord=299960949
33 ms
WebResource.axd
125 ms
Buttons_templated.css
117 ms
uab_templated.css
121 ms
media_templated.css
128 ms
module_templated.css
130 ms
user-portal-icon.css
139 ms
grid-module.css
139 ms
list-module.css
144 ms
media-module.css
145 ms
FeaturedContent_templated.css
138 ms
analytics.js
41 ms
86 ms
img_ct_header-bk_rpt.gif
99 ms
img_ci_header-logo_ja2.png
65 ms
CI_ex_J.jpg
63 ms
CI_inv_J.jpg
70 ms
CICT_date_J_2017.png
70 ms
space.gif
110 ms
CI_06jp.jpg
107 ms
ci_slider02.jpg
106 ms
CI_04jp.jpg
132 ms
img_top_contents_title_ja.gif
82 ms
ci_featur01.png
120 ms
ci_featur02.png
129 ms
img_top_whatnew_title_ja.gif
114 ms
img_top_quick-ja_title.png
128 ms
img_ci_quick-l-ja_bn_01.gif
126 ms
img_ci_quick-l-ja_bn_02.gif
141 ms
img_ci_quick-l-ja_bn_04.gif
149 ms
img_ci_quick-l-ja_bn_06.jpg
159 ms
img_ci_quick-l_bn_05_jp2016.png
166 ms
tit_contact.gif
149 ms
Org_RE_WEB_G.gif
154 ms
White-TM.png
166 ms
collect
22 ms
collect
18 ms
collect
17 ms
40 ms
Print_templated.css
31 ms
print_contents.css
31 ms
print.css
20 ms
img_ci_header-bk_rpt_ja.gif
120 ms
img_ci_header-bk_ja.jpg
215 ms
glass_btn.png
109 ms
gnav_ja_on_01.gif
108 ms
gnav_ja_off_02.gif
106 ms
gnav_ja_off_03.gif
109 ms
gnav_ja_off_04.gif
213 ms
gnav_ja_off_05.gif
214 ms
gnav_ja_off_06.gif
231 ms
gnav_ja_off_07.gif
231 ms
loading.gif
232 ms
frame_0616.png
232 ms
img_top_reco_bk_20160112.gif
261 ms
list_diamond.gif
264 ms
separate.gif
218 ms
addthis_widget.js
34 ms
ui-bg_flat_75_ffffff_40x100.png
171 ms
uab.js
39 ms
300lo.json
67 ms
arrows.png
95 ms
bullets.png
97 ms
sh.8e5f85691f9aaa082472a194.html
58 ms
languagecustom2015sep.png
97 ms
flagImageSprite.gif
97 ms
cosme-i.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-hidden="true"] elements contain focusable descendents
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
cosme-i.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
Missing source maps for large first-party JavaScript
cosme-i.jp 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 Cosme-i.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 Cosme-i.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.
cosme-i.jp
Open Graph description is not detected on the main page of COSME I. 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: