6.2 sec in total
1.7 sec
4 sec
473 ms
Click here to check amazing WERS content for United States. Otherwise, check out these important facts you probably never knew about wers.org
We are Boston's UnCommon Radio, bringing local, alternative, indie, and iconic music to Boston music lovers. Listener supported, student run.
Visit wers.orgWe analyzed Wers.org page load time and found that the first response time was 1.7 sec and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
wers.org performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value18.3 s
0/100
25%
Value19.8 s
0/100
10%
Value5,040 ms
0/100
30%
Value0.306
38/100
15%
Value35.2 s
0/100
10%
1690 ms
27 ms
46 ms
51 ms
92 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 27% of them (41 requests) were addressed to the original Wers.org, 29% (45 requests) were made to Wers.tunegenie.com and 5% (7 requests) were made to Press.emerson.edu. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Wers.org.
Page size can be reduced by 752.5 kB (45%)
1.7 MB
927.8 kB
In fact, the total size of Wers.org main page is 1.7 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 770.8 kB which makes up the majority of the site volume.
Potential reduce by 35.4 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 5.0 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 35.4 kB or 80% of the original size.
Potential reduce by 41.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. WERS images are well optimized though.
Potential reduce by 523.4 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 523.4 kB or 68% of the original size.
Potential reduce by 152.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. Wers.org needs all CSS files to be minified and compressed as it can save up to 152.7 kB or 83% of the original size.
Number of requests can be reduced by 58 (40%)
146
88
The browser has sent 146 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WERS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
wers.org
1690 ms
style.css
27 ms
tribe-events-full.css
46 ms
tribe-events-theme.css
51 ms
jquery.js
92 ms
jquery-migrate.min.js
52 ms
jquery.cycle.all.min.js
57 ms
slides.min.jquery.js
52 ms
jquery.tools.min.js
5 ms
plusone.js
57 ms
flowplayer-3.2.6.min.js
55 ms
superfish-1.4.8.js
53 ms
blue.css
53 ms
wp-emoji-release.min.js
47 ms
analytics.js
22 ms
collect
58 ms
cb=gapi.loaded_0
59 ms
loader.js
80 ms
ico_div.png
15 ms
bgr_top_nav.png
15 ms
btn_white_big.png
16 ms
bgr_search_box.png
16 ms
bgr_menu.png
15 ms
bgr_menu_div.png
27 ms
DSC_0073-642x406.jpg
166 ms
bgr_caption.png
27 ms
twin-peaks-wers-650x400-642x399.jpg
363 ms
DSC_0080-642x406.jpg
413 ms
basia-650x400-642x400.jpg
528 ms
bgr_slider_arrows.png
38 ms
DSC_0073-60x57.jpg
649 ms
twin-peaks-wers-650x400-60x57.jpg
649 ms
DSC_0080-60x57.jpg
720 ms
wers-bg.jpg
200 ms
homepage_logo_Discover1.png
466 ms
basia-650x400-60x57.jpg
1213 ms
Inline_Rectangle.jpg
1465 ms
VuHaus_WG_1920x1080-300x194.jpg
1461 ms
DSC_0223-128x83.jpg
1489 ms
Screen-Shot-2016-02-24-at-2.25.47-PM-copy-128x83.png
1541 ms
424 ms
Club-Nouveau-128x83.png
1429 ms
bgr_bottom.png
898 ms
ico_twitter.png
911 ms
ico_facebook.png
926 ms
ico_rss.png
939 ms
bgr_footer.png
952 ms
0205_Coldplay_300.gif
429 ms
0129_ModestMouse_BrandNew_300.gif
487 ms
0205_IggyPop_3001.gif
524 ms
0116_Florence_300.gif
745 ms
0205_CHVRCHES_300.gif
745 ms
ga.js
89 ms
loader
170 ms
ico_sub.png
708 ms
__utm.gif
11 ms
font-awesome.min.css
6 ms
plugins.css
17 ms
custom.modernizr.js
12 ms
log4javascript.min.js
25 ms
jquery.min.js
32 ms
all.js
270 ms
jquery.easing.min.js
11 ms
jquery.slimscroll.min.js
6 ms
pushstream.js
13 ms
jsrender.js
12 ms
m2g_widgets.js
9 ms
widget_plugins.js
11 ms
css
25 ms
tg_loading.gif
22 ms
-_Ctzj9b56b8RgXW8FAriS3USBnSvpkopQaUR-2r7iU.ttf
31 ms
CcKI4k9un7TZVWzRVT-T8y3USBnSvpkopQaUR-2r7iU.ttf
40 ms
fontawesome-webfont.woff
9 ms
112 ms
slotbase.html
80 ms
xd_arbiter.php
215 ms
xd_arbiter.php
451 ms
184 ms
163 ms
xd_arbiter.php
243 ms
google_service.js
160 ms
119 ms
120 ms
198 ms
194 ms
205 ms
202 ms
203 ms
206 ms
282 ms
282 ms
282 ms
282 ms
293 ms
297 ms
358 ms
361 ms
358 ms
361 ms
378 ms
388 ms
450 ms
448 ms
450 ms
448 ms
467 ms
514 ms
530 ms
531 ms
533 ms
533 ms
553 ms
567 ms
602 ms
604 ms
605 ms
594 ms
google_ads.js
91 ms
543 ms
562 ms
ads
43 ms
506 ms
500 ms
jstag
10 ms
osd.js
59 ms
acj
163 ms
tribe-events-full-mobile.css
20 ms
tribe-events-theme-mobile.css
16 ms
pd
61 ms
aceUAC.js
8 ms
rr
6 ms
ri
48 ms
dref=http%253A%252F%252Fwers.tunegenie.com%252Fplugins%252Fonair%252F%253Fcolorscheme%253Dlight
38 ms
253 ms
dref=http%253A%252F%252Fwers.tunegenie.com%252Fplugins%252Fonair%252F%253Fcolorscheme%253Dlight
16 ms
83a3e14b-215a-d7fc-1b98-a2a5159c309b
67 ms
openx
58 ms
pixel
62 ms
CSG_TWW_MKT_20080513_01%20_photo_300x250.jpg
7 ms
moatad.js
7 ms
n.js
28 ms
openx
15 ms
sd
29 ms
like.php
77 ms
sd
45 ms
sd
47 ms
sd
31 ms
sd
27 ms
fy8tT2klpgR.js
482 ms
LVx-xkvaJ0b.png
544 ms
cs.ashx
17 ms
beacon.js
5 ms
100x100bb.jpg
33 ms
fy8tT2klpgR.js
203 ms
wers.org 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.
wers.org 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
wers.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wers.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Wers.org 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.
wers.org
Open Graph description is not detected on the main page of WERS. 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: