Tools & Wizards About Us
ivalue.be screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    57% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

ivalue.be

Digital agency iValue stapt in het huwelijksbootje met iO | iO

Page Load Speed

7 sec in total

First Response

315 ms

Resources Loaded

6.3 sec

Page Rendered

347 ms

ivalue.be screenshot

About Website

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

iValue en iO worden samen jouw end-to-end partner met expertise in marketing, technologie, content, creatie, en strategie.

Visit ivalue.be

Key Findings

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

Performance Metrics

ivalue.be performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

65/100

25%

SI (Speed Index)

Value14.8 s

1/100

10%

TBT (Total Blocking Time)

Value2,730 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.096

90/100

15%

TTI (Time to Interactive)

Value19.5 s

2/100

10%

Network Requests Diagram

ivalue.be

315 ms

www.ivalue.be

1321 ms

1521 ms

css

70 ms

style.css.php

809 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 36% of them (12 requests) were addressed to the original Ivalue.be, 12% (4 requests) were made to Fonts.gstatic.com and 9% (3 requests) were made to Secure.gravatar.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Ivalue.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 101.4 kB (20%)

Content Size

519.6 kB

After Optimization

418.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 16.8 kB

  • Original 22.5 kB
  • After minification 21.5 kB
  • After compression 5.7 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 16.8 kB or 75% of the original size.

Image Optimization

-5%

Potential reduce by 19.9 kB

  • Original 380.9 kB
  • After minification 361.0 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. IValue images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 53.5 kB

  • Original 102.4 kB
  • After minification 102.4 kB
  • After compression 48.9 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 53.5 kB or 52% of the original size.

CSS Optimization

-81%

Potential reduce by 11.1 kB

  • Original 13.8 kB
  • After minification 11.4 kB
  • After compression 2.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. Ivalue.be needs all CSS files to be minified and compressed as it can save up to 11.1 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (65%)

Requests Now

26

After Optimization

9

  • Images
  • JavaScript
  • CSS

The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IValue. 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 from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

ivalue.be

ivalue.be

315 ms

www.ivalue.be

www.ivalue.be

1321 ms

1521 ms

css

css

70 ms

style.css.php

style.css.php

809 ms

1396 ms

jquery.min.js

jquery.min.js

77 ms

1372 ms

gprofiles.js

gprofiles.js

164 ms

1483 ms

devicepx-jetpack.js

devicepx-jetpack.js

52 ms

e-201611.js

e-201611.js

51 ms

slicknav.css

slicknav.css

86 ms

fbevents.js

fbevents.js

372 ms

analytics.js

analytics.js

135 ms

logo.png

logo.png

163 ms

homepage-banner_02.jpg

homepage-banner_02.jpg

682 ms

PartnerBadge-Horizontal-300x112-300x112.png

PartnerBadge-Horizontal-300x112-300x112.png

163 ms

clients.png

clients.png

341 ms

count.js

count.js

231 ms

linkid.js

linkid.js

182 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

211 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

251 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

282 ms

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf

276 ms

pta.js

pta.js

890 ms

hovercard.css

hovercard.css

167 ms

services.css

services.css

237 ms

collect

collect

124 ms

g.gif

g.gif

82 ms

148 ms

ga-audiences

ga-audiences

63 ms

49858d0b.js

49858d0b.js

975 ms

Accessibility Review

ivalue.be accessibility score

90

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

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.

Best Practices

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

High

Missing source maps for large first-party JavaScript

SEO Factors

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

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ivalue.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 Ivalue.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

ivalue.be

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