3.6 sec in total
223 ms
3 sec
388 ms
Click here to check amazing Livingmusic content. Otherwise, check out these important facts you probably never knew about livingmusic.com
Celebrating the cultures & creatures of the whole Earth
Visit livingmusic.comWe analyzed Livingmusic.com page load time and found that the first response time was 223 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
livingmusic.com performance score
name
value
score
weighting
Value11.2 s
0/100
10%
Value22.4 s
0/100
25%
Value21.6 s
0/100
10%
Value3,870 ms
1/100
30%
Value0.019
100/100
15%
Value22.2 s
2/100
10%
223 ms
533 ms
37 ms
51 ms
79 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Livingmusic.com, 68% (45 requests) were made to Paulwinter.com and 5% (3 requests) were made to S.gravatar.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Paulwinter.com.
Page size can be reduced by 317.4 kB (27%)
1.2 MB
847.1 kB
In fact, the total size of Livingmusic.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. 40% of websites need less resources to load. Images take 764.5 kB which makes up the majority of the site volume.
Potential reduce by 25.2 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 25.2 kB or 77% of the original size.
Potential reduce by 53.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. Livingmusic images are well optimized though.
Potential reduce by 153.5 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 153.5 kB or 58% of the original size.
Potential reduce by 85.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. Livingmusic.com needs all CSS files to be minified and compressed as it can save up to 85.3 kB or 83% of the original size.
Number of requests can be reduced by 34 (62%)
55
21
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Livingmusic. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
livingmusic.com
223 ms
www.paulwinter.com
533 ms
css
37 ms
css
51 ms
style.css
79 ms
nextgen_gallery_related_images.css
104 ms
social_widget.css
101 ms
tribe-events-full.min.css
116 ms
widgets.css
132 ms
superfish.css
111 ms
jquery.fancybox-1.3.4.css
125 ms
flexslider.css
149 ms
jquery.js
237 ms
jquery-migrate.min.js
166 ms
ajax.js
195 ms
functional.css
177 ms
admin-ajax.php
1991 ms
e-201611.js
8 ms
conversion.js
29 ms
devicepx-jetpack.js
5 ms
gprofiles.js
63 ms
wpgroho.js
313 ms
superfish.js
315 ms
supersubs.js
314 ms
jquery.fancybox-1.3.4.pack.js
259 ms
jquery.fitvids.js
314 ms
jquery.isotope.min.js
314 ms
jquery.flexslider-min.js
320 ms
theme_trust.js
319 ms
all.frontend.min.js
335 ms
e-201611.js
30 ms
analytics.js
11 ms
pw-logo.png
103 ms
April-10th.jpg
265 ms
Saudade-Website-Slide1.jpg
287 ms
count_me_in_home.jpg
258 ms
a2046084032_16-280x280.jpg
276 ms
Pete-300-280x280.jpg
350 ms
count-me-in-300x300-280x280.png
442 ms
earth-music-cover-300-280x280.jpg
410 ms
Silver_Solstice6-copy-280x280.jpg
348 ms
facebook.png
424 ms
twitter.png
427 ms
youtube.png
502 ms
lastfm.png
470 ms
pandora.png
513 ms
bandcamp.png
502 ms
collect
17 ms
left.jpg
518 ms
right.jpg
664 ms
btn_bkg.png
512 ms
s-BiyweUPV0v-yRb-cjciBsxEYwM7FgeyaSgU71cLG0.woff
8 ms
EFpQQyG9GqCrobXxL-KRMQFhaRv2pGgT5Kf0An0s4MM.woff
13 ms
QQt14e8dY39u-eYBZmppwTqR_3kx9_hJXbbyU8S6IN0.woff
17 ms
Tenderness-webfont.woff
540 ms
collect
60 ms
ga-audiences
39 ms
www.paulwinter.com
265 ms
light-arrows.png
81 ms
loading-icon-128x128.gif
79 ms
g.gif
19 ms
49 ms
96 ms
hovercard.css
71 ms
services.css
95 ms
28 ms
livingmusic.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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
livingmusic.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
General
Impact
Issue
Registers an unload listener
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
livingmusic.com 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Livingmusic.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 Livingmusic.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.
livingmusic.com
Open Graph data is detected on the main page of Livingmusic. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: