Tools & Wizards About Us
nascom.be screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

nascom.be

make it fly is nu Dynamate | Digitale experts in web, apps… | Dynamate

Page Load Speed

3.5 sec in total

First Response

312 ms

Resources Loaded

2.9 sec

Page Rendered

327 ms

nascom.be screenshot

About Website

Click here to check amazing Nascom content for Belgium. Otherwise, check out these important facts you probably never knew about nascom.be

De expertise van make it fly leeft verder binnen Dynamate. Je vindt er dezelfde mensen, dezelfde kwaliteit en een uitgebreider digitaal en IT-aanbod.

Visit nascom.be

Key Findings

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

Performance Metrics

nascom.be performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value14.9 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.378

28/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

nascom.be

312 ms

www.nascom.be

633 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

165 ms

css_UqOoffvk-FuWbV_8eQT7rRkyNlgHbJYnIPpRiPfBsCw.css

183 ms

css_KpHsFsHL5G3x9EUJr5pMqQKsGs4fdCXEGrY6HhOgLHA.css

178 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 96% of them (89 requests) were addressed to the original Nascom.be, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (702 ms) belongs to the original domain Nascom.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 271.8 kB (15%)

Content Size

1.8 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 30.1 kB

  • Original 36.1 kB
  • After minification 32.8 kB
  • After compression 6.0 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 30.1 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 48.8 kB

  • Original 1.5 MB
  • After minification 1.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. Nascom images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 107.2 kB

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

CSS Optimization

-81%

Potential reduce by 85.7 kB

  • Original 105.4 kB
  • After minification 104.3 kB
  • After compression 19.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. Nascom.be needs all CSS files to be minified and compressed as it can save up to 85.7 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (13%)

Requests Now

91

After Optimization

79

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nascom.be

nascom.be

312 ms

www.nascom.be

www.nascom.be

633 ms

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css

165 ms

css_UqOoffvk-FuWbV_8eQT7rRkyNlgHbJYnIPpRiPfBsCw.css

css_UqOoffvk-FuWbV_8eQT7rRkyNlgHbJYnIPpRiPfBsCw.css

183 ms

css_KpHsFsHL5G3x9EUJr5pMqQKsGs4fdCXEGrY6HhOgLHA.css

css_KpHsFsHL5G3x9EUJr5pMqQKsGs4fdCXEGrY6HhOgLHA.css

178 ms

css_vlWeR1jayHYsF4bwVy6XOGHDD-9HxTQkR9NDLu5hHK8.css

css_vlWeR1jayHYsF4bwVy6XOGHDD-9HxTQkR9NDLu5hHK8.css

178 ms

css_hg68RM-92vf9LJAXIk6yklX52sAJX6Wd2ncrdn6Uirw.css

css_hg68RM-92vf9LJAXIk6yklX52sAJX6Wd2ncrdn6Uirw.css

176 ms

css_p55PnnbgeG1tOjab4rog4SQyEXzUxMPPQ72buTQMmBQ.css

css_p55PnnbgeG1tOjab4rog4SQyEXzUxMPPQ72buTQMmBQ.css

266 ms

js_UWQINlriydSoeSiGQxToOUdv493zEa7dpsXC1OtYlZU.js

js_UWQINlriydSoeSiGQxToOUdv493zEa7dpsXC1OtYlZU.js

275 ms

js_cyMM8LWJnjj9HKH-29oT6CebO_jNPJEicmEd7Ldra9o.js

js_cyMM8LWJnjj9HKH-29oT6CebO_jNPJEicmEd7Ldra9o.js

176 ms

js_I8Lcsev_jtw6DmL_OMb3JAmZDD0_KVFXuI1ZzKQAtA8.js

js_I8Lcsev_jtw6DmL_OMb3JAmZDD0_KVFXuI1ZzKQAtA8.js

179 ms

modernizr.min.js

modernizr.min.js

72 ms

js_MRJGmiHDN-YmxpVwJXrmhddeFsDyTTAop4jAFfeWcSc.js

js_MRJGmiHDN-YmxpVwJXrmhddeFsDyTTAop4jAFfeWcSc.js

178 ms

js_gqCxheYGfaukw4pL5hzx5l81xftyfR1a0e1pM9BMMII.js

js_gqCxheYGfaukw4pL5hzx5l81xftyfR1a0e1pM9BMMII.js

269 ms

gtm.js

gtm.js

81 ms

nascom.svg

nascom.svg

125 ms

logo.png

logo.png

123 ms

02.jpg

02.jpg

180 ms

03.jpg

03.jpg

174 ms

04.jpg

04.jpg

178 ms

06.jpg

06.jpg

126 ms

00.jpg

00.jpg

267 ms

05.jpg

05.jpg

190 ms

07.jpg

07.jpg

184 ms

08.jpg

08.jpg

348 ms

01.jpg

01.jpg

353 ms

09.jpg

09.jpg

356 ms

11.jpg

11.jpg

268 ms

duo-nascom.jpg

duo-nascom.jpg

284 ms

stulens_new.jpg

stulens_new.jpg

354 ms

ab_inbev.png

ab_inbev.png

350 ms

bongo.png

bongo.png

378 ms

cm.png

cm.png

436 ms

healthconnect.png

healthconnect.png

434 ms

id-t.png

id-t.png

441 ms

informazout.png

informazout.png

443 ms

kmda.png

kmda.png

446 ms

kwadro.png

kwadro.png

474 ms

materialise.png

materialise.png

513 ms

mercedes_benz.png

mercedes_benz.png

520 ms

mobistar.png

mobistar.png

530 ms

unibind.png

unibind.png

532 ms

port_of_antwerp.png

port_of_antwerp.png

532 ms

raz_war.png

raz_war.png

567 ms

recordbank_logo.png

recordbank_logo.png

596 ms

recticel.png

recticel.png

607 ms

smiths.png

smiths.png

618 ms

sony.png

sony.png

619 ms

studio100.png

studio100.png

568 ms

tec7.png

tec7.png

606 ms

toyota.png

toyota.png

622 ms

vandevelde.png

vandevelde.png

576 ms

vtm.png

vtm.png

587 ms

BryantPro-Bold.svg

BryantPro-Bold.svg

670 ms

analytics.js

analytics.js

11 ms

collect

collect

11 ms

BryantPro-Regular.svg

BryantPro-Regular.svg

543 ms

iconic.woff

iconic.woff

586 ms

vrt.png

vrt.png

599 ms

BryantPro-Regular.woff

BryantPro-Regular.woff

92 ms

BryantPro-Bold.woff

BryantPro-Bold.woff

191 ms

00_0.jpg

00_0.jpg

97 ms

vandevelde_1.jpg

vandevelde_1.jpg

180 ms

bike7_0.jpg

bike7_0.jpg

92 ms

02_0.jpg

02_0.jpg

176 ms

vandevelde_2.jpg

vandevelde_2.jpg

160 ms

bike7_1.jpg

bike7_1.jpg

178 ms

03_0.jpg

03_0.jpg

268 ms

vandevelde_4.jpg

vandevelde_4.jpg

191 ms

bike7_2.jpg

bike7_2.jpg

322 ms

04_0.jpg

04_0.jpg

262 ms

vandevelde_5.jpg

vandevelde_5.jpg

360 ms

bike7_3.jpg

bike7_3.jpg

269 ms

01_0.jpg

01_0.jpg

379 ms

vandevelde_3.jpg

vandevelde_3.jpg

354 ms

bike7_6.jpg

bike7_6.jpg

356 ms

vandevelde_6.jpg

vandevelde_6.jpg

359 ms

08_0.jpg

08_0.jpg

499 ms

vandevelde_10.jpg

vandevelde_10.jpg

441 ms

bike7_8.jpg

bike7_8.jpg

443 ms

vandevelde_7.jpg

vandevelde_7.jpg

453 ms

bike7_5.jpg

bike7_5.jpg

459 ms

05_0.jpg

05_0.jpg

472 ms

06_0.jpg

06_0.jpg

614 ms

vandevelde_11.jpg

vandevelde_11.jpg

532 ms

bike7_10.jpg

bike7_10.jpg

545 ms

09_0.jpg

09_0.jpg

657 ms

bike7_7.jpg

bike7_7.jpg

566 ms

10.jpg

10.jpg

657 ms

vandevelde_8.jpg

vandevelde_8.jpg

620 ms

bike7_9.jpg

bike7_9.jpg

636 ms

vandevelde_9.jpg

vandevelde_9.jpg

660 ms

11_0.jpg

11_0.jpg

702 ms

Accessibility Review

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

nascom.be best practices score

75

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

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

nascom.be SEO score

79

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

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a valid hreflang

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

    EN

  • Encoding

    UTF-8

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

nascom.be

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