Tools & Wizards About Us
was-wir-essen.de screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

was-wir-essen.de

was-wir-essen-Blog- BZfE

Page Load Speed

3.8 sec in total

First Response

407 ms

Resources Loaded

2.5 sec

Page Rendered

946 ms

was-wir-essen.de screenshot

About Website

Click here to check amazing Was Wir Essen content for Germany. Otherwise, check out these important facts you probably never knew about was-wir-essen.de

„Lebensmittel entdecken“, „mit Freude gärtnern“ oder „lecker mit der Familie essen“: Zu diesen Themen bloggen drei junge Frauen für den aid infodienst.

Visit was-wir-essen.de

Key Findings

We analyzed Was-wir-essen.de page load time and found that the first response time was 407 ms and then it took 3.4 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

was-wir-essen.de performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

was-wir-essen.de

407 ms

www.was-wir-essen.de

387 ms

7630.css

204 ms

widgets.js

120 ms

1140.jpg

639 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 81% of them (34 requests) were addressed to the original Was-wir-essen.de, 7% (3 requests) were made to Platform.twitter.com and 7% (3 requests) were made to Shop.aid.de. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Was-wir-essen.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 106.6 kB (17%)

Content Size

640.6 kB

After Optimization

534.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Was-wir-essen.de main page is 640.6 kB. 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 511.9 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 15.6 kB

  • Original 21.4 kB
  • After minification 20.5 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 15.6 kB or 73% of the original size.

Image Optimization

-2%

Potential reduce by 8.9 kB

  • Original 511.9 kB
  • After minification 503.0 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. Was Wir Essen images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 35.7 kB

  • Original 54.9 kB
  • After minification 54.9 kB
  • After compression 19.1 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 35.7 kB or 65% of the original size.

CSS Optimization

-88%

Potential reduce by 46.3 kB

  • Original 52.4 kB
  • After minification 33.0 kB
  • After compression 6.1 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. Was-wir-essen.de needs all CSS files to be minified and compressed as it can save up to 46.3 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (25%)

Requests Now

40

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Was Wir Essen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.

Network Requests Diagram

was-wir-essen.de

was-wir-essen.de

407 ms

www.was-wir-essen.de

www.was-wir-essen.de

387 ms

7630.css

7630.css

204 ms

widgets.js

widgets.js

120 ms

1140.jpg

1140.jpg

639 ms

1218.jpg

1218.jpg

626 ms

3440.jpg

3440.jpg

491 ms

btn_search.gif

btn_search.gif

191 ms

aid_wwe_1_logo.png

aid_wwe_1_logo.png

285 ms

aid_wwe_2_bild.png

aid_wwe_2_bild.png

473 ms

header_right.jpg

header_right.jpg

201 ms

nav_erzeu.jpg

nav_erzeu.jpg

200 ms

nav_verar.jpg

nav_verar.jpg

200 ms

nav_einkauf.jpg

nav_einkauf.jpg

382 ms

nav_zuberei.jpg

nav_zuberei.jpg

387 ms

nav_gesund.jpg

nav_gesund.jpg

388 ms

nav_verbrau.jpg

nav_verbrau.jpg

386 ms

bg_right_breadcrumb_curve.gif

bg_right_breadcrumb_curve.gif

470 ms

bg_left_breadcrumb_curve.gif

bg_left_breadcrumb_curve.gif

601 ms

news_bg_left.jpg

news_bg_left.jpg

600 ms

news_bg_right.jpg

news_bg_right.jpg

601 ms

energy-drink_dose_strohhalm_100.jpg

energy-drink_dose_strohhalm_100.jpg

768 ms

ico_arrow_double_right.gif

ico_arrow_double_right.gif

769 ms

ico_arrow_right.gif

ico_arrow_right.gif

768 ms

trauben_kernlos_100.jpg

trauben_kernlos_100.jpg

795 ms

frau_jung_obst_hamburger_100.jpg

frau_jung_obst_hamburger_100.jpg

892 ms

tomaten_sorten_100.jpg

tomaten_sorten_100.jpg

893 ms

kartoffeln_kochtopf_100.jpg

kartoffeln_kochtopf_100.jpg

963 ms

kartoffeln_schale_100.jpg

kartoffeln_schale_100.jpg

997 ms

blumenkohlcurry_150.jpg

blumenkohlcurry_150.jpg

996 ms

footericons_20.png

footericons_20.png

995 ms

logo_aid_fuer_wwe.gif

logo_aid_fuer_wwe.gif

1092 ms

bg_left_bottom_curve.gif

bg_left_bottom_curve.gif

1092 ms

bg_right_top_curve.gif

bg_right_top_curve.gif

1157 ms

logo_medienshop.jpg

logo_medienshop.jpg

1186 ms

355_100.jpg

355_100.jpg

1185 ms

bg_right_bottom_curve.gif

bg_right_bottom_curve.gif

1186 ms

piwik.js

piwik.js

413 ms

button.b059c0eb61ea902a882e5c5b3c66a17a.js

button.b059c0eb61ea902a882e5c5b3c66a17a.js

71 ms

tweet_button.baa54ded21a982344c4ced326592f3de.de.html

tweet_button.baa54ded21a982344c4ced326592f3de.de.html

124 ms

jot

jot

89 ms

print.css

print.css

200 ms

Accessibility Review

was-wir-essen.de accessibility score

92

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

[aria-hidden="true"] elements contain focusable descendents

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

was-wir-essen.de 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

was-wir-essen.de SEO score

76

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

High

Page is blocked from indexing

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 Was-wir-essen.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 Was-wir-essen.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

was-wir-essen.de

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