11.1 sec in total
871 ms
9.9 sec
388 ms
Welcome to rafre.co.jp homepage info - get ready to check Rafre best content for Japan right away, or after learning these important things about rafre.co.jp
さいたま新都心のホテル、ラフレさいたまの公式サイト。宿泊、レストラン、会議・宴会場のほか、フィットネスクラブなども備え、多彩な用途にお応えします。
Visit rafre.co.jpWe analyzed Rafre.co.jp page load time and found that the first response time was 871 ms and then it took 10.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
rafre.co.jp performance score
871 ms
326 ms
333 ms
821 ms
1831 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that all of those requests were addressed to Rafre.co.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain Rafre.co.jp.
Page size can be reduced by 520.1 kB (16%)
3.3 MB
2.8 MB
In fact, the total size of Rafre.co.jp main page is 3.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. 35% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 24.2 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 24.2 kB or 75% of the original size.
Potential reduce by 154.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. Rafre images are well optimized though.
Potential reduce by 152.2 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 152.2 kB or 73% of the original size.
Potential reduce by 189.2 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. Rafre.co.jp needs all CSS files to be minified and compressed as it can save up to 189.2 kB or 88% of the original size.
Number of requests can be reduced by 59 (58%)
101
42
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rafre. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
rafre.co.jp
871 ms
style.css
326 ms
_else.css
333 ms
style.css
821 ms
index.css
1831 ms
script.js
2008 ms
common.css
2521 ms
pagelayout.css
642 ms
printlayout.css
174 ms
blockskin.css
667 ms
overwrite.css
171 ms
style.css
171 ms
theme.css
171 ms
_ie8v.css
175 ms
_else.css
183 ms
jquery-1.6.3.min.js
840 ms
jquery.easing.1.3.js
188 ms
movie.js
163 ms
parts.js
347 ms
fx.js
494 ms
override.js
339 ms
load.js
360 ms
vc_mid_2.jpg
170 ms
vc_top_2.jpg
1600 ms
1_ic_bdprint3.png
175 ms
1_ic_bdtext3_s.png
187 ms
1_ic_bdtext3_m.png
166 ms
1_ic_bdtext3_l.png
179 ms
83z83e838B838983t838C838D83S201304.jpg
327 ms
engine.js
321 ms
1_menuh_e_l.png
298 ms
1_menuh_e_r.png
309 ms
1_menuh_e_bg_top.gif
325 ms
1_menuh_e_bg_cr.png
444 ms
Real_col_HomeA.png
459 ms
1_menuh_e_bg.png
469 ms
8AO8ACF.jpg
1517 ms
819983X83C815B83g83x83b83h.jpg
1417 ms
838C83K815B838D96E9.jpg
1085 ms
8199898389EF8FEA.jpg
959 ms
819920120329D9B0C1AA93X95DC8AO8ACF_.jpg
5402 ms
1_bf2_tl.png
1130 ms
1_bf2_tr.png
1250 ms
1_bf2_tc.png
1300 ms
1_bf2_ml.png
1413 ms
1_bf2_mr.png
1469 ms
1_bf2_bg.png
1578 ms
838983t838C8Ft82BE82E682E881i83s839383N81j.png
1600 ms
83T838B815B83e838D83S200x588DB68AF182B9.jpg
1638 ms
8FH839690A388C1838D83S200x58_8DB68AF182B9.jpg
1690 ms
8DCA95o98O838D83S200x588DB68AF182B9.jpg
1730 ms
838C83K815B838D838D83S200x588DB68AF182B9.jpg
1740 ms
1_bf2_bl.png
1786 ms
1_bf2_br.png
1808 ms
1_bf2_bc.png
1867 ms
1_bf1_tl.png
1913 ms
1_bf1_tr.png
1904 ms
1_bf1_tc.png
1971 ms
1_bf1_ml.png
1863 ms
1_bf1_mr.png
1927 ms
1_bf1_bg.png
1945 ms
1_bf1_bl.png
1967 ms
1_bf1_br.png
2026 ms
1_bf1_bc.png
1872 ms
sign.png
1928 ms
sign.png
1936 ms
sign.png
1969 ms
sign.png
1995 ms
nivo-slider.css
1907 ms
custom-nivo-slider.css
1940 ms
jquery.nivo.slider.pack.js
1928 ms
sign.png
1498 ms
sign.png
1403 ms
sign.png
1403 ms
hr.png
1310 ms
btn_type_a_015B15D.png
1271 ms
btn_type_a_015B15D.png
1222 ms
h4.gif
1244 ms
tabular_th.gif
1249 ms
8DX90V-83u838D83O.jpg
1206 ms
8DX90V-838C83X83g83898393.jpg
1196 ms
hr.gif
1241 ms
1_bf3_tl.png
1228 ms
1_bf3_tr.png
1268 ms
1_bf3_tc.png
1196 ms
1_bf3_ml.png
1192 ms
1_bf3_mr.png
1261 ms
1_bf3_bg.png
1212 ms
net.r.jpg
1238 ms
838983938360838183j8385815B88EA979795B68CBE82CC82DD1.jpg
1221 ms
8E9197BF90BF8B81.jpg
1193 ms
83p815B83e83B81E89EF8Bc975C96F1.jpg
1254 ms
1_bf3_bl.png
1210 ms
1_bf3_br.png
1234 ms
1_bf3_bc.png
1230 ms
sign.jpg
1204 ms
sign.jpg
1241 ms
sign.jpg
1212 ms
sign.jpg
1213 ms
83v838983C8380.jpg
1228 ms
bk1_top.gif
1228 ms
em_meiryo.png
1230 ms
loading.gif
1029 ms
rafre.co.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rafre.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 Rafre.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.
rafre.co.jp
Open Graph data is detected on the main page of Rafre. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: