Tools & Wizards About Us
leohouse.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

leohouse.jp

注文住宅･自由設計の家づくりはハウスメーカーの【レオハウス】

Page Load Speed

11.5 sec in total

First Response

661 ms

Resources Loaded

10.5 sec

Page Rendered

320 ms

leohouse.jp screenshot

About Website

Click here to check amazing Leohouse content for Japan. Otherwise, check out these important facts you probably never knew about leohouse.jp

自由設計･注文住宅･ローコスト住宅･一戸建てを建てるならハウスメーカー･住宅メーカーのレオハウスにお任せください。東証一部上場ナックの企業グループ。資料請求･展示場の見学･お問い合わせなど、お気軽にご相談ください。

Visit leohouse.jp

Key Findings

We analyzed Leohouse.jp page load time and found that the first response time was 661 ms and then it took 10.8 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

leohouse.jp performance score

0

Network Requests Diagram

mainpc.php

661 ms

import.css

323 ms

default.css

324 ms

light.css

373 ms

dark.css

373 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 75% of them (68 requests) were addressed to the original Leohouse.jp, 3% (3 requests) were made to Googleadservices.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.4 sec) belongs to the original domain Leohouse.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 353.6 kB (11%)

Content Size

3.2 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 21.0 kB

  • Original 28.1 kB
  • After minification 25.9 kB
  • After compression 7.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 21.0 kB or 75% of the original size.

Image Optimization

-5%

Potential reduce by 153.5 kB

  • Original 2.9 MB
  • After minification 2.7 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. Leohouse images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 161.1 kB

  • Original 283.9 kB
  • After minification 259.1 kB
  • After compression 122.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 161.1 kB or 57% of the original size.

CSS Optimization

-78%

Potential reduce by 17.9 kB

  • Original 23.0 kB
  • After minification 15.1 kB
  • After compression 5.1 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. Leohouse.jp needs all CSS files to be minified and compressed as it can save up to 17.9 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (36%)

Requests Now

85

After Optimization

54

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mainpc.php

mainpc.php

661 ms

import.css

import.css

323 ms

default.css

default.css

324 ms

light.css

light.css

373 ms

dark.css

dark.css

373 ms

bar.css

bar.css

373 ms

nivo-slider.css

nivo-slider.css

524 ms

style.css

style.css

643 ms

rov.js

rov.js

692 ms

innerbanner.js

innerbanner.js

691 ms

pullmenu.js

pullmenu.js

692 ms

mm_menu.js

mm_menu.js

929 ms

leo_css.css

leo_css.css

893 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

1012 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

1492 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

1247 ms

default.css

default.css

747 ms

style.css

style.css

949 ms

ga.js

ga.js

32 ms

headerbase1.png

headerbase1.png

323 ms

logo.png

logo.png

324 ms

headertel1a.png

headertel1a.png

483 ms

navi_bg.png

navi_bg.png

324 ms

gNav_li_bg.png

gNav_li_bg.png

374 ms

mainpic_wall.jpg

mainpic_wall.jpg

704 ms

loading.gif

loading.gif

695 ms

6.jpg

6.jpg

921 ms

20.jpg

20.jpg

1628 ms

21.jpg

21.jpg

1679 ms

22.jpg

22.jpg

1788 ms

23.jpg

23.jpg

1660 ms

2.jpg

2.jpg

1827 ms

4.jpg

4.jpg

1853 ms

24.jpg

24.jpg

2600 ms

900pxbar.png

900pxbar.png

2033 ms

allfull_banner-3.png

allfull_banner-3.png

2425 ms

zeh_pc_banner.png

zeh_pc_banner.png

2346 ms

banner_surprise700.png

banner_surprise700.png

2571 ms

img_1dan.png

img_1dan.png

2980 ms

img_2dan.png

img_2dan.png

3161 ms

img_3dan.png

img_3dan.png

3656 ms

img_4dan.png

img_4dan.png

3734 ms

showroom_map01h.jpg

showroom_map01h.jpg

3505 ms

dot_700.png

dot_700.png

2969 ms

top_org.png

top_org.png

3290 ms

banner_nac.jpg

banner_nac.jpg

3301 ms

banner_nm.jpg

banner_nm.jpg

3482 ms

ban200_statement.jpg

ban200_statement.jpg

3849 ms

tvcm_bn.png

tvcm_bn.png

3861 ms

storeevent_ban2.jpg

storeevent_ban2.jpg

3966 ms

reasonwhy.jpg

reasonwhy.jpg

4065 ms

tel_bn2.png

tel_bn2.png

4135 ms

ask_bn2.png

ask_bn2.png

4292 ms

__utm.gif

__utm.gif

10 ms

bg-h3.png

bg-h3.png

3937 ms

autotag.html

autotag.html

3977 ms

tag.js

tag.js

9 ms

tag

tag

4 ms

bg-side-h3.png

bg-side-h3.png

4022 ms

list-arw.png

list-arw.png

4133 ms

lhi_00000584.jpg

lhi_00000584.jpg

4299 ms

lhi_00000462.jpg

lhi_00000462.jpg

4284 ms

lhi_00000466.jpg

lhi_00000466.jpg

4400 ms

lhi_00000467.jpg

lhi_00000467.jpg

4349 ms

lhi_00000469.gif

lhi_00000469.gif

3962 ms

footerbase1.png

footerbase1.png

3909 ms

bl_track.js

bl_track.js

365 ms

conversion.js

conversion.js

515 ms

conversion.js

conversion.js

54 ms

c

c

820 ms

conversion.js

conversion.js

1139 ms

827 ms

14 ms

35 ms

41 ms

tel_bn2b.png

tel_bn2b.png

483 ms

conversion_async.js

conversion_async.js

11 ms

fbevents.js

fbevents.js

135 ms

tag

tag

3 ms

ask_bn2b.png

ask_bn2b.png

483 ms

top.png

top.png

323 ms

headertel1b.png

headertel1b.png

484 ms

mainpc.php

mainpc.php

561 ms

bullets.png

bullets.png

374 ms

x.js

x.js

559 ms

13 ms

19 ms

15 ms

collectionx.aspx

collectionx.aspx

401 ms

item.js

item.js

369 ms

KcDeqwasAgent.js

KcDeqwasAgent.js

148 ms

SEO Factors

leohouse.jp SEO score

0

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

leohouse.jp

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