Report Summary

  • 0

    Performance

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

maasch-berlin.de

Maasch-berlin.de

Page Load Speed

2.7 sec in total

First Response

267 ms

Resources Loaded

2.4 sec

Page Rendered

58 ms

maasch-berlin.de screenshot

About Website

Welcome to maasch-berlin.de homepage info - get ready to check Maasch Berlin best content for Germany right away, or after learning these important things about maasch-berlin.de

Visit maasch-berlin.de

Key Findings

We analyzed Maasch-berlin.de page load time and found that the first response time was 267 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

maasch-berlin.de performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.6 s

46/100

10%

Network Requests Diagram

maasch-berlin.de

267 ms

maasch-berlin

490 ms

originTrials.41d7301a.bundle.min.js

29 ms

minified.js

34 ms

focus-within-polyfill.js

70 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Maasch-berlin.de, 50% (17 requests) were made to Static.parastorage.com and 32% (11 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Polyfill-fastly.io.

Page Optimization Overview & Recommendations

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

Content Size

375.5 kB

After Optimization

238.1 kB

In fact, the total size of Maasch-berlin.de main page is 375.5 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. 45% of websites need less resources to load. Javascripts take 374.1 kB which makes up the majority of the site volume.

HTML Optimization

-48%

Potential reduce by 325 B

  • Original 676 B
  • After minification 672 B
  • After compression 351 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 325 B or 48% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 773 B
  • After minification 773 B

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

JavaScript Optimization

-37%

Potential reduce by 137.1 kB

  • Original 374.1 kB
  • After minification 374.0 kB
  • After compression 237.0 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 137.1 kB or 37% of the original size.

Requests Breakdown

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

Requests Now

19

After Optimization

7

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

Accessibility Review

maasch-berlin.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

maasch-berlin.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

maasch-berlin.de SEO score

58

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 Maasch-berlin.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 Maasch-berlin.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 Maasch Berlin. 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: