3.6 sec in total
167 ms
2.4 sec
1 sec
Click here to check amazing WFGR content for United States. Otherwise, check out these important facts you probably never knew about wfgr.com
98.7 WFGR Grand Rapids Classic Hits & Classic Rock Radio, a Townsquare Media station, plays the Classic Hits & Classic Rocks music in Grand Rapids, Michigan on WFGR-FM.
Visit wfgr.comWe analyzed Wfgr.com page load time and found that the first response time was 167 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
wfgr.com performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value5.7 s
17/100
25%
Value18.1 s
0/100
10%
Value30,100 ms
0/100
30%
Value0.078
95/100
15%
Value45.5 s
0/100
10%
167 ms
69 ms
96 ms
59 ms
58 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 9% of them (13 requests) were addressed to the original Wfgr.com, 37% (54 requests) were made to Wac.450f.edgecastcdn.net and 10% (15 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (756 ms) belongs to the original domain Wfgr.com.
Page size can be reduced by 998.5 kB (56%)
1.8 MB
793.2 kB
In fact, the total size of Wfgr.com main page is 1.8 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. Javascripts take 701.5 kB which makes up the majority of the site volume.
Potential reduce by 132.8 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 132.8 kB or 78% of the original size.
Potential reduce by 39.9 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. WFGR images are well optimized though.
Potential reduce by 470.8 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 470.8 kB or 67% of the original size.
Potential reduce by 354.9 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. Wfgr.com needs all CSS files to be minified and compressed as it can save up to 354.9 kB or 87% of the original size.
Number of requests can be reduced by 82 (60%)
136
54
The browser has sent 136 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WFGR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 56 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
wfgr.com
167 ms
style.css
69 ms
social-overlay.css
96 ms
style.css
59 ms
admin.css
58 ms
sp-gallery.css
60 ms
jquery.fancybox-1.3.3.css
97 ms
ts3.css
119 ms
facebook-auth.css
107 ms
radio-players.css
105 ms
jquery-1.7.2.min.js
108 ms
handlebars.min.js
108 ms
radio-players.js
107 ms
html5.js
115 ms
external-tracking.min.js
117 ms
amzn_ads.js
12 ms
tsmadhelper.js
170 ms
plugin.css
189 ms
datatables.css
222 ms
listen-live-bar.js
188 ms
audio-player.js
166 ms
local_experts.css
165 ms
geo-spam-prevention.js
166 ms
jquery.fancybox-1.3.3.pack.js
166 ms
loyalty.js
173 ms
jquery.cycle.min.js
173 ms
sp-gallery.js
173 ms
tsmclip.min.js
175 ms
jquery.easing-1.3.pack.js
174 ms
jquery.sonar.min.js
60 ms
sonar.load.js
179 ms
make_homepage.js
180 ms
internaladapi.js
181 ms
townsquaresponsors.js
178 ms
overlaylogo.js
181 ms
internaladapiajax.js
275 ms
facebook-auth.js
275 ms
RAvk1rfG.js
13 ms
loyalty_ftlink_link.js
281 ms
social-tracking.js
275 ms
auto-tagger.js
53 ms
more-button.js
270 ms
jquery.tsc-sliders.js
274 ms
jquery.template.js
272 ms
49 ms
wp-emoji-release.min.js
113 ms
request_song.js
238 ms
social-overlay.js
234 ms
dl-video.js
516 ms
now-playing.js
505 ms
rta.js
49 ms
bid
141 ms
beacon.js
94 ms
dc.js
99 ms
background.jpg
438 ms
all.js
306 ms
blank_1x1.png
373 ms
TSI_Promo.png
363 ms
kurt-300.jpg
351 ms
shocking-crimes.jpg
409 ms
guardians-300.jpg
354 ms
deadpool-300.jpg
347 ms
seizeDeal.jpg
346 ms
logo.png
175 ms
fbicon.png
153 ms
JoJoGirardonWFGR2.jpg
171 ms
JoJoGirardonWFGR2.jpg
148 ms
Steve-Labenz.jpg
344 ms
Love-pizza.jpg
343 ms
red.png
335 ms
wx_66.png
334 ms
wfgr.png
390 ms
1x1.gif
383 ms
295-dark.png
376 ms
366-dark.png
376 ms
442-dark.png
376 ms
443-dark.png
375 ms
622-dark.png
376 ms
header-trans-2.png
325 ms
search-icon.png
324 ms
social_sprite.png
322 ms
ryan-adams-300.jpg
325 ms
OpenSans-Semibold-webfont.woff
324 ms
default_control_sprite.png
352 ms
OpenSans-Bold-webfont.woff
343 ms
__utm.gif
178 ms
OpenSans-ExtraBold-webfont.woff
263 ms
modernpics-webfont.woff
189 ms
__utm.gif
173 ms
__utm.gif
172 ms
__utm.gif
174 ms
__utm.gif
174 ms
net.php
86 ms
pixel
125 ms
generic
115 ms
generic
75 ms
pixel
76 ms
160 ms
xrefid.xgi
94 ms
pixel.gif
9 ms
pixel.gif
7 ms
xd_arbiter.php
163 ms
xd_arbiter.php
372 ms
756 ms
xrefid.xgi
36 ms
gpt.js
70 ms
now-playing
66 ms
widgets.js
315 ms
60x60bb.jpg
106 ms
60x60bb.jpg
149 ms
60x60bb.jpg
96 ms
60x60bb.jpg
104 ms
60x60bb.jpg
106 ms
xd_arbiter.php
60 ms
GettyImages-513405792.jpg
160 ms
RS10524_480802190.jpg
158 ms
Cloudy-city.jpg
132 ms
collage1.jpg
158 ms
pubads_impl_82.js
25 ms
graph.facebook.com
222 ms
Casey-Kasem_hi.jpg
137 ms
GettyImages-516379184.jpg
137 ms
container.html
55 ms
like.php
77 ms
like.php
89 ms
like.php
109 ms
page.php
143 ms
ads
520 ms
qeKvIRsJabD.js
182 ms
LVx-xkvaJ0b.png
149 ms
qeKvIRsJabD.js
329 ms
bC7hIHbP4Mf.css
101 ms
gPLjjXw4kx2.css
104 ms
q68gy-v_YMF.js
135 ms
YvxwM8R7ol8.js
167 ms
ihptErjAmMX.js
156 ms
10615982_10152585228012052_52439856297771794_n.jpg
215 ms
ZS8q378OQsF.png
130 ms
wL6VQj7Ab77.png
127 ms
s7jcwEQH7Sx.png
128 ms
expansion_embed.js
83 ms
R9a_DtVRZgv.js
51 ms
cUDgRFxaoIk.js
53 ms
0JBr1QHp8Gi.js
51 ms
kDOzhTr2W91.js
51 ms
wfgr.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.
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
wfgr.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Page has valid source maps
wfgr.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wfgr.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 Wfgr.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.
wfgr.com
Open Graph data is detected on the main page of WFGR. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: