1.8 sec in total
446 ms
1.1 sec
250 ms
Click here to check amazing Wrnr Tune Genie content for United States. Otherwise, check out these important facts you probably never knew about wrnr.tunegenie.com
The latest Playlists for 103.1 WRNR
Visit wrnr.tunegenie.comWe analyzed Wrnr.tunegenie.com page load time and found that the first response time was 446 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
wrnr.tunegenie.com performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value4.3 s
40/100
25%
Value6.8 s
34/100
10%
Value4,200 ms
1/100
30%
Value0.296
40/100
15%
Value18.8 s
3/100
10%
446 ms
28 ms
30 ms
33 ms
33 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 31% of them (20 requests) were addressed to the original Wrnr.tunegenie.com, 22% (14 requests) were made to D1m4chtmmj9qtf.cloudfront.net and 6% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (446 ms) belongs to the original domain Wrnr.tunegenie.com.
Page size can be reduced by 881.4 kB (74%)
1.2 MB
303.1 kB
In fact, the total size of Wrnr.tunegenie.com main page is 1.2 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. 60% of websites need less resources to load. Javascripts take 644.9 kB which makes up the majority of the site volume.
Potential reduce by 151.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. This page needs HTML code to be minified as it can gain 18.5 kB, which is 11% 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 151.8 kB or 92% of the original size.
Potential reduce by 958 B
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. Wrnr Tune Genie images are well optimized though.
Potential reduce by 436.0 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 436.0 kB or 68% of the original size.
Potential reduce by 292.7 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. Wrnr.tunegenie.com needs all CSS files to be minified and compressed as it can save up to 292.7 kB or 83% of the original size.
Number of requests can be reduced by 29 (49%)
59
30
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wrnr Tune Genie. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
wrnr.tunegenie.com
446 ms
font-awesome.min.css
28 ms
picker.default.css
30 ms
picker.default.date.css
33 ms
tooltipster.css
33 ms
app.css
35 ms
custom.modernizr.js
32 ms
google_service.js
44 ms
jquery.min.js
28 ms
sdk.js
101 ms
jquery.easing.min.js
24 ms
css
26 ms
ga.js
13 ms
google_ads.js
52 ms
ggcmb400.js
134 ms
log4javascript.min.js
25 ms
picker.js
25 ms
picker.date.js
25 ms
picker.legacy.js
24 ms
pushstream.js
29 ms
lib_all.js
33 ms
m2g_all.js
31 ms
appconfig.js
149 ms
quant.js
41 ms
bg-head-grad.png
72 ms
index_header2_01.png
338 ms
tg-logo.png
14 ms
tg_loading.gif
14 ms
-_Ctzj9b56b8RgXW8FAriS3USBnSvpkopQaUR-2r7iU.ttf
75 ms
CcKI4k9un7TZVWzRVT-T8y3USBnSvpkopQaUR-2r7iU.ttf
74 ms
ads
43 ms
fontawesome-webfont.woff
40 ms
pixel;r=892333984;a.1=p-5fwnyx84aph8E;labels.1=new_rock;fpan=1;fpa=P0-292890252-1456814327222;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456814327222;tzo=-180;ref=;url=http%3A%2F%2Fwrnr.tunegenie.com%2F;ogl=site_name.103%252E1%20WRNR
114 ms
slotbase.html
83 ms
slotvideos.html
152 ms
localshows.html
149 ms
localshowstease.html
154 ms
recommendedshows.html
155 ms
singlevideo.html
156 ms
me_nav.html
182 ms
me_nav_playlists.html
221 ms
ytplaylist.html
222 ms
savetoplaylists.html
236 ms
saveform.html
236 ms
hourslinks.html
237 ms
hourscontainers.html
283 ms
playliststip.html
294 ms
playliststip_anon.html
293 ms
preroll_ad_raw.html
303 ms
preroll_ad_vast.html
305 ms
preroll_ad_google.html
315 ms
iframe_api
26 ms
120 ms
xd_arbiter.php
65 ms
xd_arbiter.php
140 ms
www-widgetapi.js
23 ms
65 ms
xd_arbiter.php
39 ms
www-embed-player-vflQrT_sR.css
38 ms
www-embed-player.js
51 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
48 ms
ad_status.js
53 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
45 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
52 ms
update.js
25 ms
wrnr.tunegenie.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
Links do not have a discernible name
wrnr.tunegenie.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
wrnr.tunegenie.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 Wrnr.tunegenie.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 Wrnr.tunegenie.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.
wrnr.tunegenie.com
Open Graph description is not detected on the main page of Wrnr Tune Genie. 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: