Tools & Wizards About Us
e-myhome.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

e-myhome.co.jp

横浜の不動産は東宝ハウス横浜 - 新築一戸建て・中古一戸建て・土地・中古マンション

Page Load Speed

8.1 sec in total

First Response

517 ms

Resources Loaded

6.6 sec

Page Rendered

905 ms

e-myhome.co.jp screenshot

About Website

Visit e-myhome.co.jp now to see the best up-to-date E Myhome content for Japan and also check out these interesting facts you probably never knew about e-myhome.co.jp

神奈川・横浜の不動産なら東宝ハウス横浜へ。地域に密着した不動産、新築一戸建て、中古一戸建て、土地などの物件探しをお手伝い致します。無料会員登録で未公開物件情報閲覧出来ます。

Visit e-myhome.co.jp

Key Findings

We analyzed E-myhome.co.jp page load time and found that the first response time was 517 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

e-myhome.co.jp performance score

0

Network Requests Diagram

e-myhome.co.jp

517 ms

www.e-myhome.co.jp

1342 ms

layout.css

906 ms

text.css

694 ms

jquery-1.11.1.min.js

1391 ms

Our browser made a total of 131 requests to load all elements on the main page. We found that 78% of them (102 requests) were addressed to the original E-myhome.co.jp, 6% (8 requests) were made to Tg.socdm.com and 2% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain E-myhome.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 405.7 kB (16%)

Content Size

2.5 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of E-myhome.co.jp main page is 2.5 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. 40% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 78.7 kB

  • Original 94.4 kB
  • After minification 84.4 kB
  • After compression 15.7 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 10.0 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 78.7 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 122.3 kB

  • Original 2.1 MB
  • After minification 2.0 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. E Myhome images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 145.0 kB

  • Original 241.7 kB
  • After minification 234.8 kB
  • After compression 96.6 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 145.0 kB or 60% of the original size.

CSS Optimization

-81%

Potential reduce by 59.6 kB

  • Original 73.2 kB
  • After minification 55.6 kB
  • After compression 13.6 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. E-myhome.co.jp needs all CSS files to be minified and compressed as it can save up to 59.6 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

120

After Optimization

84

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

e-myhome.co.jp

e-myhome.co.jp

517 ms

www.e-myhome.co.jp

www.e-myhome.co.jp

1342 ms

layout.css

layout.css

906 ms

text.css

text.css

694 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

1391 ms

common.js

common.js

523 ms

jquery_auto.js

jquery_auto.js

360 ms

font-awesome.min.css

font-awesome.min.css

938 ms

my.jquery.accordion.js

my.jquery.accordion.js

546 ms

top.js

top.js

696 ms

so_sg.js

so_sg.js

119 ms

jquery.spy-effect.js

jquery.spy-effect.js

371 ms

s_retargeting.js

s_retargeting.js

554 ms

conversion.js

conversion.js

14 ms

chili-1.7.pack.js

chili-1.7.pack.js

187 ms

jquery.easing.js

jquery.easing.js

175 ms

jquery.dimensions.js

jquery.dimensions.js

176 ms

jquery.prex_accordion.js

jquery.prex_accordion.js

175 ms

img

img

608 ms

bg_wrapper.jpg

bg_wrapper.jpg

200 ms

bg_header_r.jpg

bg_header_r.jpg

195 ms

logo.jpg

logo.jpg

196 ms

menu01.jpg

menu01.jpg

194 ms

menu02.jpg

menu02.jpg

199 ms

menu03.jpg

menu03.jpg

196 ms

menu04.jpg

menu04.jpg

351 ms

menu05.jpg

menu05.jpg

352 ms

menu06.jpg

menu06.jpg

352 ms

menu07.jpg

menu07.jpg

355 ms

btn_header_src.jpg

btn_header_src.jpg

368 ms

top_banner.png

top_banner.png

542 ms

top_bnr_map01.jpg

top_bnr_map01.jpg

539 ms

top_bnr_map02.jpg

top_bnr_map02.jpg

537 ms

top_bnr_map03.jpg

top_bnr_map03.jpg

537 ms

top_bnr_map04.jpg

top_bnr_map04.jpg

539 ms

whatsnew.gif

whatsnew.gif

552 ms

bn_seminar.png

bn_seminar.png

878 ms

top_tit_sale.jpg

top_tit_sale.jpg

710 ms

arrow_down.gif

arrow_down.gif

709 ms

top_tit_seminars.jpg

top_tit_seminars.jpg

711 ms

top_tit_reccomend.jpg

top_tit_reccomend.jpg

720 ms

k604984_2.jpg

k604984_2.jpg

919 ms

k606706_2.jpg

k606706_2.jpg

882 ms

k606013_2.jpg

k606013_2.jpg

888 ms

k605993_2.jpg

k605993_2.jpg

1066 ms

k604073_2.jpg

k604073_2.jpg

