6.9 sec in total
1.1 sec
4.9 sec
810 ms
Click here to check amazing Riolounge content. Otherwise, check out these important facts you probably never knew about riolounge.com.br
Um breve resumo da descrição do site
Visit riolounge.com.brWe analyzed Riolounge.com.br page load time and found that the first response time was 1.1 sec and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
riolounge.com.br performance score
1109 ms
715 ms
283 ms
275 ms
473 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 63% of them (52 requests) were addressed to the original Riolounge.com.br, 12% (10 requests) were made to Static.xx.fbcdn.net and 11% (9 requests) were made to Guialounge.com.br. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Riolounge.com.br.
Page size can be reduced by 866.2 kB (40%)
2.2 MB
1.3 MB
In fact, the total size of Riolounge.com.br main page is 2.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 90.4 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 54.9 kB, which is 54% 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 90.4 kB or 90% of the original size.
Potential reduce by 33.7 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. Riolounge images are well optimized though.
Potential reduce by 385.9 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 385.9 kB or 73% of the original size.
Potential reduce by 356.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. Riolounge.com.br needs all CSS files to be minified and compressed as it can save up to 356.2 kB or 85% of the original size.
Number of requests can be reduced by 43 (54%)
80
37
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Riolounge. 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 10 to 1 for CSS and as a result speed up the page load time.
riolounge.com.br
1109 ms
www.riolounge.com.br
715 ms
bootstrap.min.css
283 ms
bootstrap-responsive.min.css
275 ms
style.css
473 ms
light.css
279 ms
icons.css
323 ms
font-awesome.css
331 ms
css
69 ms
alert.css
463 ms
28e6a886c59f05b9dec2ed8e32fe9efd.jpg
1141 ms
likebox.php
212 ms
jquery.min.js
721 ms
theme20.js
451 ms
bootstrap.min.js
454 ms
jquery.prettyPhoto.js
454 ms
jquery.flexslider-min.js
717 ms
jquery.nicescroll.min.js
905 ms
custom.js
783 ms
jquery.tweet.js
785 ms
jquery.jplayer.js
785 ms
_ttw-music-player-min.js
905 ms
myplaylist.js
907 ms
jquery.masonry.min.js
905 ms
countdown.js
910 ms
jquery.themepunch.plugins.min.js
911 ms
jquery.themepunch.revolution.min.js
916 ms
js
57 ms
gmap3.js
919 ms
facebook.js
917 ms
main.js
926 ms
jquery.printElement.js
928 ms
facebook_user.jpg
928 ms
logo_top.png
1118 ms
logo_riolounge.png
1120 ms
breadcrumbs1.png
2481 ms
5d1aa2e629bb0884c4c028815b93ef82.jpg
1118 ms
26687a4f12f42040a46a67599ae697df.png
1446 ms
c1caadae09a9f7ee717973146f675043.jpg
1118 ms
4f5980e30310ddc8fd9e2bfbb698ba35.jpg
1118 ms
7965f503055815e080a17c3743298667.jpg
1115 ms
4f87823fa77b0b24252f6d412c3a0bb3.jpg
1345 ms
ac669ec93b9f923d5def3c53831ce562.jpg
1186 ms
ebiMDO3r-8l.css
141 ms
FAHeNGXgPup.js
187 ms
FJmpeSpHpjS.js
451 ms
0wM5s1Khldu.js
354 ms
1bNoFZUdlYZ.js
352 ms
light_bg.jpg
654 ms
_header.png
585 ms
button_bg.png
579 ms
logo_bemvindo.png
585 ms
-g5pDUSRgvxvOl5u-a_WHw.woff
124 ms
fontawesome-webfont.woff
603 ms
fontawesome-webfont.woff
662 ms
I6-MnjEovm5.js
223 ms
pQrUxxo5oQp.js
224 ms
sdk.js
71 ms
forms.js
171 ms
form_login.js
173 ms
form_cadastro.js
174 ms
form_cadastro_facebook.js
330 ms
form_cadastro_editar.js
332 ms
form_cadastro_editar_facebook.js
335 ms
form_cadastro_senha.js
351 ms
form_aniversario.js
380 ms
form_lista.js
408 ms
form_contato.js
414 ms
jquery.maskedinput.min.js
472 ms
75 ms
xd_arbiter.php
124 ms
xd_arbiter.php
186 ms
analytics.js
809 ms
mini_welcome-to-rio-sette-leblon-20-fev-2016-23f26fa4be2f3c879d471e3b91113e78.jpg
714 ms
gradient.png
196 ms
Metrize-Icons.woff
584 ms
xd_arbiter.php
124 ms
collect
82 ms
login_button.php
132 ms
Gq6M-kL4JDw.js
101 ms
jVG1f1GslU7.png
42 ms
luFYNPLo3dO.gif
47 ms
print.css
144 ms
riolounge.com.br SEO score
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Riolounge.com.br can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Riolounge.com.br 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.
riolounge.com.br
Open Graph data is detected on the main page of Riolounge. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: