Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

toex.lixil.co.jp

LIXIL | エクステリア

Page Load Speed

11.6 sec in total

First Response

1.2 sec

Resources Loaded

10 sec

Page Rendered

377 ms

toex.lixil.co.jp screenshot

About Website

Welcome to toex.lixil.co.jp homepage info - get ready to check Toex LIXIL best content for Japan right away, or after learning these important things about toex.lixil.co.jp

住まいをつつむ門扉、フェンス、カーポート、ガーデンルームなど、エクステリア商品をご紹介したラインアップページです。さまざまなデザインや機能性をもったアイテム同士の組み合わせで、エクステリアの表情は無限に広がります。

Visit toex.lixil.co.jp

Key Findings

We analyzed Toex.lixil.co.jp page load time and found that the first response time was 1.2 sec and then it took 10.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

toex.lixil.co.jp performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

39/100

25%

SI (Speed Index)

Value16.2 s

0/100

10%

TBT (Total Blocking Time)

Value2,610 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.206

60/100

15%

TTI (Time to Interactive)

Value24.7 s

0/100

10%

Network Requests Diagram

toex.lixil.co.jp

1194 ms

reset_exslvzr.css

497 ms

common.css

679 ms

clearfix_exslvzr.css

518 ms

layout.css

572 ms

Our browser made a total of 148 requests to load all elements on the main page. We found that 74% of them (109 requests) were addressed to the original Toex.lixil.co.jp, 5% (7 requests) were made to Apis.google.com and 2% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (5.5 sec) relates to the external source Search.lixil.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 421.1 kB (25%)

Content Size

1.7 MB

After Optimization

1.2 MB

In fact, the total size of Toex.lixil.co.jp main page is 1.7 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. 60% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 38.5 kB

  • Original 50.8 kB
  • After minification 44.8 kB
  • After compression 12.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 6.0 kB, which is 12% 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 38.5 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 4.9 kB

  • Original 1.1 MB
  • After minification 1.1 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. Toex LIXIL images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 300.6 kB

  • Original 456.6 kB
  • After minification 415.0 kB
  • After compression 156.0 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 300.6 kB or 66% of the original size.

CSS Optimization

-88%

Potential reduce by 77.1 kB

  • Original 87.9 kB
  • After minification 63.0 kB
  • After compression 10.8 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. Toex.lixil.co.jp needs all CSS files to be minified and compressed as it can save up to 77.1 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 78 (53%)

Requests Now

146

After Optimization

68

The browser has sent 146 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Toex LIXIL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

toex.lixil.co.jp accessibility score

61

Accessibility Issues

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

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

toex.lixil.co.jp best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

toex.lixil.co.jp SEO score

77

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

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 Toex.lixil.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 Toex.lixil.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 Toex LIXIL. 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: