Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

ovam.be

Dienstverlening

Page Load Speed

3.5 sec in total

First Response

386 ms

Resources Loaded

2.8 sec

Page Rendered

329 ms

ovam.be screenshot

About Website

Welcome to ovam.be homepage info - get ready to check Ovam best content for Belgium right away, or after learning these important things about ovam.be

De OVAM streeft samen met u naar een duurzaam afval- en materialenbeheer en een propere bodem in Vlaanderen. Selecteer hieronder het thema waar u concrete informatie over zoekt.

Visit ovam.be

Key Findings

We analyzed Ovam.be page load time and found that the first response time was 386 ms and then it took 3.1 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

ovam.be performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value52.7 s

0/100

25%

SI (Speed Index)

Value13.8 s

1/100

10%

TBT (Total Blocking Time)

Value1,870 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.095

91/100

15%

TTI (Time to Interactive)

Value51.5 s

0/100

10%

Network Requests Diagram

ovam.be

386 ms

css_kShW4RPmRstZ3SpIC-ZvVGNFVAi0WEMuCnI0ZkYIaFw.css

170 ms

css_NOrDTOVgfuXvlnYDuDqBTQ7RYeyepdyqD6-L0bBjCA8.css

166 ms

GlobalHeader.css

932 ms

GlobalFooter.css

920 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 62% of them (38 requests) were addressed to the original Ovam.be, 25% (15 requests) were made to Widgets.vlaanderen.be and 5% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Ovam.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (37%)

Content Size

3.1 MB

After Optimization

1.9 MB

In fact, the total size of Ovam.be main page is 3.1 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. 55% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 95.6 kB

  • Original 124.3 kB
  • After minification 119.0 kB
  • After compression 28.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 95.6 kB or 77% of the original size.

Image Optimization

-5%

Potential reduce by 74.2 kB

  • Original 1.5 MB
  • After minification 1.4 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. Ovam images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 654.8 kB

  • Original 978.0 kB
  • After minification 930.7 kB
  • After compression 323.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 654.8 kB or 67% of the original size.

CSS Optimization

-69%

Potential reduce by 339.3 kB

  • Original 491.1 kB
  • After minification 488.1 kB
  • After compression 151.8 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. Ovam.be needs all CSS files to be minified and compressed as it can save up to 339.3 kB or 69% of the original size.

Requests Breakdown

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

Requests Now

55

After Optimization

22

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

Accessibility Review

ovam.be accessibility score

81

Accessibility Issues

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

Image elements do not have [alt] attributes

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

Heading elements are not in a sequentially-descending order

Best Practices

ovam.be 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

ovam.be 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 Ovam.be 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 Ovam.be 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 Ovam. 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: