17.4 sec in total
1.8 sec
15.3 sec
330 ms
Visit replan.ne.jp now to see the best up-to-date Replan content for Japan and also check out these interesting facts you probably never knew about replan.ne.jp
北海道から「住まい」「暮らし」のほんとうをお届けするウェブマガジン。北海道・東北エリアの住宅実例や家づくりに関するアイディア、暮らしの情報など。
Visit replan.ne.jpWe analyzed Replan.ne.jp page load time and found that the first response time was 1.8 sec and then it took 15.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.
replan.ne.jp performance score
name
value
score
weighting
Value8.5 s
0/100
10%
Value8.9 s
1/100
25%
Value25.9 s
0/100
10%
Value580 ms
51/100
30%
Value0.764
5/100
15%
Value13.5 s
11/100
10%
1789 ms
17 ms
370 ms
377 ms
850 ms
Our browser made a total of 149 requests to load all elements on the main page. We found that 70% of them (104 requests) were addressed to the original Replan.ne.jp, 6% (9 requests) were made to Plugins.mixi.jp and 4% (6 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Replan.ne.jp.
Page size can be reduced by 794.6 kB (31%)
2.6 MB
1.8 MB
In fact, the total size of Replan.ne.jp main page is 2.6 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 1.6 MB which makes up the majority of the site volume.
Potential reduce by 56.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.1 kB, which is 23% 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 56.8 kB or 81% of the original size.
Potential reduce by 57.8 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. Replan images are well optimized though.
Potential reduce by 543.0 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 543.0 kB or 67% of the original size.
Potential reduce by 136.9 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. Replan.ne.jp needs all CSS files to be minified and compressed as it can save up to 136.9 kB or 84% of the original size.
Number of requests can be reduced by 58 (39%)
147
89
The browser has sent 147 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Replan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
www.replan.ne.jp
1789 ms
jsapi
17 ms
reset.css
370 ms
base.css
377 ms
normalize.css
850 ms
output.css
904 ms
screen.css
698 ms
jquery.bxslider.css
703 ms
html5.js
30 ms
feeda.js
765 ms
feedb.js
1007 ms
topsy.css
1041 ms
tabmenu.css
1081 ms
fancybox.css
1102 ms
pagenavi-css.css
1042 ms
jetpack.css
1671 ms
jquery.js
1942 ms
jquery-migrate.min.js
1400 ms
jquery.fancybox.js
1543 ms
bookmark_button.js
313 ms
jquery-1.9.1.min.js
1780 ms
css3-mediaqueries.js
1491 ms
tabmenu.js
1379 ms
jquery.bxslider.min.js
1926 ms
jquery.tile.min.js
1674 ms
e-201611.js
4 ms
13 ms
default+en.css
3 ms
default+en.I.js
4 ms
wp-emoji-release.min.js
1574 ms
button-only.gif
177 ms
skip.gif
520 ms
home.gif
477 ms
main1_4.jpg
1063 ms
m51.jpg
1323 ms
m111.jpg
1510 ms
men2015.jpg
1778 ms
main2015maki.jpg
1689 ms
m8.jpg
1440 ms
m8webcenter.jpg
1919 ms
mainkenchiku.jpg
2367 ms
m8shin.jpg
2788 ms
bosyu.jpg
2008 ms
bosyu2.jpg
2227 ms
cba16006321194d5e3ef95a319067e6b-212x3001-160x113.jpg
2349 ms
5d9e9f6d2af40267b74180e269388780-192x3001-160x113.png
2678 ms
232d8586740f18c35124179c3ef11c1a-160x113.png
2968 ms
d10133-1458112542-0-150x1501-150x113.jpg
2751 ms
477d66dc8eaec383783cd31f3309bd66-300x2101-160x113.png
3025 ms
12111dc2eae619dffb69cdb6170fdaa6-300x2111-160x113.png
3325 ms
d10051-1458095945-0-150x1501-150x113.jpg
3191 ms
d25800a61e4ac12d07ecd2c9fc3ed083-300x2431-160x113.jpg
3356 ms
thumb.jpg
3183 ms
hforestajp-1456629795-0-150x1501-150x113.jpg
3518 ms
t_oho.jpg
3710 ms
mousou.jpg
3699 ms
t_reptate.jpg
3749 ms
t_npo110.jpg
3677 ms
1.jpg
3908 ms
2.jpg
4021 ms
3.jpg
4217 ms
4.jpg
4229 ms
all.js
75 ms
5.jpg
4194 ms
6.jpg
4180 ms
widgets.js
11 ms
136 ms
plugins.js
366 ms
xd_arbiter.php
72 ms
xd_arbiter.php
128 ms
383 ms
7.jpg
4215 ms
ga.js
134 ms
tag.js
134 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
145 ms
g.gif
83 ms
8.jpg
4096 ms
__utm.gif
25 ms
9.jpg
4241 ms
xd_arbiter.php
69 ms
10.jpg
4253 ms
11.jpg
4237 ms
like.php
93 ms
reset.css
14 ms
entry-button.css
14 ms
button-counter.gif
22 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
17 ms
wy1X4hBW7e7.js
144 ms
LVx-xkvaJ0b.png
155 ms
jot
94 ms
12.jpg
3777 ms
13.jpg
3594 ms
14.jpg
3653 ms
15.jpg
3849 ms
01.jpg
4076 ms
01.jpg
3843 ms
01.jpg
3791 ms
01.jpg
3694 ms
01.jpg
3753 ms
01.jpg
3890 ms
miyagi2016.jpg
4082 ms
en2015.jpg
3752 ms
asa2016.jpg
3644 ms
t_reform2016.jpg
3715 ms
kurashihint.jpg
3748 ms
hp.jpg
3769 ms
tosumai.jpg
3760 ms
repab.jpg
3643 ms
s-syacyoblog.gif
3483 ms
twitter.gif
3708 ms
top-one.gif
3545 ms
s-rpmail.gif
3627 ms
s-otoi.gif
3520 ms
logo2.gif
3738 ms
qmark.gif
3550 ms
bx_loader.gif
3718 ms
1.jpg
3582 ms
2.jpg
3592 ms
3.jpg
3575 ms
4.jpg
3643 ms
5.jpg
3685 ms
6.jpg
3754 ms
7.jpg
3597 ms
8.jpg
3573 ms
9.jpg
3550 ms
10.jpg
3627 ms
11.jpg
3669 ms
12.jpg
3738 ms
13.jpg
3614 ms
14.jpg
3451 ms
15.jpg
3295 ms
controls.png
3021 ms
main1_4.jpg
3945 ms
Gfeeds
321 ms
Gfeeds
353 ms
favorite.pl
398 ms
mixi_check_entry.css
8 ms
errorreport.production.js
293 ms
json.js
295 ms
underscore-string-1.3.3-2.0.0-compress.js
296 ms
namespace-brook-compress.js
296 ms
prototype-effects-1.6.1-1.8.3-compress.js
444 ms
mixi.js
304 ms
favorite.production.js
584 ms
jquery-1.7.1.min-noconflict-compress.js
734 ms
analytics.js
3 ms
comment001.gif
6 ms
favorite_button004.png
6 ms
comment_content_top001.gif
4 ms
replan.ne.jp accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
replan.ne.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
replan.ne.jp SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Replan.ne.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Replan.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.
replan.ne.jp
Open Graph data is detected on the main page of Replan. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: