Report Summary

  • 35

    Performance

    Renders faster than
    54% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

ffgb.be

Deep foundations specialist - Franki Foundations Belgium

Page Load Speed

4.8 sec in total

First Response

344 ms

Resources Loaded

3.2 sec

Page Rendered

1.2 sec

ffgb.be screenshot

About Website

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

Key Findings

We 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.

Performance Metrics

ffgb.be performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value6.9 s

33/100

10%

TBT (Total Blocking Time)

Value420 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0.351

31/100

15%

TTI (Time to Interactive)

Value9.0 s

34/100

10%

Network Requests Diagram

ffgb.be

344 ms

ffgb.be

356 ms

www.ffgb.be

918 ms

otSDKStub.js

51 ms

picturefill.min.js

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 Optimization Overview & Recommendations

Page size can be reduced by 169.7 kB (2%)

Content Size

11.0 MB

After Optimization

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.

HTML Optimization

-83%

Potential reduce by 151.4 kB

  • Original 183.1 kB
  • After minification 163.7 kB
  • After compression 31.8 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.

Image Optimization

-0%

Potential reduce by 2.5 kB

  • Original 10.7 MB
  • After minification 10.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. Ffgb images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.1 kB

  • Original 90.0 kB
  • After minification 89.9 kB
  • After compression 88.8 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

-27%

Potential reduce by 14.7 kB

  • Original 53.6 kB
  • After minification 53.6 kB
  • After compression 38.9 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.

Requests Breakdown

Number of requests can be reduced by 11 (25%)

Requests Now

44

After Optimization

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.

Accessibility Review

ffgb.be accessibility score

57

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

ARIA input fields do not have accessible names

High

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

High

[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

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

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

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

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

ffgb.be best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

Missing source maps for large first-party JavaScript

SEO Factors

ffgb.be SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    EN

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: