Tools & Wizards About Us
indis.be screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

indis.be

INDIS nv | The Right Source makes all the Difference

Page Load Speed

4.9 sec in total

First Response

1.1 sec

Resources Loaded

3.4 sec

Page Rendered

334 ms

indis.be screenshot

About Website

Click here to check amazing INDIS content for Egypt. Otherwise, check out these important facts you probably never knew about indis.be

INDIS nv is a sourcing and distribution company of raw materials, primarily for the pharmaceutical market and industry, but also for the food, feed, cosmetic and chemical markets.

Visit indis.be

Key Findings

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

Performance Metrics

indis.be performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value13.7 s

11/100

10%

Network Requests Diagram

www.indis.be

1137 ms

webfont.js

29 ms

js

71 ms

script.js

68 ms

css

147 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 58% of them (23 requests) were addressed to the original Indis.be, 30% (12 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Indis.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 817.9 kB (18%)

Content Size

4.6 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Indis.be main page is 4.6 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. 35% of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 28.8 kB

  • Original 38.7 kB
  • After minification 37.6 kB
  • After compression 9.9 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 28.8 kB or 74% of the original size.

Image Optimization

-3%

Potential reduce by 115.3 kB

  • Original 3.6 MB
  • After minification 3.5 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. INDIS images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 491.3 kB

  • Original 665.4 kB
  • After minification 665.4 kB
  • After compression 174.1 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 491.3 kB or 74% of the original size.

CSS Optimization

-86%

Potential reduce by 182.5 kB

  • Original 212.5 kB
  • After minification 187.3 kB
  • After compression 30.0 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. Indis.be needs all CSS files to be minified and compressed as it can save up to 182.5 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

26

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.indis.be

www.indis.be

1137 ms

webfont.js

webfont.js

29 ms

js

js

71 ms

script.js

script.js

68 ms

css

css

147 ms

normalize.css

normalize.css

133 ms

components.css

components.css

187 ms

indis-nv.css

indis-nv.css

462 ms

style.min.css

style.min.css

599 ms

common.css

common.css

279 ms

jquery.min.js

jquery.min.js

463 ms

jquery-migrate.min.js

jquery-migrate.min.js

280 ms

indis-nv.js

indis-nv.js

737 ms

udesly-frontend-scripts.js

udesly-frontend-scripts.js

371 ms

log

log

411 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

18 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

22 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

25 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xk.ttf

25 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

25 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf

27 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rm.ttf

28 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf

28 ms

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf

BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf

27 ms

oY1Z8e7OuLXkJGbXtr5ba7ZlbKUZ.ttf

oY1Z8e7OuLXkJGbXtr5ba7ZlbKUZ.ttf

28 ms

1cXxaUPOAJv9sG4I-DJWiHGA.ttf

1cXxaUPOAJv9sG4I-DJWiHGA.ttf

214 ms

1cX0aUPOAJv9sG4I-DJeV1WQhuCs.ttf

1cX0aUPOAJv9sG4I-DJeV1WQhuCs.ttf

67 ms

indisnv_logo_2019_black2_50px.png

indisnv_logo_2019_black2_50px.png

97 ms

indisnv_dotsswirl2.png

indisnv_dotsswirl2.png

188 ms

border_01.png

border_01.png

97 ms

foto02.jpg

foto02.jpg

739 ms

indis-building-2022_v01.png

indis-building-2022_v01.png

650 ms

indisnv_background01.jpg

indisnv_background01.jpg

189 ms

transport.png

transport.png

652 ms

indis-group.png

indis-group.png

210 ms

sgs.png

sgs.png

280 ms

feedchain_round_o_transp.png

feedchain_round_o_transp.png

374 ms

icon_phone.png

icon_phone.png

303 ms

email-icon-white.svg

email-icon-white.svg

372 ms

linkdin-icon-white.svg

linkdin-icon-white.svg

395 ms

Accessibility Review

indis.be accessibility score

94

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

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

Links do not have a discernible name

Best Practices

indis.be best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

indis.be

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