Tools & Wizards About Us

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 50

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

widex.de

Keller & Kalmbach | C-Teile-Management & Onlineshop

Page Load Speed

3.7 sec in total

First Response

470 ms

Resources Loaded

3.2 sec

Page Rendered

71 ms

About Website

Click here to check amazing Widex content. Otherwise, check out these important facts you probably never knew about widex.de

Keller & Kalmbach ist der Spezialist für Verbindungselemente und Befestigungstechnik. Wir sind Experte, wenn es um intelligentes C-Teile-Management geht.

Visit widex.de

Key Findings

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

widex.de performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value650 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value0.063

97/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

www.keller-kalmbach.de

470 ms

app.js

719 ms

kuk_responsive.css

363 ms

addons_responsive.css

333 ms

all.css

28 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Widex.de, 8% (6 requests) were made to Cloud.ccm19.de and 1% (1 request) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (796 ms) relates to the external source Keller-kalmbach.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 185.0 kB (43%)

Content Size

432.3 kB

After Optimization

247.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Widex.de main page is 432.3 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. 25% of websites need less resources to load. Images take 209.4 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 184.6 kB

  • Original 209.1 kB
  • After minification 129.2 kB
  • After compression 24.5 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 79.9 kB, which is 38% 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 184.6 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 403 B

  • Original 209.4 kB
  • After minification 209.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. Widex images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 5 B

  • Original 2.3 kB
  • After minification 2.3 kB
  • After compression 2.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 11.6 kB
  • After minification 11.6 kB
  • After compression 11.6 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. Widex.de has all CSS files already compressed.

Requests Breakdown

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

Requests Now

73

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

widex.de accessibility score

50

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-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

High

[aria-*] attributes are not valid or misspelled

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

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.

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

High

Some elements have a [tabindex] value greater than 0

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

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

widex.de SEO score

81

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Widex.de 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 Widex.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 Widex. 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: