2.1 sec in total
548 ms
1.5 sec
108 ms
Welcome to whjjam.com homepage info - get ready to check Whjjam best content right away, or after learning these important things about whjjam.com
Don't miss out on the latest from News Radio 920 AM & 104.7 FM, Providence's News, Traffic & Weather
Visit whjjam.comWe analyzed Whjjam.com page load time and found that the first response time was 548 ms and then it took 1.6 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.
whjjam.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value4.6 s
34/100
25%
Value42.5 s
0/100
10%
Value79,170 ms
0/100
30%
Value0.005
100/100
15%
Value104.1 s
0/100
10%
548 ms
488 ms
484 ms
487 ms
459 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Whjjam.com, 8% (4 requests) were made to I.iheart.com and 2% (1 request) were made to Newsradiori.iheart.com. The less responsive or slowest element that took the longest time to load (833 ms) relates to the external source Z.moatads.com.
Page size can be reduced by 1.6 MB (79%)
2.0 MB
426.9 kB
In fact, the total size of Whjjam.com main page is 2.0 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. 50% of websites need less resources to load. HTML takes 1.6 MB which makes up the majority of the site volume.
Potential reduce by 1.4 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.4 MB or 85% of the original size.
Potential reduce by 393 B
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. Whjjam images are well optimized though.
Potential reduce by 177.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 177.1 kB or 66% of the original size.
Potential reduce by 3.1 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. Whjjam.com needs all CSS files to be minified and compressed as it can save up to 3.1 kB or 11% of the original size.
Number of requests can be reduced by 44 (88%)
50
6
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whjjam. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
newsradiori.iheart.com
548 ms
bundle.b4784393326cfefc06fa.css
488 ms
sites-local.f4601bc8219098567a86.css
484 ms
core-components-tiles-OnairTileLoader-component.d9b89684bedbb0c4b00f.css
487 ms
core-page-blocks-datasource-DatasourceLoader-component.d0d7c906ff67d191c4e4.css
459 ms
Datasource-component.21b2d627bf3f26b77cdb.css
425 ms
Grid-component.9e05f3f8fa0e6b993347.css
434 ms
components-tiles-ContentTile-component.a5e9ee6f3bc07a62d945.css
462 ms
TrafficTile-component.7ce458744ec9f4e49d10.css
465 ms
Heading-component.d79a5c95e6ef67a97bca.css
463 ms
LoadMoreFromCursor-component.4a7a0f66bc2d890b3034.css
463 ms
Show-component.608ec1ff0656c8b676a1.css
463 ms
FauxButton-component.1f25bb623660eb4f88c1.css
462 ms
AptivadaKeywordContest-component.ff94331856c0bb091379.css
485 ms
Podcasts-component.f6328fb51c2f2829facf.css
482 ms
ImageTile-component.c2cbd469fbc0bd11cbdf.css
483 ms
Card-component.c66d212af09897afcdd6.css
483 ms
WeatherTile-component.ca557d80a0c5075ed0c1.css
483 ms
moatheader.js
833 ms
5a7a0470fcfa19529647f384
459 ms
f79fc341-a979-4863-81b0-eea1ddc6e07b
275 ms
f79fc341-a979-4863-81b0-eea1ddc6e07b
491 ms
627ed0263f19c6325b37ec16
536 ms
runtime.6b4924f16f0540cb95f3.js
182 ms
vendor.710290aee3274352d59a.js
399 ms
bundle.493e54a605c4909893ed.js
460 ms
src_app_core_chrome_AppTray_component_tsx-src_app_core_chrome_Footer_component_tsx-src_app_co-d67451.a19849dbbcd5f0a50bfc.js
432 ms
sites-local.37d46712c4175db4e3c9.js
398 ms
MagicLink-component.d8ebec3fff267f1ceb57.js
398 ms
core-components-tiles-OnairTileLoader-component.3660133e9ae8cc8c3dbd.js
398 ms
core-page-blocks-datasource-DatasourceLoader-component.c4fb328c3b6211b7ca76.js
445 ms
Datasource-component.1c017bbd80cc11bfd075.js
444 ms
Grid-component.d1391a391db391ba3293.js
443 ms
ContentFeedItem-component.18a0bca380789d53b358.js
442 ms
components-tiles-ContentTile-component.c15ed61ef8b431c7c7ce.js
449 ms
LeadFeedItem-component.7349c61d3b98434fc28f.js
443 ms
core-components-tiles-WeatherTileLoader-component.f557adc4bb831fc87d0d.js
449 ms
TrafficTile-component.3c995ef5999160daa0e7.js
447 ms
Heading-component.28a08a32215f3defa880.js
443 ms
LoadMoreFromCursor-component.a8dbeb4c1b1e9069f823.js
448 ms
core-page-blocks-podcast-PodcastsLoader-component.e465f719fda6f62933b2.js
447 ms
ShowCollection-component.1b6eeb0052640df16d06.js
451 ms
Show-component.89404286ecfc5ad39b2b.js
336 ms
core-page-blocks-contest-KeywordContestLoader-component.5435e7b603530e153d88.js
336 ms
DateTimeDisplay-component.9a93eb94463384ae2d8e.js
329 ms
FauxButton-component.7c8a6b13cd1c228006f2.js
329 ms
AptivadaKeywordContest-component.d68029097edc45b79723.js
388 ms
Podcasts-component.f5680d63b1cb0cc53655.js
377 ms
ImageTile-component.aeb6fa3cc19b574f5fe1.js
359 ms
Card-component.1d445a58a8168579c2aa.js
372 ms
WeatherTile-component.d8855671dcba7efd2257.js
371 ms
whjjam.com accessibility score
whjjam.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
Missing source maps for large first-party JavaScript
whjjam.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 Whjjam.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 Whjjam.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.
whjjam.com
Open Graph data is detected on the main page of Whjjam. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: