Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

bauer-schmidt.com

Bauer Schmidt - alles unter einem Dach | Essen, Trinken, Feiern, Schlafen

Page Load Speed

2.3 sec in total

First Response

533 ms

Resources Loaded

1.4 sec

Page Rendered

409 ms

bauer-schmidt.com screenshot

About Website

Visit bauer-schmidt.com now to see the best up-to-date Bauer Schmidt content and also check out these interesting facts you probably never knew about bauer-schmidt.com

Visit bauer-schmidt.com

Key Findings

We analyzed Bauer-schmidt.com page load time and found that the first response time was 533 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

bauer-schmidt.com performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

57/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.558

13/100

15%

TTI (Time to Interactive)

Value7.0 s

53/100

10%

Network Requests Diagram

bauer-schmidt.com

533 ms

node.css

78 ms

ckeditor.css

86 ms

lightbox.css

86 ms

defaults.css

90 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 70% of them (38 requests) were addressed to the original Bauer-schmidt.com, 13% (7 requests) were made to Translate.googleapis.com and 6% (3 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (683 ms) relates to the external source Sm-weilerbach.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 125.5 kB (14%)

Content Size

891.6 kB

After Optimization

766.1 kB

In fact, the total size of Bauer-schmidt.com main page is 891.6 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. 35% of websites need less resources to load. Images take 649.2 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 20.4 kB

  • Original 27.5 kB
  • After minification 24.1 kB
  • After compression 7.2 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.4 kB, which is 12% 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 20.4 kB or 74% of the original size.

Image Optimization

-1%

Potential reduce by 8.6 kB

  • Original 649.2 kB
  • After minification 640.5 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. Bauer Schmidt images are well optimized though.

JavaScript Optimization

-38%

Potential reduce by 64.2 kB

  • Original 170.4 kB
  • After minification 148.6 kB
  • After compression 106.1 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 64.2 kB or 38% of the original size.

CSS Optimization

-72%

Potential reduce by 32.3 kB

  • Original 44.6 kB
  • After minification 33.4 kB
  • After compression 12.3 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. Bauer-schmidt.com needs all CSS files to be minified and compressed as it can save up to 32.3 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (52%)

Requests Now

52

After Optimization

25

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

Accessibility Review

bauer-schmidt.com accessibility score

66

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[role]s do not have all required [aria-*] attributes

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.

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

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

bauer-schmidt.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Page has valid source maps

SEO Factors

bauer-schmidt.com SEO score

77

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

High

Tap targets are not sized appropriately

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 Bauer-schmidt.com 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 Bauer-schmidt.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 Bauer Schmidt. 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: