Tools & Wizards About Us
waagen.lu screenshot

Report Summary

  • 82

    Performance

    Renders faster than
    87% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

waagen.lu

waagen.lu - Shop für Waagen und Software | Smarter wiegen

Page Load Speed

3.1 sec in total

First Response

224 ms

Resources Loaded

2.7 sec

Page Rendered

208 ms

waagen.lu screenshot

About Website

Click here to check amazing Waagen content for Germany. Otherwise, check out these important facts you probably never knew about waagen.lu

Wir versenden Waagen seit 2003 günstig, schnell und sicher in alle Länder der EU und in die Schweiz. Geprüfter Shop mit Geld-zurück-Garantie (TS).

Visit waagen.lu

Key Findings

We analyzed Waagen.lu page load time and found that the first response time was 224 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

waagen.lu performance score

82

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

60/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.7 s

90/100

10%

Network Requests Diagram

waagen.lu

224 ms

waagen.lu

527 ms

www.waagen.lu

853 ms

screen.css

126 ms

article.js

246 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 95% of them (38 requests) were addressed to the original Waagen.lu, 3% (1 request) were made to Static.getclicky.com and 3% (1 request) were made to In.getclicky.com. The less responsive or slowest element that took the longest time to load (853 ms) belongs to the original domain Waagen.lu.

Page Optimization Overview & Recommendations

Page size can be reduced by 35.3 kB (16%)

Content Size

216.5 kB

After Optimization

181.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Waagen.lu main page is 216.5 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. 20% of websites need less resources to load. Images take 171.5 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 28.1 kB

  • Original 36.8 kB
  • After minification 34.2 kB
  • After compression 8.7 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 28.1 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 4.4 kB

  • Original 171.5 kB
  • After minification 167.1 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. Waagen images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 174 B

  • Original 563 B
  • After minification 563 B
  • After compression 389 B

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 174 B or 31% of the original size.

CSS Optimization

-34%

Potential reduce by 2.6 kB

  • Original 7.7 kB
  • After minification 7.2 kB
  • After compression 5.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. Waagen.lu needs all CSS files to be minified and compressed as it can save up to 2.6 kB or 34% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (22%)

Requests Now

37

After Optimization

29

  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Waagen. 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

waagen.lu

waagen.lu

224 ms

waagen.lu

waagen.lu

527 ms

www.waagen.lu

www.waagen.lu

853 ms

screen.css

screen.css

126 ms

article.js

article.js

246 ms

blank.png

blank.png

311 ms

smartlux_logo_45.png

smartlux_logo_45.png

322 ms

DEU.gif

DEU.gif

314 ms

cart_blue.gif

cart_blue.gif

336 ms

online.gif

online.gif

333 ms

js

js

33 ms

paketwaage-ohaus-courier-5000-c52-r-165.jpg

paketwaage-ohaus-courier-5000-c52-r-165.jpg

361 ms

paketwaage-ohaus-courier-7000-c71-r-165.jpg

paketwaage-ohaus-courier-7000-c71-r-165.jpg

425 ms

geeichte-plattformwaage-ohaus-defender-5000-m-edelstahl-dual-range-td52xw-ql-165.png

geeichte-plattformwaage-ohaus-defender-5000-m-edelstahl-dual-range-td52xw-ql-165.png

427 ms

geeichte-plattformwaage-ohaus-defender-3000-m-i-d33p-standard-mit-stativ-165.png

geeichte-plattformwaage-ohaus-defender-3000-m-i-d33p-standard-mit-stativ-165.png

440 ms

M.gif

M.gif

452 ms

ohaus-navigator-nv-nvt-waage-165.jpg

ohaus-navigator-nv-nvt-waage-165.jpg

462 ms

ohaus-ranger-3000-digitalwaage-165.jpg

ohaus-ranger-3000-digitalwaage-165.jpg

482 ms

ohaus-ranger-7000-industrie-praezisionswaage-165.jpg

ohaus-ranger-7000-industrie-praezisionswaage-165.jpg

542 ms

ej-praezisionswaage-165.jpg

ej-praezisionswaage-165.jpg

552 ms

FX-i-laborwaage.jpg

FX-i-laborwaage.jpg

556 ms

ohaus-pioneer-precision-px-praezisionswaage-180-165.jpg

ohaus-pioneer-precision-px-praezisionswaage-180-165.jpg

578 ms

mikrowaage-bm-165.jpg

mikrowaage-bm-165.jpg

585 ms

gx-a-ec-geeichte-praezisionswaage-0_1g-165.png

gx-a-ec-geeichte-praezisionswaage-0_1g-165.png

705 ms

geeichte-ladenwaage-kern-rpb-standard-version-165.png

geeichte-ladenwaage-kern-rpb-standard-version-165.png

660 ms

geeichte-juwelierwaage-ohaus-scout-sjx1502m.png

geeichte-juwelierwaage-ohaus-scout-sjx1502m.png

671 ms

ohaus-ranger-3000-geeicht-165.png

ohaus-ranger-3000-geeicht-165.png

691 ms

geeichte-waage-hl-3000lwp-ec.png

geeichte-waage-hl-3000lwp-ec.png

699 ms

visa-master-paypal-barzahlen-139x23.png

visa-master-paypal-barzahlen-139x23.png

709 ms

kern-premium-consulting-partner-120.png

kern-premium-consulting-partner-120.png

776 ms

ohaus-vip-partner-logo-240.png

ohaus-vip-partner-logo-240.png

788 ms

waagen-marken-120-2023.png

waagen-marken-120-2023.png

814 ms

waagen_logo_s.gif

waagen_logo_s.gif

691 ms

global_nav_bg.gif

global_nav_bg.gif

695 ms

global_nav_a_bg.png

global_nav_a_bg.png

699 ms

nav_arrow_off.gif

nav_arrow_off.gif

762 ms

check_white.gif

check_white.gif

773 ms

FRA.gif

FRA.gif

798 ms

in.php

in.php

106 ms

print.css

print.css

124 ms

Accessibility Review

waagen.lu accessibility score

72

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

High

Some elements have a [tabindex] value greater than 0

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Form elements do not have associated labels

Best Practices

waagen.lu best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

waagen.lu 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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Waagen.lu 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 Waagen.lu main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

waagen.lu

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