privacycommission.be Website Information
Daily Unique Visits: 40,809
Daily Page Views: 244,854
Income Per Day: $490
Estimated Value: $352,800
privacycommission.be is registered under .BE top-level domain. Please check other sites in .BE zone.
Website privacycommission.be is using the following name servers:
- ns5.g-net.be
- ns2.g-net.be
- ns.g-net.be
and is probably hosted by SmalS-MvM. See the full list of other websites hosted by SmalS-MvM.
The highest website privacycommission.be position in Alexa rank database was 33042 and the lowest rank position was 996642. Current position of privacycommission.be in Alexa rank database is 35145.
Desktop speed score of privacycommission.be (83/100) is better than the results of 76.15% of other sites and shows that the page is performing great on desktop computers.
Mobile usability score of privacycommission.be (65/100) is better than the results of 13.11% of other sites and means that the page is not mobile-friendly.
Mobile speed score of privacycommission.be (71/100) is better than the results of 78.26% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
privacycommission.be Alexa Rank
The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.
privacycommission.be whois
WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.
%
% The WHOIS service offered by DNS Belgium and the access to the records in the DNS Belgium
% WHOIS database are provided for information purposes only. It allows
% persons to check whether a specific domain name is still available or not
% and to obtain information related to the registration records of
% existing domain names.
%
% DNS Belgium cannot, under any circumstances, be held liable where the stored
% information would prove to be incomplete or inaccurate in any sense.
%
% By submitting a query you agree not to use the information made available
% to:
% - allow, enable or otherwise support the transmission of unsolicited,
% commercial advertising or other solicitations whether via email or otherwise;
% - target advertising in any possible way;
% - to cause nuisance in any possible way to the domain name holders by sending
% messages to them (whether by automated, electronic processes capable of
% enabling high volumes or other possible means).
%
% Without prejudice to the above, it is explicitly forbidden to extract, copy
% and/or use or re-utilise in any form and by any means (electronically or
% not) the whole or a quantitatively or qualitatively substantial part
% of the contents of the WHOIS database without prior and explicit permission
% by DNS Belgium, nor in any attempt thereof, to apply automated, electronic
% processes to DNS Belgium (or its systems).
%
% You agree that any reproduction and/or transmission of data for commercial
% purposes will always be considered as the extraction of a substantial
% part of the content of the WHOIS database.
%
% By submitting the query you agree to abide by this policy and accept that
% DNS Belgium can take measures to limit the use of its whois services in order to
% protect the privacy of its registrants or the integrity of the database.
%
Domain: privacycommission.be
Status: NOT AVAILABLE
Registered: Tue May 11 2004
Registrant:
Not shown, please visit www.dnsbelgium.be for webbased whois.
Registrar Technical Contacts:
Registrar:
Name: Registrar.eu
Website: https://www.openprovider.com/
Nameservers:
elma.ns.cloudflare.com
piers.ns.cloudflare.com
Keys:
keyTag:2371 flags:KSK protocol:3 algorithm:ECDSAP256SHA256 pubKey:mdsswUyr3DPW132mOi8V9xESWE8jTo0dxCjjnopKl+GqJxpVXckHAeF+KkxLbxILfDLUT0rAK9iUzy1L53eKGQ==
Flags:
clientTransferProhibited
Please visit www.dnsbelgium.be for more info.
privacycommission.be server information
Servers Location
privacycommission.be desktop page speed rank
Last tested: 2015-09-28
privacycommission.be Desktop Speed Test Quick Summary
priority - 8Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
http://www.privacycommission.be/misc/jquery.once.js?v=1.2 (3 days)
http://www.privacycommission.be/modules/field/theme/field.css?nqr8pt (3 days)
http://www.privacycommission.be/modules/locale/locale.css?nqr8pt (3 days)
http://www.privacycommission.be/modules/node/node.css?nqr8pt (3 days)
http://www.privacycommission.be/modules/search/search.css?nqr8pt (3 days)
http://www.privacycommission.be/modules/system/system.base.css?nqr8pt (3 days)
http://www.privacycommission.be/modules/system/system.menus.css?nqr8pt (3 days)
http://www.privacycommission.be/modules/system/system.messages.css?nqr8pt (3 days)
http://www.privacycommission.be/modules/system/system.theme.css?nqr8pt (3 days)
http://www.privacycommission.be/modules/user/user.css?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/modules/…ustom_facet.css?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/modules/…utocomplete.css?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/modules/…autocomplete.js?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/modules/…utocomplete.css?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/modules/…autocomplete.js?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/modules/…/css/ctools.css?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/modules/…te_api/date.css?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/modules/…epicker.1.7.css?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/modules/…jquery.min.js?v=1.10.2 (3 days)
http://www.privacycommission.be/sites/all/modules/…css/lexicon.css?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/modules/…s/css/views.css?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/themes/p…n/css/style.css?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/themes/p…zr-2.0.6.min.js?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/themes/p…on/js/script.js?nqr8pt (3 days)
http://www.privacycommission.be/sites/privacycommi…bxSlider.min.js?nqr8pt (3 days)
http://www.privacycommission.be/sites/privacycommi…y.easing.1.3.js?nqr8pt (3 days)
http://www.privacycommission.be/sites/privacycommi…_the_picture.js?nqr8pt (3 days)
priority - 6Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 10 blocking script resources and 18 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
http://www.privacycommission.be/misc/jquery.once.js?v=1.2
http://www.privacycommission.be/misc/drupal.js?nqr8pt
http://www.privacycommission.be/sites/all/modules/…autocomplete.js?nqr8pt
http://www.privacycommission.be/sites/all/modules/…autocomplete.js?nqr8pt
http://www.privacycommission.be/sites/privacycommi…bxSlider.min.js?nqr8pt
http://www.privacycommission.be/sites/privacycommi…y.easing.1.3.js?nqr8pt
http://www.privacycommission.be/sites/privacycommi…_the_picture.js?nqr8pt
http://www.privacycommission.be/sites/all/themes/p…zr-2.0.6.min.js?nqr8pt
http://www.privacycommission.be/sites/all/themes/p…on/js/script.js?nqr8pt
Optimize CSS Delivery of the following:
http://www.privacycommission.be/modules/system/system.menus.css?nqr8pt
http://www.privacycommission.be/modules/system/system.messages.css?nqr8pt
http://www.privacycommission.be/modules/system/system.theme.css?nqr8pt
http://www.privacycommission.be/sites/all/modules/…ustom_facet.css?nqr8pt
http://www.privacycommission.be/sites/all/modules/…te_api/date.css?nqr8pt
http://www.privacycommission.be/sites/all/modules/…epicker.1.7.css?nqr8pt
http://www.privacycommission.be/modules/field/theme/field.css?nqr8pt
http://www.privacycommission.be/modules/node/node.css?nqr8pt
http://www.privacycommission.be/modules/search/search.css?nqr8pt
http://www.privacycommission.be/modules/user/user.css?nqr8pt
http://www.privacycommission.be/sites/all/modules/…s/css/views.css?nqr8pt
http://www.privacycommission.be/sites/all/modules/…utocomplete.css?nqr8pt
http://www.privacycommission.be/sites/all/modules/…utocomplete.css?nqr8pt
http://www.privacycommission.be/sites/all/modules/…/css/ctools.css?nqr8pt
http://www.privacycommission.be/sites/all/modules/…css/lexicon.css?nqr8pt
http://www.privacycommission.be/modules/locale/locale.css?nqr8pt
http://www.privacycommission.be/sites/all/themes/p…n/css/style.css?nqr8pt
priority - 3Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 31.6KiB (12% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…ges/bck_balloonTop.png could save 2.9KiB (89% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…images/lgo_cbpl_en.png could save 2.9KiB (28% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…/btn_carrouselNext.png could save 1.2KiB (58% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…/btn_moreFlashHome.png could save 1.1KiB (49% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…ages/ill_arrowBlue.png could save 1,001B (80% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…images/bul_content.png could save 977B (86% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…l_bullCarrousel_HL.png could save 970B (78% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…ages/bck_flashHome.jpg could save 945B (2% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…ges/ill_navPointer.png could save 943B (84% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…images/bul_funcNav.png could save 923B (87% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…es/bck_mainNavLine.png could save 920B (91% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…ges/btn_searchPlus.png could save 919B (70% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…/images/bck_search.png could save 918B (55% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…ion/images/bck_box.png could save 911B (85% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…ges/ill_arrowWhite.png could save 911B (78% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…es/bck_mainNavHome.png could save 910B (82% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…on/images/bck_page.png could save 706B (1% reduction).
Losslessly compressing http://www.privacycommission.be/sites/privacycommi…12_0.jpg?itok=BW9wGkq_ could save 512B (5% reduction).
priority - 1Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 7.8KiB (51% reduction).
Minifying http://www.privacycommission.be/sites/all/modules/…autocomplete.js?nqr8pt could save 2.2KiB (34% reduction) after compression.
Minifying http://www.privacycommission.be/sites/privacycommi…y.easing.1.3.js?nqr8pt could save 1.1KiB (58% reduction) after compression.
Minifying http://www.privacycommission.be/misc/jquery.once.js?v=1.2 could save 816B (76% reduction) after compression.
priority - 1Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 3.3KiB (24% reduction).
Minifying http://www.privacycommission.be/modules/system/system.base.css?nqr8pt could save 825B (44% reduction) after compression.
priority - 0Reduce server response time
privacycommission.be Desktop Resource Breakdown
Total Resources | 54 |
Number of Hosts | 2 |
Static Resources | 49 |
JavaScript Resources | 10 |
CSS Resources | 18 |
privacycommission.be mobile page speed rank
Last tested: 2019-07-04
privacycommission.be Mobile Speed Test Quick Summary
priority - 24Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 10 blocking script resources and 18 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
http://www.privacycommission.be/misc/jquery.once.js?v=1.2
http://www.privacycommission.be/misc/drupal.js?nqr8pt
http://www.privacycommission.be/sites/all/modules/…autocomplete.js?nqr8pt
http://www.privacycommission.be/sites/all/modules/…autocomplete.js?nqr8pt
http://www.privacycommission.be/sites/privacycommi…bxSlider.min.js?nqr8pt
http://www.privacycommission.be/sites/privacycommi…y.easing.1.3.js?nqr8pt
http://www.privacycommission.be/sites/privacycommi…_the_picture.js?nqr8pt
http://www.privacycommission.be/sites/all/themes/p…zr-2.0.6.min.js?nqr8pt
http://www.privacycommission.be/sites/all/themes/p…on/js/script.js?nqr8pt
Optimize CSS Delivery of the following:
http://www.privacycommission.be/modules/system/system.menus.css?nqr8pt
http://www.privacycommission.be/modules/system/system.messages.css?nqr8pt
http://www.privacycommission.be/modules/system/system.theme.css?nqr8pt
http://www.privacycommission.be/sites/all/modules/…ustom_facet.css?nqr8pt
http://www.privacycommission.be/sites/all/modules/…te_api/date.css?nqr8pt
http://www.privacycommission.be/sites/all/modules/…epicker.1.7.css?nqr8pt
http://www.privacycommission.be/modules/field/theme/field.css?nqr8pt
http://www.privacycommission.be/modules/node/node.css?nqr8pt
http://www.privacycommission.be/modules/search/search.css?nqr8pt
http://www.privacycommission.be/modules/user/user.css?nqr8pt
http://www.privacycommission.be/sites/all/modules/…s/css/views.css?nqr8pt
http://www.privacycommission.be/sites/all/modules/…utocomplete.css?nqr8pt
http://www.privacycommission.be/sites/all/modules/…utocomplete.css?nqr8pt
http://www.privacycommission.be/sites/all/modules/…/css/ctools.css?nqr8pt
http://www.privacycommission.be/sites/all/modules/…css/lexicon.css?nqr8pt
http://www.privacycommission.be/modules/locale/locale.css?nqr8pt
http://www.privacycommission.be/sites/all/themes/p…n/css/style.css?nqr8pt
priority - 12Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
http://www.privacycommission.be/misc/jquery.once.js?v=1.2 (3 days)
http://www.privacycommission.be/modules/field/theme/field.css?nqr8pt (3 days)
http://www.privacycommission.be/modules/locale/locale.css?nqr8pt (3 days)
http://www.privacycommission.be/modules/node/node.css?nqr8pt (3 days)
http://www.privacycommission.be/modules/search/search.css?nqr8pt (3 days)
http://www.privacycommission.be/modules/system/system.base.css?nqr8pt (3 days)
http://www.privacycommission.be/modules/system/system.menus.css?nqr8pt (3 days)
http://www.privacycommission.be/modules/system/system.messages.css?nqr8pt (3 days)
http://www.privacycommission.be/modules/system/system.theme.css?nqr8pt (3 days)
http://www.privacycommission.be/modules/user/user.css?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/modules/…ustom_facet.css?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/modules/…utocomplete.css?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/modules/…autocomplete.js?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/modules/…utocomplete.css?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/modules/…autocomplete.js?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/modules/…/css/ctools.css?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/modules/…te_api/date.css?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/modules/…epicker.1.7.css?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/modules/…jquery.min.js?v=1.10.2 (3 days)
http://www.privacycommission.be/sites/all/modules/…css/lexicon.css?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/modules/…s/css/views.css?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/themes/p…n/css/style.css?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/themes/p…zr-2.0.6.min.js?nqr8pt (3 days)
http://www.privacycommission.be/sites/all/themes/p…on/js/script.js?nqr8pt (3 days)
http://www.privacycommission.be/sites/privacycommi…bxSlider.min.js?nqr8pt (3 days)
http://www.privacycommission.be/sites/privacycommi…y.easing.1.3.js?nqr8pt (3 days)
http://www.privacycommission.be/sites/privacycommi…_the_picture.js?nqr8pt (3 days)
priority - 3Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 31.6KiB (12% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…ges/bck_balloonTop.png could save 2.9KiB (89% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…images/lgo_cbpl_en.png could save 2.9KiB (28% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…/btn_carrouselNext.png could save 1.2KiB (58% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…/btn_moreFlashHome.png could save 1.1KiB (49% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…ages/ill_arrowBlue.png could save 1,001B (80% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…images/bul_content.png could save 977B (86% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…l_bullCarrousel_HL.png could save 970B (78% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…ages/bck_flashHome.jpg could save 945B (2% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…ges/ill_navPointer.png could save 943B (84% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…images/bul_funcNav.png could save 923B (87% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…es/bck_mainNavLine.png could save 920B (91% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…ges/btn_searchPlus.png could save 919B (70% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…/images/bck_search.png could save 918B (55% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…ion/images/bck_box.png could save 911B (85% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…ges/ill_arrowWhite.png could save 911B (78% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…es/bck_mainNavHome.png could save 910B (82% reduction).
Losslessly compressing http://www.privacycommission.be/sites/all/themes/p…on/images/bck_page.png could save 706B (1% reduction).
Losslessly compressing http://www.privacycommission.be/sites/privacycommi…12_0.jpg?itok=BW9wGkq_ could save 512B (5% reduction).
priority - 1Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 7.8KiB (51% reduction).
Minifying http://www.privacycommission.be/sites/all/modules/…autocomplete.js?nqr8pt could save 2.2KiB (34% reduction) after compression.
Minifying http://www.privacycommission.be/sites/privacycommi…y.easing.1.3.js?nqr8pt could save 1.1KiB (58% reduction) after compression.
Minifying http://www.privacycommission.be/misc/jquery.once.js?v=1.2 could save 816B (76% reduction) after compression.
priority - 1Reduce server response time
priority - 1Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 3.3KiB (24% reduction).
Minifying http://www.privacycommission.be/modules/system/system.base.css?nqr8pt could save 825B (44% reduction) after compression.
privacycommission.be Mobile Resource Breakdown
Total Resources | 54 |
Number of Hosts | 2 |
Static Resources | 49 |
JavaScript Resources | 10 |
CSS Resources | 18 |
privacycommission.be mobile page usability
Last tested: 2019-07-04
privacycommission.be Mobile Usability Test Quick Summary
priority - 36Use legible font sizes
The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.
The following text fragments have a small font size. Increase the font size to make them more legible.
Jump to Navigation
renders only 4 pixels tall (12 CSS pixels).© 2015 Commiss…ion of Privacy
and 10 others render only 4 pixels tall (11 CSS pixels).EN
renders only 4 pixels tall (11 CSS pixels).The Privacy Co…gly protected,
and 1 others render only 4 pixels tall (12 CSS pixels).The Belgian Pr…e on Facebook.
renders only 5 pixels tall (14 CSS pixels).Consult the Du…ly theme page.
renders only 5 pixels tall (14 CSS pixels).PRIVACY TOPICS
renders only 6 pixels tall (16 CSS pixels).Our opinions,…ecommendations
and 3 others render only 4 pixels tall (11 CSS pixels).LEGISLATION & STANDARDS
renders only 6 pixels tall (16 CSS pixels).DECISIONS
renders only 6 pixels tall (16 CSS pixels).ABOUT THE CPP
renders only 6 pixels tall (16 CSS pixels).PUBLICATIONS
renders only 6 pixels tall (16 CSS pixels).Search form
renders only 7 pixels tall (20 CSS pixels).Search
renders only 5 pixels tall (14 CSS pixels).MAKE OR MANAGE
and 4 others render only 5 pixels tall (14 CSS pixels).us
renders only 4 pixels tall (12 CSS pixels).a data breach
renders only 4 pixels tall (12 CSS pixels).an authorisation
renders only 4 pixels tall (12 CSS pixels).a notification
renders only 4 pixels tall (12 CSS pixels).the public register
renders only 4 pixels tall (12 CSS pixels).Related websites
renders only 7 pixels tall (20 CSS pixels).anthologieprivacy.be
and 1 others render only 5 pixels tall (15 CSS pixels).A website with…ch and French.
and 1 others render only 4 pixels tall (12 CSS pixels).In the picture
renders only 7 pixels tall (20 CSS pixels).Prevent data breaches
renders only 6 pixels tall (16 CSS pixels).Following seve…omputer files.
renders only 4 pixels tall (12 CSS pixels).Recently publi…n this website
and 2 others render only 7 pixels tall (20 CSS pixels).you are filmed…illance camera
and 8 others render only 4 pixels tall (11 CSS pixels).Other topics t…ion deals with
and 1 others render only 4 pixels tall (11 CSS pixels).For more infor…se consult our
and 3 others render only 4 pixels tall (11 CSS pixels).priority - 10Configure the viewport
Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.
priority - 8Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
<a href="/en/sitemap" class="">Site map</a>
and 7 others are close to other tap targets.<a href="/en" class="language-link active">en</a>
is close to 2 other tap targets.<a href="http://www.pri…a-van-de-maand" class="more">Consult the Du…ly theme page.</a>
is close to 1 other tap targets.<a href="/en/privacy-topics" class="main-link">Privacy topics</a>
is close to 3 other tap targets.<a href="/en/privacy-topics" class="main-link">Privacy topics</a>
is close to 2 other tap targets.<div>The topics we…with every day</div>
is close to 2 other tap targets.<div>The topics we…with every day</div>
and 1 others are close to other tap targets.<input id="edit-submit--2" type="submit" name="op" class="form-submit">
is close to 2 other tap targets.<a href="/en/search/site" class="advanced-search"></a>
is close to 1 other tap targets.<a href="http://www.pri…/en/contact-us" class="cta-1">Contact us</a>
is close to 1 other tap targets.<a href="http://www.pri…e-donn%C3%A9es" class="cta-5">Notify a data breach</a>
is close to 2 other tap targets.<a href="http://www.pri…authorization#" class="cta-2">Request an authorisation</a>
is close to 2 other tap targets.<a href="https://eloket…iteLanguage=fr" class="cta-3">Make or manage a notification</a>
is close to 2 other tap targets.<a href="https://eloket…iteLanguage=fr" class="cta-4">Consult the public register</a>
is close to 1 other tap targets.<a href="/fr/cameras-de-surveillance">Surveillance cameras</a>
and 5 others are close to other tap targets.priority - 3Size content to viewport
The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.
The page content is 1,000 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:
<a href="" class="bx-next">next</a>
falls outside the viewport.The element
<div id="stamp">
falls outside the viewport.privacycommission.be HTML validation
Errors
Attribute “xmlns:content” not allowed here.
"...IE)]><!--> <html lang="en" class="no-js" dir="ltr" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#"> <!--<..."
Attribute “xmlns:dc” not allowed here.
"...IE)]><!--> <html lang="en" class="no-js" dir="ltr" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#"> <!--<..."
Attribute “xmlns:foaf” not allowed here.
"...IE)]><!--> <html lang="en" class="no-js" dir="ltr" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#"> <!--<..."
Attribute “xmlns:og” not allowed here.
"...IE)]><!--> <html lang="en" class="no-js" dir="ltr" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#"> <!--<..."
Attribute “xmlns:rdfs” not allowed here.
"...IE)]><!--> <html lang="en" class="no-js" dir="ltr" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#"> <!--<..."
Attribute “xmlns:sioc” not allowed here.
"...IE)]><!--> <html lang="en" class="no-js" dir="ltr" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#"> <!--<..."
Attribute “xmlns:sioct” not allowed here.
"...IE)]><!--> <html lang="en" class="no-js" dir="ltr" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#"> <!--<..."
Attribute “xmlns:skos” not allowed here.
"...IE)]><!--> <html lang="en" class="no-js" dir="ltr" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#"> <!--<..."
Attribute “xmlns:xsd” not allowed here.
"...IE)]><!--> <html lang="en" class="no-js" dir="ltr" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#"> <!--<..."
The “profile” attribute on the “head” element is obsolete. To declare which “meta” terms are used in the document, instead register the names as meta extensions. To trigger specific UA behaviors, use a “link” element instead.
"...[endif]--> <head profile="http://www.w3.org/1999/xhtml/vocab"> <me..."
Element “li” not allowed as child of element “nav” in this context. (Suppressing further errors from this subtree.)
"... <li><a hre..." Line: 96 Column: 96 - 99
"...p</a></li><li><a hre..." Line: 96 Column: 180 - 183
"...y</a></li><li><a hre..." Line: 96 Column: 255 - 258
"...Q</a></li><li><a hre..." Line: 96 Column: 331 - 334
"...s</a></li><li><a hre..." Line: 96 Column: 407 - 410
"...s</a></li><li><a hre..."
When the attribute “xml:lang” in no namespace is specified, the element must also have the attribute “lang” present with the same value.
"...nl first"><a href="/nl" class="language-link" xml:lang="nl">nl</a>..." Line: 123 Column: 23 - 79
"...n active"><a href="/en" class="language-link active" xml:lang="en">en</a>..." Line: 124 Column: 16 - 65
"...lass="fr"><a href="/fr" class="language-link" xml:lang="fr">fr</a>..." Line: 125 Column: 21 - 70
"..."de last"><a href="/de" class="language-link" xml:lang="de">de</a>..."
An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
"...ast odd"> <img src="/sites/all/themes/privacycommission/images/mail.png" /> ..."
Warnings
Attribute with the local name “xmlns:content” is not serializable as XML 1.0.
"...IE)]><!--> <html lang="en" class="no-js" dir="ltr" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#"> <!--<..."
Attribute with the local name “xmlns:dc” is not serializable as XML 1.0.
"...IE)]><!--> <html lang="en" class="no-js" dir="ltr" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#"> <!--<..."
Attribute with the local name “xmlns:foaf” is not serializable as XML 1.0.
"...IE)]><!--> <html lang="en" class="no-js" dir="ltr" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#"> <!--<..."
Attribute with the local name “xmlns:og” is not serializable as XML 1.0.
"...IE)]><!--> <html lang="en" class="no-js" dir="ltr" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#"> <!--<..."
Attribute with the local name “xmlns:rdfs” is not serializable as XML 1.0.
"...IE)]><!--> <html lang="en" class="no-js" dir="ltr" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#"> <!--<..."
Attribute with the local name “xmlns:sioc” is not serializable as XML 1.0.
"...IE)]><!--> <html lang="en" class="no-js" dir="ltr" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#"> <!--<..."
Attribute with the local name “xmlns:sioct” is not serializable as XML 1.0.
"...IE)]><!--> <html lang="en" class="no-js" dir="ltr" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#"> <!--<..."
Attribute with the local name “xmlns:skos” is not serializable as XML 1.0.
"...IE)]><!--> <html lang="en" class="no-js" dir="ltr" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#"> <!--<..."
Attribute with the local name “xmlns:xsd” is not serializable as XML 1.0.
"...IE)]><!--> <html lang="en" class="no-js" dir="ltr" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/terms/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#"> <!--<..."
Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.
"...floatR"> <section class="region region-search-block"> <..." Line: 117 Column: 14 - 51
"... <section class="region region-header"> <..." Line: 132 Column: 10 - 52
"... <section class="region region-highlighted"> <..." Line: 153 Column: 9 - 48
"...> <section class="region region-home-cta"> <..." Line: 209 Column: 15 - 60
"... <section class="region region-home-carrousel"> <..." Line: 242 Column: 13 - 50
"... <section class="region region-bottom"> <..." Line: 259 Column: 9 - 50
"...> <section class="region region-bottom-bar"> <..."
Article lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all articles.
"...der"> <article id="block-locale-language" class="block block-locale first last odd"> ..." Line: 154 Column: 5 - 81
"...cta"> <article id="block-views-cta-block" class="block block-views first last odd"> ..." Line: 277 Column: 5 - 73
"...ist"> <article id="block-block-1" class="block block-block first last odd"> ..."
Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools).
"...fix"> <h1 id="intro">The Pr..."
privacycommission.be similar domains
www.privacycommission.net
www.privacycommission.org
www.privacycommission.info
www.privacycommission.biz
www.privacycommission.us
www.privacycommission.mobi
www.rivacycommission.be
www.privacycommission.be
www.orivacycommission.be
www.porivacycommission.be
www.oprivacycommission.be
www.lrivacycommission.be
www.plrivacycommission.be
www.lprivacycommission.be
www.pivacycommission.be
www.peivacycommission.be
www.preivacycommission.be
www.perivacycommission.be
www.pdivacycommission.be
www.prdivacycommission.be
www.pdrivacycommission.be
www.pfivacycommission.be
www.prfivacycommission.be
www.pfrivacycommission.be
www.ptivacycommission.be
www.prtivacycommission.be
www.ptrivacycommission.be
www.prvacycommission.be
www.pruvacycommission.be
www.priuvacycommission.be
www.pruivacycommission.be
www.prjvacycommission.be
www.prijvacycommission.be
www.prjivacycommission.be
www.prkvacycommission.be
www.prikvacycommission.be
www.prkivacycommission.be
www.provacycommission.be
www.priovacycommission.be
www.proivacycommission.be
www.priacycommission.be
www.pricacycommission.be
www.privcacycommission.be
www.pricvacycommission.be
www.prifacycommission.be
www.privfacycommission.be
www.prifvacycommission.be
www.prigacycommission.be
www.privgacycommission.be
www.prigvacycommission.be
www.pribacycommission.be
www.privbacycommission.be
www.pribvacycommission.be
www.privcycommission.be
www.privqcycommission.be
www.privaqcycommission.be
www.privqacycommission.be
www.privwcycommission.be
www.privawcycommission.be
www.privwacycommission.be
www.privscycommission.be
www.privascycommission.be
www.privsacycommission.be
www.privzcycommission.be
www.privazcycommission.be
www.privzacycommission.be
www.privaycommission.be
www.privaxycommission.be
www.privacxycommission.be
www.privaxcycommission.be
www.privadycommission.be
www.privacdycommission.be
www.privadcycommission.be
www.privafycommission.be
www.privacfycommission.be
www.privafcycommission.be
www.privavycommission.be
www.privacvycommission.be
www.privavcycommission.be
www.privaccommission.be
www.privactcommission.be
www.privacytcommission.be
www.privactycommission.be
www.privacgcommission.be
www.privacygcommission.be
www.privacgycommission.be
www.privachcommission.be
www.privacyhcommission.be
www.privachycommission.be
www.privacucommission.be
www.privacyucommission.be
www.privacuycommission.be
www.privacyommission.be
www.privacyxommission.be
www.privacycxommission.be
www.privacyxcommission.be
www.privacydommission.be
www.privacycdommission.be
www.privacydcommission.be
www.privacyfommission.be
www.privacycfommission.be
www.privacyfcommission.be
www.privacyvommission.be
www.privacycvommission.be
www.privacyvcommission.be
www.privacycmmission.be
www.privacycimmission.be
www.privacycoimmission.be
www.privacyciommission.be
www.privacyckmmission.be
www.privacycokmmission.be
www.privacyckommission.be
www.privacyclmmission.be
www.privacycolmmission.be
www.privacyclommission.be
www.privacycpmmission.be
www.privacycopmmission.be
www.privacycpommission.be
www.privacycomission.be
www.privacyconmission.be
www.privacycomnmission.be
www.privacyconmmission.be
www.privacycojmission.be
www.privacycomjmission.be
www.privacycojmmission.be
www.privacycokmission.be
www.privacycomkmission.be
www.privacycomnission.be
www.privacycommnission.be
www.privacycomjission.be
www.privacycommjission.be
www.privacycomkission.be
www.privacycommkission.be
www.privacycommssion.be
www.privacycommussion.be
www.privacycommiussion.be
www.privacycommuission.be
www.privacycommjssion.be
www.privacycommijssion.be
www.privacycommkssion.be
www.privacycommikssion.be
www.privacycommossion.be
www.privacycommiossion.be
www.privacycommoission.be
www.privacycommision.be
www.privacycommiwsion.be
www.privacycommiswsion.be
www.privacycommiwssion.be
www.privacycommiesion.be
www.privacycommisesion.be
www.privacycommiession.be
www.privacycommidsion.be
www.privacycommisdsion.be
www.privacycommidssion.be
www.privacycommizsion.be
www.privacycommiszsion.be
www.privacycommizssion.be
www.privacycommixsion.be
www.privacycommisxsion.be
www.privacycommixssion.be
www.privacycommiasion.be
www.privacycommisasion.be
www.privacycommiassion.be
www.privacycommiswion.be
www.privacycommisswion.be
www.privacycommiseion.be
www.privacycommisseion.be
www.privacycommisdion.be
www.privacycommissdion.be
www.privacycommiszion.be
www.privacycommisszion.be
www.privacycommisxion.be
www.privacycommissxion.be
www.privacycommisaion.be
www.privacycommissaion.be
www.privacycommisson.be
www.privacycommissuon.be
www.privacycommissiuon.be
www.privacycommissuion.be
www.privacycommissjon.be
www.privacycommissijon.be
www.privacycommissjion.be
www.privacycommisskon.be
www.privacycommissikon.be
www.privacycommisskion.be
www.privacycommissoon.be
www.privacycommissioon.be
www.privacycommissoion.be
www.privacycommissin.be
www.privacycommissiin.be
www.privacycommissioin.be
www.privacycommissiion.be
www.privacycommissikn.be
www.privacycommissiokn.be
www.privacycommissiln.be
www.privacycommissioln.be
www.privacycommissilon.be
www.privacycommissipn.be
www.privacycommissiopn.be
www.privacycommissipon.be
www.privacycommissio.be
www.privacycommissiob.be
www.privacycommissionb.be
www.privacycommissiobn.be
www.privacycommissioh.be
www.privacycommissionh.be
www.privacycommissiohn.be
www.privacycommissioj.be
www.privacycommissionj.be
www.privacycommissiojn.be
www.privacycommissiom.be
www.privacycommissionm.be
www.privacycommissiomn.be
privacycommission.be Ping
Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.
privacycommission.be TRACEROUTE
Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.