9.8 sec in total
73 ms
8.6 sec
1.1 sec
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 73 ms and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
ignis.jp performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value28.0 s
0/100
25%
Value18.2 s
0/100
10%
Value1,580 ms
12/100
30%
Value0.003
100/100
15%
Value63.3 s
0/100
10%
73 ms
610 ms
943 ms
65 ms
731 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 79% of them (64 requests) were addressed to the original Ignis.jp, 12% (10 requests) were made to Api.albion.co.jp and 5% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (5.1 sec) belongs to the original domain Ignis.jp.
Page size can be reduced by 2.8 MB (11%)
24.9 MB
22.2 MB
In fact, the total size of Ignis.jp main page is 24.9 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. Only a small number of websites need less resources to load. Images take 23.9 MB which makes up the majority of the site volume.
Potential reduce by 652.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. 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 652.3 kB or 90% of the original size.
Potential reduce by 2.0 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. IGNIS images are well optimized though.
Potential reduce by 70.9 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 70.9 kB or 22% of the original size.
Potential reduce by 29.7 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 29.7 kB or 86% of the original size.
Number of requests can be reduced by 6 (8%)
73
67
The browser has sent 73 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 7 to 1 for JavaScripts and as a result speed up the page load time.
ignis.jp
73 ms
ignis.jp
610 ms
www.ignis.jp
943 ms
gtm.js
65 ms
main.css
731 ms
main.js
879 ms
news-json_read.js
618 ms
jquery.min.js
29 ms
bundle.js
1107 ms
group-aiakba__main.png
1249 ms
IG_24summer_top_pc.jpg
843 ms
IG_24summer_top_sp.jpg
841 ms
IG_whiteline_top_pc.jpg
844 ms
IG_whiteline_top_sp.jpg
841 ms
io.jpg
175 ms
icon_arrow.svg
836 ms
IG_24summer_news01.jpg
960 ms
IG_24summer_news02_limited_n.jpg
1027 ms
IG_24summer_news03.png
1445 ms
IG_24summer_news04.png
1429 ms
news_240711.png
1453 ms
btn_arrow.svg
1437 ms
product_01.jpg
1549 ms
product_01_sp_0.jpeg
1602 ms
product_02.jpg
1595 ms
product_02_sp.jpg
1597 ms
product_03.jpg
1608 ms
product_03_sp.jpg
1885 ms
product_04.jpg
1709 ms
product_04_sp.jpg
1806 ms
product_05.jpg
1760 ms
product_05_sp.jpg
1755 ms
product_06.jpg
2205 ms
product_06_sp.jpg
1866 ms
product_07.jpg
2346 ms
product_07_sp.jpg
2355 ms
product_08.jpg
1959 ms
product_08_sp.jpg
2027 ms
contents_01.jpg
2043 ms
contents_02.jpg
2610 ms
contents_03.jpg
2176 ms
contents_04.jpg
2617 ms
contents_05.jpg
2335 ms
20240704_%E3%83%A4%E3%83%9E%E3%83%A8%E3%83%A2%E3%82%AD%E3%82%99%E5%8F%8E%E7%A9%AB_1.png
2369 ms
group-aiakug__main.png
1227 ms
group-aiakxe__main.png
1519 ms
group-aiakyk__main.png
1224 ms
group-aiakyq__main.png
1223 ms
group-aiakyp__main.png
1233 ms
group-aiakmf__main.png
2377 ms
group-aiakuk__main.png
2374 ms
group-aiakyd__main.png
2376 ms
group-aiakmc__main.png
2609 ms
20240620_%E7%B7%91%E8%82%A5_1_sumb.jpg
2779 ms
20240613_sumb_02.png
2438 ms
css
463 ms
chunk.vendors~block-slider~block-video~common-aside-flow-line~leaf-root~list-how-to~ritual-root.js
1691 ms
chunk.common-aside-flow-line.js
1689 ms
coupon
1870 ms
coupon
1929 ms
news
2197 ms
main.css
2317 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
49 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
95 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
95 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
96 ms
20240510_%E3%82%BB%E3%82%99%E3%83%8B%E3%82%A2%E3%82%AA%E3%82%A4%E5%AE%9A%E6%A4%8D.png
1833 ms
IG_24summer_sscampaign_banner_sp.png
5050 ms
ignis_SP_onlinebanner.jpg
1519 ms
IG_24summer_sscampaign_banner_pc_0.png
4638 ms
ignis_pc_onlinebanner.png
1509 ms
ig_float_btn.svg
4635 ms
common-aside-shop-pc.jpg
4537 ms
01.jpg
4479 ms
02.jpg
4498 ms
03.jpg
4476 ms
04.jpg
4478 ms
05.jpg
4385 ms
06.jpg
4334 ms
ig_bg.jpg
4331 ms
io_image-pc.jpg
3482 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
Image elements do not have [alt] attributes
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
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
ignis.jp SEO score
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 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: