Tools & Wizards About Us
flux.be screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% 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

  • 93

    SEO

    Google-friendlier than
    83% of websites

flux.be

Webdesign Antwerpen | Webdesign Flux | Website laten maken

Page Load Speed

3.2 sec in total

First Response

448 ms

Resources Loaded

2.3 sec

Page Rendered

371 ms

flux.be screenshot

About Website

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

Flux is een webdesign bureau uit Antwerpen. Wilt u een website laten maken? Flux Webdesign maakt websites waarin communicatie centraal staat.

Visit flux.be

Key Findings

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

Performance Metrics

flux.be performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value1,190 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

Network Requests Diagram

flux.be

448 ms

flux.be

517 ms

siteground-optimizer-combined-css-ef8fb5d44002232033caf40f9113d65b.css

392 ms

DOMPurify.min.js

265 ms

jquery.min.js

359 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 87% of them (48 requests) were addressed to the original Flux.be, 5% (3 requests) were made to Googletagmanager.com and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (665 ms) belongs to the original domain Flux.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 298.7 kB (23%)

Content Size

1.3 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flux.be main page is 1.3 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. 60% of websites need less resources to load. Images take 605.7 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 89.8 kB

  • Original 109.4 kB
  • After minification 104.1 kB
  • After compression 19.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. 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 89.8 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 7.4 kB

  • Original 605.7 kB
  • After minification 598.2 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. Flux images are well optimized though.

JavaScript Optimization

-38%

Potential reduce by 169.1 kB

  • Original 439.6 kB
  • After minification 439.6 kB
  • After compression 270.6 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 169.1 kB or 38% of the original size.

CSS Optimization

-22%

Potential reduce by 32.4 kB

  • Original 145.5 kB
  • After minification 145.5 kB
  • After compression 113.1 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. Flux.be needs all CSS files to be minified and compressed as it can save up to 32.4 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (53%)

Requests Now

45

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

flux.be

flux.be

448 ms

flux.be

flux.be

517 ms

siteground-optimizer-combined-css-ef8fb5d44002232033caf40f9113d65b.css

siteground-optimizer-combined-css-ef8fb5d44002232033caf40f9113d65b.css

392 ms

DOMPurify.min.js

DOMPurify.min.js

265 ms

jquery.min.js

jquery.min.js

359 ms

bodhi_svg_inline.min.js

bodhi_svg_inline.min.js

286 ms

cookie-law-info.min.js

cookie-law-info.min.js

291 ms

js

js

65 ms

js

js

110 ms

flying-pages.min.js

flying-pages.min.js

290 ms

wpbf-site.min.js

wpbf-site.min.js

349 ms

comment-reply.min.js

comment-reply.min.js

380 ms

js

js

76 ms

vc-flux-settings-google-maps.min.js

vc-flux-settings-google-maps.min.js

386 ms

vc-flux-settings-counter.min.js

vc-flux-settings-counter.min.js

386 ms

wpbf-premium.min.js

wpbf-premium.min.js

545 ms

lazysizes.min.js

lazysizes.min.js

544 ms

ls.unveilhooks.min.js

ls.unveilhooks.min.js

547 ms

ls.native-loading.min.js

ls.native-loading.min.js

548 ms

slick.min.js

slick.min.js

548 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

548 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

550 ms

lottie-player.js

lottie-player.js

665 ms

bdetection.min.js

bdetection.min.js

662 ms

flux-custom-js.min.js

flux-custom-js.min.js

662 ms

js_composer_front.min.js

js_composer_front.min.js

662 ms

gtm.js

gtm.js

107 ms

logo-icon-color.svg

logo-icon-color.svg

202 ms

opener-foto-9.png

opener-foto-9.png

620 ms

dot-dark-blue.svg

dot-dark-blue.svg

257 ms

smartmockups_lpsfs3hw-768x512.jpg

smartmockups_lpsfs3hw-768x512.jpg

380 ms

smartmockups_lq2d0cdu-768x544.jpg

smartmockups_lq2d0cdu-768x544.jpg

379 ms

smartmockups_lpsgnbhj-768x632.jpg

smartmockups_lpsgnbhj-768x632.jpg

260 ms

smartmockups_lq2956kd-768x469.jpg

smartmockups_lq2956kd-768x469.jpg

261 ms

smartmockups_lq254185-e1702377154437-768x446.jpg

smartmockups_lq254185-e1702377154437-768x446.jpg

616 ms

smartmockups_lq271o2p-768x432.jpg

smartmockups_lq271o2p-768x432.jpg

405 ms

smartmockups_lpsc4m1o-768x512.jpg

smartmockups_lpsc4m1o-768x512.jpg

404 ms

smartmockups_lpsczycy-e1701782122619-768x518.jpg

smartmockups_lpsczycy-e1701782122619-768x518.jpg

612 ms

smartmockups_lpshxvlr-e1701790368656-768x471.jpg

smartmockups_lpshxvlr-e1701790368656-768x471.jpg

613 ms

smartmockups_lpjrzwjq-768x512.jpg

smartmockups_lpjrzwjq-768x512.jpg

615 ms

dot-dark-pink.svg

dot-dark-pink.svg

612 ms

quote-light-blue.svg

quote-light-blue.svg

615 ms

dot-teal.svg

dot-teal.svg

616 ms

TrendsGazellen_2024-300x286.png

TrendsGazellen_2024-300x286.png

618 ms

analytics.js

analytics.js

131 ms

open-sans-v17-latin-regular.woff

open-sans-v17-latin-regular.woff

313 ms

open-sans-v17-latin-600.woff

open-sans-v17-latin-600.woff

312 ms

open-sans-v17-latin-700.woff

open-sans-v17-latin-700.woff

313 ms

nhunica.woff

nhunica.woff

385 ms

fa-solid-900.woff

fa-solid-900.woff

386 ms

fa-regular-400.woff

fa-regular-400.woff

386 ms

fa-brands-400.woff

fa-brands-400.woff

387 ms

page-builder-framework.woff

page-builder-framework.woff

460 ms

collect

collect

86 ms

collect

collect

82 ms

Accessibility Review

flux.be accessibility score

91

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

SEO Factors

flux.be SEO score

93

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

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

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

flux.be

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