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

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

77/100

10%

LCP (Largest Contentful Paint)

Value2.2 s

94/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value6,750 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value26.8 s

0/100

10%

www.iheart.com

239 ms

runtime.www.js

22 ms

360.www.js

39 ms

932.www.js

27 ms

6474.www.js

66 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Iheart.co.nz, 18% (22 requests) were made to I.iheart.com and 2% (2 requests) were made to Z.moatads.com. The less responsive or slowest element that took the longest time to load (239 ms) relates to the external source Iheart.com.

Content Size

4.4 MB

After Optimization

3.8 MB

In fact, the total size of Iheart.co.nz main page is 4.4 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. Only a small number of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 256.6 kB

Original 332.0 kB
After minification 332.0 kB
After compression 75.5 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 256.6 kB or 77% of the original size.

Image Optimization

-6%

Potential reduce by 177.4 kB

Original 2.8 MB
After minification 2.7 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. IHeart images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 213.1 kB

Original 1.2 MB
After minification 1.2 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 213.1 kB or 17% of the original size.

Requests Now

117

After Optimization

The browser has sent 117 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 92 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

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

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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 Iheart.co.nz 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 Iheart.co.nz 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

iheart.co.nz

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Listen to Your Favorite Music, Podcasts, and Radio Stations for Free! – iHeart

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

www.iheart.com

runtime.www.js

360.www.js

932.www.js

6474.www.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

www.iheart.com

runtime.www.js

360.www.js

932.www.js

6474.www.js

1884.www.js

entry.www.js

8240.www.js

6638.www.js

9351.www.js

8288.www.js

5494.www.js

5759.www.js

560.www.js

9547.www.js

4909.www.js

3573.www.js

265.www.js

9260.www.js

5681.www.js

8130.www.js

5108.www.js

3231.www.js

7320.www.js

4406.www.js

4004.www.js

743.www.js

5282.www.js

6458.www.js

5516.www.js

412.www.js

4984.www.js

1076.www.js

293.www.js

440.www.js

4277.www.js

moatheader.js

215270876

66f75a40c125741ece2a1b61

66f6bdd422c012bd5298c206

66f6fe4c727fd699a978e8b5

66f70d431e34b841e5479ba3

66f707f6622200d625ee5dd4

66f707561e34b841e5479b94