Tools & Wizards About Us
weissenfels.net screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

weissenfels.net

Technische Produkte für Haus und Industrie - Handelsagentur Udo Weißenfels

Page Load Speed

4 sec in total

First Response

597 ms

Resources Loaded

3.1 sec

Page Rendered

275 ms

weissenfels.net screenshot

About Website

Welcome to weissenfels.net homepage info - get ready to check Weissenfels best content right away, or after learning these important things about weissenfels.net

Handelsagentur Udo Weißenfels ✓ über 20 Jahre Erfahrung ✓ große Auswahl an technischen Produkten ✓ faire Preise ✓ international ✓ Wir freuen uns auf Sie!

Visit weissenfels.net

Key Findings

We analyzed Weissenfels.net page load time and found that the first response time was 597 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

weissenfels.net performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value7.2 s

29/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.329

35/100

15%

TTI (Time to Interactive)

Value9.3 s

32/100

10%

Network Requests Diagram

weissenfels.net

597 ms

content.css

103 ms

slideshow.css

204 ms

cookieconsent.min.css

271 ms

jquery.fancybox.min.css

290 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 87% of them (53 requests) were addressed to the original Weissenfels.net, 3% (2 requests) were made to Platform.twitter.com and 3% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (758 ms) belongs to the original domain Weissenfels.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 73.3 kB (6%)

Content Size

1.3 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weissenfels.net main page is 1.3 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. 45% of websites need less resources to load. Images take 953.9 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 39.3 kB

  • Original 50.5 kB
  • After minification 46.7 kB
  • After compression 11.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. 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 39.3 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 8.0 kB

  • Original 953.9 kB
  • After minification 945.9 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. Weissenfels images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 8.1 kB

  • Original 250.5 kB
  • After minification 250.4 kB
  • After compression 242.4 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

-24%

Potential reduce by 17.8 kB

  • Original 75.8 kB
  • After minification 75.8 kB
  • After compression 57.9 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. Weissenfels.net needs all CSS files to be minified and compressed as it can save up to 17.8 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (57%)

Requests Now

58

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weissenfels.net

weissenfels.net

597 ms

content.css

content.css

103 ms

slideshow.css

slideshow.css

204 ms

cookieconsent.min.css

cookieconsent.min.css

271 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

290 ms

jquery.min.js

jquery.min.js

389 ms

jquery-noconflict.js

jquery-noconflict.js

292 ms

jquery-migrate.min.js

jquery-migrate.min.js

306 ms

mootools-core.js

mootools-core.js

401 ms

core.js

core.js

366 ms

mootools-mobile.js

mootools-mobile.js

401 ms

rokmediaqueries.js

rokmediaqueries.js

401 ms

roksprocket.js

roksprocket.js

415 ms

moofx.js

moofx.js

559 ms

features.js

features.js

500 ms

slideshow.js

slideshow.js

501 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

607 ms

cookieconsent.min.js

cookieconsent.min.js

504 ms

init.js

init.js

520 ms

bootstrap.css

bootstrap.css

625 ms

joomlaplates.css

joomlaplates.css

606 ms

theme.css

theme.css

633 ms

custom.css

custom.css

623 ms

uikit.js

uikit.js

658 ms

autocomplete.js

autocomplete.js

711 ms

search.js

search.js

712 ms

tooltip.js

tooltip.js

733 ms

sticky.js

sticky.js

722 ms

social.js

social.js

730 ms

theme.js

theme.js

758 ms

weissenfels-call.png

weissenfels-call.png

119 ms

weissenfels-logo.png

weissenfels-logo.png

119 ms

weissenfels-logo-mobil.png

weissenfels-logo-mobil.png

118 ms

image_weissenfels_2.jpg

image_weissenfels_2.jpg

491 ms

image_weissenfels_1.jpg

image_weissenfels_1.jpg

276 ms

image_weissenfels_3.jpg

image_weissenfels_3.jpg

287 ms

image_weissenfels_4.jpg

image_weissenfels_4.jpg

393 ms

loeschwasser-behaelter.png

loeschwasser-behaelter.png

219 ms

KAT_Trinkwassertank_weissenfels_.jpg

KAT_Trinkwassertank_weissenfels_.jpg

315 ms

KAT_Pellettank_Weissenfels.jpg

KAT_Pellettank_Weissenfels.jpg

320 ms

flexible-behaelter.png

flexible-behaelter.png

372 ms

regenwasser-nutzung.png

regenwasser-nutzung.png

478 ms

KAT_Waermepumpe-weissenfels.jpg

KAT_Waermepumpe-weissenfels.jpg

421 ms

heizung-sanitaer.png

heizung-sanitaer.png

419 ms

begleitheizung.png

begleitheizung.png

472 ms

hebekissen.png

hebekissen.png

493 ms

rettungsprodukte.png

rettungsprodukte.png

523 ms

oelsperren.png

oelsperren.png

518 ms

fliesenheizung.png

fliesenheizung.png

574 ms

onlineshop-banner.jpg

onlineshop-banner.jpg

669 ms

matomo.js

matomo.js

586 ms

widgets.js

widgets.js

92 ms

plusone.js

plusone.js

52 ms

sdk.js

sdk.js

28 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

535 ms

sdk.js

sdk.js

4 ms

56 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

7 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

57 ms

settings

settings

99 ms

matomo.php

matomo.php

654 ms

Accessibility Review

weissenfels.net accessibility score

94

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

weissenfels.net 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

weissenfels.net SEO score

91

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 Weissenfels.net 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 Weissenfels.net 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

weissenfels.net

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