Tools & Wizards About Us
geigenbauer-berlin.de screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

geigenbauer-berlin.de

Home – Geigenbaumeister Felix Scheit

Page Load Speed

4.4 sec in total

First Response

677 ms

Resources Loaded

3.3 sec

Page Rendered

362 ms

geigenbauer-berlin.de screenshot

About Website

Click here to check amazing Geigenbauer Berlin content. Otherwise, check out these important facts you probably never knew about geigenbauer-berlin.de

Visit geigenbauer-berlin.de

Key Findings

We analyzed Geigenbauer-berlin.de page load time and found that the first response time was 677 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

geigenbauer-berlin.de performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value430 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0.066

97/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

www.geigenbauer-berlin.de

677 ms

wp-emoji-release.min.js

133 ms

style.min.css

275 ms

classic-themes.min.css

318 ms

styles.css

328 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 85% of them (33 requests) were addressed to the original Geigenbauer-berlin.de, 13% (5 requests) were made to Use.typekit.net and 3% (1 request) were made to P.typekit.net. The less responsive or slowest element that took the longest time to load (998 ms) belongs to the original domain Geigenbauer-berlin.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 155.6 kB (9%)

Content Size

1.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Geigenbauer-berlin.de main page is 1.7 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. 40% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 51.2 kB

  • Original 64.1 kB
  • After minification 62.5 kB
  • After compression 13.0 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 51.2 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 4.9 kB

  • Original 1.1 MB
  • After minification 1.1 MB

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

JavaScript Optimization

-15%

Potential reduce by 53.0 kB

  • Original 357.4 kB
  • After minification 357.4 kB
  • After compression 304.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 53.0 kB or 15% of the original size.

CSS Optimization

-23%

Potential reduce by 46.6 kB

  • Original 198.6 kB
  • After minification 198.3 kB
  • After compression 152.0 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. Geigenbauer-berlin.de needs all CSS files to be minified and compressed as it can save up to 46.6 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (73%)

Requests Now

33

After Optimization

9

  • Images
  • JavaScript
  • CSS

The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Geigenbauer 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 12 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.geigenbauer-berlin.de

www.geigenbauer-berlin.de

677 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

133 ms

style.min.css

style.min.css

275 ms

classic-themes.min.css

classic-themes.min.css

318 ms

styles.css

styles.css

328 ms

js_composer.min.css

js_composer.min.css

559 ms

bootstrap.min.css

bootstrap.min.css

331 ms

base.min.css

base.min.css

494 ms

style.min.css

style.min.css

382 ms

other.min.css

other.min.css

534 ms

style.css

style.css

438 ms

style.css

style.css

444 ms

kzf1hlv.css

kzf1hlv.css

85 ms

jquery.min.js

jquery.min.js

598 ms

jquery-migrate.min.js

jquery-migrate.min.js

554 ms

language-cookie.js

language-cookie.js

578 ms

all.min.css

all.min.css

675 ms

rs6.css

rs6.css

680 ms

rbtools.min.js

rbtools.min.js

873 ms

rs6.min.js

rs6.min.js

899 ms

gsap.min.js

gsap.min.js

753 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

710 ms

ScrollMagic.min.js

ScrollMagic.min.js

789 ms

animation.gsap.min.js

animation.gsap.min.js

781 ms

js_composer_front.min.js

js_composer_front.min.js

818 ms

main.min.js

main.min.js

998 ms

p.css

p.css

28 ms

icon-menu-close.svg

icon-menu-close.svg

276 ms

logo-weiss@2x.png

logo-weiss@2x.png

336 ms

dummy.png

dummy.png

329 ms

bild-reparatur-CH__0721-min.jpg

bild-reparatur-CH__0721-min.jpg

588 ms

bild-neubau-CH__0666-min.jpg

bild-neubau-CH__0666-min.jpg

891 ms

bild-verkauf-CH__0805-min.jpg

bild-verkauf-CH__0805-min.jpg

459 ms

Wand_Pat@2.jpg

Wand_Pat@2.jpg

767 ms

d

d

18 ms

flaticon.woff

flaticon.woff

421 ms

d

d

52 ms

d

d

50 ms

d

d

49 ms

Accessibility Review

geigenbauer-berlin.de accessibility score

97

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

Links do not have a discernible name

Best Practices

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

SEO Factors

geigenbauer-berlin.de SEO score

93

Search Engine Optimization Advices

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

    DE

  • Encoding

    UTF-8

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

geigenbauer-berlin.de

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