Tools & Wizards About Us
corazon.pe screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

corazon.pe

Escucha Radio Corazón EN VIVO: Vive+

Page Load Speed

2 sec in total

First Response

34 ms

Resources Loaded

1.7 sec

Page Rendered

232 ms

corazon.pe screenshot

About Website

Visit corazon.pe now to see the best up-to-date Corazon content for Peru and also check out these interesting facts you probably never knew about corazon.pe

La mejor música romántica por Radio Corazón EN VIVO 94,3 FM. Últimas Noticias y streaming de Bachatas, Baladas y Pop Latino por Radio Corazón Vive+

Visit corazon.pe

Key Findings

We analyzed Corazon.pe page load time and found that the first response time was 34 ms and then it took 1.9 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

corazon.pe performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value28.2 s

0/100

10%

TBT (Total Blocking Time)

Value7,690 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.707

7/100

15%

TTI (Time to Interactive)

Value47.3 s

0/100

10%

Network Requests Diagram

corazon.pe

34 ms

main.css

530 ms

iwIZKHA0.js

28 ms

functions.js

629 ms

gpt.js

70 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Corazon.pe, 33% (14 requests) were made to Scorazon.radio-grpp.io and 24% (10 requests) were made to F.radio-grpp.io. The less responsive or slowest element that took the longest time to load (951 ms) relates to the external source Scorazon.radio-grpp.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 84.9 kB (21%)

Content Size

403.7 kB

After Optimization

318.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 72.0 kB

  • Original 84.4 kB
  • After minification 71.1 kB
  • After compression 12.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 13.2 kB, which is 16% 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 72.0 kB or 85% of the original size.

Image Optimization

-22%

Potential reduce by 8.7 kB

  • Original 38.7 kB
  • After minification 30.1 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, Corazon needs image optimization as it can save up to 8.7 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 799 B

  • Original 255.9 kB
  • After minification 255.9 kB
  • After compression 255.1 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

-14%

Potential reduce by 3.4 kB

  • Original 24.7 kB
  • After minification 24.7 kB
  • After compression 21.3 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. Corazon.pe needs all CSS files to be minified and compressed as it can save up to 3.4 kB or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (29%)

Requests Now

35

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

corazon.pe

corazon.pe

34 ms

main.css

main.css

530 ms

iwIZKHA0.js

iwIZKHA0.js

28 ms

functions.js

functions.js

629 ms

gpt.js

gpt.js

70 ms

is_movil.js

is_movil.js

527 ms

libs.js

libs.js

748 ms

hammer.min.js

hammer.min.js

951 ms

rc-app.js

rc-app.js

949 ms

css

css

34 ms

cx.js

cx.js

323 ms

gtm.js

gtm.js

274 ms

334933_1630689.webp

334933_1630689.webp

624 ms

533653_1630874.webp

533653_1630874.webp

734 ms

stikio-tuscanciones150-1724155613630-1629636mp4_1629637.webp

stikio-tuscanciones150-1724155613630-1629636mp4_1629637.webp

848 ms

334933_1630689.webp

334933_1630689.webp

916 ms

533653_1630874.webp

533653_1630874.webp

916 ms

stikio-tuscanciones150-1724155613630-1629636mp4_1629637.webp

stikio-tuscanciones150-1724155613630-1629636mp4_1629637.webp

913 ms

playstore.svg

playstore.svg

318 ms

logo_corazon.svg

logo_corazon.svg

316 ms

right-arrow.svg

right-arrow.svg

434 ms

logo.rpp.white.png

logo.rpp.white.png

436 ms

pubads_impl.js

pubads_impl.js

276 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

211 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

213 ms

icomoon.ttf

icomoon.ttf

327 ms

raleway-bold-webfont.woff

raleway-bold-webfont.woff

329 ms

raleway-medium-webfont.woff

raleway-medium-webfont.woff

329 ms

bg_destaques.png

bg_destaques.png

320 ms

sprites.png

sprites.png

389 ms

332533_1611328.jpg

332533_1611328.jpg

438 ms

181418_1587215.jpg

181418_1587215.jpg

522 ms

082608_1611329.jpg

082608_1611329.jpg

628 ms

252725_1580237.jpg

252725_1580237.jpg

711 ms

303230_1605351.jpg

303230_1605351.jpg

712 ms

233323_1605352.jpg

233323_1605352.jpg

715 ms

142714_1566318.jpg

142714_1566318.jpg

713 ms

440844_1621604.jpg

440844_1621604.jpg

712 ms

524852_1547647.jpg

524852_1547647.jpg

731 ms

322332_1624443.jpg

322332_1624443.jpg

814 ms

KFOkCnqEu92Fr1Mu51xIIzc.ttf

KFOkCnqEu92Fr1Mu51xIIzc.ttf

50 ms

1028310

1028310

82 ms

Accessibility Review

corazon.pe accessibility score

75

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

corazon.pe best practices score

67

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

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

corazon.pe SEO score

90

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 Corazon.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 Corazon.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

corazon.pe

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