5.2 sec in total
473 ms
4.4 sec
270 ms
Welcome to ignis.jp homepage info - get ready to check IGNIS best content for Japan right away, or after learning these important things about ignis.jp
「イグニス」と「イグニスイオ」個性の異なる2つのシリーズからなる本来の美しさを喚起する化粧品ブランド「イグニス」の公式サイトです。 | 生きた美しさを。「イグニス」は、植物の恵みで、すこやかでゆるぎない美しさを育むスキンケアシリーズです。
Visit ignis.jpWe analyzed Ignis.jp page load time and found that the first response time was 473 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.
ignis.jp performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value13.4 s
0/100
25%
Value13.1 s
2/100
10%
Value2,660 ms
4/100
30%
Value1.053
2/100
15%
Value13.1 s
12/100
10%
473 ms
296 ms
296 ms
298 ms
30 ms
Our browser made a total of 128 requests to load all elements on the main page. We found that 84% of them (107 requests) were addressed to the original Ignis.jp, 2% (3 requests) were made to Google-analytics.com and 2% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Ignis.jp.
Page size can be reduced by 136.5 kB (6%)
2.2 MB
2.1 MB
In fact, the total size of Ignis.jp main page is 2.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. 55% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 37.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 37.0 kB or 80% of the original size.
Potential reduce by 41.8 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. IGNIS images are well optimized though.
Potential reduce by 44.8 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 44.8 kB or 62% of the original size.
Potential reduce by 12.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. Ignis.jp needs all CSS files to be minified and compressed as it can save up to 12.9 kB or 77% of the original size.
Number of requests can be reduced by 19 (15%)
126
107
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IGNIS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
ignis.jp
473 ms
normalize.css
296 ms
base.css
296 ms
index.css
298 ms
jquery.min.js
30 ms
jsapi
17 ms
common.js
296 ms
ajax_common.js
336 ms
index.js
337 ms
google_tracking.js
441 ms
share.js
334 ms
setFooter.js
303 ms
analytics.js
21 ms
widgets.js
237 ms
index_op_t01.png
230 ms
blank.gif
230 ms
cmn_header_t01.gif
228 ms
cmn_header_t02_on.gif
228 ms
cmn_header_t03.gif
229 ms
cmn_header_t04.gif
227 ms
cmn_header_t05.gif
334 ms
cmn_header_t06.gif
326 ms
cmn_header_t07.gif
333 ms
cmn_header_t07_on.gif
329 ms
cmn_header_t07_04.gif
331 ms
cmn_header_t07_01.gif
327 ms
cmn_header_t07_02.gif
476 ms
cmn_header_t07_03.gif
479 ms
cmn_header_t08.gif
479 ms
idx_stit01.gif
488 ms
idx_pu_p01.jpg
780 ms
idx_pu_icon_new.png
482 ms
idx_pu_icon_ni.gif
625 ms
idx_pu_p02.jpg
776 ms
idx_pu_icon_coupon.gif
630 ms
idx_pu_p03.jpg
634 ms
idx_pu_p04.jpg
942 ms
idx_pu_p05.jpg
918 ms
idx_pu_icon_li.gif
777 ms
idx_pu_p06.jpg
932 ms
idx_pu_icon_news.gif
923 ms
idx_stit02.gif
926 ms
idx_pruducts_p01.png
924 ms
idx_pruducts_p02.png
1065 ms
index_products_btn_l.gif
1072 ms
index_products_btn_r.gif
1073 ms
idx_bm_bg01.jpg
1224 ms
idx_stit03.png
1082 ms
idx_bm_t01.png
1092 ms
sdk.js
59 ms
idx_bm_t02.png
1355 ms
share_button.html
337 ms
linkid.js
64 ms
collect
51 ms
collect
180 ms
173 ms
feed
262 ms
xd_arbiter.php
94 ms
xd_arbiter.php
105 ms
25
1947 ms
idx_bm_btn01.png
1149 ms
idx_stit04.gif
1012 ms
inst_btn.png
1024 ms
fb_btn.png
1155 ms
idx_pagetop.gif
1160 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
32 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
75 ms
like.php
107 ms
idx_btm_btn01.gif
1079 ms
idx_btm_btn03.gif
1188 ms
idx_btm_btn05.jpg
1344 ms
cmn_footer_t02.gif
1200 ms
cmn_footer_t03.gif
1209 ms
cmn_footer_t04.gif
1225 ms
bt_check_1.png
61 ms
rU2ubZ6l1Q5.js
85 ms
LVx-xkvaJ0b.png
45 ms
cmn_footer_t05.gif
1189 ms
cmn_footer_t01.gif
1203 ms
cmn_header_bg01.gif
1210 ms
cmn_header_bg03.gif
1227 ms
cmn_header_bg02.gif
1324 ms
jot
101 ms
idx_stitbg01.gif
1194 ms
idx_bm_p01.png
1650 ms
idx_bg01.gif
1204 ms
cmn_footer_bg02.gif
1085 ms
cmn_ar01.gif
1182 ms
cmn_footer_bg01.gif
1188 ms
idx_main01.jpg
2268 ms
idx_main02.jpg
2153 ms
idx_main03.jpg
1920 ms
AIAVYE-S.jpg
152 ms
AIAJMQ-S.jpg
150 ms
AIAJAR-S.jpg
231 ms
AIAJAT-S.jpg
301 ms
AIAJPE-S.jpg
300 ms
AIAJLF-S.jpg
382 ms
AIAIRE-S.jpg
447 ms
AIAVCB-S.jpg
447 ms
AIAJMO-S.jpg
533 ms
AIAJAU-S.jpg
596 ms
AIAJCK-S.jpg
597 ms
AIAJYP-S.jpg
683 ms
AIAJLA-S.jpg
744 ms
AIAJLB-S.jpg
744 ms
AIAJLC-S.jpg
793 ms
AIAVBI-S.jpg
831 ms
AIAJMM-S.jpg
891 ms
AIAJPC-S.jpg
892 ms
AIAIBW-S.jpg
941 ms
AIAJRZ-S.jpg
984 ms
AIAJHJ-S.jpg
1025 ms
AIAJUO-S.jpg
1038 ms
AIAJYM-S.jpg
1040 ms
AIAJYL-S.jpg
1087 ms
AIAJUP-S.jpg
1132 ms
idx_products_cmntbg01.png
1131 ms
cmn_header_t03_on.gif
158 ms
cmn_header_t04_on.gif
151 ms
cmn_header_t05_on.gif
155 ms
cmn_header_t06_on.gif
154 ms
index_products_btn_l_on.gif
156 ms
index_products_btn_r_on.gif
155 ms
idx_bm_btn01_on.png
298 ms
idx_pagetop_on.gif
301 ms
idx_btm_btn01_on.gif
301 ms
idx_btm_btn03_on.gif
299 ms
ignis.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
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
ignis.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
ignis.jp SEO score
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 doesn't use 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 Ignis.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 Ignis.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.
ignis.jp
Open Graph data is detected on the main page of IGNIS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: