Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

Page Load Speed

2.4 sec in total

First Response

177 ms

Resources Loaded

2 sec

Page Rendered

243 ms

umusic.com screenshot

About Website

Visit umusic.com now to see the best up-to-date Umusic content for Germany and also check out these interesting facts you probably never knew about umusic.com

Company information for Universal Music Group, a division of Vivendi.

Visit umusic.com

Key Findings

We analyzed Umusic.com page load time and found that the first response time was 177 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

umusic.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value19.2 s

0/100

25%

SI (Speed Index)

Value10.9 s

6/100

10%

TBT (Total Blocking Time)

Value1,490 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value24.6 s

0/100

10%

Network Requests Diagram

umusic.com

177 ms

www.universalmusic.com

1427 ms

wp-emoji-release.min.js

11 ms

foundation.min.css

28 ms

main.css

20 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Umusic.com, 90% (60 requests) were made to D1ow492s4ccivt.cloudfront.net and 6% (4 requests) were made to Universalmusic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Universalmusic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 576.9 kB (3%)

Content Size

20.1 MB

After Optimization

19.5 MB

In fact, the total size of Umusic.com main page is 20.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. Only a small number of websites need less resources to load. Images take 19.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 64.4 kB

  • Original 77.7 kB
  • After minification 72.6 kB
  • After compression 13.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 64.4 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 6.3 kB

  • Original 19.4 MB
  • After minification 19.4 MB

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. Umusic images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 237.7 kB

  • Original 343.4 kB
  • After minification 338.2 kB
  • After compression 105.7 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 237.7 kB or 69% of the original size.

CSS Optimization

-91%

Potential reduce by 268.5 kB

  • Original 295.8 kB
  • After minification 250.7 kB
  • After compression 27.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. Umusic.com needs all CSS files to be minified and compressed as it can save up to 268.5 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (12%)

Requests Now

65

After Optimization

57

The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Umusic. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

umusic.com accessibility score

86

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

umusic.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

umusic.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Umusic.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Umusic.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.

Social Sharing Optimization

Open Graph data is detected on the main page of Umusic. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: