Tools & Wizards About Us
tostem-fc.jp screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

tostem-fc.jp

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

Page Load Speed

7.2 sec in total

First Response

549 ms

Resources Loaded

5.8 sec

Page Rendered

913 ms

tostem-fc.jp screenshot

About Website

Welcome to tostem-fc.jp homepage info - get ready to check Tostem Fc best content for Japan right away, or after learning these important things about tostem-fc.jp

インプラス,サッシはマドリエNET 全国版はこちら！マドリエは地域密着型『住まいの何でも相談口』リクシルフランチャイズチェーン(LIXIL FC)情報サイトです。

Visit tostem-fc.jp

Key Findings

We analyzed Tostem-fc.jp page load time and found that the first response time was 549 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

tostem-fc.jp performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value15.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.8 s

0/100

25%

SI (Speed Index)

Value18.0 s

0/100

10%

TBT (Total Blocking Time)

Value170 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value1.326

0/100

15%

TTI (Time to Interactive)

Value17.5 s

4/100

10%

Network Requests Diagram

tostem-fc.jp

549 ms

www.lixil-madolier.jp

962 ms

NationalTopPage.df

743 ms

jquery-ui.min.css

728 ms

analytics.js

25 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Tostem-fc.jp, 83% (69 requests) were made to Lixil-madolier.jp and 4% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Lixil-madolier.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 84.2 kB (72%)

Content Size

116.3 kB

After Optimization

32.1 kB

  • HTML
  • JavaScript

In fact, the total size of Tostem-fc.jp main page is 116.3 kB. 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. HTML takes 63.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 52.2 kB

  • Original 63.4 kB
  • After minification 56.7 kB
  • After compression 11.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. This page needs HTML code to be minified as it can gain 6.7 kB, which is 11% 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 52.2 kB or 82% of the original size.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.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 32.0 kB or 60% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (45%)

Requests Now

75

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tostem-fc.jp

tostem-fc.jp

549 ms

www.lixil-madolier.jp

www.lixil-madolier.jp

962 ms

NationalTopPage.df

NationalTopPage.df

743 ms

jquery-ui.min.css

jquery-ui.min.css

728 ms

analytics.js

analytics.js

25 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

930 ms

jquery-ui.min.js

jquery-ui.min.js

1307 ms

datepicker-ja.js

datepicker-ja.js

567 ms

jquery.ui.touch-punch.min.js

jquery.ui.touch-punch.min.js

575 ms

ckeditor.js

ckeditor.js

1733 ms

all.css

all.css

1131 ms

owl.carousel.css

owl.carousel.css

769 ms

owl.theme.default.css

owl.theme.default.css

909 ms

owl.carousel.js

owl.carousel.js

1155 ms

ofi.min.js

ofi.min.js

1090 ms

js

js

65 ms

js

js

122 ms

nationaltop.js

nationaltop.js

1115 ms

css2

css2

39 ms

Frame.css

Frame.css

1271 ms

AppFrame.css

AppFrame.css

1300 ms

animate.css

animate.css

1506 ms

designer.css

designer.css

1348 ms

areaQueryForm.css

areaQueryForm.css

1452 ms

sectionTitle.css

sectionTitle.css

1485 ms

mainArea.css

mainArea.css

1491 ms

pager.css

pager.css

1541 ms

Entry.css

Entry.css

1634 ms

style.css

style.css

1671 ms

jquery.rwdImageMaps.js

jquery.rwdImageMaps.js

1299 ms

FramePC.css

FramePC.css

216 ms

AppFramePC.css

AppFramePC.css

216 ms

css

css

83 ms

logo-header.png

logo-header.png

216 ms

icon_question_gray.png

icon_question_gray.png

215 ms

icon_map_gray.png

icon_map_gray.png

216 ms

icon_menu.png

icon_menu.png

214 ms

menu.png

menu.png

408 ms

close.png

close.png

409 ms

n11.jpg

n11.jpg

757 ms

n22.jpg

n22.jpg

410 ms

n33.jpg

n33.jpg

754 ms

n44.jpg

n44.jpg

409 ms

icon_map.png

icon_map.png

590 ms

MAP.png

MAP.png

954 ms

js

js

106 ms

collect

collect

78 ms

search.png

search.png

395 ms

search-mark.png

search-mark.png

387 ms

icon_question.png

icon_question.png

573 ms

img1.jpg

img1.jpg

588 ms

img2.jpg

img2.jpg

587 ms

img3.jpg

img3.jpg

746 ms

img4.jpg

img4.jpg

741 ms

icon_info.png

icon_info.png

767 ms

bottom5.jpg

bottom5.jpg

781 ms

bottom6.jpg

bottom6.jpg

780 ms

bottom7.jpg

bottom7.jpg

924 ms

bottom8.jpg

bottom8.jpg

934 ms

bottom4.jpg

bottom4.jpg

943 ms

bottom2.jpg

bottom2.jpg

946 ms

bottom3.jpg

bottom3.jpg

973 ms

bottom1.jpg

bottom1.jpg

974 ms

bottom9.jpg

bottom9.jpg

1105 ms

bottom10.png

bottom10.png

1122 ms

saved_resource(2).html

saved_resource(2).html

1121 ms

collect

collect

150 ms

JTUSjIg69CK48gW7PXooxW4.ttf

JTUSjIg69CK48gW7PXooxW4.ttf

120 ms

fa-solid-900.woff

fa-solid-900.woff

938 ms

fa-regular-400.woff

fa-regular-400.woff

972 ms

ga-audiences

ga-audiences

39 ms

reset.css

reset.css

187 ms

common.css

common.css

194 ms

20170224132213.png

20170224132213.png

191 ms

20161027105108.png

20161027105108.png

183 ms

20161027105109.png

20161027105109.png

191 ms

20161027105110.png

20161027105110.png

230 ms

20161027105111.png

20161027105111.png

365 ms

css

css

18 ms

2sDfZG1Wl4LcnbuKjk0j.ttf

2sDfZG1Wl4LcnbuKjk0j.ttf

4 ms

2sDcZG1Wl4LcnbuCNWgzaGW8.ttf

2sDcZG1Wl4LcnbuCNWgzaGW8.ttf

9 ms

FrameSP.css

FrameSP.css

195 ms

AppFrameSP.css

AppFrameSP.css

195 ms

Accessibility Review

tostem-fc.jp accessibility score

75

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Internationalization and localization

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

Impact

Issue

High

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

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

tostem-fc.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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

tostem-fc.jp SEO score

87

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 uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tostem-fc.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Tostem-fc.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.

Social Sharing Optimization

tostem-fc.jp

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