902 ms

k593988_2.jpg

k593988_2.jpg

1221 ms

k578645_2.jpg

k578645_2.jpg

1227 ms

k603436_2.jpg

k603436_2.jpg

1064 ms

k574793_2.jpg

k574793_2.jpg

1629 ms

k604053_2.jpg

k604053_2.jpg

1286 ms

k603617_2.jpg

k603617_2.jpg

1240 ms

k603090_2.jpg

k603090_2.jpg

1414 ms

k603344_2.jpg

k603344_2.jpg

1396 ms

k603633_2.jpg

k603633_2.jpg

1534 ms

k603618_2.jpg

k603618_2.jpg

1233 ms

k603181_2.jpg

k603181_2.jpg

1472 ms

k603057_2.jpg

k603057_2.jpg

1916 ms

k603091_2.jpg

k603091_2.jpg

1403 ms

k602915_2.jpg

k602915_2.jpg

1408 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1573 ms

tag.js

tag.js

13 ms

js

js

398 ms

tag

tag

11 ms

ga.js

ga.js

5 ms

__utm.gif

__utm.gif

38 ms

49 ms

k602914_2.jpg

k602914_2.jpg

1460 ms

42 ms

btn_s_reg.jpg

btn_s_reg.jpg

1599 ms

bukken_num01.png

bukken_num01.png

1590 ms

bukken_num02.png

bukken_num02.png

1422 ms

bukken_num03.png

bukken_num03.png

1435 ms

bukken_num04.png

bukken_num04.png

1499 ms

bukken_num05.png

bukken_num05.png

1581 ms

bukken_num06.png

bukken_num06.png

1590 ms

bukken_num07.png

bukken_num07.png

1593 ms

sosync

sosync

196 ms

btn_s_hikoukai.png

btn_s_hikoukai.png

1512 ms

btn_s_merit.png

btn_s_merit.png

1572 ms

ti_s_login.png

ti_s_login.png

1582 ms

btn_s_longin.png

btn_s_longin.png

1582 ms

19 ms

sync

sync

506 ms

sync_before

sync_before

192 ms

sync_before

sync_before

195 ms

sync_before

sync_before

371 ms

idsync

idsync

373 ms

sync

sync

378 ms

20 ms

btn_src.jpg

btn_src.jpg

1444 ms

staff_banner.gif

staff_banner.gif

1524 ms

fb_banner.gif

fb_banner.gif

1567 ms

banner_sindan.jpg

banner_sindan.jpg

1563 ms

title_satei.jpg

title_satei.jpg

1560 ms

pixel

pixel

15 ms

cs

cs

325 ms

sync

sync

597 ms

banner_voice.jpg

banner_voice.jpg

1429 ms

48_vc_img1.jpg

48_vc_img1.jpg

1524 ms

sync

sync

496 ms

is

is

781 ms

Pug

Pug

19 ms

sd

sd

27 ms

47_vc_img1.jpg

47_vc_img1.jpg

1408 ms

46_vc_img1.jpg

46_vc_img1.jpg

1412 ms

45_vc_img1.jpg

45_vc_img1.jpg

1411 ms

ico_arrow_blue.jpg

ico_arrow_blue.jpg

1381 ms

tap.php

tap.php

6 ms

ad_PRG_1.jpg

ad_PRG_1.jpg

1379 ms

2_sm_banner.gif

2_sm_banner.gif

1386 ms

banner_white_m.jpg

banner_white_m.jpg

1395 ms

bnr_tetsukekin.jpg

bnr_tetsukekin.jpg

1253 ms

bnr_thr_recrute.jpg

bnr_thr_recrute.jpg

1429 ms

logo_thr.jpg

logo_thr.jpg

1742 ms

logo_footer.jpg

logo_footer.jpg

1334 ms

session.php

session.php

1325 ms

bg_bkbox_comment.jpg

bg_bkbox_comment.jpg

1185 ms

bg_s_bukken_num.png

bg_s_bukken_num.png

1190 ms

arrow_off.gif

arrow_off.gif

1202 ms

arrow2.gif

arrow2.gif

1207 ms

bg_footer.jpg

bg_footer.jpg

1210 ms

ico_arrow_gray.jpg

ico_arrow_gray.jpg

1226 ms

menu01_on.jpg

menu01_on.jpg

1229 ms

menu02_on.jpg

menu02_on.jpg

1303 ms

menu03_on.jpg

menu03_on.jpg

1227 ms

menu04_on.jpg

menu04_on.jpg

1221 ms

menu05_on.jpg

menu05_on.jpg

1230 ms

menu06_on.jpg

menu06_on.jpg

1228 ms

menu07_on.jpg

menu07_on.jpg

1287 ms

__utm.gif

__utm.gif

7 ms

SEO Factors

e-myhome.co.jp SEO score

0

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 E-myhome.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 E-myhome.co.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

e-myhome.co.jp

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