Tools & Wizards About Us
edelman.be screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

edelman.be

Homepage | Edelman Brussels

Page Load Speed

1.9 sec in total

First Response

97 ms

Resources Loaded

895 ms

Page Rendered

924 ms

edelman.be screenshot

About Website

Click here to check amazing Edelman content for United States. Otherwise, check out these important facts you probably never knew about edelman.be

Visit edelman.be

Key Findings

We analyzed Edelman.be page load time and found that the first response time was 97 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

edelman.be performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value3.3 s

91/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

edelman.be

97 ms

www.edelman.be

137 ms

fontloader.built.js

8 ms

css_n6Qd-z5_JNAt1RyymOhU8RlFA7Og8wgb7h1OdZwumVc.css

50 ms

css_xCTskHaYdjUDoGVLu0VsQibebBoZVu5gBhuR_2ppI-8.css

205 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 43% of them (20 requests) were addressed to the original Edelman.be, 49% (23 requests) were made to Edelmanbe.cachefly.net and 4% (2 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (205 ms) belongs to the original domain Edelman.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 226.9 kB (8%)

Content Size

2.9 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Edelman.be main page is 2.9 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 68.1 kB

  • Original 80.9 kB
  • After minification 67.2 kB
  • After compression 12.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 13.8 kB, which is 17% 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 68.1 kB or 84% of the original size.

Image Optimization

-6%

Potential reduce by 158.6 kB

  • Original 2.6 MB
  • After minification 2.4 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. Edelman images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 67 B

  • Original 196.4 kB
  • After minification 196.4 kB
  • After compression 196.3 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

-2%

Potential reduce by 113 B

  • Original 5.3 kB
  • After minification 5.3 kB
  • After compression 5.2 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. Edelman.be has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (29%)

Requests Now

35

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

edelman.be

edelman.be

97 ms

www.edelman.be

www.edelman.be

137 ms

fontloader.built.js

fontloader.built.js

8 ms

css_n6Qd-z5_JNAt1RyymOhU8RlFA7Og8wgb7h1OdZwumVc.css

css_n6Qd-z5_JNAt1RyymOhU8RlFA7Og8wgb7h1OdZwumVc.css

50 ms

css_xCTskHaYdjUDoGVLu0VsQibebBoZVu5gBhuR_2ppI-8.css

css_xCTskHaYdjUDoGVLu0VsQibebBoZVu5gBhuR_2ppI-8.css

205 ms

ram0gas.css

ram0gas.css

132 ms

DXI_FINAL.jpg

DXI_FINAL.jpg

113 ms

js_yGI-MtzmF3kSlp11hSdOjE178LF_lMpy-wYDkNRWT4U.js

js_yGI-MtzmF3kSlp11hSdOjE178LF_lMpy-wYDkNRWT4U.js

53 ms

page.js

page.js

126 ms

js_n7as4375nVOidHDmYycdhZ7d_BdPjICuJo0ps_W-gYc.js

js_n7as4375nVOidHDmYycdhZ7d_BdPjICuJo0ps_W-gYc.js

59 ms

app.built.js

app.built.js

103 ms

gtm.js

gtm.js

88 ms

gtag.js

gtag.js

93 ms

js__uR46sPBi9S3viqBy-1FBgLYpFVCj663wEJ68rJiju0.js

js__uR46sPBi9S3viqBy-1FBgLYpFVCj663wEJ68rJiju0.js

92 ms

EGA_FINAL.jpg

EGA_FINAL.jpg

108 ms

megamenu-banner_Trust23.png

megamenu-banner_Trust23.png

109 ms

RE%20Trust23.jpg

RE%20Trust23.jpg

107 ms

ETB24%20Report%20Title.png

ETB24%20Report%20Title.png

110 ms

david_plas_63102.jpg

david_plas_63102.jpg

109 ms

footer_logo_new.svg

footer_logo_new.svg

110 ms

ETB24%20Final%20Hero.png

ETB24%20Final%20Hero.png

79 ms

AdobeStock_562689714.jpeg

AdobeStock_562689714.jpeg

79 ms

AdobeStock_535681584.jpeg

AdobeStock_535681584.jpeg

77 ms

sola-kabuta-OUd5sX6-_Wc-unsplash.jpg

sola-kabuta-OUd5sX6-_Wc-unsplash.jpg

81 ms

AdobeStock_492354873.jpeg

AdobeStock_492354873.jpeg

75 ms

AdobeStock_345110333_Editorial_Use_Only.jpeg

AdobeStock_345110333_Editorial_Use_Only.jpeg

79 ms

AdobeStock_252120435.jpeg

AdobeStock_252120435.jpeg

83 ms

AdobeStock_224698511.jpeg

AdobeStock_224698511.jpeg

82 ms

AdobeStock_449308752.jpeg

AdobeStock_449308752.jpeg

84 ms

Janssen_Make_Blood_cancer_visible.jpg

Janssen_Make_Blood_cancer_visible.jpg

84 ms

jezael-melgoza-layMbSJ3YOE-unsplash.jpg

jezael-melgoza-layMbSJ3YOE-unsplash.jpg

86 ms

1390927061.jpg

1390927061.jpg

89 ms

1243654157.jpg

1243654157.jpg

88 ms

AdobeStock_484694910.jpeg

AdobeStock_484694910.jpeg

91 ms

AdobeStock_294184057.jpeg

AdobeStock_294184057.jpeg

88 ms

Homepage_950x634.png

Homepage_950x634.png

91 ms

p.css

p.css

34 ms

opensans-regular.woff

opensans-regular.woff

118 ms

opensans-light.woff

opensans-light.woff

117 ms

opensans-bold.woff

opensans-bold.woff

118 ms

opensans-extrabold.woff

opensans-extrabold.woff

116 ms

Inter-Regular.woff

Inter-Regular.woff

11 ms

Inter-Light.woff

Inter-Light.woff

10 ms

Inter-Bold.woff

Inter-Bold.woff

10 ms

Inter-ExtraBold.woff

Inter-ExtraBold.woff

10 ms

d

d

65 ms

icomoon.woff

icomoon.woff

9 ms

Accessibility Review

edelman.be accessibility score

96

Accessibility Issues

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

Best Practices

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

edelman.be SEO score

86

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

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

    EN

  • Encoding

    UTF-8

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

edelman.be

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