Tools & Wizards About Us
forem.be screenshot

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

forem.be

Emploi Formation Wallonie - Espace Citoyens - Le Forem

Page Load Speed

4.7 sec in total

First Response

526 ms

Resources Loaded

3.5 sec

Page Rendered

642 ms

forem.be screenshot

About Website

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

Retrouvez les offres d'emploi, les formations, les services et toutes les infos du Forem utiles et nécessaires pour les citoyens, demandeurs d'emploi et travailleurs

Visit forem.be

Key Findings

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

Performance Metrics

forem.be performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value10,620 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.807

5/100

15%

TTI (Time to Interactive)

Value22.2 s

1/100

10%

Network Requests Diagram

forem.be

526 ms

www.leforem.be

947 ms

clientlib-dependencies.lc-4f19849f1e55701ab8b6ef569685f13d-lc.min.css

182 ms

clientlib-base.lc-70267407c54bfd3d524dbb8e5bf56862-lc.min.css

360 ms

clientlib-site.lc-1b9c9d064a20867e86bd8d08dbcdf203-lc.min.css

364 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Forem.be, 98% (65 requests) were made to Leforem.be. The less responsive or slowest element that took the longest time to load (947 ms) relates to the external source Leforem.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 144.3 kB (7%)

Content Size

2.1 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 73.0 kB

  • Original 88.4 kB
  • After minification 70.0 kB
  • After compression 15.3 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 18.4 kB, which is 21% 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 73.0 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 39.3 kB

  • Original 1.8 MB
  • After minification 1.7 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. Forem images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 30.4 kB

  • Original 193.9 kB
  • After minification 192.9 kB
  • After compression 163.5 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 30.4 kB or 16% of the original size.

CSS Optimization

-31%

Potential reduce by 1.7 kB

  • Original 5.4 kB
  • After minification 5.4 kB
  • After compression 3.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. Forem.be needs all CSS files to be minified and compressed as it can save up to 1.7 kB or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (37%)

Requests Now

57

After Optimization

36

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

forem.be

forem.be

526 ms

www.leforem.be

www.leforem.be

947 ms

clientlib-dependencies.lc-4f19849f1e55701ab8b6ef569685f13d-lc.min.css

clientlib-dependencies.lc-4f19849f1e55701ab8b6ef569685f13d-lc.min.css

182 ms

clientlib-base.lc-70267407c54bfd3d524dbb8e5bf56862-lc.min.css

clientlib-base.lc-70267407c54bfd3d524dbb8e5bf56862-lc.min.css

360 ms

clientlib-site.lc-1b9c9d064a20867e86bd8d08dbcdf203-lc.min.css

clientlib-site.lc-1b9c9d064a20867e86bd8d08dbcdf203-lc.min.css

364 ms

clientlib-foremWebComponent.lc-ca4b12963e37046e07d88faffe3bb629-lc.min.css

clientlib-foremWebComponent.lc-ca4b12963e37046e07d88faffe3bb629-lc.min.css

628 ms

clientlib-site.lc-0b6d7f5383ce0d0cd2cc28a279a41139-lc.min.css

clientlib-site.lc-0b6d7f5383ce0d0cd2cc28a279a41139-lc.min.css

380 ms

tarteaucitron.js

tarteaucitron.js

287 ms

swiped-events.js

swiped-events.js

195 ms

tacjs.prod.js

tacjs.prod.js

290 ms

polyfill.js

polyfill.js

369 ms

fn.js

fn.js

376 ms

events-new-design.js

events-new-design.js

381 ms

crc-new-design.js

crc-new-design.js

387 ms

offersearch.js

offersearch.js

678 ms

chatbot.prod.js

chatbot.prod.js

464 ms

cobrowsing.prod.js

cobrowsing.prod.js

471 ms

newsletter.js

newsletter.js

476 ms

message.prod.js

message.prod.js

487 ms

slide.js

slide.js

676 ms

clientlib-foremWebComponent.lc-e8bf3ffe53f18cccc1ca08b42c57e19d-lc.min.js

clientlib-foremWebComponent.lc-e8bf3ffe53f18cccc1ca08b42c57e19d-lc.min.js

685 ms

clientlib-site.lc-ee58dd63f4c70f7873b2544f36569b60-lc.min.js

clientlib-site.lc-ee58dd63f4c70f7873b2544f36569b60-lc.min.js

675 ms

core.wcm.components.commons.datalayer.v1.min.js

core.wcm.components.commons.datalayer.v1.min.js

676 ms

FOREM-Logo.svg

FOREM-Logo.svg

97 ms

newspaper-light.svg

newspaper-light.svg

100 ms

envelope-light.svg

envelope-light.svg

94 ms

search-light.svg

search-light.svg

97 ms

Icon-user.svg

Icon-user.svg

120 ms

Icon-home.svg

Icon-home.svg

122 ms

Icon-login.svg

Icon-login.svg

188 ms

Icon-user-settings.svg

Icon-user-settings.svg

190 ms

Icon-penclip.svg

Icon-penclip.svg

190 ms

Icon-student-hat.svg

Icon-student-hat.svg

193 ms

chevron-right-regular.svg

chevron-right-regular.svg

215 ms

campagne-formations.jpeg

campagne-formations.jpeg

399 ms

slider-formations-langues.jpeg

slider-formations-langues.jpeg

474 ms

Icon-profile.svg

Icon-profile.svg

280 ms

Icon-tools.svg

Icon-tools.svg

284 ms

Icon-telescope.svg

Icon-telescope.svg

288 ms

Citoyen-money.svg

Citoyen-money.svg

309 ms

construis-ton-avenir-info-une.png

construis-ton-avenir-info-une.png

813 ms

adobestock-432629012.jpeg

adobestock-432629012.jpeg

468 ms

calendar_light.svg

calendar_light.svg

403 ms

Facebook-dark.svg

Facebook-dark.svg

512 ms

Linkedin-dark.svg

Linkedin-dark.svg

562 ms

Youtube-dark.svg

Youtube-dark.svg

565 ms

Instagram-dark.svg

Instagram-dark.svg

607 ms

MS-Twitter-x.png

MS-Twitter-x.png

624 ms

tiktok.png

tiktok.png

628 ms

google-play_280.png

google-play_280.png

656 ms

Apple-badge-280.png

Apple-badge-280.png

619 ms

FOREM-Logo.svg

FOREM-Logo.svg

661 ms

logo_UE-wallonie.svg

logo_UE-wallonie.svg

677 ms

Synerjob.png

Synerjob.png

677 ms

Poppins-Medium.ttf

Poppins-Medium.ttf

694 ms

Poppins-Regular.ttf

Poppins-Regular.ttf

782 ms

Poppins-Light.ttf

Poppins-Light.ttf

886 ms

Poppins-Thin.ttf

Poppins-Thin.ttf

811 ms

Poppins-SemiBold.ttf

Poppins-SemiBold.ttf

821 ms

Poppins-Bold.ttf

Poppins-Bold.ttf

764 ms

Poppins-ExtraBold.ttf

Poppins-ExtraBold.ttf

798 ms

image-vignette-jysk-1920x1080.jpeg

image-vignette-jysk-1920x1080.jpeg

536 ms

travailler-en-flandre-tuile.jpeg

travailler-en-flandre-tuile.jpeg

511 ms

ores-technicien-raccordeur-tuile.jpeg

ores-technicien-raccordeur-tuile.jpeg

475 ms

tarteaucitron.css

tarteaucitron.css

95 ms

tarteaucitron.en.js

tarteaucitron.en.js

109 ms

Accessibility Review

forem.be accessibility score

71

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[role]s do not have all required [aria-*] attributes

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

Links do not have a discernible name

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

forem.be best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

forem.be SEO score

100

Search Engine Optimization Advices

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

    N/A

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Forem.be can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is French. Our system also found out that Forem.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

forem.be

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