9.7 sec in total
1.5 sec
7.9 sec
267 ms
Visit eyefulhome.jp now to see the best up-to-date Eyefulhome content for Japan and also check out these interesting facts you probably never knew about eyefulhome.jp
住宅メーカーと工務店のメリットを併せもったフランチャイズのハウスメーカー『アイフルホーム』は、抜本的に住宅供給システムの全プロセスを見直し、品質を高めることで良い家を合理的な価格で提供する事を実現しました。商品情報、お近くの住宅展示場・モデルハウスのご案内、キャンペーン情報、建築工法、住宅ローン、新築時にかかる税金等、一戸建て住宅を注文住宅で建てる際の情報が満載です。
Visit eyefulhome.jpWe analyzed Eyefulhome.jp page load time and found that the first response time was 1.5 sec and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
eyefulhome.jp performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value26.1 s
0/100
25%
Value16.1 s
0/100
10%
Value2,000 ms
7/100
30%
Value0
100/100
15%
Value40.8 s
0/100
10%
1549 ms
560 ms
375 ms
566 ms
379 ms
Our browser made a total of 239 requests to load all elements on the main page. We found that 69% of them (166 requests) were addressed to the original Eyefulhome.jp, 2% (5 requests) were made to Google-analytics.com and 2% (4 requests) were made to Navicast.jp. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Eyefulhome.jp.
Page size can be reduced by 427.6 kB (13%)
3.3 MB
2.9 MB
In fact, the total size of Eyefulhome.jp main page is 3.3 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. 60% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 54.4 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 12.4 kB, which is 18% 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 54.4 kB or 80% of the original size.
Potential reduce by 178.0 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. Eyefulhome images are well optimized though.
Potential reduce by 164.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 164.6 kB or 62% 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. Eyefulhome.jp needs all CSS files to be minified and compressed as it can save up to 30.5 kB or 84% of the original size.
Number of requests can be reduced by 105 (50%)
212
107
The browser has sent 212 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eyefulhome. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
eyefulhome.jp
1549 ms
css.js
560 ms
pagetop.js
375 ms
fontchanger.js
566 ms
run_flash.js
379 ms
cngimg.js
388 ms
caution.js
562 ms
top.js
568 ms
AC_RunActiveContent.js
775 ms
jquery.js
1118 ms
jquery.transitionAnimate.js
748 ms
fadeslideshow.js
939 ms
ipadTopData.js
754 ms
ipad_set.js
934 ms
style.css
1132 ms
top3.css
975 ms
ipad_main.css
939 ms
s.js
945 ms
win_ie.css
578 ms
g.RcvShowcase
1076 ms
conversion.js
14 ms
NavicastApi.js
758 ms
common.css
379 ms
lb
26 ms
logo01.gif
200 ms
navi_dotted.gif
191 ms
lb
21 ms
logo02.gif
189 ms
g_navi001.gif
196 ms
navi_dotted.gif
197 ms
g_navi002.gif
192 ms
g_navi003.gif
197 ms
g_navi004.gif
386 ms
g_navi005.gif
386 ms
g_navi006.gif
406 ms
g_navi007.gif
388 ms
g_navi008.gif
388 ms
h_navi01.gif
404 ms
h_navi02.gif
559 ms
h_navi03.gif
564 ms
ttl_search.gif
567 ms
btn_search.gif
568 ms
btn_document_request00.gif
595 ms
menu1_menu1.png
594 ms
menu1_menu2.png
748 ms
menu1_img1.png
1124 ms
menu1_back1.png
943 ms
FLM_Image_11.png
758 ms
FLM_Image_12.png
788 ms
FLM_Image_13.png
789 ms
FLM_Image_14.png
934 ms
FLM_Image_15.png
946 ms
FLM_Image_16.png
983 ms
FLM_Image_17.png
983 ms
FLM_Image_18.png
1122 ms
FLM_Image_19.png
1131 ms
FLM_Image_20.png
1134 ms
FLM_Image_21.png
1185 ms
FLM_Image_22.png
1186 ms
120620keyword_photo_on_08.png
1308 ms
120620keyword_photo_off_08.png
1310 ms
120620keyword_photo_on_10.png
1320 ms
120620keyword_photo_off_10.png
1142 ms
FLM_Image_30.png
1188 ms
FLM_Image_29.png
1186 ms
FLM_Image_33.png
1307 ms
FLM_Image_32.png
1310 ms
FLM_Image_35.png
1322 ms
gtm.js
68 ms
ga.js
30 ms
bl_track.js
372 ms
50 ms
__utm.gif
23 ms
synapcap.js
635 ms
FLM_Image_36.png
1135 ms
FLM_Image_39.png
1189 ms
FLM_Image_38.png
1187 ms
41 ms
menu1_kodawari_back1.png
1290 ms
collect
68 ms
menu1_kodawari_back2.png
1287 ms
NavicastTmg.php
192 ms
analytics.js
16 ms
menu1_back2.png
1293 ms
46 ms
27 ms
collect
21 ms
collect
27 ms
collect
30 ms
collect
38 ms
26 ms
baner1.jpg
1719 ms
baner3.jpg
1206 ms
baner13.jpg
1412 ms
menu2_back.png
1871 ms
menu3_img1.png
1285 ms
menu3_img2.png
1488 ms
NavicastApi2.php
195 ms
NavicastApi2.php
575 ms
bl_track.cgi
383 ms
menu3_img3.png
1231 ms
menu3_img4_1.png
1308 ms
menu3_img4_2.png
1368 ms
menu3_img4_3.png
1371 ms
menu3_img4.png
1319 ms
menu3_img5_1.png
1332 ms
menu3_img5_2.png
1403 ms
menu3_img5_3.png
1371 ms
menu3_img5.png
1457 ms
menu3_img6.png
1343 ms
menu3_img7.png
1343 ms
menu4_back.png
1998 ms
menu5_img1.png
1611 ms
s_retargeting.js
534 ms
menu5_img2.png
1628 ms
menu5_img3.png
1630 ms
menu5_img4.png
1533 ms
menu5_back.png
1343 ms
menu6_img1.png
1525 ms
menu6_img2.png
1618 ms
menu8_back.png
1628 ms
menu7_mirairich.jpg
1818 ms
menu8_img1.png
1919 ms
menu8_img2.png
1735 ms
detail_share_bg.png
1627 ms
close.png
1678 ms
main_back.png
2937 ms
menu1.png
1765 ms
menu_selected.png
1696 ms
menu_point.png
1696 ms
menu2.png
1714 ms
rtm.js
239 ms
x.js
548 ms
15 ms
18 ms
menu3.png
1765 ms
menu4.png
1693 ms
RequestHandlingServlet
474 ms
menu5.png
1598 ms
menu6.png
1630 ms
menu7.png
1544 ms
menu8.png
1649 ms
top_banner01.jpg
1604 ms
top_banner20.jpg
1603 ms
top_rakurashi2015.jpg
1546 ms
collectionx.aspx
328 ms
top.js
300 ms
top_banner17.jpg
1526 ms
park_btn01.jpg
1650 ms
park_btn02.jpg
1604 ms
park_btn03.jpg
1598 ms
park_btn04.jpg
1549 ms
park_btn05.jpg
1548 ms
set
302 ms
park_btn13.jpg
1656 ms
park_btn07.jpg
1676 ms
KcDeqwasAgent.js
151 ms
park_btn08.jpg
1486 ms
Collection.aspx
155 ms
park_btn009.jpg
1430 ms
park_btn10.jpg
1363 ms
park_btn11.jpg
1499 ms
park_btn14.jpg
1484 ms
news_title.gif
1482 ms
rtbsync.js
14 ms
Sync.aspx
299 ms
Sync.aspx
326 ms
Sync.aspx
318 ms
Sync.aspx
327 ms
Sync.aspx
328 ms
Sync.aspx
331 ms
Sync.aspx
302 ms
Sync.aspx
308 ms
Sync.aspx
329 ms
Sync.aspx
313 ms
Sync.aspx
310 ms
Sync.aspx
318 ms
Sync.aspx
330 ms
Sync.aspx
302 ms
Sync.aspx
305 ms
Sync.aspx
331 ms
DynamicRetargetUserSync.aspx
309 ms
Collection.aspx
334 ms
btn_press_release.gif
1425 ms
bnr_reform.jpg
1366 ms
bnr_yokai_cp_160128.jpg
1382 ms
sub_b_enjoy.jpg
1377 ms
sub_b34.jpg
1324 ms
sub_b_antlers.jpg
1363 ms
304 ms
cs
391 ms
sync
15 ms
Sync.aspx
498 ms
cookiesync
304 ms
sync
614 ms
btn_sonybank.jpg
1324 ms
sd
6 ms
tap.php
14 ms
sub_b51.jpg
1368 ms
sub_b_mail.jpg
1323 ms
sub_b06.jpg
1320 ms
g_banner_header.gif
1289 ms
btn_lixil.jpg
1330 ms
Collection.aspx
150 ms
Collection.aspx
164 ms
Collection.aspx
160 ms
line_header.gif
1218 ms
mapuser
157 ms
Collection.aspx
156 ms
menu_back.png
1556 ms
topbanner_bg.gif
1319 ms
Collection.aspx
168 ms
tate.gif
1287 ms
l_bg.gif
1312 ms
pixel
27 ms
park_bgtt.jpg
1412 ms
Collection.aspx
160 ms
days.gif
1182 ms
icon_link03.gif
1319 ms
logo_lixil-juken_top.gif
1283 ms
fontsize_s.gif
1316 ms
Collection.aspx
301 ms
Collection.aspx
167 ms
fontsize.gif
1205 ms
fontsize_m.gif
1315 ms
fontsize_l.gif
1316 ms
fontsize_m_here.gif
1323 ms
park_btn01_over.jpg
197 ms
park_btn02_over.jpg
189 ms
park_btn03_over.jpg
191 ms
park_btn04_over.jpg
198 ms
park_btn05_over.jpg
197 ms
park_btn06_over.jpg
196 ms
park_btn07_over.jpg
384 ms
park_btn08_over.jpg
379 ms
park_btn09_over.jpg
408 ms
park_btn10_over.jpg
393 ms
park_btn12_over.jpg
386 ms
park_btn11_over.jpg
387 ms
eyefulhome.jp accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
eyefulhome.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
eyefulhome.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eyefulhome.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 Eyefulhome.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.
eyefulhome.jp
Open Graph description is not detected on the main page of Eyefulhome. 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: