Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

vuhaus.com

Live Sessions

Page Load Speed

9.8 sec in total

First Response

195 ms

Resources Loaded

3.4 sec

Page Rendered

6.3 sec

vuhaus.com screenshot

About Website

Click here to check amazing Vuhaus content for United States. Otherwise, check out these important facts you probably never knew about vuhaus.com

Discover new and emerging artists, watch videos and live stream rare in-studio performances and concerts, all curated by Public Radio's best music radio stations.

Visit vuhaus.com

Key Findings

We analyzed Vuhaus.com page load time and found that the first response time was 195 ms and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

vuhaus.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value14.8 s

0/100

25%

SI (Speed Index)

Value7.4 s

28/100

10%

TBT (Total Blocking Time)

Value930 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

www.vuhaus.com

195 ms

app.css

23 ms

app.d.js

169 ms

vendor.js

144 ms

app.js

143 ms

Our browser made a total of 209 requests to load all elements on the main page. We found that 7% of them (15 requests) were addressed to the original Vuhaus.com, 85% (177 requests) were made to Vuhaus-production.imgix.net and 2% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (829 ms) relates to the external source Vuhaus-production.imgix.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.1 MB (26%)

Content Size

12.2 MB

After Optimization

9.1 MB

In fact, the total size of Vuhaus.com main page is 12.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 8.5 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 144.4 kB

  • Original 183.3 kB
  • After minification 183.3 kB
  • After compression 39.0 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 144.4 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 39.0 kB

  • Original 8.5 MB
  • After minification 8.5 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. Vuhaus images are well optimized though.

JavaScript Optimization

-84%

Potential reduce by 2.9 MB

  • Original 3.5 MB
  • After minification 2.2 MB
  • After compression 568.9 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 2.9 MB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (5%)

Requests Now

204

After Optimization

193

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

Accessibility Review

vuhaus.com accessibility score

84

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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.

Best Practices

vuhaus.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

vuhaus.com SEO score

89

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vuhaus.com 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 Vuhaus.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 description is not detected on the main page of Vuhaus. 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: