Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

banneke.com

Handverlesene Spirituosen aus aller Welt - Banneke Feinkost flüssig | Banneke

Page Load Speed

10.7 sec in total

First Response

570 ms

Resources Loaded

9.8 sec

Page Rendered

325 ms

banneke.com screenshot

About Website

Visit banneke.com now to see the best up-to-date Banneke content for Germany and also check out these interesting facts you probably never knew about banneke.com

Mehrfach ausgezeichneter Fachhändler für exklusive Spirituosen. Whiskey, Wein, Champagner, Likör, Weinbrand uvm. Über 5.000 Sorten aller führenden Marken.

Visit banneke.com

Key Findings

We analyzed Banneke.com page load time and found that the first response time was 570 ms and then it took 10.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

banneke.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value1,280 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.165

71/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

banneke.com

570 ms

www.banneke.com

1116 ms

7c5a9efefb7334a43ea63448dadd7684.css

360 ms

prototype.js

722 ms

jquery-1.10.2.min.js

718 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 90% of them (99 requests) were addressed to the original Banneke.com, 2% (2 requests) were made to Fonts.googleapis.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Banneke.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (59%)

Content Size

2.5 MB

After Optimization

1.0 MB

In fact, the total size of Banneke.com main page is 2.5 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. Javascripts take 939.2 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 203.4 kB

  • Original 237.0 kB
  • After minification 228.2 kB
  • After compression 33.6 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 203.4 kB or 86% of the original size.

Image Optimization

-19%

Potential reduce by 166.5 kB

  • Original 868.2 kB
  • After minification 701.7 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. Obviously, Banneke needs image optimization as it can save up to 166.5 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-74%

Potential reduce by 693.1 kB

  • Original 939.2 kB
  • After minification 788.9 kB
  • After compression 246.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 693.1 kB or 74% of the original size.

CSS Optimization

-87%

Potential reduce by 421.2 kB

  • Original 484.9 kB
  • After minification 412.8 kB
  • After compression 63.7 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. Banneke.com needs all CSS files to be minified and compressed as it can save up to 421.2 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (44%)

Requests Now

104

After Optimization

58

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

Accessibility Review

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

High

ARIA IDs are not unique

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

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

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

banneke.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

banneke.com SEO score

83

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

    EN

  • Encoding

    UTF-8

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