16.7 sec in total
432 ms
15.7 sec
488 ms
Click here to check amazing Intellex content for Japan. Otherwise, check out these important facts you probably never knew about intellex.jp
インテリックスは、リノベーション、中古マンション再生流通事業のインテリックスグループ。お客様の理想の住まいを実現するために、仕入れ・設計・施工・販売・保証を一貫してご提供する「リノベーション総合企業」です。
Visit intellex.jpWe analyzed Intellex.jp page load time and found that the first response time was 432 ms and then it took 16.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
intellex.jp performance score
432 ms
423 ms
523 ms
568 ms
360 ms
Our browser made a total of 172 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Intellex.jp, 52% (89 requests) were made to Intellex.co.jp and 12% (20 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (11.9 sec) relates to the external source Intellex.co.jp.
Page size can be reduced by 695.1 kB (30%)
2.3 MB
1.6 MB
In fact, the total size of Intellex.jp main page is 2.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. 65% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 50.3 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 9.7 kB, which is 15% 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 50.3 kB or 80% of the original size.
Potential reduce by 82.1 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. Intellex images are well optimized though.
Potential reduce by 430.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 430.3 kB or 75% of the original size.
Potential reduce by 132.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. Intellex.jp needs all CSS files to be minified and compressed as it can save up to 132.5 kB or 83% of the original size.
Number of requests can be reduced by 93 (56%)
165
72
The browser has sent 165 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Intellex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
intellex.jp
432 ms
www.intellex.jp
423 ms
www.intellex.co.jp
523 ms
bootstrap.min.css
568 ms
main.css
360 ms
home.css
364 ms
slick.css
376 ms
ga.js
8 ms
eir.js
377 ms
brick.js
34 ms
UA-2196876-3.js
346 ms
jquery.min.js
40 ms
bootstrap.min.js
3731 ms
slick.js
3732 ms
scripts.js
534 ms
jQueryAutoHeight.js
556 ms
home.js
572 ms
main.css
522 ms
gtm.js
74 ms
logo.png
190 ms
nav_01.png
197 ms
nav_02.png
196 ms
nav_03.png
180 ms
nav_04.png
2637 ms
nav_05.png
2638 ms
nav_06.png
2638 ms
img-slide_04.jpg
2655 ms
img-slide_02.png
2641 ms
img-slide_03.jpg
3160 ms
img-slide_01.jpg
2692 ms
img-lead.png
2640 ms
img_033_off.jpg
2647 ms
icn_new.png
2643 ms
img_032_off.jpg
2648 ms
img_031_off.jpg
3393 ms
img_030_off.jpg
2649 ms
img_001_off.jpg
2688 ms
img_002_off.jpg
2913 ms
img_003_off.jpg
3253 ms
img_004_off.jpg
3062 ms
bnr-searchProperty_2_1.png
3201 ms
service-bnr-A.png
3515 ms
service-bnr-B.png
3850 ms
service-bnr-C.png
3866 ms
pickup_03.png
3734 ms
icn_seminarEvent.png
3440 ms
pickup_21.png
4014 ms
icn_service.png
3627 ms
pickup_11.jpg
11925 ms
icn_news.png
3816 ms
pickup_19.png
4468 ms
icn_recommended.png
4003 ms
pickup_20.png
4413 ms
tag.js
193 ms
gtm.js
61 ms
analytics.js
12 ms
brick.common.js
2622 ms
brick.conc.js
10 ms
brick.heatmap.js
2622 ms
brick.ltv.js
2620 ms
sdk.js
2617 ms
top_1510.js
2588 ms
collect
18 ms
collect
64 ms
conversion_async.js
22 ms
31 ms
49 ms
37 ms
pickup_06.png
4228 ms
rss.gif
4013 ms
bnr-studio.png
8226 ms
bnr-intellexRenovationReport_pc.png
4193 ms
tag
64 ms
bnr-ir_pc.png
1946 ms
bnr-recruit_pc.png
1951 ms
bnr-intellexRenovationReport.png
3638 ms
bnr-intellexFacebook.png
3638 ms
bnr-ir.png
3634 ms
bnr-recruit.png
3633 ms
announcement_21.js
1412 ms
ttl-phone.png
4400 ms
img-phone_3927.png
3814 ms
img-phone_3705.png
3805 ms
img-phone_3986.png
3802 ms
img-phone_8940.png
3976 ms
brick.lib.js
321 ms
btn-contactForm.png
3957 ms
icn-link.png
3959 ms
121 ms
footer_bnr_04.png
4113 ms
xd_arbiter.php
74 ms
xd_arbiter.php
128 ms
footer_bnr_01.png
3909 ms
brick.heatmap_base.js
163 ms
footer_bnr_02.png
3773 ms
icn-pageTop.png
3829 ms
icn-home.png
3799 ms
icn-back.png
3772 ms
img-pipe.png
3773 ms
icn-mail.png
3739 ms
icn-access.png
3698 ms
ttl-case.png
3600 ms
icn.png
3607 ms
ttl-searchResidence.png
4435 ms
ttl-service.png
3552 ms
ttl-pickup.png
3551 ms
ttl-information.png
3515 ms
ttl-news-release.png
3576 ms
ir_material7.gif
177 ms
space.gif
313 ms
ir_material6.gif
313 ms
url.gif
348 ms
pr.gif
350 ms
pdf.gif
362 ms
press.gif
400 ms
sync.php
2137 ms
fbevents.js
68 ms
ya.js
348 ms
21 ms
icn-menu.png
3412 ms
page.php
233 ms
ttl-contact.png
3322 ms
icn-hyphen.png
3377 ms
yIdHYsCA3B1.css
84 ms
qBBLx_j_YWO.css
103 ms
MrIRm6wo5X6.css
123 ms
4tREr7E_Ufc.css
137 ms
q68gy-v_YMF.js
155 ms
k19Xse48j5I.js
175 ms
ihptErjAmMX.js
173 ms
3So47A9WcrL.js
140 ms
cUsKAwzqrQw.js
191 ms
6PDLJFN-l6_.js
204 ms
NkeUJp899Dp.js
174 ms
FzGTmhgBEqv.js
204 ms
pb.js
2156 ms
1788 ms
11898694_829598640481075_3288608376644630871_n.jpg
1605 ms
safe_image.php
1623 ms
105 ms
safe_image.php
103 ms
safe_image.php
105 ms
safe_image.php
104 ms
safe_image.php
89 ms
safe_image.php
103 ms
safe_image.php
89 ms
11202848_823244834449789_5563376256147200311_n.jpg
66 ms
11755343_983866431680907_2618540911247419592_n.jpg
94 ms
12107988_1506016909715088_1242096177608203958_n.png
109 ms
wL6VQj7Ab77.png
52 ms
s7jcwEQH7Sx.png
58 ms
GtIpNnEyqq_.png
56 ms
lRyN50VcaFW.js
44 ms
sync.php
161 ms
R9a_DtVRZgv.js
21 ms
cUDgRFxaoIk.js
22 ms
0JBr1QHp8Gi.js
26 ms
kDOzhTr2W91.js
23 ms
collect
10 ms
collect
13 ms
get
314 ms
collect
3 ms
get
614 ms
collect
3 ms
img_033_on.jpg
788 ms
img_032_on.jpg
758 ms
img_031_on.jpg
1316 ms
img_030_on.jpg
711 ms
img_001_on.jpg
587 ms
img_002_on.jpg
357 ms
img_003_on.jpg
1097 ms
img_004_on.jpg
979 ms
intellex.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Intellex.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 Intellex.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.
intellex.jp
Open Graph description is not detected on the main page of Intellex. 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: