15.9 sec in total
319 ms
15.4 sec
232 ms
Click here to check amazing Nazareth content for Belgium. Otherwise, check out these important facts you probably never knew about nazareth.be
Klik hier voor de homepage van de officiële website van gemeente en OCMW Nazareth, samen het lokaal bestuur Nazareth. Ontdek hier onze evenementen,
Visit nazareth.beWe analyzed Nazareth.be page load time and found that the first response time was 319 ms and then it took 15.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
nazareth.be performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value20.3 s
0/100
25%
Value11.1 s
6/100
10%
Value11,600 ms
0/100
30%
Value0.33
34/100
15%
Value24.3 s
0/100
10%
319 ms
365 ms
537 ms
206 ms
396 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 53% of them (67 requests) were addressed to the original Nazareth.be, 14% (18 requests) were made to Static.xx.fbcdn.net and 13% (17 requests) were made to Tools.uitdatabank.be. The less responsive or slowest element that took the longest time to load (11.2 sec) belongs to the original domain Nazareth.be.
Page size can be reduced by 1.0 MB (60%)
1.7 MB
699.0 kB
In fact, the total size of Nazareth.be main page is 1.7 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. 45% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 59.1 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 59.1 kB or 81% of the original size.
Potential reduce by 46.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. Nazareth images are well optimized though.
Potential reduce by 834.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 834.3 kB or 79% of the original size.
Potential reduce by 110.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. Nazareth.be needs all CSS files to be minified and compressed as it can save up to 110.1 kB or 84% of the original size.
Number of requests can be reduced by 79 (64%)
124
45
The browser has sent 124 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nazareth. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
nazareth.be
319 ms
www.nazareth.be
365 ms
home.html
537 ms
daisy.css
206 ms
jquery-ui-1.8.custom.css
396 ms
jquery-1.4.2.js
800 ms
jquery-ui-1.8.custom.js
1115 ms
jquery.utils.js
760 ms
jquery.daisy.i18n-en.js
382 ms
jquery.daisy.i18n-nl.js
392 ms
ui.datepicker-nl.js
567 ms
daisy.js
583 ms
calendar.js
696 ms
styleswitch.js
755 ms
jquery.datetimepicker.js
779 ms
jquery.versionmode.js
948 ms
menu.js
963 ms
slimbox2.css
979 ms
slimbox2.js
1027 ms
jquery.EmbedPicasaGallery.js
1140 ms
input-placeholder-text.js
1093 ms
1520.js
270 ms
reset.css
993 ms
layout.css
1228 ms
navigation.css
1066 ms
extras.css
11229 ms
docstyle.css
1150 ms
workflow.css
1212 ms
bg_body.png
205 ms
headerfoto.jpg
654 ms
b_search.png
205 ms
home_icon.png
206 ms
breadcrumb-arrow-icon.png
219 ms
data
223 ms
data
380 ms
data
404 ms
data
389 ms
data
522 ms
data
515 ms
data
663 ms
data
594 ms
data
588 ms
data
701 ms
data
734 ms
data
803 ms
data
813 ms
data
869 ms
data
885 ms
data
903 ms
data
923 ms
all.js
159 ms
bg_header.png
1014 ms
bg_container_m.png
1005 ms
logo_nazareth.png
1060 ms
outside__ffffff_24.png
1090 ms
bg_horzNav.png
1091 ms
div_horzNav.png
1096 ms
bg_dropdown.png
1205 ms
data
1720 ms
data
1696 ms
home_btn.png
1280 ms
bullet_white.gif
1286 ms
middleCol_h1_r.png
1289 ms
middleCol_h1_l.png
1381 ms
corners.png
1463 ms
h_nazareth_131_0_81190.gif
77 ms
load.js
172 ms
horzLine.png
1287 ms
rightCol_h1_r.png
1290 ms
182 ms
ga.js
6 ms
rightCol_h1_l.png
1385 ms
xd_arbiter.php
148 ms
xd_arbiter.php
257 ms
bg_footer.png
1449 ms
__utm.gif
20 ms
shared.js
85 ms
cnjquery-1.5.2.min.js
151 ms
page.php
333 ms
cnjquery-ui-1.8.11.custom.min.js
151 ms
cnjquery-ui-datepicker-nl-BE.js
76 ms
OuamSSjcmsY.css
172 ms
_QsWeqtE88z.css
217 ms
m3UplzJmRpp.css
256 ms
gevUuEH7cch.css
295 ms
gP0dke6H83j.css
299 ms
q68gy-v_YMF.js
335 ms
YvxwM8R7ol8.js
377 ms
ihptErjAmMX.js
350 ms
3So47A9WcrL.js
300 ms
cUsKAwzqrQw.js
410 ms
jquery.url.js
76 ms
jquery.rule.js
76 ms
event_detail.js
76 ms
login_popup.js
76 ms
tooltip.js
150 ms
11232905_841542402592268_2351408004691143299_n.jpg
231 ms
safe_image.php
174 ms
safe_image.php
215 ms
407668_230046150408566_137009707_n.jpg
262 ms
12512379_206956736328674_213382588167447307_n.jpg
351 ms
12523857_206956752995339_3253390266163936765_n.jpg
424 ms
735091_206956739662007_2438015232199992982_n.jpg
497 ms
1794699_206956942995320_9057432926693862183_n.jpg
398 ms
1910049_206956946328653_7675747621263799844_n.jpg
376 ms
471_981046121975228_1877966167624425177_n.jpg
389 ms
12801693_202464193446341_2963902781981397602_n.jpg
422 ms
12814702_202464190113008_7200258064483064881_n.jpg
417 ms
1934679_202464200113007_1563932718844984583_n.jpg
431 ms
12042728_202464206779673_8100074965711926806_n.jpg
437 ms
12799205_202464213446339_1106456940396038036_n.jpg
490 ms
1779684_226311724221441_232631449_n.jpg
462 ms
wL6VQj7Ab77.png
74 ms
s7jcwEQH7Sx.png
75 ms
GtIpNnEyqq_.png
74 ms
lRyN50VcaFW.js
42 ms
activities.js
77 ms
tracking.js
285 ms
gtm_link_tracking.js
77 ms
R9a_DtVRZgv.js
41 ms
cUDgRFxaoIk.js
41 ms
0JBr1QHp8Gi.js
41 ms
kDOzhTr2W91.js
44 ms
loadResults
665 ms
gtm.js
52 ms
jquery-ui.css
87 ms
ajax-loader.gif
78 ms
nazareth.be accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
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
nazareth.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
nazareth.be SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
NL
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nazareth.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 Nazareth.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.
nazareth.be
Open Graph description is not detected on the main page of Nazareth. 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: