2.3 sec in total
135 ms
1.6 sec
549 ms
Click here to check amazing Thunder Tampa Bay content for United States. Otherwise, check out these important facts you probably never knew about thundertampabay.com
Tampa Bay's Impact Radio
Visit thundertampabay.comWe analyzed Thundertampabay.com page load time and found that the first response time was 135 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
thundertampabay.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value4.5 s
37/100
25%
Value11.9 s
4/100
10%
Value5,000 ms
0/100
30%
Value0.094
91/100
15%
Value21.7 s
1/100
10%
135 ms
104 ms
24 ms
42 ms
49 ms
Our browser made a total of 157 requests to load all elements on the main page. We found that 4% of them (7 requests) were addressed to the original Thundertampabay.com, 19% (30 requests) were made to Flint-img.ccrd.clearchannel.com and 18% (28 requests) were made to Content.clearchannel.com. The less responsive or slowest element that took the longest time to load (613 ms) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 1.5 MB (53%)
2.8 MB
1.3 MB
In fact, the total size of Thundertampabay.com main page is 2.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. 80% 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. Javascripts take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 89.9 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. This page needs HTML code to be minified as it can gain 18.8 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 89.9 kB or 80% of the original size.
Potential reduce by 50.5 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. Thunder Tampa Bay images are well optimized though.
Potential reduce by 1.1 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.1 MB or 71% of the original size.
Potential reduce by 237.6 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. Thundertampabay.com needs all CSS files to be minified and compressed as it can save up to 237.6 kB or 81% of the original size.
Number of requests can be reduced by 96 (62%)
154
58
The browser has sent 154 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thunder Tampa Bay. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 74 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
thundertampabay.com
135 ms
www.thundertampabay.com
104 ms
core.css
24 ms
app.css
42 ms
ihearticons.css
49 ms
station_styles.css
144 ms
custom.modernizr.js
46 ms
jquery.js
55 ms
jquery.cookie.js
46 ms
sdk.min.js
74 ms
ads.min.js
45 ms
plusone.js
96 ms
slider.min.js
42 ms
timeline.min.js
44 ms
LAB.min.js
44 ms
main.min.js
44 ms
foundation.js
44 ms
foundation.orbit.js
47 ms
foundation.forms.js
47 ms
foundation.section.js
47 ms
foundation.reveal.js
47 ms
init.js
46 ms
challenge
47 ms
gpt.js
138 ms
analytics.js
136 ms
cb=gapi.loaded_0
130 ms
thumbNew.php
155 ms
widgets.js
136 ms
cb=gapi.loaded_1
123 ms
fastbutton
141 ms
search_btn_icon_black.png
114 ms
default
114 ms
0.jpg
107 ms
spark-mobile-play-button-sprite-v2.png
72 ms
spark-mobile-iheartradio-logo.png
71 ms
localinfo_weather_icons.png
72 ms
localinfo_traffic_icon.png
73 ms
module-title-corner.png
73 ms
0.jpg
74 ms
thunder_spark_logo_0_1415611505.png
101 ms
thumbCrop.php
75 ms
thumbCrop.php
94 ms
thumbCrop.php
93 ms
thumbNew.php
91 ms
thumbCrop.php
89 ms
thumbCrop.php
90 ms
thumbCrop.php
171 ms
thumbCrop.php
170 ms
thumbCrop.php
94 ms
thumbCrop.php
94 ms
thumbCrop.php
172 ms
thumbCrop.php
95 ms
thumbCrop.php
95 ms
thumbCrop.php
96 ms
thumbCrop.php
172 ms
thumbCrop.php
96 ms
thumbCrop.php
166 ms
thumbCrop.php
184 ms
thumbCrop.php
185 ms
thumbCrop.php
186 ms
thumbCrop.php
187 ms
thumbCrop.php
185 ms
thumbCrop.php
186 ms
thumbCrop.php
283 ms
like.php
306 ms
p2
101 ms
cb=gapi.loaded_0
105 ms
cb=gapi.loaded_1
116 ms
pubads_impl_82.js
90 ms
postmessageRelay
119 ms
embed.html
257 ms
ti.js
56 ms
ads
197 ms
container.html
32 ms
3193398744-postmessagerelay.js
173 ms
rpc:shindig_random.js
111 ms
e2eDetect.js
23 ms
s_code.js
168 ms
HTMLPoll.js
22 ms
234 ms
siteconfig.js
199 ms
recaptcha.js
16 ms
p
158 ms
bOa0NM1Her35hWadbi-bnq.js
151 ms
PollsController.js
144 ms
g6qlE9hbcrtCq0agucy03kPIdFYel5UicYHotHMXHKo.js
73 ms
timeline_more.html
593 ms
module-title-corner.png
41 ms
cc.js
128 ms
widget.now-playing.min.js
124 ms
widget.shoutout.min.js
123 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
206 ms
dynamic-lead-nav-sprite-black.png
15 ms
qeKvIRsJabD.js
563 ms
LVx-xkvaJ0b.png
613 ms
refresh.png
57 ms
audio.png
70 ms
text.png
70 ms
help.png
70 ms
logo.png
70 ms
cb=gapi.loaded_0
66 ms
DARTfooterNewSplit.js
69 ms
DFPheader.js
112 ms
json2.js
134 ms
jquery.min.js
133 ms
jquery.cookie.js
154 ms
HTMLPlayer.js
168 ms
FlashPlayer.js
153 ms
EmbedPlayer.js
152 ms
SharePanelManager.js
152 ms
LayoutManager.js
164 ms
MediaManager.js
185 ms
PreRollManager.js
171 ms
GlobalDataObj.js
170 ms
TrackingObject.js
170 ms
WidgetModeView.js
191 ms
ima3.js
78 ms
ads
88 ms
quickio.js
104 ms
v2
86 ms
widget.shoutout.css
28 ms
bridge.min.js
26 ms
reload
42 ms
ads
36 ms
dpx
24 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
39 ms
image
40 ms
s_code-secure.js
75 ms
ads
71 ms
ca.png
182 ms
s96365327823441
42 ms
xrefid.xgi
38 ms
beacon.js
83 ms
swfobject.js
56 ms
605193
54 ms
13720740562438935642
77 ms
moatad.js
212 ms
ads
72 ms
osd.js
34 ms
364 ms
16883516079599230537
16 ms
ads
35 ms
jot
98 ms
nr-885.min.js
51 ms
chartbeat.js
53 ms
rt=ifr
15 ms
tpc=na_id
20 ms
g.json
63 ms
5907
50 ms
pixel
26 ms
4 ms
25 ms
25b61230c4
45 ms
ping
17 ms
362738.gif
16 ms
619375
9 ms
664007
14 ms
thundertampabay.com accessibility score
thundertampabay.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
thundertampabay.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
ES
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thundertampabay.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it does not match the claimed English language. Our system also found out that Thundertampabay.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.
thundertampabay.com
Open Graph data is detected on the main page of Thunder Tampa Bay. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: