4.7 sec in total
1.1 sec
3.4 sec
249 ms
Welcome to nav.be homepage info - get ready to check NAV best content for Belgium right away, or after learning these important things about nav.be
Visit nav.beWe analyzed Nav.be page load time and found that the first response time was 1.1 sec and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
nav.be performance score
name
value
score
weighting
Value5.4 s
7/100
10%
Value9.0 s
1/100
25%
Value9.4 s
12/100
10%
Value5,240 ms
0/100
30%
Value0.304
39/100
15%
Value13.2 s
12/100
10%
1121 ms
330 ms
169 ms
180 ms
362 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 77% of them (64 requests) were addressed to the original Nav.be, 18% (15 requests) were made to Ads.nav.be and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Ads.nav.be.
Page size can be reduced by 315.6 kB (24%)
1.3 MB
979.8 kB
In fact, the total size of Nav.be main page is 1.3 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. 30% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 46.2 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 46.2 kB or 80% of the original size.
Potential reduce by 110.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. Obviously, NAV needs image optimization as it can save up to 110.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 142.2 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 142.2 kB or 66% of the original size.
Potential reduce by 17.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. Nav.be needs all CSS files to be minified and compressed as it can save up to 17.2 kB or 84% of the original size.
Number of requests can be reduced by 20 (24%)
82
62
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NAV. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
index.php
1121 ms
pages.css
330 ms
clearfix.css
169 ms
pages-else.css
180 ms
cufon-yui.js
362 ms
Helve_700.font.js
542 ms
jquery.js
87 ms
googleanalytics.js
250 ms
style.css
267 ms
script.js
334 ms
script.js
357 ms
kdb-uitklap.js
409 ms
rollover.js
342 ms
analytics.js
90 ms
banners.php
314 ms
banners.php
291 ms
dscn7792.JPG
617 ms
banners.php
1285 ms
banners.php
1276 ms
logo.jpg
89 ms
bgcontent.jpg
92 ms
pijl2.jpg
94 ms
spacerC.jpg
89 ms
pijl-dicht.jpg
94 ms
AR-CO-50_CMYK_nl.jpg
85 ms
benorlogo_baseline_zwart_DEF.jpg
167 ms
Daikin_Horizontal_quadri.jpg
171 ms
eni_logo_ongestreken_RGB.jpg
252 ms
Euromaf.jpg
267 ms
Kubus_logo2D_LG_rgb.png
273 ms
Promat_Logo_4C_R.jpg
272 ms
Renson.JPG
247 ms
ROCKFON_blue_614x107px%20copy%20(2).jpg
252 ms
sgs%20en%20grondwijzer.jpg
330 ms
TATA%20Steel.jpg
334 ms
WB_Wienerberger%20Building%20Material%20Solutions.jpg
335 ms
Belgaclima_NL.jpg
356 ms
CEA-BELGIUM.jpg
361 ms
derbigum.jpg
362 ms
Eurodal-RGB.jpg
409 ms
Gyproc_CMYK_HR.jpg
416 ms
L-Door.jpg
417 ms
protect.jpg
444 ms
Reynaers%20verticaal.jpg
450 ms
Saint%20Gobain%20Glass.jpg
451 ms
SYH.jpg
489 ms
velux.jpg
499 ms
opinie-kati.jpg
509 ms
pijl5.jpg
576 ms
201603161531.jpg
740 ms
pijl.jpg
582 ms
201603150945.jpg
851 ms
201603140919.jpg
890 ms
201603111658.jpg
712 ms
spacerwit.png
664 ms
collect
14 ms
101_8124b.jpg
835 ms
plan%202.jpg
881 ms
spacerEF.jpg
717 ms
papier.jpg
763 ms
geld.jpg
805 ms
daillight.jpg
869 ms
renson%20filmpjes.jpeg
791 ms
Linaqua-VIOLA.jpg
826 ms
201603171648.jpg
762 ms
201603151635.jpg
780 ms
201603030930.jpg
824 ms
helpdeskepb.jpg
893 ms
Cover.jpg
1011 ms
facebook-footer.jpg
807 ms
jquery-1.11.1.min.js
401 ms
script.js
173 ms
twitter-footer.jpg
763 ms
imu-wienerberger.jpg
162 ms
Wienerberger%20-%20lambda.gif
241 ms
Velux_ProDigital_468x60_nl.jpg
173 ms
Outdoor%20Wood%20Concept.gif
354 ms
Banner%20NAV%20site.jpg
401 ms
Soprema.jpg
322 ms
KUBUS.gif
347 ms
Promat.jpg
443 ms
Gyproc.gif
486 ms
pages-print.css
85 ms
nav.be accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
nav.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
nav.be SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
NL
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nav.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Nav.be main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
nav.be
Open Graph description is not detected on the main page of NAV. 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: