Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

hornung-feinkost.de

Feinkost, Tee & Schokolade aus Regensburg | Hornung

Page Load Speed

3.9 sec in total

First Response

327 ms

Resources Loaded

2.9 sec

Page Rendered

600 ms

About Website

Click here to check amazing Hornung Feinkost content. Otherwise, check out these important facts you probably never knew about hornung-feinkost.de

Feinkost & mehr aus Regensburg: seit 1976 ✓ >2.200 positive Bewertungen ✓ Handverlesene Produkte ✓ Versandkostenfrei ab 30€ ♥ Jetzt entdecken!

Visit hornung-feinkost.de

Key Findings

We analyzed Hornung-feinkost.de page load time and found that the first response time was 327 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

hornung-feinkost.de performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

2/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value4,000 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.109

87/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

hornung-feinkost.de

327 ms

www.hornung-feinkost.de

781 ms

css

67 ms

default.css

96 ms

jcemediabox.css

187 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 92% of them (61 requests) were addressed to the original Hornung-feinkost.de, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (966 ms) belongs to the original domain Hornung-feinkost.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 439.9 kB (19%)

Content Size

2.3 MB

After Optimization

1.8 MB

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

HTML Optimization

-76%

Potential reduce by 31.3 kB

  • Original 41.3 kB
  • After minification 38.9 kB
  • After compression 10.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 31.3 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 27.8 kB

  • Original 1.7 MB
  • After minification 1.7 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. Hornung Feinkost images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 353.0 kB

  • Original 499.0 kB
  • After minification 449.2 kB
  • After compression 146.0 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 353.0 kB or 71% of the original size.

CSS Optimization

-79%

Potential reduce by 27.8 kB

  • Original 35.3 kB
  • After minification 28.3 kB
  • After compression 7.5 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. Hornung-feinkost.de needs all CSS files to be minified and compressed as it can save up to 27.8 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (51%)

Requests Now

63

After Optimization

31

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

Accessibility Review

hornung-feinkost.de accessibility score

74

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

button, link, and menuitem elements do not have accessible names.

High

[role]s are not contained by their required parent element

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Best Practices

hornung-feinkost.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

High

Missing source maps for large first-party JavaScript

SEO Factors

hornung-feinkost.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 Hornung-feinkost.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 Hornung-feinkost.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

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