Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

cubase.net

Cubase: Music Production Software - DAW | Steinberg

Page Load Speed

3.2 sec in total

First Response

264 ms

Resources Loaded

2.3 sec

Page Rendered

699 ms

About Website

Welcome to cubase.net homepage info - get ready to check Cubase best content right away, or after learning these important things about cubase.net

Whether you want to start creating your own music or bring your production up to a professional level, Cubase guides you on your music production journey.

Visit cubase.net

Key Findings

We analyzed Cubase.net page load time and found that the first response time was 264 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

cubase.net performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value22.4 s

0/100

25%

SI (Speed Index)

Value17.6 s

0/100

10%

TBT (Total Blocking Time)

Value1,830 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value26.5 s

0/100

10%

Network Requests Diagram

cubase.net

264 ms

cubase.net

312 ms

528 ms

main.css

310 ms

steinberg-logo.svg

302 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 15% of them (2 requests) were addressed to the original Cubase.net, 62% (8 requests) were made to Steinberg.net and 15% (2 requests) were made to Ocl-steinberg-live.steinberg.net. The less responsive or slowest element that took the longest time to load (528 ms) relates to the external source Steinberg.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 178.2 kB (22%)

Content Size

792.0 kB

After Optimization

613.8 kB

In fact, the total size of Cubase.net main page is 792.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 552.6 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 178.2 kB

  • Original 209.0 kB
  • After minification 207.9 kB
  • After compression 30.8 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 178.2 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 3 B

  • Original 552.6 kB
  • After minification 552.6 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. Cubase images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 30.4 kB
  • After minification 30.4 kB
  • After compression 30.4 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. This website has mostly compressed JavaScripts.

Requests Breakdown

We found no issues to fix!

Requests Now

10

After Optimization

10

The browser has sent 10 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cubase. According to our analytics all requests are already optimized.

Accessibility Review

cubase.net accessibility score

86

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

cubase.net best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

cubase.net SEO score

86

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cubase.net 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 Cubase.net 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 Cubase. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: