Access lixil-madolier.jp. サッシ・インプラスのご相談はＬＩＸＩＬＦＣマドリエ【全国版】

name

value

score

weighting

FCP (First Contentful Paint)

Value34.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value50.5 s

0/100

25%

SI (Speed Index)

Value46.6 s

0/100

10%

TBT (Total Blocking Time)

Value970 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value1.23

1/100

15%

TTI (Time to Interactive)

Value40.3 s

0/100

10%

lixil-madolier.jp

444 ms

index.php

1914 ms

local-contents.css

774 ms

portal-contents.css

822 ms

style.css

666 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 92% of them (99 requests) were addressed to the original Lixil-madolier.jp, 2% (2 requests) were made to Tr.webantenna.info and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Lixil-madolier.jp.

Content Size

2.9 MB

After Optimization

2.6 MB

In fact, the total size of Lixil-madolier.jp main page is 2.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. 50% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 37.8 kB

Original 46.8 kB
After minification 45.4 kB
After compression 9.1 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.8 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 100.2 kB

Original 2.7 MB
After minification 2.6 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. Lixil Madolier images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 62.2 kB

Original 116.0 kB
After minification 111.5 kB
After compression 53.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 62.2 kB or 54% of the original size.

CSS Optimization

-87%

Potential reduce by 76.5 kB

Original 87.8 kB
After minification 64.5 kB
After compression 11.3 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. Lixil-madolier.jp needs all CSS files to be minified and compressed as it can save up to 76.5 kB or 87% of the original size.

Requests Now

104

After Optimization

The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lixil Madolier. 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.

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

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

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Links do not have descriptive text

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

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

JA
Language Claimed

JA
Encoding

EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lixil-madolier.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 Lixil-madolier.jp main page’s claimed encoding is euc-jp. 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

lixil-madolier.jp

Open Graph description is not detected on the main page of Lixil Madolier. 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:

Report Summary

Performance

Accessibility

Best Practices

SEO

サッシ・インプラスのご相談はＬＩＸＩＬ ＦＣ マドリエ【全国版】

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

lixil-madolier.jp

index.php

local-contents.css

portal-contents.css

style.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

lixil-madolier.jp

index.php

local-contents.css

portal-contents.css

style.css

rollover.js

jquery.js

slider.js

init.js

maphilight.js

webantenna.js

analytics.js

s20090730153035.gif

lixil_linkbanner1.gif

text_otanoshimi.png

body_bg.gif

topbar_logo.gif

search_btn.gif

header_logo.gif

header_contact_off.gif

navi_bg.gif

01_active.gif

02_off.gif

03_off.gif

04_off.gif

05_off.gif

06_off.gif

07_off.gif

all.gif

slide_shadow.gif

img4.jpg

img2w.jpg

img3b.jpg

side_bana_rechent.gif

side_bana_search.gif

side_bana_blog.gif

side_bana_iecoco.gif

side_bana_inplus2.gif

sidelabel_bg.gif

s20130611135532.jpg

s20091030164241.jpg

s20110613102155.gif

s20130819115921.gif

サッシ・インプラスのご相談はＬＩＸＩＬＦＣマドリエ【全国版】