Tools & Wizards About Us
werding.de screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

werding.de

Werding Edelstahlbeschläge Fertigung v. Türgriffen u. Stoßgriffen

Page Load Speed

6.2 sec in total

First Response

313 ms

Resources Loaded

5.6 sec

Page Rendered

292 ms

werding.de screenshot

About Website

Welcome to werding.de homepage info - get ready to check Werding best content right away, or after learning these important things about werding.de

Klein u. Großserien v. Türgriffen ➜ Stoßgriffe, Rammschutzbügel u. Absturzsicherungen. Türgriffe u. ★ Edelstahl Türbeschläge als Spezialanfertigungen.

Visit werding.de

Key Findings

We analyzed Werding.de page load time and found that the first response time was 313 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

werding.de performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value1,860 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.069

96/100

15%

TTI (Time to Interactive)

Value10.7 s

22/100

10%

Network Requests Diagram

werding.de

313 ms

www.werding.de

732 ms

widgetkit-faf47e55.css

325 ms

mootools-core.js

538 ms

core.js

218 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 98% of them (81 requests) were addressed to the original Werding.de, 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Werding.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 776.7 kB (51%)

Content Size

1.5 MB

After Optimization

731.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Werding.de main page is 1.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. 40% of websites need less resources to load. Javascripts take 756.2 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 50.2 kB

  • Original 60.7 kB
  • After minification 58.6 kB
  • After compression 10.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. 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 50.2 kB or 83% of the original size.

Image Optimization

-7%

Potential reduce by 33.5 kB

  • Original 480.5 kB
  • After minification 447.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. Werding images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 515.7 kB

  • Original 756.2 kB
  • After minification 740.4 kB
  • After compression 240.5 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 515.7 kB or 68% of the original size.

CSS Optimization

-84%

Potential reduce by 177.5 kB

  • Original 211.0 kB
  • After minification 173.9 kB
  • After compression 33.5 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. Werding.de needs all CSS files to be minified and compressed as it can save up to 177.5 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

79

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

werding.de

werding.de

313 ms

www.werding.de

www.werding.de

732 ms

widgetkit-faf47e55.css

widgetkit-faf47e55.css

325 ms

mootools-core.js

mootools-core.js

538 ms

core.js

core.js

218 ms

caption.js

caption.js

226 ms

jquery.js

jquery.js

677 ms

widgetkit-ea74605b.js

widgetkit-ea74605b.js

322 ms

mootools-more.js

mootools-more.js

966 ms

reset.css

reset.css

450 ms

layout.css

layout.css

531 ms

typography.css

typography.css

556 ms

menus.css

menus.css

664 ms

modules.css

modules.css

747 ms

system.css

system.css

755 ms

extensions.css

extensions.css

749 ms

style.css

style.css

884 ms

blue.css

blue.css

894 ms

custom.css

custom.css

1173 ms

warp.js

warp.js

1005 ms

accordionmenu.js

accordionmenu.js

1004 ms

dropdownmenu.js

dropdownmenu.js

1104 ms

spotlight.js

spotlight.js

1119 ms

template.js

template.js

1181 ms

reset.css

reset.css

1185 ms

style.css

style.css

1187 ms

grid.css

grid.css

1325 ms

nivo-slider.css

nivo-slider.css

1345 ms

superfish.css

superfish.css

1386 ms

search.js

search.js

3145 ms

superfish.js

superfish.js

1312 ms

jquery.nivo.slider.js

jquery.nivo.slider.js

1433 ms

cufon-yui.js

cufon-yui.js

1571 ms

cufon-replace.js

cufon-replace.js

1481 ms

Lane_-_Narrow_400.font.js

Lane_-_Narrow_400.font.js

1617 ms

lightbox.js

lightbox.js

1032 ms

mediaelement-and-player.js

mediaelement-and-player.js

1281 ms

spotlight.js

spotlight.js

1092 ms

system.css

system.css

890 ms

system.css

system.css

936 ms

page_bg.jp

page_bg.jp

115 ms

bg.jpg

bg.jpg

323 ms

bg-2.jpg

bg-2.jpg

226 ms

logo.png

logo.png

227 ms

frontale-2.gif

frontale-2.gif

436 ms

searchbox_bg.png

searchbox_bg.png

335 ms

searchbox_magnifier.png

searchbox_magnifier.png

441 ms

searchbox_reset.png

searchbox_reset.png

450 ms

ue_b.png

ue_b.png

538 ms

schalengriffe.jpg

schalengriffe.jpg

1448 ms

objektbau-tuergriffe.jpg

objektbau-tuergriffe.jpg

773 ms

rammschutzbuegel.jpg

rammschutzbuegel.jpg

764 ms

design-tuergriffe.jpg

design-tuergriffe.jpg

805 ms

fingerscan-tuergriffe.jpg

fingerscan-tuergriffe.jpg

1137 ms

kamera-tuergriffe.jpg

kamera-tuergriffe.jpg

1108 ms

naturholz-tuergriffe.jpg

naturholz-tuergriffe.jpg

1139 ms

schalengriffe.jpg

schalengriffe.jpg

1445 ms

objektbau-tuergriffe-2.jpg

objektbau-tuergriffe-2.jpg

1446 ms

rammschutz.jpg

rammschutz.jpg

1446 ms

design-tuergriffe.jpg

design-tuergriffe.jpg

1447 ms

fingerscan-tuergriffe-1.jpg

fingerscan-tuergriffe-1.jpg

1545 ms

naturholz-tuergriffe.jpg

naturholz-tuergriffe.jpg

1577 ms

kamera-tuergriffe-2016.png

kamera-tuergriffe-2016.png

2416 ms

rostfrei_grau.png

rostfrei_grau.png

1610 ms

bg-form-top.png

bg-form-top.png

440 ms

marker-top.png

marker-top.png

572 ms

bg-menu.jpg

bg-menu.jpg

572 ms

bg-slider.jpg

bg-slider.jpg

608 ms

arrow.png

arrow.png

642 ms

button_arrow.png

button_arrow.png

652 ms

marker-1.gif

marker-1.gif

789 ms

footer_menu_bg.png

footer_menu_bg.png

794 ms

footer_anchor.png

footer_anchor.png

833 ms

social_icons.png

social_icons.png

1077 ms

footermenu_item_bg.png

footermenu_item_bg.png

862 ms

ga.js

ga.js

175 ms

slideshow.js

slideshow.js

1023 ms

search_bg.png

search_bg.png

757 ms

__utm.gif

__utm.gif

13 ms

more.gif

more.gif

224 ms

span.png

span.png

214 ms

bull-h.png

bull-h.png

221 ms

bull.png

bull.png

228 ms

Accessibility Review

werding.de accessibility score

84

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

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.

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

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

SEO Factors

werding.de SEO score

92

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

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

werding.de

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