Tools & Wizards About Us
cubase.de screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

cubase.de

Cubase: Musikproduktionssoftware | Steinberg

Page Load Speed

3.5 sec in total

First Response

289 ms

Resources Loaded

3.1 sec

Page Rendered

109 ms

cubase.de screenshot

About Website

Click here to check amazing Cubase content. Otherwise, check out these important facts you probably never knew about cubase.de

Ganz gleich, ob du gerade erst anfängst, deine eigene Musik zu produzieren oder ein professionelleres Niveau erreichen möchtest, Cubase hilt dir dabei.

Visit cubase.de

Key Findings

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

Performance Metrics

cubase.de performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value24.0 s

0/100

25%

SI (Speed Index)

Value14.3 s

1/100

10%

TBT (Total Blocking Time)

Value1,580 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value20.9 s

2/100

10%

Network Requests Diagram

cubase.de

289 ms

viewforum.php

615 ms

viewforum.php

728 ms

styleswitcher.js

116 ms

forum_fn.js

218 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Cubase.de, 96% (27 requests) were made to Steinberg.net. The less responsive or slowest element that took the longest time to load (728 ms) relates to the external source Steinberg.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 32.1 kB (74%)

Content Size

43.3 kB

After Optimization

11.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cubase.de main page is 43.3 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. HTML takes 23.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 18.7 kB

  • Original 23.2 kB
  • After minification 21.3 kB
  • After compression 4.5 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.7 kB or 80% of the original size.

Image Optimization

-34%

Potential reduce by 1.6 kB

  • Original 4.7 kB
  • After minification 3.1 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. Obviously, Cubase needs image optimization as it can save up to 1.6 kB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-78%

Potential reduce by 9.5 kB

  • Original 12.2 kB
  • After minification 7.8 kB
  • After compression 2.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 9.5 kB or 78% of the original size.

CSS Optimization

-73%

Potential reduce by 2.3 kB

  • Original 3.2 kB
  • After minification 2.3 kB
  • After compression 858 B

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. Cubase.de needs all CSS files to be minified and compressed as it can save up to 2.3 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (76%)

Requests Now

25

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cubase.de

cubase.de

289 ms

viewforum.php

viewforum.php

615 ms

viewforum.php

viewforum.php

728 ms

styleswitcher.js

styleswitcher.js

116 ms

forum_fn.js

forum_fn.js

218 ms

style.php

style.php

611 ms

normal.css

normal.css

452 ms

steinbergwowww.png

steinbergwowww.png

208 ms

icon_topic_latest.gif

icon_topic_latest.gif

211 ms

corners_left.png

corners_left.png

123 ms

corners_right.png

corners_right.png

133 ms

icon_home.gif

icon_home.gif

132 ms

icon_fontsize.gif

icon_fontsize.gif

131 ms

icon_faq.gif

icon_faq.gif

253 ms

icon_members.gif

icon_members.gif

253 ms

icon_thanks_toplist.gif

icon_thanks_toplist.gif

246 ms

icon_thanks.gif

icon_thanks.gif

251 ms

icon_register.gif

icon_register.gif

370 ms

icon_logout.gif

icon_logout.gif

363 ms

gradient.gif

gradient.gif

368 ms

forum_read.gif

forum_read.gif

368 ms

forum_read_locked.gif

forum_read_locked.gif

409 ms

button_topic_new.gif

button_topic_new.gif

426 ms

bg_button.gif

bg_button.gif

477 ms

arrow_left.gif

arrow_left.gif

473 ms

print.css

print.css

136 ms

medium.css

medium.css

108 ms

large.css

large.css

106 ms

Accessibility Review

cubase.de accessibility score

92

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

Best Practices

cubase.de 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.de 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

    DE

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cubase.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Cubase.de 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

cubase.de

Open Graph description is not detected on the main page of Cubase. 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: