Tools & Wizards About Us
ovam.be screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

ovam.be

Dienstverlening

Page Load Speed

8.7 sec in total

First Response

296 ms

Resources Loaded

5.8 sec

Page Rendered

2.6 sec

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 296 ms and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

ovam.be performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value36.9 s

0/100

25%

SI (Speed Index)

Value18.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,630 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.079

94/100

15%

TTI (Time to Interactive)

Value43.3 s

0/100

10%

Network Requests Diagram

ovam.be

296 ms

ovam.be

373 ms

ovam.vlaanderen.be

1005 ms

matomo.js

100 ms

clay.css

1606 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Ovam.be, 77% (37 requests) were made to Ovam.vlaanderen.be and 10% (5 requests) were made to Prod.widgets.burgerprofiel.vlaanderen.be. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Ovam.vlaanderen.be.

Page Optimization Overview & Recommendations

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

Content Size

16.7 MB

After Optimization

15.7 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ovam.be main page is 16.7 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. Images take 16.1 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 57.9 kB

  • Original 71.6 kB
  • After minification 63.6 kB
  • After compression 13.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. This page needs HTML code to be minified as it can gain 8.0 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 57.9 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 573.5 kB

  • Original 16.1 MB
  • After minification 15.5 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

-73%

Potential reduce by 360.7 kB

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

Requests Breakdown

Number of requests can be reduced by 20 (50%)

Requests Now

40

After Optimization

20

  • Images
  • JavaScript
  • CSS

The browser has sent 40 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 14 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ovam.be

ovam.be

296 ms

ovam.be

ovam.be

373 ms

ovam.vlaanderen.be

ovam.vlaanderen.be

1005 ms

matomo.js

matomo.js

100 ms

clay.css

clay.css

1606 ms

main.css

main.css

534 ms

combo

combo

401 ms

js_loader_config

js_loader_config

280 ms

combo

combo

1232 ms

js_bundle_config

js_bundle_config

370 ms

main.css

main.css

1414 ms

index.js

index.js

471 ms

index.js

index.js

424 ms

embed

embed

526 ms

copypastesubscribeformlogic.js

copypastesubscribeformlogic.js

30 ms

embed

embed

538 ms

main.css

main.css

373 ms

main.css

main.css

397 ms

main.css

main.css

463 ms

main.css

main.css

480 ms

main.js

main.js

538 ms

matomo.php

matomo.php

430 ms

configs.php

configs.php

387 ms

logo_be.png

logo_be.png

107 ms

cc486880-2465-77bd-798f-9abdc79d7624

cc486880-2465-77bd-798f-9abdc79d7624

181 ms

index.min.js

index.min.js

327 ms

noise-white-light.png

noise-white-light.png

182 ms

noise-black-light.png

noise-black-light.png

181 ms

87bea949-b72c-7e8f-d8ec-ffc87f8c5988

87bea949-b72c-7e8f-d8ec-ffc87f8c5988

522 ms

33a81bbf-4278-ff84-63e0-00f6c0bfe6b5

33a81bbf-4278-ff84-63e0-00f6c0bfe6b5

442 ms

22a4c721-eef4-7a82-bf86-de92998931cd

22a4c721-eef4-7a82-bf86-de92998931cd

718 ms

9a26c5fc-d2e0-81c2-c0fb-c5c5cc342cd3

9a26c5fc-d2e0-81c2-c0fb-c5c5cc342cd3

2513 ms

1a5c9ab2-5ca6-7a1c-71f6-1c0a18d27192

1a5c9ab2-5ca6-7a1c-71f6-1c0a18d27192

346 ms

e6ab3b84-95ea-d687-9a9b-91806ab99ab3

e6ab3b84-95ea-d687-9a9b-91806ab99ab3

1462 ms

6c636a1d-395c-623d-30cf-020f206b86f3

6c636a1d-395c-623d-30cf-020f206b86f3

1253 ms

FlandersArtSans-Regular.woff

FlandersArtSans-Regular.woff

534 ms

FlandersArtSans-Medium.woff

FlandersArtSans-Medium.woff

614 ms

FlandersArtSans-Light.woff

FlandersArtSans-Light.woff

626 ms

FlandersArtSans-Bold.woff

FlandersArtSans-Bold.woff

704 ms

remixicon.woff

remixicon.woff

729 ms

714da7c9-12cf-1cba-49f3-d8cc1fb87f3c

714da7c9-12cf-1cba-49f3-d8cc1fb87f3c

781 ms

c70b0eaa-1588-3d92-18fe-afbf776b6121

c70b0eaa-1588-3d92-18fe-afbf776b6121

1351 ms

a8016a5c-929d-7fda-2f45-7c8dcb5214b1

a8016a5c-929d-7fda-2f45-7c8dcb5214b1

889 ms

e5725b98-857b-352e-8668-b0c79434f9fe

e5725b98-857b-352e-8668-b0c79434f9fe

854 ms

24d0ba68-c779-2a6e-be8a-c8a15bfea5dc

24d0ba68-c779-2a6e-be8a-c8a15bfea5dc

937 ms

b30a2a16-66f4-fbde-6c15-3a36f45cafb7

b30a2a16-66f4-fbde-6c15-3a36f45cafb7

966 ms

1021 ms

1029 ms

Accessibility Review

ovam.be accessibility score

88

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

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

93

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

    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

ovam.be

Open Graph data is detected on the main page of Ovam. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: