Access rodryan.iheart.com. Listen to Your Favorite Music, Podcasts, and Radio Stations for Free!

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

81/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value6,360 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value24.8 s

0/100

10%

rodryan.iheart.com

283 ms

34 ms

www.iheart.com

279 ms

553828

255 ms

runtime.www.js

63 ms

Our browser made a total of 117 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Rodryan.iheart.com, 73% (85 requests) were made to Iheart.com and 23% (27 requests) were made to I.iheart.com. The less responsive or slowest element that took the longest time to load (283 ms) belongs to the original domain Rodryan.iheart.com.

Content Size

3.5 MB

After Optimization

2.9 MB

In fact, the total size of Rodryan.iheart.com main page is 3.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. 80% 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 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 257.3 kB

Original 333.2 kB
After minification 333.2 kB
After compression 75.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 257.3 kB or 77% of the original size.

Image Optimization

-6%

Potential reduce by 119.0 kB

Original 1.9 MB
After minification 1.8 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. Rodryan IHeart images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 231.7 kB

Original 1.3 MB
After minification 1.3 MB
After compression 1.0 MB

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 231.7 kB or 18% of the original size.

Requests Now

107

After Optimization

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-*] attributes do not match their roles

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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.

High

Image elements do not have [alt] attributes

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

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

UTF-8

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

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