4.3 sec in total
649 ms
2.7 sec
942 ms
Visit avlo.be now to see the best up-to-date AVLO content for Belgium and also check out these interesting facts you probably never knew about avlo.be
atletiek, lokeren, avlo, start 2 run, lopen, sport, hobby, sprint, spring
Visit avlo.beWe analyzed Avlo.be page load time and found that the first response time was 649 ms 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.
avlo.be performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value4.6 s
35/100
25%
Value4.0 s
81/100
10%
Value190 ms
90/100
30%
Value0.063
97/100
15%
Value5.0 s
77/100
10%
649 ms
162 ms
28 ms
189 ms
244 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 60% of them (31 requests) were addressed to the original Avlo.be, 19% (10 requests) were made to Static.xx.fbcdn.net and 15% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Avlo.be.
Page size can be reduced by 467.7 kB (8%)
5.5 MB
5.1 MB
In fact, the total size of Avlo.be main page is 5.5 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. Images take 5.1 MB which makes up the majority of the site volume.
Potential reduce by 28.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. This page needs HTML code to be minified as it can gain 4.2 kB, which is 11% 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 28.7 kB or 79% of the original size.
Potential reduce by 122.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. AVLO images are well optimized though.
Potential reduce by 149.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 149.1 kB or 66% of the original size.
Potential reduce by 167.9 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. Avlo.be needs all CSS files to be minified and compressed as it can save up to 167.9 kB or 86% of the original size.
Number of requests can be reduced by 18 (37%)
49
31
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AVLO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
avlo.be
649 ms
jquery.min.js
162 ms
css
28 ms
typography2.php
189 ms
bootstrap.css
244 ms
bootstrap-responsive.css
182 ms
font-awesome.css
187 ms
style.css
183 ms
jquery.min.js
325 ms
jquery-noconflict.js
256 ms
jquery-migrate.min.js
256 ms
bootstrap.min.js
255 ms
custom.js
256 ms
jquery.min.js
68 ms
pdf_button.png
276 ms
jeugdinfo.jpg
351 ms
veldlooplokeren_banner.png
351 ms
Starttorun.jpg
273 ms
veldloopzele.png
274 ms
citytrail.png
430 ms
atletiekinfo.png
587 ms
shop.png
430 ms
imschoot.jpg
430 ms
vaneetvelde.png
585 ms
optieksonck.jpg
474 ms
stany.png
592 ms
belfius.jpg
592 ms
82 ms
bg.jpg
1080 ms
avlo.png
85 ms
indoor_kaag_009.JPG
1673 ms
fontawesome-webfont.woff
239 ms
vertical-right.png
83 ms
likebox.php
187 ms
SkKWi5-9qSV.css
87 ms
5qLhvfW20va.css
107 ms
_rx8naC75Dy.js
165 ms
b94UUzHjapV.js
199 ms
0wM5s1Khldu.js
163 ms
TTCre3391I0.js
163 ms
424921_387479524597822_1003217935_n.jpg
121 ms
1491764_805027579509679_6557814262854038048_n.png
83 ms
12144856_1004609942893921_6163904199234723871_n.jpg
90 ms
12243308_931128900300214_3861441923169695134_n.jpg
130 ms
12647147_1657886517795645_3307905699235592578_n.jpg
132 ms
1904089_10152244464528584_2016492774_n.jpg
164 ms
10307195_10152797085077722_3949068142971013604_n.jpg
90 ms
12733358_10207284356999761_3935073710106147141_n.jpg
116 ms
wL6VQj7Ab77.png
24 ms
s7jcwEQH7Sx.png
26 ms
I6-MnjEovm5.js
25 ms
f6T91Deal_q.js
36 ms
avlo.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
Links do not have a discernible name
avlo.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
avlo.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
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Avlo.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 Avlo.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.
avlo.be
Open Graph description is not detected on the main page of AVLO. 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: