Tools & Wizards About Us
radio.rpp.pe screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

radio.rpp.pe

RPP Noticias, 'la voz de todo el Perú' en vivo las 24 horas | RPP Player | AUDIOPLAYER PERÚ.

Page Load Speed

2.1 sec in total

First Response

9 ms

Resources Loaded

1.6 sec

Page Rendered

448 ms

radio.rpp.pe screenshot

About Website

Welcome to radio.rpp.pe homepage info - get ready to check Radio RPP best content for Peru right away, or after learning these important things about radio.rpp.pe

Toda la información al instante, escucha radio y podcast gratis. La Rotativa, Ampliación de noticias, El gran resumen de la hora, Fútbol como cancha, Los chistosos, Conexión, Así Somos, Enfoque de los...

Visit radio.rpp.pe

Key Findings

We analyzed Radio.rpp.pe page load time and found that the first response time was 9 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

radio.rpp.pe performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value19.9 s

0/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value1,870 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.1 s

3/100

10%

Network Requests Diagram

radio.rpp.pe

9 ms

radio.rpp.pe

25 ms

96 ms

radio.css

444 ms

main.css

656 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Radio.rpp.pe, 48% (20 requests) were made to Mds.rpp-noticias.io and 14% (6 requests) were made to S.rpp-noticias.io. The less responsive or slowest element that took the longest time to load (745 ms) relates to the external source S.rpp-noticias.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 313.7 kB (51%)

Content Size

618.6 kB

After Optimization

304.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Radio.rpp.pe main page is 618.6 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. 65% of websites need less resources to load. Javascripts take 332.8 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 137.1 kB

  • Original 160.0 kB
  • After minification 136.9 kB
  • After compression 22.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. This page needs HTML code to be minified as it can gain 23.0 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 137.1 kB or 86% of the original size.

Image Optimization

-18%

Potential reduce by 1.8 kB

  • Original 10.2 kB
  • After minification 8.4 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 RPP needs image optimization as it can save up to 1.8 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-25%

Potential reduce by 81.8 kB

  • Original 332.8 kB
  • After minification 332.5 kB
  • After compression 251.0 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 81.8 kB or 25% of the original size.

CSS Optimization

-80%

Potential reduce by 93.1 kB

  • Original 115.7 kB
  • After minification 115.2 kB
  • After compression 22.6 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. Radio.rpp.pe needs all CSS files to be minified and compressed as it can save up to 93.1 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (53%)

Requests Now

36

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

radio.rpp.pe

radio.rpp.pe

9 ms

radio.rpp.pe

radio.rpp.pe

25 ms

96 ms

radio.css

radio.css

444 ms

main.css

main.css

656 ms

api:client.js

api:client.js

23 ms

tm22924.js

tm22924.js

66 ms

gpt.js

gpt.js

97 ms

subRPlayer.js

subRPlayer.js

437 ms

libs.js

libs.js

561 ms

rpp-app.v2.js

rpp-app.v2.js

743 ms

radio_player.js

radio_player.js

745 ms

fb.js

fb.js

744 ms

login_init.js

login_init.js

745 ms

sw-installer.js

sw-installer.js

744 ms

idsync.js

idsync.js

55 ms

sdk.js

sdk.js

152 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

85 ms

gtm.js

gtm.js

233 ms

logo_rotafono_rpp_header.svg

logo_rotafono_rpp_header.svg

220 ms

btn__icon--facebook.png

btn__icon--facebook.png

219 ms

btn__icon--google.png

btn__icon--google.png

219 ms

btn__icon--correo.png

btn__icon--correo.png

220 ms

rpp_player.svg

rpp_player.svg

279 ms

grupo-rpp.png

grupo-rpp.png

280 ms

radio_live_s.svg

radio_live_s.svg

279 ms

account_off.svg

account_off.svg

380 ms

placeholder_4x4_rpp.svg

placeholder_4x4_rpp.svg

379 ms

placeholder_rpp.svg

placeholder_rpp.svg

378 ms

logo.svg

logo.svg

395 ms

usr

usr

220 ms

pubads_impl.js

pubads_impl.js

120 ms

sf-pro-text_regular.woff

sf-pro-text_regular.woff

513 ms

icomoon.ttf

icomoon.ttf

322 ms

sf-pro-text_bold.woff

sf-pro-text_bold.woff

612 ms

loaderopti.svg

loaderopti.svg

380 ms

sdk.js

sdk.js

11 ms

1028310

1028310

97 ms

req

req

85 ms

loaderopti.svg

loaderopti.svg

189 ms

idsync.js

idsync.js

101 ms

loader.svg

loader.svg

103 ms

Accessibility Review

radio.rpp.pe accessibility score

89

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

radio.rpp.pe best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

radio.rpp.pe SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

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

radio.rpp.pe

Open Graph data is detected on the main page of Radio RPP. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: