21.9 sec in total
4.5 sec
16.1 sec
1.3 sec
Welcome to weeklymusiccommentary.com homepage info - get ready to check Weekly Music Commentary best content right away, or after learning these important things about weeklymusiccommentary.com
All music, every week
Visit weeklymusiccommentary.comWe analyzed Weeklymusiccommentary.com page load time and found that the first response time was 4.5 sec and then it took 17.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
weeklymusiccommentary.com performance score
name
value
score
weighting
Value9.1 s
0/100
10%
Value16.7 s
0/100
25%
Value32.0 s
0/100
10%
Value4,410 ms
0/100
30%
Value0.063
97/100
15%
Value17.9 s
3/100
10%
4525 ms
291 ms
132 ms
395 ms
1042 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 26% of them (23 requests) were addressed to the original Weeklymusiccommentary.com, 10% (9 requests) were made to I2.wp.com and 8% (7 requests) were made to Translate.googleapis.com. The less responsive or slowest element that took the longest time to load (7.6 sec) relates to the external source I2.wp.com.
Page size can be reduced by 523.7 kB (10%)
5.1 MB
4.5 MB
In fact, the total size of Weeklymusiccommentary.com main page is 5.1 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. Images take 4.3 MB which makes up the majority of the site volume.
Potential reduce by 63.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 63.1 kB or 81% of the original size.
Potential reduce by 11.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. Weekly Music Commentary images are well optimized though.
Potential reduce by 287.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 287.0 kB or 57% of the original size.
Potential reduce by 162.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. Weeklymusiccommentary.com needs all CSS files to be minified and compressed as it can save up to 162.6 kB or 84% of the original size.
Number of requests can be reduced by 46 (56%)
82
36
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weekly Music Commentary. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.weeklymusiccommentary.com
4525 ms
wp-emoji-release.min.js
291 ms
css
132 ms
style.css
395 ms
admin-ajax.php
1042 ms
jetpack.css
271 ms
jquery.js
477 ms
jquery-migrate.min.js
1106 ms
element.js
1192 ms
banners
1298 ms
output.css
213 ms
jquery.cycle.js
364 ms
slideshow-shortcode.js
340 ms
photon.js
715 ms
devicepx-jetpack.js
170 ms
gprofiles.js
212 ms
wpgroho.js
476 ms
main.min.js
679 ms
wp-embed.min.js
815 ms
e-201614.js
1167 ms
Take-6-WMC-photo.jpg
7641 ms
Common-WMC.jpg
1419 ms
Wale-Press-Site-JimmyFontaine.jpg
1156 ms
lg-share-en.gif
128 ms
background.png
296 ms
new-wmc-logo.png
1147 ms
line-db9f0e.png
178 ms
sprite.png
177 ms
loader.gif
1113 ms
slider-db9f0e.png
181 ms
Fifth-2BHarmony-2BWMC.jpg
1660 ms
Ne-yo2-WMC.jpg
1417 ms
Hinder-WMC-Photo.jpg
3201 ms
Maurice-White.jpg
1370 ms
Mavin_Obi_Somto_Photography-27.jpg
1536 ms
Charlie-Puth-%E2%80%93-Pub-4-%E2%80%93-Catie-Laffoon.jpg
1140 ms
Tower-of-power.jpg
2095 ms
Keke-wyatt2-WMC-Photo.jpg
1103 ms
Take-6-WMC-photo.jpg
214 ms
Jully-Black-WMC-photo.jpg
1770 ms
Charlie-Puth-%E2%80%93-Pub-4-%E2%80%93-Catie-Laffoon.jpg
258 ms
Alessia-Cara.jpg
2027 ms
Alexandra-2BDemetree-2Bby-2BMelinda-2BNorris.jpg
2689 ms
WILL-PROMO-3-copy.jpg
1100 ms
UyYrYy3ltEffJV9QueSi4UpeNX8RPf6i6WQfJWyCWEs.ttf
267 ms
Q_pTky3Sc3ubRibGToTAYjnFfol0SnfBMmbnmUK0fZM.ttf
348 ms
fontello.woff
249 ms
translateelement.css
302 ms
main.js
377 ms
bnr-tag_1.0.9.js
562 ms
banners
563 ms
banners
558 ms
widget.png
812 ms
cm
441 ms
cm
437 ms
widgets.js
510 ms
element_main.js
510 ms
black.png
760 ms
analytics.js
492 ms
hovercard.css
186 ms
services.css
187 ms
cm
113 ms
cm
115 ms
AV_IMDb-companion-banner_MITJS2_FT_300x250_V285446212_.jpg
436 ms
218 ms
210 ms
free-songs-and-deals-300._V204838852_.gif
218 ms
g.gif
180 ms
bounce-tag_1.0.23.js
224 ms
20160408_017970359_image-banner.cib
237 ms
collect
146 ms
rhpop_1.1.42.js
285 ms
button.71000885400e222c3c0eec823f8f93f0.js
759 ms
translate_24dp.png
280 ms
l
133 ms
googlelogo_color_42x16dp.png
290 ms
collect
301 ms
jquery.min.js
621 ms
cleardot.gif
277 ms
te_ctrl3.gif
79 ms
loading.gif
119 ms
googlelogo_color_68x28dp.png
139 ms
ga-audiences
374 ms
te_bk.gif
57 ms
follow_button.fd774b599f565016d763dd860cb31c79.en.html
90 ms
bnrcore_1.0.30.js
98 ms
findBanner
63 ms
findBanner
133 ms
jot
200 ms
dow_wat_300x250_en_ad_v.png
102 ms
weeklymusiccommentary.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
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
Links do not have a discernible name
weeklymusiccommentary.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
weeklymusiccommentary.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 Weeklymusiccommentary.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 Weeklymusiccommentary.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.
weeklymusiccommentary.com
Open Graph data is detected on the main page of Weekly Music Commentary. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: