Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

inax.co.jp

INAXのトイレ・タイル建材

Page Load Speed

5.1 sec in total

First Response

338 ms

Resources Loaded

4.6 sec

Page Rendered

230 ms

inax.co.jp screenshot

About Website

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.jp

Key Findings

We 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.

Performance Metrics

inax.co.jp performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value16.7 s

0/100

25%

SI (Speed Index)

Value10.2 s

9/100

10%

TBT (Total Blocking Time)

Value3,050 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.25

50/100

15%

TTI (Time to Interactive)

Value20.9 s

2/100

10%

Network Requests Diagram

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

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 Optimization Overview & Recommendations

Page size can be reduced by 376.1 kB (34%)

Content Size

1.1 MB

After Optimization

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.

HTML Optimization

-80%

Potential reduce by 52.8 kB

  • Original 66.0 kB
  • After minification 63.6 kB
  • After compression 13.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 52.8 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 1.6 kB

  • Original 465.7 kB
  • After minification 464.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. Inax images are well optimized though.

JavaScript Optimization

-44%

Potential reduce by 156.6 kB

  • Original 354.8 kB
  • After minification 348.6 kB
  • After compression 198.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 156.6 kB or 44% of the original size.

CSS Optimization

-74%

Potential reduce by 165.0 kB

  • Original 222.0 kB
  • After minification 202.3 kB
  • After compression 56.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. 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.

Requests Breakdown

Number of requests can be reduced by 51 (64%)

Requests Now

80

After Optimization

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.

Accessibility Review

inax.co.jp accessibility score

83

Accessibility Issues

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

inax.co.jp best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

inax.co.jp SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    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.

Social Sharing Optimization

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: