Tools & Wizards About Us
nivelles.be screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

nivelles.be

Accueil — Nivelles

Page Load Speed

5.1 sec in total

First Response

343 ms

Resources Loaded

3.4 sec

Page Rendered

1.4 sec

nivelles.be screenshot

About Website

Visit nivelles.be now to see the best up-to-date Nivelles content for Belgium and also check out these interesting facts you probably never knew about nivelles.be

Visit nivelles.be

Key Findings

We analyzed Nivelles.be page load time and found that the first response time was 343 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

nivelles.be performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value960 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

nivelles.be

343 ms

www.nivelles.be

730 ms

font-awesome.min.css

67 ms

ods-widgets.min.css

55 ms

faceted-jquery.min.css

166 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 51% of them (33 requests) were addressed to the original Nivelles.be, 17% (11 requests) were made to Actualites.enwallonie.be and 11% (7 requests) were made to Agenda.enwallonie.be. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Actualites.enwallonie.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 130.2 kB (5%)

Content Size

2.9 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 67.3 kB

  • Original 88.0 kB
  • After minification 87.9 kB
  • After compression 20.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 67.3 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 20.2 kB

  • Original 2.0 MB
  • After minification 2.0 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. Nivelles images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 38.6 kB

  • Original 720.5 kB
  • After minification 720.5 kB
  • After compression 681.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. This website has mostly compressed JavaScripts.

CSS Optimization

-24%

Potential reduce by 4.1 kB

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

Requests Breakdown

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

Requests Now

60

After Optimization

26

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nivelles.be

nivelles.be

343 ms

www.nivelles.be

www.nivelles.be

730 ms

font-awesome.min.css

font-awesome.min.css

67 ms

ods-widgets.min.css

ods-widgets.min.css

55 ms

faceted-jquery.min.css

faceted-jquery.min.css

166 ms

faceted-view.min.css

faceted-view.min.css

244 ms

faceted-edit.min.css

faceted-edit.min.css

244 ms

messagesviewlet-plone6.css

messagesviewlet-plone6.css

246 ms

fullscreen.css

fullscreen.css

246 ms

smartweb-common-view-compiled.css

smartweb-common-view-compiled.css

248 ms

smartweb-view-compiled.css

smartweb-view-compiled.css

260 ms

smartweb-webcomponents-compiled.css

smartweb-webcomponents-compiled.css

325 ms

swiper-bundle.min.css

swiper-bundle.min.css

326 ms

theme.css

theme.css

503 ms

@@custom.css

@@custom.css

327 ms

jquery.min.js

jquery.min.js

66 ms

angular.min.js

angular.min.js

67 ms

angular-sanitize.min.js

angular-sanitize.min.js

66 ms

ods-widgets.min.js

ods-widgets.min.js

67 ms

swiper-bundle.min.js

swiper-bundle.min.js

416 ms

smartweb-swiperconfig-compiled.js

smartweb-swiperconfig-compiled.js

344 ms

bundle-remote.min.js

bundle-remote.min.js

404 ms

fullscreen.js

fullscreen.js

405 ms

bundle.min.js

bundle.min.js

739 ms

smartweb-common-view-compiled.js

smartweb-common-view-compiled.js

430 ms

js.cookie-2.0.3.min.js

js.cookie-2.0.3.min.js

486 ms

messagesviewlet.js

messagesviewlet.js

485 ms

patched.web3862.eea.faceted-jquery.min.js

patched.web3862.eea.faceted-jquery.min.js

646 ms

faceted-view.min.js

faceted-view.min.js

535 ms

faceted-edit.min.js

faceted-edit.min.js

567 ms

smartweb-view-compiled.js

smartweb-view-compiled.js

566 ms

smartweb-webcomponents-compiled.js

smartweb-webcomponents-compiled.js

790 ms

theme.js

theme.js

646 ms

bootstrap-icons.css

bootstrap-icons.css

69 ms

css2

css2

52 ms

css2

css2

73 ms

css2

css2

73 ms

css2

css2

73 ms

paysage_vignette

paysage_vignette

583 ms

paysage_vignette

paysage_vignette

742 ms

image-1920-4b6cea8c6941cafa8783733cd2bef447.jpeg

image-1920-4b6cea8c6941cafa8783733cd2bef447.jpeg

273 ms

partyd8ffa871..jpg

partyd8ffa871..jpg

591 ms

image-430-5d2e280b0bee6e45e45c69993bfffc71.png

image-430-5d2e280b0bee6e45e45c69993bfffc71.png

106 ms

image-430-06b38ad1aef4aef0f68297d780e4d3c7.png

image-430-06b38ad1aef4aef0f68297d780e4d3c7.png

106 ms

image-430-33e902eac6528e23880938c5a1c80cea.png

image-430-33e902eac6528e23880938c5a1c80cea.png

105 ms

background_image-750-316378375bb1e8cf4a28c7e76f4e1653.png

background_image-750-316378375bb1e8cf4a28c7e76f4e1653.png

164 ms

paysage_vignette

paysage_vignette

775 ms

paysage_vignette

paysage_vignette

742 ms

paysage_vignette

paysage_vignette

689 ms

paysage_vignette

paysage_vignette

737 ms

paysage_vignette

paysage_vignette

848 ms

paysage_vignette

paysage_vignette

788 ms

paysage_vignette

paysage_vignette

640 ms

paysage_vignette

paysage_vignette

780 ms

paysage_vignette

paysage_vignette

637 ms

paysage_vignette

paysage_vignette

703 ms

paysage_vignette

paysage_vignette

634 ms

paysage_vignette

paysage_vignette

664 ms

paysage_vignette

paysage_vignette

1170 ms

paysage_vignette

paysage_vignette

833 ms

paysage_vignette

paysage_vignette

850 ms

paysage_vignette

paysage_vignette

766 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4nY1M2xYkS.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4nY1M2xYkS.ttf

29 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4nY1M2xYkS.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4nY1M2xYkS.ttf

53 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4nY1M2xYkS.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4nY1M2xYkS.ttf

65 ms

Accessibility Review

nivelles.be accessibility score

91

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

nivelles.be best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

nivelles.be SEO score

77

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

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nivelles.be can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Nivelles.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

nivelles.be

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