Tools & Wizards About Us
eschenwecker.net screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

eschenwecker.net

Metzgerei Eschenwecker Regensburg: Home - frisch und lecker

Page Load Speed

3.4 sec in total

First Response

633 ms

Resources Loaded

2.6 sec

Page Rendered

207 ms

eschenwecker.net screenshot

About Website

Welcome to eschenwecker.net homepage info - get ready to check Eschenwecker best content right away, or after learning these important things about eschenwecker.net

Die Metzgerei Eschenwecker in Kumpfmühl ist einer der wenigen selbstständigen Betriebe, die in Regensburg noch traditionell handwerklich tätig sind.

Visit eschenwecker.net

Key Findings

We analyzed Eschenwecker.net page load time and found that the first response time was 633 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

eschenwecker.net performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

2/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value6.9 s

33/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.041

99/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

www.eschenwecker.net

633 ms

jquery-1.6.3.js

587 ms

jquery.easing.1.3.js

320 ms

jquery.roundabout.js

436 ms

roundabout_shapes.js

330 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 98% of them (39 requests) were addressed to the original Eschenwecker.net, 3% (1 request) were made to Consent.cookiebot.com. The less responsive or slowest element that took the longest time to load (884 ms) belongs to the original domain Eschenwecker.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 776.0 kB (39%)

Content Size

2.0 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 19.0 kB

  • Original 24.8 kB
  • After minification 23.1 kB
  • After compression 5.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. 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 19.0 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 38.6 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. Eschenwecker images are well optimized though.

JavaScript Optimization

-82%

Potential reduce by 640.6 kB

  • Original 777.9 kB
  • After minification 535.2 kB
  • After compression 137.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 640.6 kB or 82% of the original size.

CSS Optimization

-86%

Potential reduce by 77.8 kB

  • Original 90.6 kB
  • After minification 68.3 kB
  • After compression 12.8 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. Eschenwecker.net needs all CSS files to be minified and compressed as it can save up to 77.8 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (49%)

Requests Now

39

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.eschenwecker.net

www.eschenwecker.net

633 ms

jquery-1.6.3.js

jquery-1.6.3.js

587 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

320 ms

jquery.roundabout.js

jquery.roundabout.js

436 ms

roundabout_shapes.js

roundabout_shapes.js

330 ms

reset.css

reset.css

329 ms

styles.css

styles.css

620 ms

clears.css

clears.css

467 ms

prototype.js

prototype.js

884 ms

validation.js

validation.js

643 ms

builder.js

builder.js

552 ms

effects.js

effects.js

700 ms

dragdrop.js

dragdrop.js

735 ms

controls.js

controls.js

711 ms

slider.js

slider.js

738 ms

js.js

js.js

804 ms

form.js

form.js

825 ms

menu.js

menu.js

822 ms

translate.js

translate.js

845 ms

cookies.js

cookies.js

852 ms

uc.js

uc.js

39 ms

background.jpg

background.jpg

144 ms

logo.png

logo.png

150 ms

bg_nav.jpg

bg_nav.jpg

131 ms

bg_menu.jpg

bg_menu.jpg

127 ms

facebook.png

facebook.png

119 ms

img-9.jpg

img-9.jpg

344 ms

Slider_Suchen.jpg

Slider_Suchen.jpg

476 ms

img-6.jpg

img-6.jpg

484 ms

Slider_Jubi.jpg

Slider_Jubi.jpg

485 ms

img-4.jpg

img-4.jpg

319 ms

speiseplan.jpg

speiseplan.jpg

296 ms

weiter_lesen.jpg

weiter_lesen.jpg

434 ms

angebot.jpg

angebot.jpg

450 ms

wild.jpg

wild.jpg

477 ms

telefon.jpg

telefon.jpg

591 ms

separator_1line.jpg

separator_1line.jpg

528 ms

separator_2lines.jpg

separator_2lines.jpg

547 ms

bg_footer_menu.jpg

bg_footer_menu.jpg

546 ms

print.css

print.css

113 ms

Accessibility Review

eschenwecker.net accessibility score

78

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

eschenwecker.net best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

eschenwecker.net SEO score

69

Search Engine Optimization Advices

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

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 Eschenwecker.net 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 Eschenwecker.net 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

eschenwecker.net

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