Report Summary

  • 60

    Performance

    Renders faster than
    76% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

berlinbeweger.com

Berlin – KAUPERTS

Page Load Speed

1.2 sec in total

First Response

324 ms

Resources Loaded

750 ms

Page Rendered

154 ms

berlinbeweger.com screenshot

About Website

Welcome to berlinbeweger.com homepage info - get ready to check Berlin Beweger best content right away, or after learning these important things about berlinbeweger.com

Finde, was Du wirklich suchst: Geprüfte, einzigartige Angaben zu Adressen, Straßen, PLZ und Ortsteilen. KAUPERTS kennt sich aus.

Visit berlinbeweger.com

Key Findings

We analyzed Berlinbeweger.com page load time and found that the first response time was 324 ms and then it took 904 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

berlinbeweger.com performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.02

100/100

15%

TTI (Time to Interactive)

Value5.9 s

65/100

10%

Network Requests Diagram

berlinbeweger.de

324 ms

valid-xhtml10

29 ms

ubuntu-logo.png

93 ms

Our browser made a total of 3 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Berlinbeweger.com, 33% (1 request) were made to W3.org. The less responsive or slowest element that took the longest time to load (324 ms) relates to the external source Berlinbeweger.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 8.6 kB (58%)

Content Size

14.9 kB

After Optimization

6.2 kB

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

HTML Optimization

-75%

Potential reduce by 8.6 kB

  • Original 11.5 kB
  • After minification 8.5 kB
  • After compression 2.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. This page needs HTML code to be minified as it can gain 3.0 kB, which is 26% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 8.6 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 3.4 kB
  • After minification 3.4 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. Berlin Beweger images are well optimized though.

Requests Breakdown

We found no issues to fix!

Requests Now

2

After Optimization

2

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

Accessibility Review

berlinbeweger.com accessibility score

81

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

berlinbeweger.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

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

High

Browser errors were logged to the console

SEO Factors

berlinbeweger.com SEO score

92

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

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Berlinbeweger.com can be misinterpreted by Google and other search engines. Our service has detected that German 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 Berlinbeweger.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 Berlin Beweger. 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: