2 sec in total
25 ms
1.6 sec
367 ms
Welcome to iheart.com homepage info - get ready to check IHeart best content for United States right away, or after learning these important things about iheart.com
iHeart. All your favorite music, podcasts, and radio stations available for free. Listen to thousands of live radio stations or create your own artist stations and playlists. Get the latest music and ...
Visit iheart.comWe analyzed Iheart.com page load time and found that the first response time was 25 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 35% of websites can load faster.
iheart.com performance score
name
value
score
weighting
Value2.3 s
74/100
10%
Value2.3 s
93/100
25%
Value6.9 s
33/100
10%
Value4,610 ms
0/100
30%
Value0
100/100
15%
Value22.9 s
1/100
10%
25 ms
32 ms
21 ms
16 ms
10 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 9% of them (9 requests) were addressed to the original Iheart.com, 19% (20 requests) were made to I.iheart.com and 11% (12 requests) were made to Iscale.iheart.com. The less responsive or slowest element that took the longest time to load (470 ms) relates to the external source Api2.iheart.com.
Page size can be reduced by 547.5 kB (21%)
2.6 MB
2.1 MB
In fact, the total size of Iheart.com main page is 2.6 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 1.7 MB which makes up the majority of the site volume.
Potential reduce by 89.4 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 89.4 kB or 84% of the original size.
Potential reduce by 47.8 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. IHeart images are well optimized though.
Potential reduce by 391.9 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 391.9 kB or 53% of the original size.
Potential reduce by 18.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. Iheart.com needs all CSS files to be minified and compressed as it can save up to 18.3 kB or 77% of the original size.
Number of requests can be reduced by 43 (45%)
95
52
The browser has sent 95 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 28 to 1 for JavaScripts and as a result speed up the page load time.
iheart.com
25 ms
www.iheart.com
32 ms
web.css
21 ms
polyfills-6.3.0.min.js
16 ms
2802421395.js
10 ms
register2.php
190 ms
SynchroClient2.js
15 ms
51 ms
web.js
80 ms
es6-promise-2.0.1.modded.min.js
79 ms
20 ms
logo-white.png
17 ms
afr.php
374 ms
appboy.min.css
231 ms
appboy.min.js
261 ms
loginOrCreateOauthUser;clientType=web;pname=OrganicWeb;signupFlow=anon;country=US;uid=1458467790113
470 ms
jwplayer.js
409 ms
beacon.js
143 ms
cc.js
231 ms
tr
168 ms
ga.js
166 ms
localytics.min.js
143 ms
ando.js
109 ms
ggcmb400.js
230 ms
s_code.js
230 ms
getClientConfig
324 ms
cast_sender.js
130 ms
getLiveRadioAdConfig
275 ms
gpt.js
79 ms
swfobject-2.2.min.js
23 ms
Bp4Groa9BssG1QcQgABAAAAPQIJABgAAAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAADgCuAAEAAAAAAAEADAAAAAEAAAAAAAIABwCNAAEAAAAAAAMADABFAAEAAAAAAAQADACiAAEAAAAAAAUACwAkAAEAAAAAAAYADABpAAEAAAAAAAoAGgDGAAMAAQQJAAEAGAAMAAMAAQQJAAIADgCUAAMAAQQJAAMAGABRAAMAAQQJAAQAGACuAAMAAQQJAAUAFgAvAAMAAQQJAAYAGAB1AAMAAQQJAAoANADgaWhlYXJ0aWNvbnMzAGkAaABlAGEAcgB0AGkAYwBvAG4AcwAzVmVyc2lvbiAxLjAAVgBlAHIAcwBpAG8AbgAgADEALgAwaWhlYXJ0aWNvbnMzAGkAaABlAGEAcgB0AGkAYwBvAG4AcwAzaWhlYXJ0aWNvbnMzAGkAaABlAGEAcgB0AGkAYwBvAG4AcwAzUmVndWxhcgBSAGUAZwB1AGwAYQByaWhlYXJ0aWNvbnMzAGkAaABlAGEAcgB0AGkAYwBvAG4AcwAzRm9udCBnZW5lcmF0ZWQgYnkgSWNvTW9vbi4ARgBvAG4AdAAgAGcAZQBuAGUAcgBhAHQAZQBkACAAYgB5ACAASQBjAG8ATQBvAG8AbgAuAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
22 ms
ajs.php
120 ms
lg.php
255 ms
1.gif
230 ms
font-awesome.min.css
61 ms
pubads_impl_82.js
116 ms
image.gif
144 ms
__utm.gif
65 ms
ajs.php
196 ms
lg.php
222 ms
glcfg400.js
71 ms
image.gif
43 ms
collect
123 ms
container.html
57 ms
show_companion_ad.js
58 ms
pldpr400.js
44 ms
ls.html
57 ms
NaN
40 ms
63 ms
genre
93 ms
markets
84 ms
m
39 ms
cfg
320 ms
googima.js
217 ms
jwpsrv.js
467 ms
lg.php
243 ms
2509
236 ms
aHR0cCUzQSUyRiUyRnJhZGlvZWRpdC5paGVhcnQuY29tJTJGc2VydmljZSUyRmltZyUyRm5vcCgpJTJGYXNzZXRzJTJGaW1hZ2VzJTJGNGVmZWJkNjUtM2M1Yi00ZjI4LTk2MjgtODcyODIzOWI5YjllLnBuZw==
189 ms
2501
159 ms
4902
167 ms
2505
166 ms
6395
167 ms
2525
186 ms
5376
209 ms
2513
210 ms
4776
213 ms
1073
222 ms
6455
211 ms
289 ms
rt=ifr
48 ms
ima3.js
68 ms
s3386210440192
62 ms
pixel
76 ms
tpc=na_id
73 ms
5907
103 ms
g.json
234 ms
103
101 ms
genre
69 ms
genre-game-bg.jpg
215 ms
193 ms
pixel
171 ms
a3147f2f-28b6-4711-8672-e40ced959367
118 ms
022d7fc8-4a99-4f4b-a2e5-7ca4bed64fb7
95 ms
46ec6e15-ae18-4787-9a82-f8e449c1198c
95 ms
c45bbec4-04a7-4e3a-b74b-2bf208b539b2
94 ms
f4dc6bca-8539-40ff-b44d-b822fd01ace3
93 ms
43febcd0-e4ab-4203-b687-fd3d2bd49c56
97 ms
fa8798c1-8f24-49f8-bdb3-8c9034b4c087
91 ms
6255790f-8f06-43b3-a250-55ed5744faa1
94 ms
a0fb5fbe-bc01-440a-9155-b4974693b5a1
95 ms
97a0e1ba-492a-4164-9c32-52075ca00255
100 ms
7ff83477-bd5f-4714-a442-9d5639c23c37
99 ms
2ae79673-6efb-4576-b5b2-457967b5cca4
97 ms
86c01b8f-4747-43ae-bb41-070a3ffb5d3e
95 ms
eb6fbf19-9c74-42a9-93b2-ab20b705bf1f
99 ms
c5e44487-0be1-4da9-9349-aaf7ce66486f
96 ms
5292b6cb-e93a-42ec-b0eb-dee9ca31821b
99 ms
2b9c5d03-9e7c-40a2-a960-125447f295ee
100 ms
d220b890-dcc8-4c5a-b9df-484777053b36
104 ms
e11325a9-cf2d-48c7-9f91-cdedf4ca1d79
102 ms
7835c9f4-ee43-4d05-a43b-4fe5e4e54af6
95 ms
67 ms
s38418148853816
68 ms
s31836541644297
37 ms
362738.gif
28 ms
iheart.com accessibility score
ARIA
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.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
iheart.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
iheart.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iheart.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 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.
iheart.com
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: