Tools & Wizards About Us
haase-food.com screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

haase-food.com

Haase Food GmbH | Der Spezialist für Popcorn, Nachos, Zuckerwatte, Slush, Waffeln, Mandeln und mehr

Page Load Speed

4 sec in total

First Response

231 ms

Resources Loaded

3.4 sec

Page Rendered

328 ms

haase-food.com screenshot

About Website

Welcome to haase-food.com homepage info - get ready to check Haase Food best content for Germany right away, or after learning these important things about haase-food.com

Der Onlineshop für Fun-Food und Leckereien.

Visit haase-food.com

Key Findings

We analyzed Haase-food.com page load time and found that the first response time was 231 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

haase-food.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value7.9 s

43/100

10%

Network Requests Diagram

haase-food.com

231 ms

shop.haase-food.com

852 ms

ocb_autosuggest.css

110 ms

superfish.css

217 ms

flexslider.css

295 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Haase-food.com, 94% (79 requests) were made to Shop.haase-food.com and 2% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Shop.haase-food.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 236.1 kB (11%)

Content Size

2.2 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Haase-food.com main page is 2.2 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. 40% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 99.3 kB

  • Original 111.5 kB
  • After minification 70.9 kB
  • After compression 12.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 40.6 kB, which is 36% 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 99.3 kB or 89% of the original size.

Image Optimization

-4%

Potential reduce by 72.5 kB

  • Original 1.8 MB
  • After minification 1.8 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. Haase Food images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 54.8 kB

  • Original 203.4 kB
  • After minification 201.4 kB
  • After compression 148.6 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 54.8 kB or 27% of the original size.

CSS Optimization

-15%

Potential reduce by 9.5 kB

  • Original 61.9 kB
  • After minification 61.9 kB
  • After compression 52.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. Haase-food.com needs all CSS files to be minified and compressed as it can save up to 9.5 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 58 (75%)

Requests Now

77

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

haase-food.com

haase-food.com

231 ms

shop.haase-food.com

shop.haase-food.com

852 ms

ocb_autosuggest.css

ocb_autosuggest.css

110 ms

superfish.css

superfish.css

217 ms

flexslider.css

flexslider.css

295 ms

pure-min.css

pure-min.css

296 ms

grids-responsive-min.css

grids-responsive-min.css

299 ms

bootstrap.min.css

bootstrap.min.css

410 ms

side-menu.css

side-menu.css

312 ms

oxid.css

oxid.css

429 ms

jscrollpane.css

jscrollpane.css

398 ms

cookieconsent.min.css

cookieconsent.min.css

27 ms

cookieconsent.min.js

cookieconsent.min.js

34 ms

jquery.min.js

jquery.min.js

506 ms

jquery.cookie.js

jquery.cookie.js

402 ms

jquery-ui.min.js

jquery-ui.min.js

629 ms

bootstrap.min.js

bootstrap.min.js

506 ms

ocb_autosuggest.js

ocb_autosuggest.js

526 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

527 ms

hoverIntent.js

hoverIntent.js

535 ms

supersubs.js

supersubs.js

606 ms

superfish.js

superfish.js

618 ms

flexnav-touch.js

flexnav-touch.js

614 ms

ui.js

ui.js

625 ms

navislider.js

navislider.js

672 ms

lazyload.js

lazyload.js

710 ms

oxcenterelementonhover.js

oxcenterelementonhover.js

718 ms

oxsearch.js

oxsearch.js

731 ms

modernizr.custom.min.js

modernizr.custom.min.js

734 ms

oxplaceholderfallback.js

oxplaceholderfallback.js

749 ms

oxinnerlabel.js

oxinnerlabel.js

752 ms

oxmodalpopup.js

oxmodalpopup.js

813 ms

oxinputvalidator.js

oxinputvalidator.js

822 ms

oxequalizer.js

oxequalizer.js

835 ms

oxajax.js

oxajax.js

853 ms

oxcountdown.js

oxcountdown.js

856 ms

oxminibasket.js

oxminibasket.js

859 ms

piwik.js

piwik.js

689 ms

books.svg

books.svg

431 ms

logo.png

logo.png

436 ms

Germany.png

Germany.png

448 ms

United-Kingdom.png

United-Kingdom.png

459 ms

France.png

France.png

476 ms

Spain.png

Spain.png

477 ms

Italy.png

Italy.png

537 ms

Denmark.png

Denmark.png

540 ms

Estonia.png

Estonia.png

551 ms

Greece.png

Greece.png

564 ms

Croatia.png

Croatia.png

586 ms

Latvia.png

Latvia.png

584 ms

Lithuania.png

Lithuania.png

642 ms

30DAD0_1_0.woff

30DAD0_1_0.woff

729 ms

Hungary.png

Hungary.png

628 ms

Poland.png

Poland.png

646 ms

30DAD0_0_0.woff

30DAD0_0_0.woff

760 ms

Portugal.png

Portugal.png

653 ms

Romania.png

Romania.png

636 ms

Slovenia.png

Slovenia.png

642 ms

Slovakia.png

Slovakia.png

659 ms

Finland.png

Finland.png

669 ms

Sweden.png

Sweden.png

670 ms

Czech-Republic.png

Czech-Republic.png

682 ms

Bulgaria.png

Bulgaria.png

659 ms

x.png

x.png

671 ms

logo_hopser-food.png

logo_hopser-food.png

786 ms

mais_banner_2024_480.jpg

mais_banner_2024_480.jpg

669 ms

natais_sale_480.jpg

natais_sale_480.jpg

697 ms

nacho_chips_banner_2024_480.jpg

nacho_chips_banner_2024_480.jpg

708 ms

7029_oel_banner3_2024_480.jpg

7029_oel_banner3_2024_480.jpg

751 ms

mais_banner_august_2023_2_480.jpg

mais_banner_august_2023_2_480.jpg

772 ms

mais_banner_august_2023_3_480.jpg

mais_banner_august_2023_3_480.jpg

760 ms

flexslider-icon.woff

flexslider-icon.woff

695 ms

mais_banner_august_2023_4_480.jpg

mais_banner_august_2023_4_480.jpg

707 ms

1606_banner_20243_480.jpg

1606_banner_20243_480.jpg

783 ms

haase_story_banner_2020_480.jpg

haase_story_banner_2020_480.jpg

829 ms

historie_banner_2020_480.jpg

historie_banner_2020_480.jpg

929 ms

logo-dgp.png

logo-dgp.png

732 ms

haase-icon-story.png

haase-icon-story.png

753 ms

haase-icon-pfeil.png

haase-icon-pfeil.png

758 ms

vatmsg-bg.png

vatmsg-bg.png

793 ms

1606_banner_20243_1240.jpg

1606_banner_20243_1240.jpg

945 ms

mais_banner_2024_1240.jpg

mais_banner_2024_1240.jpg

1303 ms

natais_sale_1240.jpg

natais_sale_1240.jpg

1131 ms

piwik.php

piwik.php

330 ms

Accessibility Review

haase-food.com accessibility score

98

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

Links do not have a discernible name

Best Practices

haase-food.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

haase-food.com SEO score

87

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

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 Haase-food.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 Haase-food.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

haase-food.com

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