8.1 sec in total
1.2 sec
5.9 sec
1 sec
Click here to check amazing Excerent content for Japan. Otherwise, check out these important facts you probably never knew about excerent.jp
東京都心の高級マンションの物件探しならエクセレントへ!新築・デザイナーズ・分譲賃貸・高層マンションなど、様々な賃貸情報を多数掲載しています。あなたにぴったりの物件をエリア・路線・駅名などから探せます。
Visit excerent.jpWe analyzed Excerent.jp page load time and found that the first response time was 1.2 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
excerent.jp performance score
name
value
score
weighting
Value7.8 s
0/100
10%
Value14.4 s
0/100
25%
Value13.3 s
2/100
10%
Value140 ms
95/100
30%
Value0
100/100
15%
Value9.6 s
29/100
10%
1156 ms
191 ms
362 ms
366 ms
368 ms
Our browser made a total of 169 requests to load all elements on the main page. We found that 70% of them (118 requests) were addressed to the original Excerent.jp, 7% (12 requests) were made to Static.xx.fbcdn.net and 4% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Excerent.jp.
Page size can be reduced by 410.3 kB (16%)
2.5 MB
2.1 MB
In fact, the total size of Excerent.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. 70% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 78.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. 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 78.8 kB or 84% of the original size.
Potential reduce by 124.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. Excerent images are well optimized though.
Potential reduce by 154.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 154.6 kB or 67% of the original size.
Potential reduce by 52.4 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. Excerent.jp needs all CSS files to be minified and compressed as it can save up to 52.4 kB or 81% of the original size.
Number of requests can be reduced by 38 (23%)
166
128
The browser has sent 166 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Excerent. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
excerent.jp
1156 ms
reset.css
191 ms
module.css
362 ms
index.css
366 ms
system_extend.css
368 ms
lib.js
575 ms
common.js
383 ms
index.js
393 ms
owl.carousel.css
541 ms
owl.theme.css
546 ms
owl.carousel.min.js
550 ms
plusone.js
97 ms
bookmark_button.js
324 ms
getseal
157 ms
analytics.js
32 ms
button-only.gif
284 ms
bg.png
336 ms
header_navi_01_off.png
336 ms
header_navi_02_off.png
336 ms
header_navi_03_off.png
337 ms
logo.png
337 ms
text_header.png
337 ms
btn_contact_off.png
474 ms
navi_01_off.png
468 ms
navi_02_off.png
466 ms
navi_03_off.png
470 ms
navi_04_off.png
488 ms
navi_05_off.png
487 ms
navi_06_off.png
648 ms
main_02.jpg
1017 ms
main_01.jpg
1753 ms
article_1_759_1403244258.jpg
850 ms
article_1_918_1406888444.jpg
877 ms
article_1_566_1404374765.jpg
878 ms
article_1_44_1428280875.jpg
1009 ms
article_1_1239_1401534637.jpg
1041 ms
article_1_562_1406950266.jpg
1259 ms
arrow_prev_01.png
1074 ms
arrow_next_01.png
1189 ms
article_1_181_1401537569.jpg
1203 ms
article_1_1062_1404378477.jpg
1232 ms
article_1_1367_1412989084.jpg
1465 ms
article_1_9_1405219798.jpg
1548 ms
article_1_1553_1448096285.jpg
1387 ms
article_1_633_1409982824.jpg
1423 ms
article_1_643_1401170828.jpg
1452 ms
article_1_1007_1401159005.jpg
1573 ms
article_1_280_1405231167.jpg
1614 ms
article_1_66_1401179398.jpg
1644 ms
article_1_26_1401169202.jpg
1662 ms
article_1_18_1407745814.jpg
1729 ms
all.js
22 ms
article_1_86_1407215846.jpg
1756 ms
cb=gapi.loaded_0
116 ms
widgets.js
117 ms
collect
139 ms
getseal
272 ms
cb=gapi.loaded_1
63 ms
fastbutton
135 ms
collect
115 ms
219 ms
176 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
175 ms
article_1_1338_1407494614.jpg
1475 ms
article_1_639_1407651838.jpg
1505 ms
article_1_676_1407658059.jpg
1723 ms
article_1_919_1418538076.jpg
1581 ms
article_1_731_1401532246.jpg
1602 ms
article_1_35_1403242353.jpg
1611 ms
xd_arbiter.php
51 ms
xd_arbiter.php
92 ms
ping
165 ms
postmessageRelay
92 ms
cb=gapi.loaded_0
33 ms
cb=gapi.loaded_1
35 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
92 ms
api.js
29 ms
core:rpc:shindig.random:shindig.sha1.js
93 ms
2536007149-postmessagerelay.js
57 ms
article_1_476_1406950931.jpg
1535 ms
article_1_42_1403169979.jpg
1566 ms
article_1_255_1401523291.jpg
1628 ms
article_1_1634_1429841659.jpg
1651 ms
article_1_775_1401411682.jpg
1644 ms
article_1_602_1401415552.jpg
1703 ms
like.php
95 ms
reset.css
16 ms
entry-button.css
15 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
45 ms
button-counter.gif
10 ms
like_box.php
132 ms
rU2ubZ6l1Q5.js
32 ms
LVx-xkvaJ0b.png
24 ms
article_1_1066_1405058548.jpg
1578 ms
vnOEFRQrI0K.css
16 ms
3lyjJsCltNS.css
10 ms
_rx8naC75Dy.js
19 ms
b94UUzHjapV.js
38 ms
0wM5s1Khldu.js
36 ms
TTCre3391I0.js
46 ms
jot
113 ms
10300892_724374657627220_6978595866704106739_n.jpg
45 ms
10401965_724377584293594_6134323463076863567_n.jpg
13 ms
10354686_10150004552801856_220367501106153455_n.jpg
14 ms
12369026_710242885742124_8602758261710164460_n.jpg
16 ms
10613004_731002490320018_708090092904101600_n.jpg
14 ms
72295_606010232792058_1886112742_n.jpg
14 ms
wL6VQj7Ab77.png
11 ms
s7jcwEQH7Sx.png
11 ms
I6-MnjEovm5.js
2 ms
f6T91Deal_q.js
5 ms
article_1_1051_1401420212.jpg
1404 ms
article_1_1561_1430037632.jpg
1402 ms
article_1_1574_1419140708.jpg
1429 ms
article_1_158_1401596606.jpg
1307 ms
article_1_885_1411374598.jpg
1366 ms
article_1_48_1402923439.jpg
1378 ms
article_1_352_1406361699.jpg
1378 ms
article_1_1669_1430465513.jpg
1273 ms
article_1_1129_1401343288.jpg
1289 ms
article_1_454_1401096255.jpg
1268 ms
article_1_1346_1411193006.jpg
1313 ms
article_1_377_1408853189.jpg
1224 ms
article_1_626_1402909633.jpg
1226 ms
tit_topics.png
1190 ms
tit_search.png
1210 ms
bnr_owner.png
1315 ms
bnr_card.png
1190 ms
bnr_rent_lower.png
1190 ms
bnr_staff.png
1178 ms
tit_info.png
1182 ms
tit_shinjyuku.png
1128 ms
tab_01_off.png
1203 ms
tab_02_off.png
1236 ms
tab_03_off.png
1197 ms
article_1_1999_1452570666.jpg
1206 ms
article_1_19981452569403.jpg
1130 ms
article_1_2001_1453610245.jpg
1113 ms
article_1_1694_1439893165.jpg
1200 ms
btn_pagetop.png
1190 ms
gif-load.gif
1155 ms
bg_header_01.png
1186 ms
bg_02.png
1133 ms
bg_navi.png
1111 ms
bg_main.png
1205 ms
tit_main_01.png
1179 ms
tit_main_02.png
1155 ms
socialLink_sprite3.png
1160 ms
tit_01.png
1140 ms
bg_search.png
1131 ms
btn_search.png
1211 ms
bg_shinjyuku.png
1168 ms
tab_01_on.png
1152 ms
tab_02_on.png
1145 ms
tab_03_on.png
1140 ms
icon_next.png
1144 ms
bg_footer_02.png
1216 ms
bg_footer_01.png
1158 ms
bg_footer_03.png
1151 ms
header_navi_01_on.png
190 ms
header_navi_02_on.png
184 ms
header_navi_03_on.png
181 ms
btn_contact_on.png
184 ms
navi_01_on.png
192 ms
navi_02_on.png
198 ms
navi_03_on.png
360 ms
navi_04_on.png
364 ms
navi_05_on.png
365 ms
navi_06_on.png
376 ms
excerent.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[role]s do not have all required [aria-*] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
excerent.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
excerent.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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 doesn't use 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 Excerent.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 Excerent.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.
excerent.jp
Open Graph description is not detected on the main page of Excerent. 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: