10.9 sec in total
189 ms
10.1 sec
664 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 189 ms and then it took 10.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
tunedin.com performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value16.5 s
0/100
25%
Value28.4 s
0/100
10%
Value7,660 ms
0/100
30%
Value0.551
13/100
15%
Value46.4 s
0/100
10%
189 ms
427 ms
190 ms
224 ms
217 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Tunedin.com, 73% (88 requests) were made to Lightning100.com and 7% (8 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Wrlt.tunegenie.com.
Page size can be reduced by 625.9 kB (18%)
3.5 MB
2.9 MB
In fact, the total size of Tunedin.com main page is 3.5 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 2.6 MB which makes up the majority of the site volume.
Potential reduce by 439.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 439.1 kB or 86% of the original size.
Potential reduce by 149.6 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 2.9 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 34.3 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 34.3 kB or 16% of the original size.
Number of requests can be reduced by 85 (78%)
109
24
The browser has sent 109 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 59 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
tunedin.com
189 ms
lightning100.com
427 ms
wp-emoji-release.min.js
190 ms
buttons.min.css
224 ms
dashicons.min.css
217 ms
mediaelementplayer-legacy.min.css
351 ms
wp-mediaelement.min.css
394 ms
media-views.min.css
346 ms
imgareaselect.css
390 ms
style.min.css
365 ms
login-form.min.css
361 ms
member.min.css
430 ms
members.min.css
431 ms
dynamic-members.min.css
430 ms
latest-activities.min.css
458 ms
friends.min.css
427 ms
buddypress.min.css
429 ms
cleantalk-public.min.css
665 ms
frontend.css
490 ms
pmpro-member-directory.css
485 ms
video-container.min.css
487 ms
style.css
482 ms
css
393 ms
style.css
484 ms
style-buddypress.css
762 ms
ytprefs.min.css
707 ms
td_legacy_main.css
713 ms
td_standard_pack_main.css
837 ms
utils.min.js
816 ms
jquery.min.js
813 ms
jquery-migrate.min.js
1171 ms
moxie.min.js
1185 ms
plupload.min.js
1225 ms
17.js
1226 ms
confirm.min.js
1182 ms
widget-members.min.js
1181 ms
jquery-query.min.js
1254 ms
jquery-cookie.min.js
1254 ms
js
441 ms
widget.js
634 ms
snapwidget.js
679 ms
widgets.js
1157 ms
css
394 ms
fullfooter.js
2017 ms
rs6.css
1143 ms
jquery-scroll-to.min.js
1144 ms
buddypress.min.js
1097 ms
apbct-public-bundle.min.js
1098 ms
ytprefs.min.js
997 ms
underscore.min.js
1289 ms
shortcode.min.js
969 ms
backbone.min.js
1263 ms
wp-util.min.js
1359 ms
wp-backbone.min.js
1421 ms
media-models.min.js
1381 ms
wp-plupload.min.js
1378 ms
core.min.js
1383 ms
mouse.min.js
1349 ms
sortable.min.js
1356 ms
mediaelement-and-player.min.js
1353 ms
mediaelement-migrate.min.js
1301 ms
wp-mediaelement.min.js
1318 ms
api-request.min.js
1300 ms
regenerator-runtime.min.js
1148 ms
wp-polyfill.min.js
1167 ms
dom-ready.min.js
1167 ms
hooks.min.js
1387 ms
i18n.min.js
1340 ms
a11y.min.js
1282 ms
clipboard.min.js
1288 ms
media-views.min.js
933 ms
media-editor.min.js
924 ms
media-audiovideo.min.js
925 ms
qppr_frontend_script.min.js
932 ms
rbtools.min.js
885 ms
rs6.min.js
928 ms
js_posts_autoload.min.js
878 ms
tagdiv_theme.min.js
926 ms
comment-reply.min.js
898 ms
73.js
896 ms
smush-lazy-load.min.js
898 ms
fitvids.min.js
903 ms
js_files_for_front.min.js
871 ms
fbevents.js
715 ms
dummy.png
609 ms
Lightning-100-Banner.png
594 ms
Lightning-100-ad-web-banner.jpg
585 ms
NASH_Lightning100_300x250_banner300x250-1.jpg
586 ms
LOTG2022-ad-300x250_2x-e1656008500533.png
506 ms
Great-Taste-In-Tees.gif
434 ms
319_DisplayAd_300x250_M.jpg
441 ms
TEDxNashville_Banner-Ad_300x250-e1659639901187.png
438 ms
300-%C3%97-250-px-2.jpg
440 ms
analytics.js
499 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
652 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
1513 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
1535 ms
newspaper.woff
424 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
1537 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
1535 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
1535 ms
536597059832236
500 ms
print.css
1025 ms
elements.png
605 ms
collect
237 ms
collect
432 ms
jquery-2.1.4.min.js
285 ms
ga-audiences
161 ms
1660931936.jpg
169 ms
1643130932.jpg
474 ms
1658330990.jpg
479 ms
1655481827.jpg
501 ms
1658940448.jpg
480 ms
1655304184.png
775 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
150 ms
pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf
151 ms
loader2.min.js
692 ms
ajax-handler.php
523 ms
widget_iframe.9d00f3a022654eb8edfbc3190e981f9d.html
286 ms
settings
230 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
Links do not have a discernible name
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
Page has valid source maps
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: