6.8 sec in total
1.2 sec
5.1 sec
431 ms
Visit getro.com.br now to see the best up-to-date GETRO content for Brazil and also check out these interesting facts you probably never knew about getro.com.br
Visit getro.com.brWe analyzed Getro.com.br page load time and found that the first response time was 1.2 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
getro.com.br performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value8.5 s
2/100
25%
Value10.8 s
6/100
10%
Value30,980 ms
0/100
30%
Value0.01
100/100
15%
Value43.4 s
0/100
10%
1228 ms
11 ms
18 ms
20 ms
26 ms
Our browser made a total of 169 requests to load all elements on the main page. We found that 40% of them (67 requests) were addressed to the original Getro.com.br, 13% (22 requests) were made to Static.xx.fbcdn.net and 11% (19 requests) were made to Img.youtube.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Banner.hotwords.com.
Page size can be reduced by 2.4 MB (58%)
4.2 MB
1.8 MB
In fact, the total size of Getro.com.br main page is 4.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. 80% 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. CSS take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 119.7 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 119.7 kB or 83% of the original size.
Potential reduce by 45.2 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. GETRO images are well optimized though.
Potential reduce by 661.6 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 661.6 kB or 75% of the original size.
Potential reduce by 1.6 MB
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. Getro.com.br needs all CSS files to be minified and compressed as it can save up to 1.6 MB or 90% of the original size.
Number of requests can be reduced by 80 (49%)
164
84
The browser has sent 164 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GETRO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 59 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.getro.com.br
1228 ms
wp-emoji-release.min.js
11 ms
styles.css
18 ms
wp-socializer-buttons-css.css
20 ms
css
26 ms
css
43 ms
css
77 ms
gallery.min.css
22 ms
js_composer.css
43 ms
style.css
77 ms
jquery.js
33 ms
jquery-migrate.min.js
25 ms
jquery.iframetracker.js
28 ms
sam.pro.layout.min.js
32 ms
show.jsp
637 ms
venom1301.spider.ad
215 ms
banner.js
1527 ms
ad_lomadee.js
318 ms
font-awesome.min.css
34 ms
jquery.form.min.js
37 ms
scripts.js
69 ms
postviews-cache.js
71 ms
tagdiv_theme.js
141 ms
comment-reply.min.js
135 ms
wp-embed.min.js
136 ms
js_composer_front.js
137 ms
vc-accordion.js
137 ms
vc-tta-autoplay.js
137 ms
vc-tabs.js
137 ms
count.js
138 ms
widgets.js
177 ms
all.js
27 ms
plusone.js
107 ms
analytics.js
56 ms
147 ms
collect
19 ms
collect
57 ms
cb=gapi.loaded_0
21 ms
script.js
83 ms
main.js
79 ms
beacon.js
8 ms
sync
3 ms
richmedia.js
49 ms
jquery.min.js
31 ms
sync
14 ms
scriptintext.js
128 ms
scriptsello.jsp
41 ms
scriptfullpage2.jsp
72 ms
logo1.png
23 ms
24409799701_938af3f6e5_o.jpg
92 ms
default.jpg
30 ms
logo2.png
24 ms
kb01-218x150.jpg
21 ms
ico-video-large.png
21 ms
parody-218x150.jpg
23 ms
perturba25-218x150.jpg
23 ms
self35-218x150.jpg
24 ms
pior20-218x150.jpg
26 ms
oscars.jpg
28 ms
razzies.jpg
25 ms
room.jpg
29 ms
ale.jpg
45 ms
horror.jpg
33 ms
devil-218x150.jpg
53 ms
bawl-218x150.jpg
29 ms
zomb-218x150.jpg
38 ms
colors-218x150.jpg
41 ms
sincero-218x150.jpg
43 ms
sadako-218x150.jpg
45 ms
henry-324x235.jpg
49 ms
purge-100x70.jpg
50 ms
mc-100x70.jpg
53 ms
cabin-100x70.jpg
54 ms
money-100x70.jpg
53 ms
room-324x160.jpg
56 ms
regresso-324x160.jpg
55 ms
real-1-324x160.jpg
57 ms
wrong-1-324x160.jpg
99 ms
horror-324x160.jpg
58 ms
piores-1-324x160.jpg
58 ms
kb01-356x220.jpg
59 ms
parody-356x220.jpg
72 ms
perturba25-356x220.jpg
73 ms
default.jpg
25 ms
default.jpg
28 ms
default.jpg
35 ms
default.jpg
29 ms
default.jpg
32 ms
default.jpg
38 ms
default.jpg
43 ms
default.jpg
45 ms
default.jpg
46 ms
default.jpg
47 ms
default.jpg
82 ms
default.jpg
48 ms
default.jpg
50 ms
default.jpg
52 ms
default.jpg
54 ms
default.jpg
54 ms
default.jpg
54 ms
default.jpg
68 ms
newspaper.woff
79 ms
logo_hw.gif
75 ms
p
11 ms
fechar.gif
72 ms
hotslide_70x200.jpg
103 ms
imp2sello.jsp
38 ms
p
4 ms
scriptbanner.js
76 ms
p
5 ms
elements.png
41 ms
agrega2.html
59 ms
iframeContent.html
428 ms
24426999301_6ce52d8f84_o.jpg
425 ms
med00.jpg
370 ms
med01.jpg
368 ms
med02.jpg
369 ms
med12.jpg
370 ms
med05.jpg
370 ms
med04.jpg
370 ms
med07.jpg
372 ms
count.js
295 ms
player_api
130 ms
xd_arbiter.php
75 ms
xd_arbiter.php
80 ms
likebox.php
221 ms
300x250_geladeira-5304801416-535.jpg
502 ms
tm12669.js
91 ms
fontawesome-webfont.woff
61 ms
www-widgetapi.js
70 ms
usr
78 ms
loc.js
19 ms
0FYYfKM47Xg
130 ms
eBwTbg8G3cT.css
54 ms
lEC7t4ATkwe.css
49 ms
1RbJkZXL7GD.css
48 ms
_rx8naC75Dy.js
56 ms
x5F9OMjKyLw.js
73 ms
ICDbTSzjQEg.js
72 ms
TTCre3391I0.js
82 ms
rFmE1g6Dkoz.js
87 ms
7cm7D75Y0Sf.js
84 ms
C-h3nYPqETO.js
84 ms
oRoBXlHCpEy.js
84 ms
336JejShbZp.js
84 ms
sj-JwAJi4AH.js
110 ms
DKRU1bYTkTw.js
117 ms
ZNPAadQNc33.js
119 ms
W0OV23mIOyO.js
121 ms
36TdwhIHusi.js
119 ms
req
220 ms
www-embed-player-vflZsBgOl.css
149 ms
www-embed-player.js
183 ms
10896854_836557666416511_4084084918156115902_n.jpg
150 ms
427471_286561788082771_1232572799_n.jpg
43 ms
631_883624851757363_8101511239756965018_n.jpg
100 ms
12742076_968568563233505_1942173987388228409_n.jpg
99 ms
11406770_1468001916841465_3545012773335626974_n.jpg
103 ms
12573043_612366378922555_7735875907116828885_n.jpg
100 ms
922927_988252844591970_4954901889250999270_n.jpg
101 ms
11053509_1399278013724690_3114208115507501019_n.jpg
102 ms
12316664_10154545922129657_7766966730003859887_n.jpg
103 ms
wL6VQj7Ab77.png
31 ms
s7jcwEQH7Sx.png
30 ms
pUFVdPjIRct.png
29 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
46 ms
ad_status.js
36 ms
I6-MnjEovm5.js
13 ms
vlXaquuXMrr.js
8 ms
getro.com.br accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
getro.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
getro.com.br SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
PT
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Getro.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Getro.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.
getro.com.br
Open Graph description is not detected on the main page of GETRO. 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: