Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

wedi.de

wedi Systemwelt - Ganzheitliche Lösungen für modulare Badkonzepte

Page Load Speed

4.5 sec in total

First Response

320 ms

Resources Loaded

3.6 sec

Page Rendered

569 ms

wedi.de screenshot

About Website

Welcome to wedi.de homepage info - get ready to check Wedi best content for Germany right away, or after learning these important things about wedi.de

Hier finden Sie Bauplatten Lösungen, bodengleiche Duschen, Dampfbäder, Badmöbel, Wellnessobjekte und wissenswertes zur Verarbeitung und Technik.

Visit wedi.de

Key Findings

We analyzed Wedi.de page load time and found that the first response time was 320 ms and then it took 4.2 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

wedi.de performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value6.0 s

46/100

10%

TBT (Total Blocking Time)

Value850 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0.862

4/100

15%

TTI (Time to Interactive)

Value20.6 s

2/100

10%

Network Requests Diagram

wedi.de

320 ms

www.wedi.net

693 ms

merged-12622a8c8a141fc116e0728e441f5cee-e8f1b37bc66282c17923660ca9064dcb.css.gzip

278 ms

jquery-1.11.0.min-7c2fdf09c2b31c1f118bc1ddf8f5b267.js.gzip

372 ms

jquery-migrate-1.2.1.min.js

15 ms

Our browser made a total of 134 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wedi.de, 93% (125 requests) were made to Wedi.net and 4% (6 requests) were made to Scontent-fra5-2.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Scontent-fra5-2.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 189.8 kB (5%)

Content Size

3.9 MB

After Optimization

3.7 MB

In fact, the total size of Wedi.de main page is 3.9 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. Images take 3.7 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 137.0 kB

  • Original 157.3 kB
  • After minification 119.1 kB
  • After compression 20.4 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 38.2 kB, which is 24% 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 137.0 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 43.6 kB

  • Original 3.7 MB
  • After minification 3.6 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. Wedi images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 9.2 kB

  • Original 34.5 kB
  • After minification 34.5 kB
  • After compression 25.3 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 9.2 kB or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 60 (47%)

Requests Now

129

After Optimization

69

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

Accessibility Review

wedi.de accessibility score

76

Accessibility Issues

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

wedi.de SEO score

79

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

robots.txt is not valid

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 Wedi.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 Wedi.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 Wedi. 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: