4.5 sec in total
311 ms
4 sec
244 ms
Click here to check amazing A Serra content for Brazil. Otherwise, check out these important facts you probably never knew about aserra.com.br
Notícias, entretenimento e esporte da região serrana do RJ. Nova Friburgo, Petrópolis, Teresópolis, Bom Jardim, Cordeiro entre outras.
Visit aserra.com.brWe analyzed Aserra.com.br page load time and found that the first response time was 311 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
aserra.com.br performance score
311 ms
11 ms
6 ms
18 ms
7 ms
Our browser made a total of 197 requests to load all elements on the main page. We found that 19% of them (38 requests) were addressed to the original Aserra.com.br, 13% (25 requests) were made to Static.xx.fbcdn.net and 5% (10 requests) were made to Static.boo-box.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source External.xx.fbcdn.net.
Page size can be reduced by 509.4 kB (36%)
1.4 MB
905.6 kB
In fact, the total size of Aserra.com.br main page is 1.4 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. 70% of websites need less resources to load. Javascripts take 679.2 kB which makes up the majority of the site volume.
Potential reduce by 65.6 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 27.1 kB, which is 35% 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 65.6 kB or 84% of the original size.
Potential reduce by 17.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. A Serra images are well optimized though.
Potential reduce by 375.4 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 375.4 kB or 55% of the original size.
Potential reduce by 50.8 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. Aserra.com.br needs all CSS files to be minified and compressed as it can save up to 50.8 kB or 81% of the original size.
Number of requests can be reduced by 104 (57%)
181
77
The browser has sent 181 CSS, Javascripts, AJAX and image requests in order to completely render the main page of A Serra. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 61 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
aserra.com.br
311 ms
style.css
11 ms
list-rotator.css
6 ms
jquery-1.7.2.min.js
18 ms
menu.js
7 ms
jquery.list-rotator.min.js
15 ms
wp-socializer-buttons-css.css
15 ms
embed.js
88 ms
show.jsp
463 ms
ga.js
375 ms
buttons.js
370 ms
sombra-logo.jpg
359 ms
logo-aserra-index.jpg
362 ms
facebook-menu.jpg
358 ms
menu-cidade.png
358 ms
067-110x80.jpg
360 ms
059-110x80.jpg
358 ms
43-110x80.jpg
360 ms
42-110x80.jpg
358 ms
41-110x80.jpg
363 ms
401-110x80.jpg
362 ms
37-410x290.jpg
359 ms
209-110x80.jpg
359 ms
39-110x80.jpg
357 ms
30-110x80.png
362 ms
302-110x80.jpg
359 ms
234-110x80.jpg
357 ms
165-110x80.jpg
358 ms
087-110x80.jpg
360 ms
331-110x80.jpg
359 ms
178-110x80.jpg
359 ms
117-110x80.jpg
387 ms
049-110x80.jpg
377 ms
129-110x80.jpg
377 ms
logo-rodape.png
376 ms
_.gif
373 ms
bb_viewability.min.js
49 ms
list
84 ms
sdk.js
173 ms
__utm.gif
17 ms
collect
75 ms
list
391 ms
list
383 ms
min.js
132 ms
script.js
90 ms
main.js
90 ms
beacon.js
38 ms
tm11750.js
287 ms
user_sync.html
60 ms
widget.css
19 ms
bbbeacon-icon-transparent.png
24 ms
uol_728x90.html
275 ms
showad.js
33 ms
richmedia.js
76 ms
jquery.min.js
74 ms
PugMaster
157 ms
tap.php
45 ms
frameads.html
221 ms
select_arrow.png
407 ms
getAllAppDefault.esi
188 ms
284.jpg
111 ms
pixel
113 ms
Pug
109 ms
usersync.aspx
121 ms
F348FC5B-25CF-46FB-9517-90DE67A2E746
122 ms
cloudflare.min.js
112 ms
uolaf.js
321 ms
245 ms
scriptintext.js
187 ms
scriptfullpage2.jsp
125 ms
universalpixel.js
117 ms
usr
181 ms
vitrine-1.4.min.html
91 ms
analytics.js
85 ms
tm12674.js
199 ms
pixel
141 ms
0915.jpg
123 ms
Pug
126 ms
pixel
139 ms
Pug
121 ms
xd_arbiter.php
202 ms
xd_arbiter.php
320 ms
embed_enabler.min.js
88 ms
embed_enabler.min.js
86 ms
UPug
84 ms
Pug
78 ms
300 ms
collect
53 ms
collect
55 ms
getSegment.php
197 ms
checkOAuth.esi
60 ms
Pug
55 ms
Pug
55 ms
Pug
60 ms
157.jpg
43 ms
pixel.js
54 ms
generic
47 ms
google_sync_status
46 ms
req
93 ms
250x250.html
332 ms
728x90.html
310 ms
page.php
97 ms
057.jpg
17 ms
generic
15 ms
dpsync.html
56 ms
usr
97 ms
format1_f.html
543 ms
req
90 ms
UThj8VI7Xhd.css
316 ms
FL1kvZ1wVUz.css
370 ms
hSWGasuaGI8.css
411 ms
q68gy-v_YMF.js
522 ms
VvsfEObxnnn.js
556 ms
0wM5s1Khldu.js
449 ms
LTv6ZK-5zxz.js
603 ms
1FCa-btixu2.js
483 ms
7BE0CZr3HTs.js
491 ms
pQrUxxo5oQp.js
565 ms
lbnyQhD5B8P.js
565 ms
Oagsvfb4VWi.js
571 ms
Q4A0UyjU8W2.js
568 ms
1bNoFZUdlYZ.js
569 ms
Pug
69 ms
runtime.js
91 ms
embed_triggers.min.js
27 ms
t.dhj
177 ms
req
57 ms
224 ms
pixel
43 ms
pixelNavegg
200 ms
navegg
156 ms
195 ms
req
142 ms
sync
181 ms
sync
200 ms
sync
199 ms
150 ms
295 ms
293 ms
sync
182 ms
sync
176 ms
tap.php
76 ms
sync
105 ms
t.dhj
39 ms
027844424951990365
509 ms
05898890971930836
506 ms
sync
81 ms
sync
79 ms
cm
19 ms
x35248
141 ms
s-3271.xgi
14 ms
28 ms
hbpix
49 ms
pixel
20 ms
xrefid.xgi
5 ms
12 ms
eyJpZCI6ImYyOTc5Y2ZiMGY4MjM2MDQ1YjhlMDRiZTgzZTVhNjJlZDA3NzM5NTciLCJyZSI6IjZmOWIyOWE5ZWFlYTY5NzEwN2Q3NDgwNDJiMWJmZmUxIiwiZGkiOjc3NzcyMSwiZm8iOiJqc29uIiwiZmkiOiJiYmIiLCJzaSI6IjMyYTI4YjA0YTZjMDlmMWU3Y2YwZTYyZGZjZDRlMTk5NTAwN2JmZjAiLCJpbyI6MCwiZmlkIjoiMzlhYzRmYzRjZjdiOTQ1ZDk3MmRjOWRmZWQ3OTAwNDYiLCJhcCI6MSwiYWMiOiIiLCJydSI6IiIsImF0Ijoid2lkZ2V0X2Z1bGxfYWQiLCJjaSI6MTc3MTQsImFpIjo4Nzc0Niwic3IiOiI0N2NjYjA1MDA3YTUzYTIyYmFjOTJjNDJkMWVhOGM2YTZlMDkzNzFhIiwiZHQiOiIyMDE2LTAzLTIwVDEzOjU2OjI0LTAzOjAwIiwiY2IiOjh9
57 ms
2981
35 ms
blp.css
367 ms
gen.js
370 ms
fb.js
371 ms
uolsigainit.min.js
305 ms
uolsigaretarget.min.js
305 ms
1004443_488134404594425_601671960_n.png
519 ms
598603_522953827779149_983827851_n.png
571 ms
wL6VQj7Ab77.png
105 ms
s7jcwEQH7Sx.png
104 ms
348 ms
201 ms
b53Ajb4ihCP.gif
83 ms
yql
575 ms
e52235b9eba74a368818e01c18379504.jpeg
413 ms
c763091b9f634732a870b80930e6f81b.jpeg
538 ms
index.a8fc48294ca4cc10eb440189d9f22d7c.html
10 ms
buttons.ab966a004186897711de4a5ed256c924.css
25 ms
st.125da8bfe70ad3e00a35a6e4c65d8bc5.js
6 ms
css;base64,
5 ms
7HwxA8gVs6-.css
49 ms
cuTBFFsHWNo.css
50 ms
ljoX-PyMzJF.css
57 ms
njO1TPvGzoR.js
57 ms
1QuX41zDRrx.js
68 ms
safe_image.php
343 ms
safe_image.php
984 ms
safe_image.php
496 ms
safe_image.php
1296 ms
10354686_10150004552801856_220367501106153455_n.jpg
82 ms
12809665_595153227315012_3410033500926074624_n.jpg
157 ms
10384696_737022999720776_2719360355301177294_n.jpg
123 ms
12144721_901031883318226_8556061814402865589_n.jpg
127 ms
12801172_1012882598786267_2275957199317056106_n.jpg
298 ms
QDwYpIaRyfG.png
50 ms
AGUNXgX_Wx3.gif
45 ms
__2.255256-c865b8b.jpg
21 ms
__2.255256-9fdbe5b.jpg
21 ms
__2.79-9290a42.jpg
16 ms
I6-MnjEovm5.js
43 ms
aserra.com.br SEO score
PT
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aserra.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Aserra.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.
aserra.com.br
Open Graph description is not detected on the main page of A Serra. 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: