7.7 sec in total
1 sec
6.5 sec
123 ms
Welcome to reprice.co.jp homepage info - get ready to check Reprice best content for Japan right away, or after learning these important things about reprice.co.jp
再生住宅専門のリプライス【公式サイト】トップページ。累計販売実績10000件超の実績と信頼で、リフォーム済みの中古一戸建て・中古マンションを販売中。売主なので仲介手数料0円。新築でも中古でも賃貸でもない『再生住宅』でより良い生活を。
Visit reprice.co.jpWe analyzed Reprice.co.jp page load time and found that the first response time was 1 sec and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
reprice.co.jp performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value11.8 s
0/100
25%
Value8.3 s
19/100
10%
Value120 ms
97/100
30%
Value0.251
49/100
15%
Value11.0 s
20/100
10%
1004 ms
331 ms
496 ms
506 ms
360 ms
Our browser made a total of 158 requests to load all elements on the main page. We found that 66% of them (104 requests) were addressed to the original Reprice.co.jp, 4% (7 requests) were made to Tg.socdm.com and 3% (5 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Reprice.co.jp.
Page size can be reduced by 327.8 kB (41%)
795.6 kB
467.8 kB
In fact, the total size of Reprice.co.jp main page is 795.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Javascripts take 449.0 kB which makes up the majority of the site volume.
Potential reduce by 23.7 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 23.7 kB or 78% of the original size.
Potential reduce by 9.6 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. Reprice images are well optimized though.
Potential reduce by 277.8 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 277.8 kB or 62% of the original size.
Potential reduce by 16.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. Reprice.co.jp needs all CSS files to be minified and compressed as it can save up to 16.7 kB or 83% of the original size.
Number of requests can be reduced by 40 (28%)
144
104
The browser has sent 144 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Reprice. 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 as a result speed up the page load time.
reprice.co.jp
1004 ms
normalize.css
331 ms
default.css
496 ms
index.css
506 ms
common.js
360 ms
jquery-1.9.1.min.js
2419 ms
jquery.corner.js
649 ms
corner.js
522 ms
DLPO.js
701 ms
smp.js
660 ms
conversion.js
16 ms
s_retargeting.js
574 ms
conversion.js
556 ms
convert.js
461 ms
fbds.js
85 ms
cmn_logo01.gif
184 ms
cmn_pref_japan.gif
190 ms
cmn_header_tohome01.gif
163 ms
cmn_header_t01.gif
179 ms
cmn_header_t02.gif
183 ms
cmn_header_t03.gif
181 ms
cmn_gnav01.png
324 ms
cmn_gnav02.png
334 ms
cmn_gnav03.png
341 ms
cmn_gnav04.png
344 ms
cmn_gnav05.png
353 ms
i_main_p01.jpg
2747 ms
cmn_stit01.gif
485 ms
i_map_bg01.gif
833 ms
cmn_map_area01.gif
508 ms
cmn_map_hokkaido_on.gif
516 ms
cmn_map_aomori_on.gif
530 ms
cmn_map_akita_on.gif
647 ms
cmn_map_iwate_on.gif
681 ms
cmn_map_miyagi_on.gif
687 ms
cmn_map_yamagata_on.gif
705 ms
cmn_map_fukushima_on.gif
808 ms
i_map_arrow01.gif
849 ms
cmn_map_area02.gif
857 ms
cmn_map_tokyo_on.gif
882 ms
cmn_map_kanagawa_on.gif
969 ms
cmn_map_saitama_on.gif
995 ms
cmn_map_chiba_on.gif
1018 ms
cmn_map_ibaraki_on.gif
1027 ms
cmn_map_tochigi_on.gif
1059 ms
cmn_map_gunma_on.gif
1127 ms
i_map_arrow02.gif
1162 ms
cmn_map_area03.gif
1186 ms
cmn_map_nagano_on.gif
1197 ms
cmn_map_yamanashi_on.gif
1233 ms
gtm.js
42 ms
cmn_map_niigata.gif
1294 ms
tag.js
17 ms
blade_track_jp.js
367 ms
50 ms
ga.js
36 ms
conversion_async.js
14 ms
reprice.co.jp.js
22 ms
tag
25 ms
52 ms
25 ms
49 ms
conversion.js
1198 ms
basecamp.js
44 ms
56 ms
__utm.gif
26 ms
45 ms
46 ms
analytics.js
15 ms
cmn_map_toyama_on.gif
1184 ms
ecommerce.js
14 ms
cmn_map_ishikawa_on.gif
1185 ms
cmn_map_fukui_on.gif
1196 ms
i_map_arrow03.gif
1236 ms
cmn_map_area04.gif
1279 ms
collect
10 ms
collect
63 ms
cmn_map_aichi_on.gif
1318 ms
cmn_map_gifu_on.gif
1209 ms
cmn_map_mie_on.gif
1214 ms
cmn_map_shizuoka_on.gif
1255 ms
i_map_arrow04.gif
1278 ms
cmn_map_area05.gif
1322 ms
cookie_enabled_get.html
354 ms
pv_beacon.gif
360 ms
cmn_map_osaka_on.gif
1216 ms
cmn_map_hyogo_on.gif
1212 ms
cmn_map_shiga_on.gif
1257 ms
cmn_map_nara_on.gif
1252 ms
cmn_map_kyoto_on.gif
1194 ms
cmn_map_wakayama.gif
1190 ms
i_map_arrow05.gif
1206 ms
cmn_map_area06.gif
1242 ms
bl_track.cgi
365 ms
cmn_map_hiroshima_on.gif
1135 ms
cmn_map_okayama_on.gif
1176 ms
cmn_map_tottori_on.gif
1190 ms
cmn_map_shimane.gif
1205 ms
cmn_map_yamaguchi_on.gif
1221 ms
i_map_arrow06.gif
1154 ms
cmn_map_area07.gif
1175 ms
cmn_map_ehime_on.gif
1189 ms
cmn_map_kagawa_on.gif
1205 ms
cmn_map_kochi.gif
1208 ms
cmn_map_tokushima.gif
1173 ms
i_map_arrow07.gif
1176 ms
cmn_map_area08.gif
1190 ms
cmn_map_fukuoka_on.gif
1207 ms
cmn_map_oita_on.gif
1191 ms
js
595 ms
980 ms
cmn_map_kumamoto_on.gif
1180 ms
cmn_map_saga_on.gif
1167 ms
cmn_map_nagasaki.gif
1189 ms
cmn_map_miyazaki.gif
1208 ms
cmn_map_kagoshima.gif
1177 ms
cmn_map_okinawa_on.gif
1199 ms
i_map_arrow08.gif
1172 ms
cmn_stit02.gif
1192 ms
i_sstit03.gif
1209 ms
i_p_s03.jpg
1647 ms
cmn_btn01.gif
1216 ms
i_sstit01.gif
1171 ms
i_p_s01.jpg
1356 ms
i_sstit02.gif
1211 ms
i_p_s02.jpg
1157 ms
cmn_pagetop01.gif
1236 ms
cmn_header_bg01.gif
1176 ms
i_main_bg01.gif
1232 ms
sosync
184 ms
L21rdC82ODEvcGlkLzQzNzc1MDA4L3QvMA
35 ms
beacon_call.js
40 ms
i_stit_bg01.gif
1218 ms
beacon
20 ms
16 ms
17 ms
17 ms
sync
551 ms
sync_before
186 ms
sync_before
354 ms
sync_before
364 ms
idsync
369 ms
sync
366 ms
22 ms
pixel
17 ms
sync
587 ms
sync
613 ms
cs
320 ms
Pug
17 ms
is
757 ms
sd
4 ms
tap.php
7 ms
9 ms
cmn_gnav01_on.png
179 ms
cmn_gnav02_on.png
187 ms
cmn_gnav03_on.png
164 ms
cmn_gnav04_on.png
171 ms
cmn_gnav05_on.png
178 ms
reprice.co.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.
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.
reprice.co.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
reprice.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Reprice.co.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 Reprice.co.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.
reprice.co.jp
Open Graph description is not detected on the main page of Reprice. 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: