Tools & Wizards About Us
weltenburger.de screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

weltenburger.de

Page Load Speed

5.8 sec in total

First Response

1.5 sec

Resources Loaded

3.8 sec

Page Rendered

537 ms

weltenburger.de screenshot

About Website

Click here to check amazing Weltenburger content for Germany. Otherwise, check out these important facts you probably never knew about weltenburger.de

Die älteste Klosterbrauerei der Welt schafft seit anno 1050 ganz besondere Genusserlebnisse. Weltenburger Klosterbiere sind ganz besondere, kraftvolle Biere aus dem Herzen Bayerns.

Visit weltenburger.de

Key Findings

We analyzed Weltenburger.de page load time and found that the first response time was 1.5 sec and then it took 4.4 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

weltenburger.de performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value1,000 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

www.weltenburger.de

1465 ms

dashicons.min.css

206 ms

elusive.min.css

296 ms

all.min.css

396 ms

foundation-icons.min.css

297 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 89% of them (58 requests) were addressed to the original Weltenburger.de, 9% (6 requests) were made to Use.typekit.net and 2% (1 request) were made to P.typekit.net. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Weltenburger.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 323.5 kB (18%)

Content Size

1.8 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weltenburger.de main page is 1.8 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 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 316.9 kB

  • Original 354.0 kB
  • After minification 333.0 kB
  • After compression 37.1 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 316.9 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 87 B

  • 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. Weltenburger images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.9 kB

  • Original 278.7 kB
  • After minification 278.7 kB
  • After compression 276.8 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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 4.6 kB

  • Original 149.0 kB
  • After minification 149.0 kB
  • After compression 144.4 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. Weltenburger.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 36 (69%)

Requests Now

52

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.weltenburger.de

www.weltenburger.de

1465 ms

dashicons.min.css

dashicons.min.css

206 ms

elusive.min.css

elusive.min.css

296 ms

all.min.css

all.min.css

396 ms

foundation-icons.min.css

foundation-icons.min.css

297 ms

genericons.min.css

genericons.min.css

307 ms

extra.min.css

extra.min.css

308 ms

style.min.css

style.min.css

412 ms

styles.css

styles.css

392 ms

main.css

main.css

390 ms

styles.css

styles.css

407 ms

sr7.css

sr7.css

407 ms

styles.min.css

styles.min.css

487 ms

style.css

style.css

489 ms

jkj7nlo.css

jkj7nlo.css

74 ms

all.min.css

all.min.css

491 ms

style.css

style.css

510 ms

borlabs-cookie_1_de.css

borlabs-cookie_1_de.css

507 ms

wp-featherlight.min.css

wp-featherlight.min.css

514 ms

ytprefs.min.css

ytprefs.min.css

582 ms

language-cookie.js

language-cookie.js

583 ms

tptools.js

tptools.js

700 ms

sr7.js

sr7.js

822 ms

new_modernizr.min.js

new_modernizr.min.js

608 ms

jquery.min.js

jquery.min.js

717 ms

jquery-migrate.min.js

jquery-migrate.min.js

679 ms

ytprefs.min.js

ytprefs.min.js

678 ms

p.css

p.css

28 ms

material-icons.css

material-icons.css

617 ms

all.js

all.js

786 ms

index.js

index.js

683 ms

index.js

index.js

704 ms

mm.js

mm.js

718 ms

navigation.js

navigation.js

724 ms

age-gate.js

age-gate.js

935 ms

wpFeatherlight.pkgd.min.js

wpFeatherlight.pkgd.min.js

801 ms

fitvids.min.js

fitvids.min.js

818 ms

borlabs-cookie.min.js

borlabs-cookie.min.js

826 ms

bootstrap.min.css

bootstrap.min.css

417 ms

WB_Logo_weiss.svg

WB_Logo_weiss.svg

133 ms

Weltenburger-Kloster-Menue-Illustration_01.webp

Weltenburger-Kloster-Menue-Illustration_01.webp

135 ms

newspaper.svg

newspaper.svg

130 ms

shop.svg

shop.svg

128 ms

haendlersuche.svg

haendlersuche.svg

131 ms

Weltenburger-Kloster-Benediktinerband-Footer_01.png

Weltenburger-Kloster-Benediktinerband-Footer_01.png

179 ms

Weltenburger-Kloster-Benediktinerband-Footer-Mobil_01.png

Weltenburger-Kloster-Benediktinerband-Footer-Mobil_01.png

194 ms

Weltenburger-Kloster-Logo-Header-Dunkel_01.png

Weltenburger-Kloster-Logo-Header-Dunkel_01.png

195 ms

WB_Kloster_Illustration_240320@2x.png

WB_Kloster_Illustration_240320@2x.png

280 ms

d

d

67 ms

d

d

109 ms

d

d

69 ms

d

d

67 ms

d

d

67 ms

Weltenburger-Kloster-Illustration_01.png

Weltenburger-Kloster-Illustration_01.png

429 ms

Klosterbrauerei-Weltenburg-Braumeister-Fabian-Fischer_01.jpg

Klosterbrauerei-Weltenburg-Braumeister-Fabian-Fischer_01.jpg

235 ms

Weltenburger-Kloster-Buch-Asamkirche_01-scaled.jpg

Weltenburger-Kloster-Buch-Asamkirche_01-scaled.jpg

585 ms

Weltenburger-Kloster-Footer-Donaudurchbruch_01.jpg

Weltenburger-Kloster-Footer-Donaudurchbruch_01.jpg

313 ms

fa-brands-400.woff

fa-brands-400.woff

227 ms

fa-brands-400.ttf

fa-brands-400.ttf

437 ms

fa-solid-900.woff

fa-solid-900.woff

338 ms

fa-solid-900.ttf

fa-solid-900.ttf

545 ms

fa-regular-400.woff

fa-regular-400.woff

415 ms

fa-regular-400.ttf

fa-regular-400.ttf

442 ms

cd-top-arrow.svg

cd-top-arrow.svg

501 ms

borlabs-cookie-icon-black.svg

borlabs-cookie-icon-black.svg

480 ms

Accessibility Review

weltenburger.de accessibility score

64

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

weltenburger.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

weltenburger.de SEO score

86

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

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 Weltenburger.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 Weltenburger.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

weltenburger.de

Open Graph data is detected on the main page of Weltenburger. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: