10.7 sec in total
485 ms
9.3 sec
872 ms
Visit e-life.jp now to see the best up-to-date E LIFE content for Japan and also check out these interesting facts you probably never knew about e-life.jp
まだまだ見つかるいい住まい!E-LIFE(イーライフ)は全国の不動産売買・賃貸物件などを扱う不動産住宅情報サイトです。あなたにぴったりのいい住まい、住宅情報がきっと見つかります。住まい探しの総合パートナー【E-LIFE】で検索!
Visit e-life.jpWe analyzed E-life.jp page load time and found that the first response time was 485 ms and then it took 10.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
e-life.jp performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value7.3 s
4/100
25%
Value6.8 s
35/100
10%
Value170 ms
93/100
30%
Value0.132
81/100
15%
Value12.6 s
14/100
10%
485 ms
1388 ms
309 ms
315 ms
360 ms
Our browser made a total of 222 requests to load all elements on the main page. We found that 72% of them (160 requests) were addressed to the original E-life.jp, 15% (34 requests) were made to Maps.google.com and 3% (7 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain E-life.jp.
Page size can be reduced by 740.8 kB (21%)
3.5 MB
2.7 MB
In fact, the total size of E-life.jp main page is 3.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. 70% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 86.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 86.1 kB or 85% of the original size.
Potential reduce by 140.5 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. E LIFE images are well optimized though.
Potential reduce by 483.7 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 483.7 kB or 65% of the original size.
Potential reduce by 30.5 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-life.jp needs all CSS files to be minified and compressed as it can save up to 30.5 kB or 83% of the original size.
Number of requests can be reduced by 87 (40%)
215
128
The browser has sent 215 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E LIFE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
e-life.jp
485 ms
www.e-life.jp
1388 ms
base.css
309 ms
site.css
315 ms
header.css
360 ms
top.css
540 ms
js
28 ms
jquery-1.11.2.min.js
923 ms
jquery.easing-1.3.js
463 ms
map_win.js
481 ms
top_free_search.js
521 ms
common_gimmick.js
533 ms
jcarousellite.js
618 ms
jcarousellite_set.js
637 ms
all_cnt.js
693 ms
all_cnt_nm.js
706 ms
ElUtil.js
720 ms
srch_frw_top.js
773 ms
get_openhouse_map.js
959 ms
el_bb_common.js
866 ms
slider.js
889 ms
slider_set.js
897 ms
def.js
942 ms
scrolldepth.min.js
1043 ms
set_info.js
765 ms
check_UA.js
765 ms
conversion.js
19 ms
s_retargeting.js
607 ms
analytics.js
23 ms
dc.js
30 ms
collect
13 ms
inpage_linkid.js
10 ms
__utm.gif
13 ms
logo.gif
263 ms
buy.png
179 ms
kind01.png
180 ms
kind02.png
261 ms
kind03.png
267 ms
kind04.png
267 ms
kind05.png
381 ms
tokyo.gif
381 ms
kanagawa.gif
387 ms
chiba.gif
386 ms
saitama.gif
385 ms
btn1.gif
418 ms
btn2.gif
518 ms
btn3.gif
519 ms
kyword_back.png
1084 ms
kyword.png
578 ms
word_nozzle.gif
580 ms
word_explain.png
933 ms
kyword_plus.png
677 ms
kyword_out.png
678 ms
kind1.png
722 ms
851 ms
1045 ms
kind3.png
801 ms
1168 ms
1374 ms
1133 ms
kind2.png
1111 ms
1476 ms
1368 ms
1408 ms
kind5.png
1313 ms
1446 ms
1564 ms
1610 ms
fbevents.js
75 ms
158 ms
1697 ms
common.js
39 ms
map.js
40 ms
collect
93 ms
__utm.gif
92 ms
top_get_last_cond.php
1522 ms
139 ms
1717 ms
util.js
47 ms
onion.js
48 ms
openhand_8_8.cur
81 ms
1485 ms
1644 ms
118 ms
1664 ms
1917 ms
ViewportInfoService.GetViewportInfo
212 ms
stats.js
42 ms
controls.js
41 ms
transparent.png
36 ms
css
43 ms
1772 ms
1694 ms
1793 ms
left_btn.png
1700 ms
right_btn.png
1715 ms
google4.png
92 ms
mapcnt6.png
80 ms
sv5.png
79 ms
top_banner.jpg
2231 ms
tmapctrl.png
45 ms
google_white5.png
43 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
39 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
89 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
91 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
92 ms
btn.png
1794 ms
27901_sum.jpg
1751 ms
27921_sum.jpg
1727 ms
27841_sum.jpg
1719 ms
vt
82 ms
vt
144 ms
vt
75 ms
vt
74 ms
vt
71 ms
vt
70 ms
vt
116 ms
vt
147 ms
vt
117 ms
vt
143 ms
vt
134 ms
vt
186 ms
vt
160 ms
vt
192 ms
vt
196 ms
vt
189 ms
vt
194 ms
vt
230 ms
vt
230 ms
vt
226 ms
vt
233 ms
vt
238 ms
vt
247 ms
vt
268 ms
vt
266 ms
top_openhouse.php
2565 ms
27801_sum.jpg
1681 ms
27641_sum.jpg
1735 ms
27661_sum.jpg
1689 ms
25262_sum.jpg
1685 ms
25245_sum.jpg
1601 ms
AuthenticationService.Authenticate
193 ms
left.png
1566 ms
right.png
1593 ms
map_btn.png
1784 ms
loading.gif
1579 ms
image.png
1923 ms
title.png
1551 ms
btn.png
1498 ms
menu1.png
1517 ms
top.jpg
1614 ms
menu2.png
1599 ms
menu2_btn.png
2128 ms
menu3.png
1469 ms
top.png
1856 ms
menu4.png
1537 ms
top.png
2055 ms
menu5.png
1480 ms
top.png
2093 ms
menu6.png
1513 ms
menu6_btn.png
1780 ms
trend.jpg
2029 ms
smartp.jpg
1586 ms
pdf.jpg
1688 ms
facebook.gif
1678 ms
tatesuma.jpg
1685 ms
corp.jpg
1788 ms
sell.jpg
1696 ms
loan.jpg
1676 ms
moving.jpg
1708 ms
recruit_banner.png
1804 ms
recommendation.png
1791 ms
logo.png
1679 ms
geoprint_210_65.jpg
1686 ms
bn_sanjo.jpg
1641 ms
h_ms_bar_t.gif
1738 ms
h_ms_bar_b1.png
1682 ms
h_ms_bar_b2.png
1648 ms
h_ms_bar_b3.png
1628 ms
h_ms_bar_match.png
1616 ms
h_ms_bar_home.png
1491 ms
f_pt.png
1579 ms
close.png
1561 ms
btn1.png
1599 ms
btn2.png
1460 ms
btn3.png
1466 ms
btn4.png
1472 ms
btn5.png
1529 ms
induction.png
1380 ms
marker.js
36 ms
title_kind01.gif
1363 ms
area_btn.png
1387 ms
infowindow.js
4 ms
rosen_btn.png
1283 ms
title_kind02.gif
1220 ms
title_kind03.gif
1162 ms
title_kind04.gif
1127 ms
title_kind05.gif
1090 ms
search_back.jpg
1061 ms
left.png
1081 ms
right.png
1084 ms
back.png
1066 ms
bg.jpg
999 ms
title_bg.png
980 ms
back.jpg
1213 ms
back.jpg
1069 ms
top.png
1075 ms
over.png
982 ms
shadow.png
965 ms
h_ms_bar_back2.png
990 ms
h_ms_bar_back.png
1076 ms
back.png
1064 ms
area.gif
1098 ms
use.png
2445 ms
close.png
1020 ms
mysearch.png
1045 ms
point4.png
1089 ms
point1.png
1060 ms
point3.png
1099 ms
point_m.png
1042 ms
point2.png
1085 ms
QuotaService.RecordEvent
13 ms
e-life.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
e-life.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
e-life.jp SEO score
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
Document uses legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-life.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-life.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.
e-life.jp
Open Graph description is not detected on the main page of E LIFE. 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: