3.3 sec in total
150 ms
2.7 sec
506 ms
Visit tunedin.com now to see the best up-to-date Tunedin content and also check out these interesting facts you probably never knew about tunedin.com
Nashville's longest running independent radio station spotlighting community, local music, and emerging artists. Listen online or 100.1 FM!
Visit tunedin.comWe analyzed Tunedin.com page load time and found that the first response time was 150 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
tunedin.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value14.8 s
0/100
25%
Value16.0 s
0/100
10%
Value7,230 ms
0/100
30%
Value0.194
63/100
15%
Value40.9 s
0/100
10%
150 ms
290 ms
173 ms
22 ms
27 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Tunedin.com, 59% (58 requests) were made to Lightning100.com and 8% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (641 ms) relates to the external source B3.tunegenie.com.
Page size can be reduced by 497.6 kB (19%)
2.6 MB
2.1 MB
In fact, the total size of Tunedin.com main page is 2.6 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. Only a small number of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 395.6 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 395.6 kB or 87% of the original size.
Potential reduce by 32.0 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. Tunedin images are well optimized though.
Potential reduce by 36.6 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. This website has mostly compressed JavaScripts.
Potential reduce by 33.4 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. Tunedin.com needs all CSS files to be minified and compressed as it can save up to 33.4 kB or 15% of the original size.
Number of requests can be reduced by 52 (59%)
88
36
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tunedin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
tunedin.com
150 ms
lightning100.com
290 ms
style.min.css
173 ms
extendify-utilities.css
22 ms
cleantalk-public.min.css
27 ms
frontend.css
26 ms
pmpro-member-directory.css
43 ms
video-container.min.css
34 ms
Rich-Web-Video-Slider-Widget.css
48 ms
richwebicons.css
39 ms
style.css
21 ms
css
43 ms
style.css
28 ms
ytprefs.min.css
25 ms
td_legacy_main.css
46 ms
td_standard_pack_main.css
55 ms
tdb_main.css
42 ms
jquery.min.js
82 ms
jquery-migrate.min.js
83 ms
17.js
88 ms
apbct-public-bundle.min.js
96 ms
core.min.js
88 ms
Rich-Web-Video-Slider-Widget.js
88 ms
js
91 ms
ytprefs.min.js
99 ms
sdk.js
90 ms
js
79 ms
widget.js
286 ms
snapwidget.js
38 ms
rs6.css
18 ms
qppr_frontend_script.min.js
13 ms
rbtools.min.js
17 ms
rs6.min.js
34 ms
underscore.min.js
23 ms
js_posts_autoload.min.js
38 ms
tagdiv_theme.min.js
38 ms
comment-reply.min.js
37 ms
73.js
41 ms
smush-lazy-load.min.js
206 ms
fitvids.min.js
46 ms
js_files_for_front.min.js
52 ms
fullfooter.js
491 ms
fbevents.js
191 ms
CIOT_300X250-1-1.gif
260 ms
L100300-x-250-px.png
135 ms
GSOB_WRLT_300x250-1.jpg
134 ms
L100_MC_300x250_Banner.jpg
134 ms
Great-Taste-In-Tees.gif
261 ms
Lightning-100-ad-web-banner.jpg
131 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
205 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
283 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
314 ms
elements.png
241 ms
js
219 ms
analytics.js
287 ms
newspaper.woff
287 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
157 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
285 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
284 ms
jquery-2.1.4.min.js
240 ms
print.css
84 ms
collect
80 ms
1705845313.jpg
348 ms
collect
326 ms
1713565758.jpg
314 ms
1693331293.jpg
328 ms
1705579677.jpg
326 ms
1713212246.jpg
325 ms
1712725155.png
415 ms
Lightning-100-Nashville-Independent-Radio-homepage-1-800x196.png
172 ms
loader2.min.js
641 ms
player_api
179 ms
NMM-513-Wide-356x220.png
252 ms
NMM-56-Wide-356x220.png
252 ms
NMM-429-Wide-80x60.png
174 ms
MaryBragg_TieMeToYou_COVER-scaled-1-80x60.jpeg
133 ms
Now-Playing.jpg
530 ms
smush-lazyloader-4.gif
63 ms
ga-audiences
81 ms
www-widgetapi.js
4 ms
mHy6U4e_MWg
79 ms
Screenshot-2024-04-23-at-2.03.04%E2%80%AFPM-80x60.png
351 ms
422805635_7089839964430877_4845997687967851792_n-80x60.jpg
352 ms
multiultra-80x60.webp
351 ms
AutumnNicholas-15-80x60.jpg
353 ms
Mat-Kearney-80x60.png
518 ms
HCLogoWebsite-80x60.png
353 ms
www-player.css
6 ms
www-embed-player.js
35 ms
base.js
66 ms
ad_status.js
294 ms
LvMrC3vzHFP8SzxjvqNWRksbkOPiJTf11ILX4Pq8Ybc.js
120 ms
embed.js
42 ms
id
30 ms
Screenshot-2024-04-18-at-5.31.52%E2%80%AFPM-80x60.png
232 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
20 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
21 ms
Screenshot-2024-04-18-at-3.38.15%E2%80%AFPM-80x60.png
223 ms
Create
311 ms
tunedin.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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
tunedin.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
tunedin.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
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 Tunedin.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 Tunedin.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.
tunedin.com
Open Graph data is detected on the main page of Tunedin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: