4.8 sec in total
344 ms
3.2 sec
1.2 sec
Click here to check amazing Ffgb content. Otherwise, check out these important facts you probably never knew about ffgb.be
We are building strong foundations for a solid future. Specialist in deep foundations, we are happy to design and built the perfect solution for your project of construction or renovation. Our century...
Visit ffgb.beWe analyzed Ffgb.be page load time and found that the first response time was 344 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
ffgb.be performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value9.1 s
1/100
25%
Value6.9 s
33/100
10%
Value420 ms
66/100
30%
Value0.351
31/100
15%
Value9.0 s
34/100
10%
344 ms
356 ms
918 ms
51 ms
40 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 69% of them (35 requests) were addressed to the original Ffgb.be, 12% (6 requests) were made to Cdn.cookielaw.org and 6% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Ffgb.be.
Page size can be reduced by 169.7 kB (2%)
11.0 MB
10.8 MB
In fact, the total size of Ffgb.be main page is 11.0 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. 50% of websites need less resources to load. Images take 10.7 MB which makes up the majority of the site volume.
Potential reduce by 151.4 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 19.4 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 151.4 kB or 83% of the original size.
Potential reduce by 2.5 kB
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. Ffgb images are well optimized though.
Potential reduce by 1.1 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.
Potential reduce by 14.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. Ffgb.be needs all CSS files to be minified and compressed as it can save up to 14.7 kB or 27% of the original size.
Number of requests can be reduced by 11 (25%)
44
33
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ffgb. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
ffgb.be
344 ms
ffgb.be
356 ms
www.ffgb.be
918 ms
otSDKStub.js
51 ms
picturefill.min.js
40 ms
ls.bgset.min.js
193 ms
lazysizes.min.js
296 ms
jquery-3.5.0.min.js
30 ms
jquery-ui.min.js
36 ms
bodyBottom
619 ms
addthis_widget.js
224 ms
0c4acdc3-e4af-42ee-9127-bad811405ce2.json
136 ms
gtm.js
188 ms
arrow.svg
351 ms
frfo_trade_2lines_wh.png
352 ms
frfo_trade_2lines_cp-transparent.png
451 ms
piles_web2.png
481 ms
walls_web.png
484 ms
soil-imp_web.png
487 ms
hospital.png
484 ms
windmill-base.png
743 ms
infrastructure.png
743 ms
sports.png
742 ms
marine.png
743 ms
environmental.png
743 ms
industry.png
744 ms
history_header_b.jpg
975 ms
header_franki11.jpg
1449 ms
careers_franki_hp.jpg
959 ms
header_franki8.jpg
1372 ms
pic_cover_def2.jpg
1361 ms
csr-hero2.jpg
1365 ms
besix-white.png
1076 ms
frfo_trade_2lines_wh.png
1079 ms
otBannerSdk.js
20 ms
main.min.css
1217 ms
2sDfZG1Wl4LcnbuKjk0j.ttf
39 ms
2sDcZG1Wl4LcnbuCJW8zaGW8.ttf
46 ms
2sDcZG1Wl4LcnbuCNWgzaGW8.ttf
53 ms
glyphicons-halflings-regular.woff
1091 ms
en.json
116 ms
111_beinject3_738b3d210a636ff2884d11db85aa5d58_1920.jpg
65 ms
brucity-hero-b.jpg
1152 ms
otCenterRounded.json
104 ms
otPcCenter.json
35 ms
OverviewimageLR-ALEGrO2_6cc0529660b7172150cb28f5773727e7_1920.jpg
46 ms
twitter.png
88 ms
linkedin.png
132 ms
ig.png
138 ms
phone-icon.png
143 ms
mail-icon.png
144 ms
ffgb.be accessibility score
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
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
ffgb.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
ffgb.be SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ffgb.be can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ffgb.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.
ffgb.be
Open Graph data is detected on the main page of Ffgb. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: