4.8 sec in total
507 ms
4.2 sec
169 ms
Welcome to radiofunk.com.br homepage info - get ready to check Radio Funk best content right away, or after learning these important things about radiofunk.com.br
Radio Funk - A Rádio Funk toca o melhor do Funk da ostentação, do Funk carioca e todos os Funk´s que existe para que você possa sempre estar por dentro do melhor do Funk atual e relembrar o Funk do pa...
Visit radiofunk.com.brWe analyzed Radiofunk.com.br page load time and found that the first response time was 507 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
radiofunk.com.br performance score
507 ms
154 ms
35 ms
11 ms
9 ms
Our browser made a total of 184 requests to load all elements on the main page. We found that 11% of them (21 requests) were addressed to the original Radiofunk.com.br, 10% (19 requests) were made to Um.simpli.fi and 6% (11 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Encrypted-tbn0.gstatic.com.
Page size can be reduced by 404.9 kB (51%)
790.1 kB
385.2 kB
In fact, the total size of Radiofunk.com.br main page is 790.1 kB. 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 653.9 kB which makes up the majority of the site volume.
Potential reduce by 64.9 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 64.9 kB or 70% of the original size.
Potential reduce by 2.8 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. Obviously, Radio Funk needs image optimization as it can save up to 2.8 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 321.7 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 321.7 kB or 49% of the original size.
Potential reduce by 15.5 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. Radiofunk.com.br needs all CSS files to be minified and compressed as it can save up to 15.5 kB or 83% of the original size.
Number of requests can be reduced by 92 (59%)
155
63
The browser has sent 155 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Radio Funk. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 49 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
radiofunk.com.br
507 ms
css-home-new.css
154 ms
embed.js
35 ms
show_ads.js
11 ms
addthis_widget.js
9 ms
brand
14 ms
brand
27 ms
_.gif
442 ms
jquery.min.js
106 ms
back-busca.gif
787 ms
ca-pub-4778335915839197.js
422 ms
zrt_lookup.html
473 ms
show_ads_impl.js
419 ms
aparece-music.html
757 ms
radioscombr_105x105.jpg
531 ms
0.gif
394 ms
video-1.gif
833 ms
video-2.gif
1014 ms
video-3.gif
1048 ms
video-4.gif
1013 ms
top-1.gif
1013 ms
top-2.gif
1013 ms
top-3.gif
1012 ms
top-4.gif
1195 ms
logo.gif
335 ms
icon-twitter.gif
527 ms
icon-facebook.gif
528 ms
bt-player-home.gif
528 ms
divulga-1.gif
528 ms
divulga-2.gif
529 ms
indic-videos.gif
528 ms
indic-top.gif
683 ms
banner-rod-300x60-1.gif
683 ms
google_custom_search_watermark.gif
420 ms
bb_viewability.min.js
71 ms
list
206 ms
likebox.php
219 ms
small.js
77 ms
ga.js
95 ms
ads
238 ms
osd.js
36 ms
ads
249 ms
ads
387 ms
147 ms
300lo.json
142 ms
all.js&version=v2.0
832 ms
widgets.js
137 ms
plusone.js
71 ms
counter.5524cceca805eb4b9b2b.js
44 ms
__utm.gif
66 ms
__utm.gif
64 ms
ads
185 ms
sh.8e5f85691f9aaa082472a194.html
53 ms
beacon.js
84 ms
tm11750.js
173 ms
user_sync.html
83 ms
widget.css
76 ms
embed_enabler.min.js
86 ms
shares.json
82 ms
hDvwL1_H7g-.css
501 ms
56WNbrUYLbL.css
638 ms
q68gy-v_YMF.js
737 ms
FJmpeSpHpjS.js
866 ms
0wM5s1Khldu.js
820 ms
1bNoFZUdlYZ.js
818 ms
cb=gapi.loaded_0
117 ms
cb=gapi.loaded_1
114 ms
fastbutton
168 ms
dpx.js
54 ms
showad.js
63 ms
m_js_controller.js
223 ms
abg.js
335 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
272 ms
bbbeacon-icon-transparent.png
40 ms
728x90.html
269 ms
p
96 ms
tpid=1DE70445F088EE561B03413502B3FAE2
45 ms
PugMaster
64 ms
universalpixel.js
47 ms
usr
152 ms
postmessageRelay
217 ms
pixel
119 ms
Pug
117 ms
usersync.aspx
157 ms
8DFFF3AB-47EA-4F8C-BBAD-D368D5C7752E
85 ms
UPug
163 ms
cb=gapi.loaded_0
73 ms
cb=gapi.loaded_1
58 ms
176 ms
dpx
29 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
245 ms
cloudflare.min.js
59 ms
runtime.js
292 ms
embed_triggers.min.js
19 ms
aol
95 ms
Pug
153 ms
favicon
2349 ms
favicon
221 ms
nessie_icon_tiamat_white.png
190 ms
googlelogo_color_112x36dp.png
200 ms
req
182 ms
Pug
89 ms
Pug
94 ms
pixel.js
78 ms
Pug
107 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
101 ms
tc.js
110 ms
3193398744-postmessagerelay.js
133 ms
rpc:shindig_random.js
97 ms
s
76 ms
x_button_blue2.png
87 ms
Pug
90 ms
Pug
97 ms
dpsync.html
63 ms
mapuser
43 ms
Pug
132 ms
req
137 ms
p
114 ms
cb=gapi.loaded_0
93 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
30 ms
req
58 ms
y_match
21 ms
05770064089060256
179 ms
jot
178 ms
v2
48 ms
match_redirect
9 ms
29931
23 ms
dpx
6 ms
match_redirect
6 ms
tpid=C629559EF088EE56E22312AE02E91D50
7 ms
ca.png
220 ms
lr
89 ms
104 ms
xrefid.xgi
6 ms
xd_arbiter.php
215 ms
xd_arbiter.php
420 ms
282578_191738834217227_2735024_n.jpg
340 ms
1622232_810994205710751_2973114555022745896_n.jpg
427 ms
11351421_429130120591113_6327213378432812867_n.jpg
564 ms
12321659_826059250835746_7873436834950176061_n.jpg
628 ms
12805710_205663299790032_2562781087050988131_n.jpg
761 ms
12376774_1317410478275617_1612714134057593627_n.jpg
752 ms
12115629_936020143120456_3785858874773811680_n.jpg
629 ms
10354686_10150004552801856_220367501106153455_n.jpg
566 ms
12592562_951946638219501_1858403543345146279_n.jpg
630 ms
wL6VQj7Ab77.png
76 ms
s7jcwEQH7Sx.png
76 ms
lr.gif
6 ms
52154.gif
16 ms
match_redirect
14 ms
sync
10 ms
match_redirect
4 ms
C629559EF088EE56E22312AE02E91D50
35 ms
exelate
3 ms
24 ms
24 ms
17 ms
eyJpZCI6ImQ5NzZjMTVmZTA1Y2VlY2ZmZGI3NWFhODM5OTVjNWFjYTIxOWJkZTgiLCJyZSI6IjJlMjgxNzE0ZTUxMGUyNGJiNWVmMzE0YTg1NTRlNGFiIiwiZGkiOjQ2MTQxNiwiZm8iOiJqc29uIiwiZmkiOiJiYmIiLCJzaSI6IjMzM2M4YTg3NjdkMWRkYTg2MDAyMzg2MTk2YmRjYzBkZGRjNmUwNTciLCJpbyI6MCwiZmlkIjoiOTU5ZDU4YjlmNTA4NGFhZDBiNzBkMTE2Y2I3NjJlMDUiLCJhcCI6MSwiYXQiOiJ3aWRnZXRfZnVsbF9hZCIsImNpIjo5OTE4LCJhaSI6MTAwMzQ3LCJzciI6IjlmNDZjNzI3YzJiNTI3NTFkM2U5MWMwYThhZDljYzk0MmQ0MWJmNmUiLCJkdCI6IjIwMTYtMDMtMjBUMDg6MjY6NDAtMDM6MDAifQ==
63 ms
spotx_match
4 ms
fb_match
4 ms
u.php
39 ms
an
4 ms
lj_match
3 ms
cw_match
4 ms
rtset
20 ms
merge
43 ms
rb_match
3 ms
ox_match
5 ms
tap.php
6 ms
pm_match
4 ms
sd
6 ms
Pug
45 ms
pixel
15 ms
g_match
4 ms
match_redirect
3 ms
pixel
29 ms
aa_px
4 ms
activeview
13 ms
I6-MnjEovm5.js
73 ms
pQrUxxo5oQp.js
137 ms
ping
38 ms
ui
13 ms
like.php
64 ms
LVx-xkvaJ0b.png
68 ms
radiofunk.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 Radiofunk.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 Radiofunk.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.
radiofunk.com.br
Open Graph description is not detected on the main page of Radio Funk. 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: