Tools & Wizards About Us
finactum.be screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

finactum.be

Finactum, gratis financiële cijfers en kwaliteitsvolle en leesbare bedrijfsinformatie van Belgische bedrijven

Page Load Speed

6.1 sec in total

First Response

257 ms

Resources Loaded

5.5 sec

Page Rendered

295 ms

finactum.be screenshot

About Website

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

Finactum is een website met gratis financiële informatie over Belgische bedrijven met neerleggingsplicht. Daarnaast bieden we ook goedkope kwaliteitsvolle en leesbare financiële rapporten aan.

Visit finactum.be

Key Findings

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

Performance Metrics

finactum.be performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value26.1 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value7,060 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.248

50/100

15%

TTI (Time to Interactive)

Value26.8 s

0/100

10%

Network Requests Diagram

finactum.be

257 ms

www.finactum.be

466 ms

analytics.js

58 ms

finactum.css

206 ms

logo.png

469 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 77% of them (17 requests) were addressed to the original Finactum.be, 9% (2 requests) were made to Google-analytics.com and 5% (1 request) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Finactum.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 65.2 kB (64%)

Content Size

102.7 kB

After Optimization

37.5 kB

  • HTML
  • JavaScript

In fact, the total size of Finactum.be main page is 102.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Javascripts take 61.8 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 33.3 kB

  • Original 40.9 kB
  • After minification 32.0 kB
  • After compression 7.6 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.9 kB, which is 22% 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 33.3 kB or 81% of the original size.

JavaScript Optimization

-52%

Potential reduce by 32.0 kB

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

Requests Breakdown

Number of requests can be reduced by 4 (22%)

Requests Now

18

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

finactum.be

finactum.be

257 ms

www.finactum.be

www.finactum.be

466 ms

analytics.js

analytics.js

58 ms

finactum.css

finactum.css

206 ms

logo.png

logo.png

469 ms

logo_small.png

logo_small.png

291 ms

combined.js

combined.js

768 ms

js

js

43 ms

home.js

home.js

287 ms

nbb.jpg

nbb.jpg

291 ms

social.jpg

social.jpg

295 ms

staatsblad.jpg

staatsblad.jpg

470 ms

kbo.jpg

kbo.jpg

375 ms

collect

collect

13 ms

collect

collect

51 ms

city.jpg

city.jpg

771 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

234 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

310 ms

week

week

3633 ms

day

day

1903 ms

print.css

print.css

96 ms

nr-885.min.js

nr-885.min.js

56 ms

Accessibility Review

finactum.be accessibility score

65

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

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

<frame> or <iframe> elements do not have a title

High

Form elements do not have associated labels

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

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

finactum.be SEO score

90

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

finactum.be

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