14 sec in total
2.5 sec
11.3 sec
243 ms
Visit thr.ne.jp now to see the best up-to-date Thr content for Japan and also check out these interesting facts you probably never knew about thr.ne.jp
「住まい」のもっと先へ。東宝ハウスグループ。東京、神奈川、埼玉の新築中古戸建て・土地・マンション、不動産なら東宝ハウスグループにお任せください。
Visit thr.ne.jpWe analyzed Thr.ne.jp page load time and found that the first response time was 2.5 sec and then it took 11.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
thr.ne.jp performance score
2459 ms
375 ms
580 ms
31 ms
580 ms
Our browser made a total of 147 requests to load all elements on the main page. We found that 60% of them (88 requests) were addressed to the original Thr.ne.jp, 10% (15 requests) were made to Scontent.xx.fbcdn.net and 7% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (8.2 sec) belongs to the original domain Thr.ne.jp.
Page size can be reduced by 713.6 kB (37%)
1.9 MB
1.2 MB
In fact, the total size of Thr.ne.jp main page is 1.9 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. 45% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 47.8 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 29% 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 47.8 kB or 82% of the original size.
Potential reduce by 474.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. Obviously, Thr needs image optimization as it can save up to 474.5 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 118.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 118.7 kB or 44% of the original size.
Potential reduce by 72.7 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. Thr.ne.jp needs all CSS files to be minified and compressed as it can save up to 72.7 kB or 80% of the original size.
Number of requests can be reduced by 69 (51%)
136
67
The browser has sent 136 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
thr.ne.jp
2459 ms
style.css
375 ms
colorbox.css
580 ms
jquery.min.js
31 ms
jquery.imgloader.min.js
580 ms
common.js
576 ms
jquery.cookie.js
386 ms
font.js
580 ms
jquery.colorbox-min.js
765 ms
layout.css
820 ms
index.css
593 ms
about.css
587 ms
branding.css
598 ms
message.css
771 ms
president.css
783 ms
image-movie.css
782 ms
story.css
790 ms
storysingle.css
953 ms
categoryStory.css
972 ms
photoessay.css
975 ms
photo-area.css
982 ms
group.css
1007 ms
oldlist.css
1135 ms
ranking.css
1161 ms
sitemap.css
1166 ms
present.css
1173 ms
company-profile.css
1195 ms
service.css
1316 ms
guarantee.css
1350 ms
moveRanking.css
1357 ms
homestyle.css
1363 ms
homeselect.css
1388 ms
s_retargeting.js
551 ms
conversion.js
14 ms
ga.js
39 ms
head_logo.png
203 ms
cnt2_1.jpg
191 ms
cnt2_img1.jpg
194 ms
cnt3_1.jpg
192 ms
cnt3_img1.jpg
381 ms
cnt4_1.jpg
194 ms
side_ranking01.png
381 ms
side_vol13.jpg
382 ms
point3.jpg
386 ms
side_vol32.jpg
387 ms
point4.jpg
405 ms
side_vol17.jpg
582 ms
point5.jpg
592 ms
arr01.gif
593 ms
side_ranking02.png
591 ms
vol43.jpg
592 ms
vol17.jpg
605 ms
vol15.jpg
764 ms
side_banner3.jpg
1051 ms
all.js
70 ms
head_bg2.png
2657 ms
nav_sprite.png
2080 ms
mainimg.jpg
1140 ms
cnt1_bg.png
782 ms
line1.jpg
1025 ms
side_title2.jpg
1025 ms
side_title1.jpg
1220 ms
point1.jpg
1202 ms
point2.jpg
1211 ms
foot_bg1.jpg
1326 ms
foot_point1.png
1750 ms
point8.png
2173 ms
point6.jpg
1421 ms
foot_bg2.jpg
1520 ms
343be4bb-3c21-4c30-bc87-1ed1a3720f2c.js
48 ms
__utm.gif
35 ms
count.js
54 ms
WRf4.js
8 ms
collect
54 ms
108 ms
pta.js
523 ms
tag.js
17 ms
xd_arbiter.php
73 ms
xd_arbiter.php
129 ms
tag
16 ms
58 ms
ya.js
375 ms
conversion_async.js
35 ms
bt_oldlist.png
1494 ms
js_01_im.png
1382 ms
js_01_im.jpg
2536 ms
js_01_im.png
3460 ms
js_01_im.jpg
1696 ms
js_01_im.jpg
1897 ms
js_02_im.jpg
4015 ms
js_02_im.png
4825 ms
27 ms
js_02_im.jpg
2086 ms
js_02_im.jpg
2287 ms
js_03_im.jpg
2889 ms
35 ms
js_03_im.png
8249 ms
js_03_im.jpg
2708 ms
25 ms
17 ms
13 ms
18 ms
js_03_im.jpg
2880 ms
15 ms
16 ms
55 ms
like_box.php
226 ms
js_04_im.jpg
3690 ms
js_04_im.png
6466 ms
js_04_im.jpg
3417 ms
js_04_im.jpg
3600 ms
overlay.png
3782 ms
79e2b9b7.js
906 ms
wIQ5cz_qN26.css
211 ms
OAknSm1a3Ik.css
243 ms
FAHeNGXgPup.js
279 ms
ehA1CqzHyzE.js
304 ms
0wM5s1Khldu.js
267 ms
1bNoFZUdlYZ.js
268 ms
pb.js
946 ms
344 ms
11146111_1179409672074897_6574058146840633318_n.png
252 ms
1464708_744618755553993_502432272_n.jpg
267 ms
1964776_552513694846783_1252774208_n.jpg
285 ms
12654447_527900014045182_4656436756389337319_n.jpg
300 ms
611_473484129405551_276176393_n.jpg
300 ms
12743750_959211590814110_4328620843927770751_n.jpg
300 ms
1013112_179327662238755_1239653243_n.jpg
301 ms
10385382_423692934477211_5568110222040103513_n.jpg
300 ms
9241_469851903123090_615302433_n.jpg
302 ms
12046598_766528080141393_3985897857333424017_n.jpg
316 ms
10670120_846602028707687_5368237324156659297_n.jpg
318 ms
12112472_525067357660219_8431462957870279836_n.jpg
317 ms
28141_102754026436474_3432596_n.jpg
316 ms
11427182_1456049774689695_8841266931463337036_n.jpg
316 ms
1975035_239125322940241_1250763835_n.jpg
320 ms
wL6VQj7Ab77.png
102 ms
s7jcwEQH7Sx.png
100 ms
I6-MnjEovm5.js
18 ms
pQrUxxo5oQp.js
37 ms
pn
514 ms
gb.gif
1087 ms
js_02_im.png
643 ms
js_03_im.png
728 ms
js_04_im.png
739 ms
bt_left.png
844 ms
bt_right.png
1095 ms
thr.ne.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thr.ne.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 Thr.ne.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.
thr.ne.jp
Open Graph description is not detected on the main page of Thr. 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: