Tools & Wizards About Us
rtp.pt screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

rtp.pt

RTP - Rádio e Televisão de Portugal

Page Load Speed

2.3 sec in total

First Response

26 ms

Resources Loaded

1.4 sec

Page Rendered

895 ms

rtp.pt screenshot

About Website

Welcome to rtp.pt homepage info - get ready to check RTP best content for Portugal right away, or after learning these important things about rtp.pt

A RTP está próxima dos portugueses. Os programas que vê todos os dias na TV e na Rádio. Os vídeos e áudios dos seus programas preferidos, mp3, rss e online. Notícias, desporto, blogues, sugestões e as...

Visit rtp.pt

Key Findings

We analyzed Rtp.pt page load time and found that the first response time was 26 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

rtp.pt performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

17/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.078

95/100

15%

TTI (Time to Interactive)

Value4.2 s

85/100

10%

Network Requests Diagram

rtp.pt

26 ms

27 ms

js

189 ms

style-new.css

20 ms

rtp-require.js

16 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 17% of them (14 requests) were addressed to the original Rtp.pt, 55% (46 requests) were made to Cdn-images.rtp.pt and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (658 ms) relates to the external source Gapt.hit.gemius.pl.

Page Optimization Overview & Recommendations

Page size can be reduced by 122.7 kB (3%)

Content Size

4.5 MB

After Optimization

4.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rtp.pt main page is 4.5 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. 75% 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 4.1 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 61.4 kB

  • Original 75.8 kB
  • After minification 65.1 kB
  • After compression 14.3 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 10.7 kB, which is 14% 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 61.4 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 36.7 kB

  • Original 4.1 MB
  • After minification 4.0 MB

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. RTP images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 24.3 kB

  • Original 287.8 kB
  • After minification 286.9 kB
  • After compression 263.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 233 B

  • Original 65.5 kB
  • After minification 65.5 kB
  • After compression 65.2 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. Rtp.pt has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 17 (22%)

Requests Now

79

After Optimization

62

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of RTP. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

rtp.pt

rtp.pt

26 ms

27 ms

js

js

189 ms

style-new.css

style-new.css

20 ms

rtp-require.js

rtp-require.js

16 ms

homepage.nd.min.js

homepage.nd.min.js

15 ms

dfp.js

dfp.js

406 ms

analytics.js

analytics.js

398 ms

css

css

62 ms

rtp.png

rtp.png

302 ms

containr.js

containr.js

392 ms

phpThumb.php

phpThumb.php

432 ms

icon-search.svg

icon-search.svg

246 ms

social-icon-facebook.svg

social-icon-facebook.svg

242 ms

social-icon-twitter.svg

social-icon-twitter.svg

301 ms

social-icon-instagram.svg

social-icon-instagram.svg

303 ms

social-icon-youtube.svg

social-icon-youtube.svg

311 ms

social-icon-flickr.svg

social-icon-flickr.svg

309 ms

45449_71895_99638.png

45449_71895_99638.png

350 ms

41773_64314_27640.jpg

41773_64314_27640.jpg

434 ms

43456_67659_51565.jpg

43456_67659_51565.jpg

429 ms

player_RDP_internacional.jpg

player_RDP_internacional.jpg

303 ms

player_A1.jpg

player_A1.jpg

302 ms

6338_10580_30131.jpg

6338_10580_30131.jpg

432 ms

player_A3.jpg

player_A3.jpg

310 ms

d2b825069eaf241202509b4ecdb627f4

d2b825069eaf241202509b4ecdb627f4

403 ms

cac972071a9c48bc9e4e52f44c0312d5_N.jpg

cac972071a9c48bc9e4e52f44c0312d5_N.jpg

350 ms

b1c72baad582605c4554e2650e955eab_N.jpg

b1c72baad582605c4554e2650e955eab_N.jpg

396 ms

bc7575c4cfb324931be8cb267fbb2a13

bc7575c4cfb324931be8cb267fbb2a13

390 ms

405adf67f09cfe01174dc69120ae8441

405adf67f09cfe01174dc69120ae8441

407 ms

39eb0fc90fa112040aeaf3e4b22d36dd

39eb0fc90fa112040aeaf3e4b22d36dd

428 ms

868620e92ed09d4356d97e844610f9fd

868620e92ed09d4356d97e844610f9fd

427 ms

b019c6aec1b94bd0a53d9e45f04cfc22

b019c6aec1b94bd0a53d9e45f04cfc22

426 ms

82b9d6ef0447313ca0d4d99d75da797c

82b9d6ef0447313ca0d4d99d75da797c

432 ms

8042ea1fae687c581cefee45b6f81dc2

8042ea1fae687c581cefee45b6f81dc2

434 ms

9ad202008fdec2a1234238af85101769

9ad202008fdec2a1234238af85101769

432 ms

c79a6b2956e6d0a6fa0d340424294a2c

c79a6b2956e6d0a6fa0d340424294a2c

433 ms

4c15789cc4ab87e5b363ba80be8ac03f

4c15789cc4ab87e5b363ba80be8ac03f

436 ms

d46e60623deba64a4243b411d5e6612e

d46e60623deba64a4243b411d5e6612e

434 ms

ed9037fdea17ce31f3dfa127a412913a

ed9037fdea17ce31f3dfa127a412913a

435 ms

71fb7e8315acebd996379b753709e3e9

71fb7e8315acebd996379b753709e3e9

438 ms

15efe30494818cf88d2a364dd36503a1

15efe30494818cf88d2a364dd36503a1

437 ms

rtpPlay_cheioNegativo_horiz_RGB.png

rtpPlay_cheioNegativo_horiz_RGB.png

438 ms

AppleStore.png

AppleStore.png

441 ms

GooglePlay.png

GooglePlay.png

442 ms

Huawey.png

Huawey.png

442 ms

62ae6f1ad6b8c9ead86bf88fb9d881e7

62ae6f1ad6b8c9ead86bf88fb9d881e7

444 ms

0548495e32b7e5909265a9dda9490d73

0548495e32b7e5909265a9dda9490d73

448 ms

21e02030bcd97a435d52ecc6e5fcb63f

21e02030bcd97a435d52ecc6e5fcb63f

443 ms

31430dc57b16c2cc8e4385afc628c6eb

31430dc57b16c2cc8e4385afc628c6eb

449 ms

0d63112e6c04285ba9be3cec2c7cee5c

0d63112e6c04285ba9be3cec2c7cee5c

447 ms

d0eb6b31718a37cebb713f39f215fa03

d0eb6b31718a37cebb713f39f215fa03

444 ms

b38a7193071149e7c16000d43db8df9e

b38a7193071149e7c16000d43db8df9e

456 ms

font

font

349 ms

rdf-icons.woff

rdf-icons.woff

70 ms

e119ead9ae266343d336e4688615bd9a

e119ead9ae266343d336e4688615bd9a

217 ms

QWQOVZ6C.js

QWQOVZ6C.js

155 ms

gpt.js

gpt.js

222 ms

analytics.js

analytics.js

154 ms

pipe-latest.min.js

pipe-latest.min.js

147 ms

xgemius.js

xgemius.js

658 ms

42e6f6e73767ce155ac8df595b4360b8

42e6f6e73767ce155ac8df595b4360b8

154 ms

cc0b85f01ee6fabe7d92ed68b3734611

cc0b85f01ee6fabe7d92ed68b3734611

153 ms

25d2c4cf3ffc7e2e9bfd2618cc09053f

25d2c4cf3ffc7e2e9bfd2618cc09053f

126 ms

learn

learn

185 ms

d95c1dabdee3a63f381210dfe174632d

d95c1dabdee3a63f381210dfe174632d

122 ms

a6eba864e83510f24f8486c1d48644ce

a6eba864e83510f24f8486c1d48644ce

118 ms

55622f3e9bb66d5a17f1b0c63138fb26

55622f3e9bb66d5a17f1b0c63138fb26

75 ms

09c863e5c92d755ed888b39426fe2a48

09c863e5c92d755ed888b39426fe2a48

69 ms

pipeconfig

pipeconfig

325 ms

8a07f38a4b3ffc34010fb61f07e0964d

8a07f38a4b3ffc34010fb61f07e0964d

60 ms

collect

collect

22 ms

collect

collect

22 ms

rtp.png

rtp.png

46 ms

ga-audiences

ga-audiences

64 ms

pubads_impl.js

pubads_impl.js

25 ms

encrypted-tag-g.js

encrypted-tag-g.js

133 ms

esp.js

esp.js

45 ms

uid2SecureSignal.js

uid2SecureSignal.js

41 ms

connectId-gpt.js

connectId-gpt.js

42 ms

pubcid.min.js

pubcid.min.js

34 ms

collect

collect

181 ms

fpdata.js

fpdata.js

86 ms

Accessibility Review

rtp.pt accessibility score

81

Accessibility Issues

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

High

<frame> or <iframe> elements do not have a title

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

The document uses <meta http-equiv="refresh">

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

rtp.pt best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

rtp.pt SEO score

97

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rtp.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Rtp.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.

Social Sharing Optimization

rtp.pt

Open Graph description is not detected on the main page of RTP. 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: