Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

nti.be

FlexibelStuderen® doe je bij NTI | Erkende opleidingen

Page Load Speed

3.3 sec in total

First Response

383 ms

Resources Loaded

2.6 sec

Page Rendered

288 ms

nti.be screenshot

About Website

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

Ervaar het nieuwe FlexibelStuderen® van NTI en haal dat erkende diploma. Volg een MBO-, HBO-, Master- of Vakopleiding op een manier die echt bij jou past.

Visit nti.be

Key Findings

We analyzed Nti.be page load time and found that the first response time was 383 ms and then it took 2.9 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

nti.be performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value790 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

nti.be

383 ms

www.nti.be

657 ms

restyle.min.css

389 ms

jquery.js

586 ms

jquery.plugins.min.js

595 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 71% of them (25 requests) were addressed to the original Nti.be, 9% (3 requests) were made to Js.nti.be and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (810 ms) belongs to the original domain Nti.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 504.0 kB (53%)

Content Size

955.2 kB

After Optimization

451.2 kB

In fact, the total size of Nti.be main page is 955.2 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. 20% of websites need less resources to load. Javascripts take 420.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 30.3 kB

  • Original 37.3 kB
  • After minification 28.9 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 8.4 kB, which is 23% 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 30.3 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 974 B

  • Original 246.3 kB
  • After minification 245.3 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. NTI images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 264.3 kB

  • Original 420.1 kB
  • After minification 420.1 kB
  • After compression 155.8 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 264.3 kB or 63% of the original size.

CSS Optimization

-83%

Potential reduce by 208.3 kB

  • Original 251.4 kB
  • After minification 251.3 kB
  • After compression 43.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. Nti.be needs all CSS files to be minified and compressed as it can save up to 208.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (57%)

Requests Now

28

After Optimization

12

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

Accessibility Review

nti.be accessibility score

95

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.

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

nti.be best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

SEO Factors

nti.be SEO score

92

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

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

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

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