6.5 sec in total
325 ms
4.3 sec
1.9 sec
Welcome to rr.pt homepage info - get ready to check Rr best content for Portugal right away, or after learning these important things about rr.pt
Em cada momento a rádio com o espirito certo. Na rádio, no digital e em podcast.
Visit rr.ptWe analyzed Rr.pt page load time and found that the first response time was 325 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
rr.pt performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value19.2 s
0/100
25%
Value14.4 s
1/100
10%
Value16,020 ms
0/100
30%
Value1.174
1/100
15%
Value27.5 s
0/100
10%
325 ms
944 ms
720 ms
427 ms
311 ms
Our browser made a total of 138 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Rr.pt, 41% (56 requests) were made to Rr.sapo.pt and 12% (17 requests) were made to Mediaserver4.rr.pt. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Data.netscope.marktest.pt.
Page size can be reduced by 886.7 kB (50%)
1.8 MB
882.5 kB
In fact, the total size of Rr.pt main page is 1.8 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. 60% of websites need less resources to load. Javascripts take 695.9 kB which makes up the majority of the site volume.
Potential reduce by 124.0 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 124.0 kB or 84% of the original size.
Potential reduce by 68.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. Rr images are well optimized though.
Potential reduce by 483.5 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 483.5 kB or 69% of the original size.
Potential reduce by 211.0 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. Rr.pt needs all CSS files to be minified and compressed as it can save up to 211.0 kB or 83% of the original size.
Number of requests can be reduced by 63 (55%)
115
52
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
rr.pt
325 ms
rr.sapo.pt
944 ms
ink-all.min.js
720 ms
ink-flex.min.css
427 ms
font-awesome.min.css
311 ms
jquery-2.1.3.min.js
517 ms
modernizr.js
321 ms
rrcss-main.css
413 ms
videos.css
426 ms
rrcss-default.css
516 ms
rrcss-Hamburguer.css
433 ms
weather-icons.css
331 ms
home.js
106 ms
bigSlide.min.js
109 ms
autoload.js
111 ms
BreakPointsLazyLoad.js
124 ms
jwplayer.js
356 ms
AC_RunActiveContent.js
205 ms
createplayer.js
351 ms
masterMain.js
353 ms
main.js
353 ms
barra.js
426 ms
porques1657569f_square.jpg
419 ms
quaresma_300x30018800126_square.jpg
523 ms
consultor664x3731156d92d_square.jpg
417 ms
master_1200x6008632aa76_square.jpg
316 ms
master_1200x6008632aa76_base.jpg
418 ms
master_1200x6008632aa76_capa1.jpg
317 ms
putin_fotoepa1284a942_base.jpg
661 ms
master_1200x6008632aa76_large.jpg
592 ms
fechar.jpg
105 ms
icoNav.png
112 ms
logoRR.svg
112 ms
logoRRXs.svg
104 ms
butNoAr.svg
108 ms
icoSearch.png
124 ms
logoEuranet.png
205 ms
icoPlayXlarge.png
205 ms
lgs_rcom_on.png
207 ms
lgs_rfm_on.png
205 ms
lgs_mega_on.png
205 ms
lgs_sim_on.png
228 ms
lgs_intervoz_on.png
310 ms
lgs_genius_on.png
310 ms
bgMenu.png
280 ms
icoHome.png
280 ms
toggle-small-expand.png
280 ms
roboto-regular-webfont.woff
450 ms
roboto-medium-webfont.woff
521 ms
roboto-light-webfont.woff
521 ms
roboto-thin-webfont.woff
591 ms
roboto-bold-webfont.woff
590 ms
roboto-black-webfont.woff
591 ms
robotoslab-light-webfont.woff
591 ms
robotoslab-thin-webfont.woff
666 ms
robotoslab-regular-webfont.woff
667 ms
robotoslab-bold-webfont.woff
800 ms
ajs.php
327 ms
fontawesome-webfont.woff
778 ms
weathericons-regular-webfont.woff
778 ms
ribeiro_cristovao_300x3008604e964.png
423 ms
icoPlaySmall.png
417 ms
icoQuote.png
418 ms
icoAudioSmall.png
419 ms
netscope-gemius.js
1697 ms
316 ms
scorpions_300x3001274dc49_square.jpg
106 ms
mrec.aspx
113 ms
ajs.php
124 ms
trocado_por_Miudos1165fb2f_square.jpg
115 ms
depois21862698c_capa1.jpg
208 ms
0520784614049ab9_base.jpg
214 ms
policia_belga16140577_base.jpg
312 ms
parlamento_votacaosobretaxa_181215_fotomariocruzlusa13752c3d_base.jpg
480 ms
miguel_morgado1568a130_base.jpg
290 ms
ajs.php
133 ms
iframe_pub.js
105 ms
ajs.php
199 ms
13508.js
123 ms
learn
245 ms
lg.php
178 ms
analytics.js
92 ms
avisoCookies.aspx
196 ms
locutorPlayer.aspx
138 ms
sync
50 ms
bsu.css
825 ms
AppBanners.js
338 ms
285622-10.js
196 ms
collect
53 ms
collect
105 ms
sync
40 ms
285622-15.js
92 ms
0RaXcM1FOu_395154613.html
16 ms
emily.html
52 ms
emily.html
60 ms
jload
60 ms
adServer.bs
226 ms
creative_add_on.js
150 ms
48 ms
mon
48 ms
tap.php
20 ms
dt
31 ms
pixel.htm
53 ms
F4-img-2_1.jpg
8 ms
cms-2c.html
69 ms
ddc.htm
35 ms
tap.php
57 ms
2964
214 ms
Pug
71 ms
rum
58 ms
tap.php
52 ms
paulino_toponoar_146x11745912dcb_locutor.png
257 ms
pixel
64 ms
rubicon
50 ms
rubicon.ashx
165 ms
pixel
233 ms
sd
49 ms
demconf.jpg
52 ms
rum
135 ms
sync
39 ms
rs
200 ms
385636.gif
193 ms
check
203 ms
rubicon
135 ms
pixel
183 ms
tap.php
161 ms
sprite.png
140 ms
tap.php
85 ms
pixel.gif
82 ms
m.gif
79 ms
tap.php
37 ms
tap.php
36 ms
pixel
42 ms
m_yahoo.gif
30 ms
tap.php
36 ms
Pb+0hKW0OLWIgQEA2yAL2gBLuADIUlixAQGOWbkIAAgAYyCwASNEsAMjcLIEKAlFUkSyCgIHKrEGAUSxJAGIUViwQIhYsQYDRLEmAYhRWLgEAIhYsQYBRFlZWVm4Af+FsASNsQUARAAA
34 ms
match-result
171 ms
tap.php
16 ms
rr.pt 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
rr.pt 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
rr.pt 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rr.pt 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 Rr.pt 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.
rr.pt
Open Graph data is detected on the main page of Rr. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: