631 ms in total
184 ms
369 ms
78 ms
Welcome to wham1180.iheart.com homepage info - get ready to check WHAM 1180 Iheart best content for United States right away, or after learning these important things about wham1180.iheart.com
Don't miss out on the latest from NewsRadio WHAM 1180, Rochester's News, Weather & Traffic Station
Visit wham1180.iheart.comWe analyzed Wham1180.iheart.com page load time and found that the first response time was 184 ms and then it took 447 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.
wham1180.iheart.com performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value4.1 s
46/100
25%
Value7.9 s
23/100
10%
Value5,430 ms
0/100
30%
Value0
100/100
15%
Value27.2 s
0/100
10%
184 ms
165 ms
162 ms
164 ms
170 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Wham1180.iheart.com, 89% (47 requests) were made to Static.inferno.iheart.com and 8% (4 requests) were made to I.iheart.com. The less responsive or slowest element that took the longest time to load (249 ms) relates to the external source Z.moatads.com.
Page size can be reduced by 1.5 MB (77%)
1.9 MB
443.9 kB
In fact, the total size of Wham1180.iheart.com main page is 1.9 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. 70% of websites need less resources to load. HTML takes 1.5 MB which makes up the majority of the site volume.
Potential reduce by 1.3 MB
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 1.3 MB or 83% of the original size.
Potential reduce by 1.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. WHAM 1180 Iheart images are well optimized though.
Potential reduce by 177.7 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 177.7 kB or 66% of the original size.
Potential reduce by 3.2 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. Wham1180.iheart.com needs all CSS files to be minified and compressed as it can save up to 3.2 kB or 11% of the original size.
Number of requests can be reduced by 46 (88%)
52
6
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WHAM 1180 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 30 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
wham1180.iheart.com
184 ms
bundle.b4784393326cfefc06fa.css
165 ms
sites-local.f4601bc8219098567a86.css
162 ms
core-components-tiles-OnairTileLoader-component.d9b89684bedbb0c4b00f.css
164 ms
core-page-blocks-datasource-DatasourceLoader-component.d0d7c906ff67d191c4e4.css
170 ms
Datasource-component.21b2d627bf3f26b77cdb.css
170 ms
Grid-component.9e05f3f8fa0e6b993347.css
177 ms
components-tiles-ContentTile-component.a5e9ee6f3bc07a62d945.css
177 ms
TrafficTile-component.7ce458744ec9f4e49d10.css
175 ms
Heading-component.d79a5c95e6ef67a97bca.css
175 ms
LoadMoreFromCursor-component.4a7a0f66bc2d890b3034.css
177 ms
Show-component.608ec1ff0656c8b676a1.css
178 ms
core-page-blocks-datasource-DatasourceTileLoader-component.21b2d627bf3f26b77cdb.css
183 ms
FauxButton-component.1f25bb623660eb4f88c1.css
179 ms
Eyebrow-component.5399b326d85b58042faf.css
182 ms
WeatherTile-component.ca557d80a0c5075ed0c1.css
181 ms
Podcasts-component.f6328fb51c2f2829facf.css
184 ms
ImageTile-component.c2cbd469fbc0bd11cbdf.css
185 ms
Card-component.c66d212af09897afcdd6.css
186 ms
moatheader.js
249 ms
62c48055bda7e4d34c7832ea
165 ms
f79fc341-a979-4863-81b0-eea1ddc6e07b
90 ms
f79fc341-a979-4863-81b0-eea1ddc6e07b
96 ms
627ed0263f19c6325b37ec16
148 ms
runtime.6b4924f16f0540cb95f3.js
94 ms
vendor.710290aee3274352d59a.js
101 ms
bundle.493e54a605c4909893ed.js
109 ms
src_app_core_chrome_AppTray_component_tsx-src_app_core_chrome_Footer_component_tsx-src_app_co-d67451.a19849dbbcd5f0a50bfc.js
95 ms
sites-local.37d46712c4175db4e3c9.js
93 ms
MagicLink-component.d8ebec3fff267f1ceb57.js
92 ms
core-components-tiles-OnairTileLoader-component.3660133e9ae8cc8c3dbd.js
94 ms
core-page-blocks-datasource-DatasourceLoader-component.c4fb328c3b6211b7ca76.js
95 ms
Datasource-component.1c017bbd80cc11bfd075.js
95 ms
Grid-component.d1391a391db391ba3293.js
96 ms
ContentFeedItem-component.18a0bca380789d53b358.js
96 ms
components-tiles-ContentTile-component.c15ed61ef8b431c7c7ce.js
97 ms
LeadFeedItem-component.7349c61d3b98434fc28f.js
97 ms
core-components-tiles-WeatherTileLoader-component.f557adc4bb831fc87d0d.js
97 ms
TrafficTile-component.3c995ef5999160daa0e7.js
98 ms
Heading-component.28a08a32215f3defa880.js
99 ms
LoadMoreFromCursor-component.a8dbeb4c1b1e9069f823.js
98 ms
core-page-blocks-podcast-PodcastsLoader-component.e465f719fda6f62933b2.js
99 ms
ShowCollection-component.1b6eeb0052640df16d06.js
85 ms
Show-component.89404286ecfc5ad39b2b.js
80 ms
core-page-blocks-datasource-DatasourceTileLoader-component.59cc1549bce6b4b5800c.js
79 ms
FauxButton-component.7c8a6b13cd1c228006f2.js
78 ms
core-page-blocks-contest-KeywordContestLoader-component.5435e7b603530e153d88.js
79 ms
DateTimeDisplay-component.9a93eb94463384ae2d8e.js
76 ms
Eyebrow-component.bb3cb3f916a8f984fa1c.js
74 ms
WeatherTile-component.d8855671dcba7efd2257.js
72 ms
Podcasts-component.f5680d63b1cb0cc53655.js
74 ms
ImageTile-component.aeb6fa3cc19b574f5fe1.js
72 ms
Card-component.1d445a58a8168579c2aa.js
72 ms
wham1180.iheart.com accessibility score
wham1180.iheart.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
wham1180.iheart.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wham1180.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 Wham1180.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.
wham1180.iheart.com
Open Graph data is detected on the main page of WHAM 1180 Iheart. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: