Report Summary

  • 0

    Performance

  • 67

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    65% of websites

  • 67

    SEO

    Google-friendlier than
    35% of websites

cmraiser.de

www.cmraiser.de

Page Load Speed

5.8 sec in total

First Response

246 ms

Resources Loaded

5.3 sec

Page Rendered

271 ms

cmraiser.de screenshot

About Website

Visit cmraiser.de now to see the best up-to-date Cmraiser content and also check out these interesting facts you probably never knew about cmraiser.de

Trompete und Orgel, Konzerte,

Visit cmraiser.de

Key Findings

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

Performance Metrics

cmraiser.de performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value4.3 s

84/100

10%

Network Requests Diagram

cmraiser.de

246 ms

www.trompete-orgel.eu

706 ms

layout.css

113 ms

main.css

212 ms

font.css

221 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Cmraiser.de, 34% (20 requests) were made to Trompete-orgel.eu and 33% (19 requests) were made to Cdn.website-start.de. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Trompete-orgel.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 389.7 kB (37%)

Content Size

1.1 MB

After Optimization

666.0 kB

In fact, the total size of Cmraiser.de main page is 1.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. 50% of websites need less resources to load. Images take 521.9 kB which makes up the majority of the site volume.

HTML Optimization

-47%

Potential reduce by 335 B

  • Original 716 B
  • After minification 715 B
  • After compression 381 B

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 335 B or 47% of the original size.

Image Optimization

-0%

Potential reduce by 2.5 kB

  • Original 521.9 kB
  • After minification 519.3 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. Cmraiser images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 373.5 kB

  • Original 512.7 kB
  • After minification 432.9 kB
  • After compression 139.2 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 373.5 kB or 73% of the original size.

CSS Optimization

-65%

Potential reduce by 13.3 kB

  • Original 20.4 kB
  • After minification 17.4 kB
  • After compression 7.1 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. Cmraiser.de needs all CSS files to be minified and compressed as it can save up to 13.3 kB or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (61%)

Requests Now

57

After Optimization

22

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

Accessibility Review

cmraiser.de accessibility score

67

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

Best Practices

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

High

Page has valid source maps

SEO Factors

cmraiser.de SEO score

67

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

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