4 sec in total
86 ms
3.3 sec
555 ms
Visit wjr.com now to see the best up-to-date WJR content for United States and also check out these interesting facts you probably never knew about wjr.com
Detroit's News Talk 760
Visit wjr.comWe analyzed Wjr.com page load time and found that the first response time was 86 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
wjr.com performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value10.5 s
0/100
25%
Value46.3 s
0/100
10%
Value24,430 ms
0/100
30%
Value1.394
0/100
15%
Value90.4 s
0/100
10%
86 ms
183 ms
13 ms
14 ms
50 ms
Our browser made a total of 192 requests to load all elements on the main page. We found that 22% of them (43 requests) were addressed to the original Wjr.com, 7% (14 requests) were made to Static.xx.fbcdn.net and 6% (11 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (992 ms) relates to the external source Cdn-scorestream-com.s3.amazonaws.com.
Page size can be reduced by 2.7 MB (32%)
8.4 MB
5.8 MB
In fact, the total size of Wjr.com main page is 8.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. 85% 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 5.1 MB which makes up the majority of the site volume.
Potential reduce by 127.1 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 127.1 kB or 77% of the original size.
Potential reduce by 309.4 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. WJR images are well optimized though.
Potential reduce by 1.5 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 1.5 MB or 65% of the original size.
Potential reduce by 701.0 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. Wjr.com needs all CSS files to be minified and compressed as it can save up to 701.0 kB or 88% of the original size.
Number of requests can be reduced by 113 (61%)
184
71
The browser has sent 184 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WJR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 64 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
wjr.com
86 ms
www.wjr.com
183 ms
twemoji.js
13 ms
wp-emoji.js
14 ms
css
50 ms
1456522698.112.cf1b7ac96a19fa98bda1c69ecae30ff8.css
17 ms
general-ec68467.css
39 ms
layout-front_page-d78cf11.css
42 ms
responsive-grid-d2119e4.css
38 ms
style.css
42 ms
1456522698.112.ca4538396035ac922864e839ff6ac3a9.js
43 ms
jquery-migrate.js
43 ms
jquery.hoverintent.js
44 ms
jquery.superfish.js
44 ms
selectnav.js
44 ms
block-dynamic-js-layout-front_page-3f428ce.js
42 ms
jquery.fitvids.js
44 ms
responsive-grid-js-e6e6939.js
44 ms
launch.js
44 ms
prettyPhoto.css
43 ms
widget.css
46 ms
widget.css
42 ms
themify-mediaelement.min.js
42 ms
themify-mediaelement.js
41 ms
jquery.prettyPhoto.js
42 ms
widget-front-end.js
42 ms
widget-front-end.js
42 ms
font-awesome.css
34 ms
app.css
12 ms
gpt.js
42 ms
gtm.js
44 ms
analytics.js
42 ms
facebook1.png
40 ms
usmedium.jpg
109 ms
19671360-large.jpg
114 ms
275353219001_4779606048001_4435a540-96fc-46b3-9f95-a115a3f4c0ea-still.jpg
408 ms
widgets.js
25 ms
Pod-PaulWSmith.png
221 ms
jquery-1.9.1.min.js
24 ms
vert
553 ms
loader.min.js
223 ms
-20d37873b64c6ddb.jpg
187 ms
tyler-oconnor-mugjpg-be70044932522d85.jpg
87 ms
juan-uribe-f5ad60a909ea73f4.jpg
206 ms
kawhi-leonarddwight-howardcorey-brewertrevor-ariza-89fb0764da286c91.jpg
201 ms
19844723-large.jpg
86 ms
19645242-standardjpg-bbb10ac729a08c1f.jpg
185 ms
Pod-FrankBeckmann.png
185 ms
Pod-MitchAlbom.png
185 ms
twitter1.png
72 ms
WJR-BG-03.png
82 ms
site-logo-061.png
8 ms
listen-live.png
7 ms
cumulus-vip-red.png
71 ms
search_small.png
72 ms
bed-and-bread-logo-radiothon.png
73 ms
Politics-Page2.png
74 ms
MSU-SPARTANS-BBALL-PROMO-REEL.png
77 ms
flint-water-crisis-Promo-Reel-Size.png
78 ms
Treetops.jpg
79 ms
BlackHistory-Promoreel.jpg
75 ms
LaFontaine-Homepage-2.png
74 ms
pubads_impl_81.js
68 ms
collect
36 ms
linkid.js
102 ms
gtm.js
99 ms
container.html
21 ms
ads
218 ms
collect
35 ms
collect
200 ms
tgmp.min.js
23 ms
collect
144 ms
collect
264 ms
tgmp.css
198 ms
jquery.min.js
177 ms
nunjucks-slim.min.js
161 ms
video.js
161 ms
ggcmb400.js
258 ms
ima3.js
210 ms
tgstandalone-debug.min.js
257 ms
appconfig.js
439 ms
cumulus.min.js
255 ms
sdk.js
553 ms
_Incapsula_Resource
133 ms
compiled-allsites-min.js
345 ms
stat.aspx
453 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
154 ms
widgets-20151019.css
52 ms
current
432 ms
bx_loader.gif
21 ms
general-ec68467.css
20 ms
controls.png
20 ms
_Incapsula_Resource
52 ms
css
91 ms
font-awesome.min.css
98 ms
video-js.css
86 ms
12683195783626949566
226 ms
osd.js
66 ms
loader.js
171 ms
5988268894934732215
258 ms
8825202700322027770
329 ms
imgad
327 ms
imgad
318 ms
css
291 ms
css
307 ms
css
307 ms
font-awesome.min.css
196 ms
sweet-alert.min.css
588 ms
vert.css
589 ms
vertBundle.js
992 ms
syndication
293 ms
562298509647695873
293 ms
__utm.gif
103 ms
all-v1.js
204 ms
addthis_widget.js
97 ms
container
147 ms
250 ms
glcfg400.js
104 ms
wjr-logo.png
116 ms
fontawesome-webfont.woff
91 ms
icomoon.woff
88 ms
show_companion_ad.js
77 ms
container.html
76 ms
pldpr400.js
150 ms
ls.html
154 ms
01-xl.png
111 ms
640x480.jpg
307 ms
all-v2.js
104 ms
icon-get-widget-blue.png
39 ms
01-l.png
45 ms
640x480.jpg
302 ms
185 ms
collect
16 ms
xd_arbiter.php
243 ms
xd_arbiter.php
461 ms
cfg
208 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
2 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
4 ms
sUhjeM1w_normal.jpeg
149 ms
CcZaZDNWEAIkVGy.jpg:small
174 ms
CcZXSJhWAAAVxZj.jpg:small
210 ms
CcZLk1RXEAA-Kpx.jpg:small
240 ms
CcYsnL-WwAAki9h.jpg:small
243 ms
CcYrVlKW4AAa9cE.jpg:small
256 ms
CcYcdSoW4AAP-gW.jpg:small
267 ms
CcYYlggUMAAiFrF.jpg:small
265 ms
CcYU-z0UYAAqERR.jpg:small
271 ms
CcYPr-XWwAAJBk8.jpg:small
270 ms
CcYCggtUAAAidgv.jpg:small
273 ms
iframe
225 ms
23842
501 ms
sync
103 ms
generic
75 ms
jot
67 ms
generic
7 ms
um
381 ms
um
384 ms
um
377 ms
um
376 ms
um
359 ms
um
357 ms
analytics.js
81 ms
horz_w226_v2.png
125 ms
api
282 ms
bothPlatformsNavBarDark.png
96 ms
pixel.gif
24 ms
track
167 ms
fontawesome-webfont.woff
12 ms
track
172 ms
track
175 ms
collect
12 ms
collect
15 ms
300lo.json
18 ms
sh.7c7179124ea24ac6ba46caac.html
20 ms
page.php
110 ms
sz6MDy9l38p.css
286 ms
6hwGqLa-LSZ.css
354 ms
_rx8naC75Dy.js
557 ms
t-KLv3gqZy0.js
489 ms
uLtKx7ldlvR.js
624 ms
wyIfBc7KBcg.js
621 ms
eJ-OD1MiSJg.js
490 ms
hockey-128x128Dark.png
200 ms
10547591_10152766725920312_2258687245727946462_n.jpg
68 ms
1560762_10152373897330312_1065058531_n.jpg
71 ms
wL6VQj7Ab77.png
78 ms
CSXXCvknpgK.png
79 ms
b53Ajb4ihCP.gif
69 ms
R9a_DtVRZgv.js
70 ms
cUDgRFxaoIk.js
71 ms
0JBr1QHp8Gi.js
71 ms
kDOzhTr2W91.js
71 ms
wjr.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
wjr.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
wjr.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wjr.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 Wjr.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.
wjr.com
Open Graph description is not detected on the main page of WJR. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: