Tools & Wizards About Us
homemate-navi.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

homemate-navi.com

ホームメイト・リサーチ　お役立ち情報｜住まいのお役立ち情報

Page Load Speed

6.6 sec in total

First Response

1.2 sec

Resources Loaded

5.1 sec

Page Rendered

389 ms

homemate-navi.com screenshot

About Website

Visit homemate-navi.com now to see the best up-to-date Homemate Navi content for Japan and also check out these interesting facts you probably never knew about homemate-navi.com

生活情報満載！住まいと暮らしの情報収集をするなら「ホームメイト・リサーチ　お役立ち情報」！

Visit homemate-navi.com

Key Findings

We analyzed Homemate-navi.com page load time and found that the first response time was 1.2 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

homemate-navi.com performance score

0

Network Requests Diagram

www.homemate-navi.com

1176 ms

common.css

927 ms

top.css

950 ms

jquery.min.js

1516 ms

format.js

554 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 76% of them (61 requests) were addressed to the original Homemate-navi.com, 15% (12 requests) were made to Token.co.jp and 3% (2 requests) were made to Smarticon.geotrust.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Homemate-navi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 200.0 kB (24%)

Content Size

839.9 kB

After Optimization

639.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Homemate-navi.com main page is 839.9 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. 20% of websites need less resources to load. Images take 578.1 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 36.2 kB

  • Original 42.9 kB
  • After minification 26.0 kB
  • After compression 6.6 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 16.9 kB, which is 39% 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 36.2 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 12.3 kB

  • Original 578.1 kB
  • After minification 565.7 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. Homemate Navi images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 121.5 kB

  • Original 183.8 kB
  • After minification 149.2 kB
  • After compression 62.3 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 121.5 kB or 66% of the original size.

CSS Optimization

-85%

Potential reduce by 30.0 kB

  • Original 35.1 kB
  • After minification 24.5 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. Homemate-navi.com needs all CSS files to be minified and compressed as it can save up to 30.0 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (38%)

Requests Now

79

After Optimization

49

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.homemate-navi.com

www.homemate-navi.com

1176 ms

common.css

common.css

927 ms

top.css

top.css

950 ms

jquery.min.js

jquery.min.js

1516 ms

format.js

format.js

554 ms

html5.js

html5.js

97 ms

nwmatcher.js

nwmatcher.js

1247 ms

smoothscroll.js

smoothscroll.js

759 ms

jquery.font.js

jquery.font.js

797 ms

si.js

si.js

50 ms

top_bnr_life_srch_m.gif

top_bnr_life_srch_m.gif

1569 ms

bnr_tokencup_m.jpg

bnr_tokencup_m.jpg

1263 ms

bnr_virtualshop_m.png

bnr_virtualshop_m.png

1041 ms

head_bg_line.gif

head_bg_line.gif

244 ms

head_logo.gif

head_logo.gif

231 ms

hm_logo.png

hm_logo.png

211 ms

top_back.jpg

top_back.jpg

1908 ms

midashi01.gif

midashi01.gif

225 ms

button01.gif

button01.gif

232 ms

button02.gif

button02.gif

423 ms

button03.gif

button03.gif

442 ms

button04.gif

button04.gif

442 ms

button05.gif

button05.gif

444 ms

button06.gif

button06.gif

445 ms

button07.gif

button07.gif

628 ms

button08.gif

button08.gif

667 ms

button09.gif

button09.gif

670 ms

button10.gif

button10.gif

667 ms

button11.gif

button11.gif

668 ms

button12.gif

button12.gif

827 ms

top-ttl01.gif

top-ttl01.gif

887 ms

illust01.png

illust01.png

889 ms

icon-s01.gif

icon-s01.gif

885 ms

top-ttl02.gif

top-ttl02.gif

890 ms

illust02.png

illust02.png

1039 ms

icon-s02.gif

icon-s02.gif

1093 ms

top-ttl03.gif

top-ttl03.gif

1102 ms

illust03.png

illust03.png

1104 ms

icon-s03.gif

icon-s03.gif

1105 ms

kanren-midashi.gif

kanren-midashi.gif

1247 ms

kanren-button.gif

kanren-button.gif

1317 ms

kanren-icon01.gif

kanren-icon01.gif

1316 ms

top-ttl04.gif

top-ttl04.gif

1318 ms

illust04.png

illust04.png

1321 ms

icon-s04.gif

icon-s04.gif

1456 ms

top-ttl05.gif

top-ttl05.gif

1529 ms

illust05.png

illust05.png

1529 ms

icon-s05.gif

icon-s05.gif

1530 ms

bnr_homemate_l.jpg

bnr_homemate_l.jpg

1444 ms

bnr_senior_l.jpg

bnr_senior_l.jpg

1644 ms

bnr_heartmarkshop_l.png

bnr_heartmarkshop_l.png

1033 ms

bnr_tokentour_m.jpg

bnr_tokentour_m.jpg

1905 ms

bnr_reform_m.jpg

bnr_reform_m.jpg

1095 ms

bnr_nasshowroom_m.jpg

bnr_nasshowroom_m.jpg

1483 ms

bnr_sumainotenji_m.jpg

bnr_sumainotenji_m.jpg

1545 ms

bnr_hmsenryu_m.jpg

bnr_hmsenryu_m.jpg

1461 ms

bnr_hmblog_m.gif

bnr_hmblog_m.gif

1896 ms

bnr_seniorblog_m.gif

bnr_seniorblog_m.gif

1672 ms

bnr_hmsblog_m.gif

bnr_hmsblog_m.gif

1699 ms

smarticon

smarticon

43 ms

kanren-midashi02.gif

kanren-midashi02.gif

1507 ms

ga.js

ga.js

77 ms

__utm.gif

__utm.gif

28 ms

kanren-icon02.gif

kanren-icon02.gif

1463 ms

top-ttl06.gif

top-ttl06.gif

1527 ms

illust06.png

illust06.png

1519 ms

top-ttl07.gif

top-ttl07.gif

1519 ms

top-ttl08.gif

top-ttl08.gif

1509 ms

top-ttl09.gif

top-ttl09.gif

1448 ms

top-ttl10.gif

top-ttl10.gif

1517 ms

top-ttl11.gif

top-ttl11.gif

1515 ms

top-ttl12.gif

top-ttl12.gif

1524 ms

illust_move.gif

illust_move.gif

1952 ms

img_right_dt.gif

img_right_dt.gif

1444 ms

img_qr_mb.gif

img_qr_mb.gif

1446 ms

img_qr_sp.gif

img_qr_sp.gif

1497 ms

font-l.gif

font-l.gif

1502 ms

font-m.gif

font-m.gif

1507 ms

font-s.gif

font-s.gif

1446 ms

font-bg.gif

font-bg.gif

1439 ms

SEO Factors

homemate-navi.com SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Homemate-navi.com 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 Homemate-navi.com 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

homemate-navi.com

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