3.7 sec in total
291 ms
3.1 sec
215 ms
Welcome to publicprocurement.be homepage info - get ready to check Publicprocurement best content for Belgium right away, or after learning these important things about publicprocurement.be
Visit publicprocurement.beWe analyzed Publicprocurement.be page load time and found that the first response time was 291 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
publicprocurement.be performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value7.5 s
4/100
25%
Value8.5 s
18/100
10%
Value90 ms
99/100
30%
Value0.25
49/100
15%
Value5.9 s
66/100
10%
291 ms
246 ms
215 ms
199 ms
209 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 95% of them (38 requests) were addressed to the original Publicprocurement.be, 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Publicprocurement.be.
Page size can be reduced by 392.4 kB (57%)
686.1 kB
293.7 kB
In fact, the total size of Publicprocurement.be main page is 686.1 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. 15% of websites need less resources to load. CSS take 279.8 kB which makes up the majority of the site volume.
Potential reduce by 27.7 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 27.7 kB or 77% of the original size.
Potential reduce by 8.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. Publicprocurement images are well optimized though.
Potential reduce by 117.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 117.1 kB or 66% of the original size.
Potential reduce by 239.3 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. Publicprocurement.be needs all CSS files to be minified and compressed as it can save up to 239.3 kB or 86% of the original size.
Number of requests can be reduced by 19 (56%)
34
15
The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Publicprocurement. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
publicprocurement.be
291 ms
nl
246 ms
css_Vts0XjaQXkIwBk9HNAoJwrvmmE9lw6S9oxqJuhh0OB0.css
215 ms
css_raWlcTsWXdNPgSmbpRwSqHc2UwJj7EuJSVEB-WHt4Cg.css
199 ms
css_MeruUk1NiDewXFX1tKIOC-1s3GOZ9oExyQCy6mV3Fhg.css
209 ms
css_M4aNq-yFJRHRkfvwVsFvyuIN0g3nPcpjzZB3pWp8Jbc.css
197 ms
css_-yAW5SnX9B_zIIcRh8wumnm0FjYiDX7sf4yI0vOMwUw.css
530 ms
css_MPTBu5fFGMwNnNZplKVZ6Cu7B5m1aGNlX6wyO3Cf7DM.css
440 ms
js_UWQINlriydSoeSiGQxToOUdv493zEa7dpsXC1OtYlZU.js
621 ms
js_NpX2cwCeepkWZZ194B6-ViyVBHleaYLOx5R9EWBOMRU.js
398 ms
js_FzhsychCqsHF07LSEWiaUrXNhTRX6ZvZkNecehmIdew.js
418 ms
js_VfzApfXw5Gg1wII72mRxVHqMi03pt2E5HYRVjWXkwQ8.js
473 ms
js_paiTaEsc1HNeBS2rkLc1NrprKrFnApv70kuY8awAaTI.js
590 ms
ga.js
97 ms
federalheader_bg.gif
127 ms
federalheader_logo.png
197 ms
logo.png
206 ms
background-image.png
514 ms
page-title-background.png
200 ms
hp-block-1-bg.png
191 ms
cake.png
314 ms
hp-block-2-bg.png
395 ms
hp-block-icon-01.png
393 ms
hp-block-3-bg.png
384 ms
hp-block-icon-02.png
398 ms
hp-block-icon-03.png
591 ms
hp-block-icon-04.png
599 ms
hp-block-icon-05.png
602 ms
e-notifications.png
607 ms
e-tendering.png
599 ms
e-awarding.png
726 ms
e-catalogue.png
774 ms
demo.png
800 ms
extlink_s.png
735 ms
OpenSans-Regular-webfont.woff
822 ms
OpenSans-CondBold-webfont.woff
807 ms
glyphicons-regular.woff
1096 ms
OpenSans-Italic-webfont.woff
987 ms
__utm.gif
25 ms
css_AbpHGcgLb-kRsJGnwFEktk7uzpZOCcBY74-YBdrKVGs.css
107 ms
publicprocurement.be accessibility score
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
Links do not have a discernible name
publicprocurement.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
publicprocurement.be SEO score
EN
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Publicprocurement.be can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Dutch language. Our system also found out that Publicprocurement.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.
publicprocurement.be
Open Graph description is not detected on the main page of Publicprocurement. 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: