1.5 sec in total
77 ms
846 ms
585 ms
Welcome to rio-ofilme.com.br homepage info - get ready to check Rio Ofilme best content right away, or after learning these important things about rio-ofilme.com.br
RIO está de volta em RIO 2, acompanhado por novos atores e músicos. 27 De Março Nos Cinemas
Visit rio-ofilme.com.brWe analyzed Rio-ofilme.com.br page load time and found that the first response time was 77 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
rio-ofilme.com.br performance score
77 ms
173 ms
7 ms
17 ms
19 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 81% of them (63 requests) were addressed to the original Rio-ofilme.com.br, 4% (3 requests) were made to S.ytimg.com and 3% (2 requests) were made to Foxprivacy.com. The less responsive or slowest element that took the longest time to load (389 ms) relates to the external source Foxprivacy.com.
Page size can be reduced by 1.1 MB (11%)
9.7 MB
8.6 MB
In fact, the total size of Rio-ofilme.com.br main page is 9.7 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. 85% 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 8.7 MB which makes up the majority of the site volume.
Potential reduce by 18.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. This page needs HTML code to be minified as it can gain 3.1 kB, which is 13% 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 18.2 kB or 75% of the original size.
Potential reduce by 362.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. Rio Ofilme images are well optimized though.
Potential reduce by 372.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 372.9 kB or 67% of the original size.
Potential reduce by 319.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. Rio-ofilme.com.br needs all CSS files to be minified and compressed as it can save up to 319.9 kB or 85% of the original size.
Number of requests can be reduced by 24 (33%)
73
49
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rio Ofilme. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
rio-ofilme.com.br
77 ms
www.rio-ofilme.com.br
173 ms
normalize.css
7 ms
animations.css
17 ms
video-js.css
19 ms
main.css
12 ms
modernizr-dev.js
17 ms
ser7pmf.js
57 ms
footer.js
31 ms
jquery-2.0.3.min.js
22 ms
jquery.parallax.min.js
22 ms
idangerous.swiper-2.1.min.js
24 ms
video.js
25 ms
jquery.firefly.modified.js
22 ms
jquery.jscrollpane.min.js
21 ms
jquery.rwdImageMaps.js
23 ms
jquery.cookie.js
25 ms
jquery.browser.js
25 ms
ajaxify.min.js
24 ms
main.js
26 ms
footer.js
389 ms
bg-nav-mid@2x.png
15 ms
gtm.js
24 ms
bg-nav-left@2x.png
17 ms
bg-nav-right@2x.png
10 ms
bg-nav-selection@2x.png
15 ms
bg_dropdownArrow.png
14 ms
sprite.png
16 ms
arrow-button-sprite@2x.png
15 ms
nav-sprite@2x.png
14 ms
scroll-track-bg_tileY.png
20 ms
scroll-handle.png
18 ms
bg_article-mid.png
21 ms
bg_article-top.png
21 ms
bg_article-bot.png
18 ms
bgLayer-top@2x.jpg
63 ms
bgLayer-water@2x.png
111 ms
bg.gif
44 ms
bluesky.png
38 ms
logo-R.png
40 ms
logo-i.png
42 ms
logo-o.png
41 ms
logo-2.png
43 ms
modules_tickets-fandango.png
46 ms
modules_tickets-moviefone.png
43 ms
modules_tickets-yahoo.png
44 ms
title-and-date@2x.png
213 ms
spacer.png
46 ms
promo_trailer-thumb.png
326 ms
promo_poster-thumb.png
105 ms
fgLayer-croc@2x.png
106 ms
fgLayer-limbLeft@2x.png
342 ms
fgLayer-limbRight@2x.png
138 ms
fgLayer-rafael@2x.png
212 ms
fgLayer-mainBirds@2x.png
181 ms
fgLayer-topLeft-vines@2x.png
326 ms
fgLayer-topRight-vines@2x.png
335 ms
fgLayer-bottomLeft-backPlants@2x.png
336 ms
fgLayer-bottomRight-backPlants@2x.png
335 ms
fgLayer-monkeys@2x.png
333 ms
fgLayer-gabiSet@2x.png
331 ms
fgLayer-nigel@2x.png
332 ms
fgLayer-nico-and-pedro@2x.png
333 ms
fgLayer-left-sidePlants@2x.png
335 ms
fgLayer-right-frontPlants@2x.png
333 ms
footer-logos@2x.png
329 ms
rating_not-yet-rated.png
326 ms
videoseries
75 ms
analytics.js
9 ms
collect
22 ms
www-embed-player-vflfNyN_r.css
29 ms
www-embed-player.js
74 ms
base.js
104 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
51 ms
ad_status.js
57 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
90 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
93 ms
nr-885.min.js
44 ms
rio-ofilme.com.br SEO score
N/A
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rio-ofilme.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 Portuguese. Our system also found out that Rio-ofilme.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.
rio-ofilme.com.br
Open Graph data is detected on the main page of Rio Ofilme. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: