5.1 sec in total
338 ms
4.6 sec
230 ms
Welcome to inax.co.jp homepage info - get ready to check Inax best content for Japan right away, or after learning these important things about inax.co.jp
INAXのトイレ・タイル建材をご紹介する公式サイト。家づくりや暮らしに役立つ情報をご提案するコンテンツもご用意しました。
Visit inax.co.jpWe analyzed Inax.co.jp page load time and found that the first response time was 338 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
inax.co.jp performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value16.7 s
0/100
25%
Value10.2 s
9/100
10%
Value3,050 ms
2/100
30%
Value0.25
50/100
15%
Value20.9 s
2/100
10%
338 ms
663 ms
98 ms
109 ms
108 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Inax.co.jp, 55% (46 requests) were made to Lixil.co.jp and 14% (12 requests) were made to Inax.lixil.co.jp. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Lixil.co.jp.
Page size can be reduced by 376.1 kB (34%)
1.1 MB
732.4 kB
In fact, the total size of Inax.co.jp 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 465.7 kB which makes up the majority of the site volume.
Potential reduce by 52.8 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 52.8 kB or 80% of the original size.
Potential reduce by 1.6 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. Inax images are well optimized though.
Potential reduce by 156.6 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 156.6 kB or 44% of the original size.
Potential reduce by 165.0 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. Inax.co.jp needs all CSS files to be minified and compressed as it can save up to 165.0 kB or 74% of the original size.
Number of requests can be reduced by 51 (64%)
80
29
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Inax. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
inax.co.jp
338 ms
inax.lixil.co.jp
663 ms
common.v01.css
98 ms
lineup.v01.css
109 ms
print.css
108 ms
brand.css
482 ms
head.js
107 ms
jquery-1.8.3.min.js
124 ms
slick.min.js
119 ms
jquery.placeholder.js
117 ms
jquery.easing.1.3.js
124 ms
header_other.js
124 ms
footer_other.js
136 ms
module.v01.js
141 ms
foot.js
183 ms
load_cmn_footer.js
187 ms
sns_generate.js
142 ms
heightLine.js
142 ms
jquery.js
26 ms
gtm.js
167 ms
default_toiletroom_img_01.png
502 ms
default_tile_img_01.png
882 ms
default_public_img_01.png
1089 ms
default_inax.jpg
881 ms
default_navi_img_01.png.png
881 ms
default_showroom_img_01.png
1089 ms
default_catalog_img_01.png
884 ms
logo_inax.svg
65 ms
sdk.js
71 ms
bg_contents.png
103 ms
bg_topicpath.gif
499 ms
ttl_bg.png
876 ms
icon_link_l.gif
498 ms
icon_blank2.gif
501 ms
bg_inner.png
873 ms
mfx-sbox.css
53 ms
h_logo.png
823 ms
icon_close.gif
1216 ms
drop_showroom_map.gif
821 ms
drop_showroom_bn01.jpg
824 ms
drop_showroom_bn02.jpg
1403 ms
icon_disaster.png
1217 ms
bnr_safety.png
1404 ms
bnr_loc.png
1407 ms
bnr_longterm.gif
1404 ms
bnr_buhinnavi.png
1586 ms
sdk.js
4 ms
156 ms
font-awesome.css
8 ms
icon_search.png
1909 ms
utility.png
1721 ms
gnav.png
1447 ms
icon_facebook_f.png
1473 ms
icon_instagram_f.png
1694 ms
icon_twitter_f.png
1623 ms
icon_tiktok_f.png
2759 ms
copyright.gif
1841 ms
footer-logo.gif
2073 ms
btn_pagetop.png
2003 ms
line_footer.gif
2297 ms
icon_blank3.gif
2307 ms
mfx-sbox.js
57 ms
js
132 ms
js
58 ms
ytag.js
1142 ms
analytics.js
524 ms
gtm.js
392 ms
gtm.js
594 ms
gtm.js
593 ms
fbevents.js
380 ms
tag.js
455 ms
btn_close.gif
302 ms
btn_sns_twitter.gif
304 ms
btn_sns_facebook.gif
302 ms
destination
225 ms
destination
223 ms
destination
220 ms
munchkin.js
402 ms
collect
190 ms
collect
194 ms
www.lixil.co.jp
885 ms
ga-audiences
203 ms
munchkin.js
3 ms
visitWebPage
315 ms
inax.co.jp accessibility score
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.
inax.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
inax.co.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 doesn't use legible font sizes
Tap targets are not sized appropriately
JA
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inax.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 Inax.co.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
inax.co.jp
Open Graph description is not detected on the main page of Inax. 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: