4 sec in total
847 ms
2.5 sec
644 ms
Click here to check amazing Why Music Matters content. Otherwise, check out these important facts you probably never knew about whymusicmatters.co.nz
Visit whymusicmatters.co.nzWe analyzed Whymusicmatters.co.nz page load time and found that the first response time was 847 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
whymusicmatters.co.nz performance score
name
value
score
weighting
Value7.5 s
1/100
10%
Value8.9 s
1/100
25%
Value11.5 s
5/100
10%
Value1,440 ms
15/100
30%
Value0.036
100/100
15%
Value17.8 s
4/100
10%
847 ms
62 ms
113 ms
97 ms
162 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Whymusicmatters.co.nz, 67% (31 requests) were made to Whymusicmatters.com.au and 9% (4 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (847 ms) belongs to the original domain Whymusicmatters.co.nz.
Page size can be reduced by 886.8 kB (50%)
1.8 MB
874.9 kB
In fact, the total size of Whymusicmatters.co.nz main page is 1.8 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. 40% of websites need less resources to load. CSS take 660.9 kB which makes up the majority of the site volume.
Potential reduce by 18.9 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 18.9 kB or 75% of the original size.
Potential reduce by 3.5 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. Why Music Matters images are well optimized though.
Potential reduce by 304.2 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 304.2 kB or 63% of the original size.
Potential reduce by 560.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. Whymusicmatters.co.nz needs all CSS files to be minified and compressed as it can save up to 560.3 kB or 85% of the original size.
Number of requests can be reduced by 28 (68%)
41
13
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Why Music Matters. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
whymusicmatters.co.nz
847 ms
css
62 ms
grid.css
113 ms
base.css
97 ms
layout.css
162 ms
shortcodes.css
211 ms
magnific-popup.css
98 ms
mediaelementplayer.css
113 ms
why_music_matters.css
272 ms
custom.css
171 ms
style_2.1.2.css
154 ms
skiptotimestamp.js
155 ms
jquery.js
379 ms
jquery-migrate.min.js
241 ms
avia-compat.js
222 ms
avia.js
333 ms
shortcodes.js
499 ms
jquery.magnific-popup.min.js
284 ms
mediaelement-and-player.min.js
458 ms
wp-mediaelement.js
330 ms
comment-reply.min.js
458 ms
script_2.1.2.js
497 ms
wp-emoji-release.min.js
459 ms
www-widgetapi.js
266 ms
backgroundimages1.jpg
582 ms
thelogo.png
234 ms
switch-uk.jpg
122 ms
switch-us.jpg
230 ms
switch-ie.jpg
228 ms
fotterlogo.gif
230 ms
sprite.png
423 ms
pattern.gif
166 ms
analytics.js
159 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
322 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
321 ms
pointy.woff
327 ms
collect
40 ms
N2f07MfdeIk
154 ms
print.css
57 ms
www-embed-player-vfl-z2BtK.css
31 ms
www-embed-player.js
81 ms
base.js
175 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
102 ms
ad_status.js
113 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
259 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
259 ms
whymusicmatters.co.nz accessibility score
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
whymusicmatters.co.nz 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
Issues were logged in the Issues panel in Chrome Devtools
whymusicmatters.co.nz SEO score
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 Whymusicmatters.co.nz 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 Whymusicmatters.co.nz 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.
whymusicmatters.co.nz
Open Graph description is not detected on the main page of Why Music Matters. 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: