Tools & Wizards About Us

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

weda.com

WEDA | Vind je weegschaal of kassa voor retail gebruik

Page Load Speed

10.7 sec in total

First Response

492 ms

Resources Loaded

8.8 sec

Page Rendered

1.4 sec

About Website

Visit weda.com now to see the best up-to-date WEDA content and also check out these interesting facts you probably never knew about weda.com

Vind je weegschaal of kassa voor retail gebruik. Weda helpt je met het vinden van de weegschaal voor je bedrijf of voor persoonlijk gebruik.

Visit weda.com

Key Findings

We analyzed Weda.com page load time and found that the first response time was 492 ms and then it took 10.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

weda.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

44/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value2,100 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.057

98/100

15%

TTI (Time to Interactive)

Value16.9 s

5/100

10%

Network Requests Diagram

weda.com

492 ms

wp-emoji-release.min.js

145 ms

mollie-gateway-icons.min.css

248 ms

style.min.css

281 ms

vendors-style.css

285 ms

Our browser made a total of 170 requests to load all elements on the main page. We found that 80% of them (136 requests) were addressed to the original Weda.com, 3% (5 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Weda.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 603.8 kB (11%)

Content Size

5.4 MB

After Optimization

4.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weda.com main page is 5.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.7 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 112.3 kB

  • Original 137.1 kB
  • After minification 126.1 kB
  • After compression 24.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 112.3 kB or 82% of the original size.

Image Optimization

-8%

Potential reduce by 382.9 kB

  • Original 4.7 MB
  • After minification 4.3 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. WEDA images are well optimized though.

JavaScript Optimization

-22%

Potential reduce by 77.2 kB

  • Original 357.1 kB
  • After minification 357.1 kB
  • After compression 279.9 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 77.2 kB or 22% of the original size.

CSS Optimization

-13%

Potential reduce by 31.4 kB

  • Original 243.6 kB
  • After minification 243.6 kB
  • After compression 212.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. Weda.com needs all CSS files to be minified and compressed as it can save up to 31.4 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 109 (68%)

Requests Now

161

After Optimization

52

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

weda.com accessibility score

81

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.

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

weda.com 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

High

Missing source maps for large first-party JavaScript

SEO Factors

weda.com SEO score

86

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

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

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weda.com can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Weda.com 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 data is detected on the main page of WEDA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: