3.7 sec in total
357 ms
3 sec
338 ms
Welcome to aardappel.be homepage info - get ready to check Aardappel best content right away, or after learning these important things about aardappel.be
Europe's favourite since 1536
Visit aardappel.beWe analyzed Aardappel.be page load time and found that the first response time was 357 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
aardappel.be performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value18.0 s
0/100
25%
Value7.3 s
29/100
10%
Value310 ms
78/100
30%
Value0.123
83/100
15%
Value12.3 s
15/100
10%
357 ms
1299 ms
90 ms
178 ms
186 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 59% of them (40 requests) were addressed to the original Aardappel.be, 4% (3 requests) were made to Google-analytics.com and 3% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Aardappel.be.
Page size can be reduced by 414.9 kB (49%)
840.1 kB
425.2 kB
In fact, the total size of Aardappel.be main page is 840.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. 45% of websites need less resources to load. Javascripts take 386.3 kB which makes up the majority of the site volume.
Potential reduce by 82.6 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 82.6 kB or 79% of the original size.
Potential reduce by 18.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. Aardappel images are well optimized though.
Potential reduce by 263.0 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 263.0 kB or 68% of the original size.
Potential reduce by 51.0 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. Aardappel.be needs all CSS files to be minified and compressed as it can save up to 51.0 kB or 82% of the original size.
Number of requests can be reduced by 36 (58%)
62
26
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aardappel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
aardappel.be
357 ms
www.aardappel.be
1299 ms
normalize.css
90 ms
style.css
178 ms
all.css
186 ms
skinned-select.css
188 ms
wpfp.css
189 ms
postratings-css.css
188 ms
comment-reply.js
189 ms
jquery.js
525 ms
jquery-migrate.min.js
264 ms
wpfp.js
266 ms
buttons.js
7 ms
jquery.main.js
359 ms
skinned-select.js
269 ms
custom-form-elements.js
277 ms
postratings-js.js
347 ms
pinit.js
7 ms
28a91a
19 ms
css
44 ms
wp-emoji-release.min.js
196 ms
header.jpg
198 ms
btnAccount-bg-right.png
151 ms
btnAccount-bg.png
150 ms
btnAccount-person.png
151 ms
btnAccount-arrow.png
147 ms
aardappelchips-met-krab-gember-en-avocado-630x340.jpg
206 ms
ontdek.jpg
451 ms
Gevulde-aardappel-met-merguez-en-knoflook_2-150x150.jpg
201 ms
Gepofte-aardappel-met-gerookte-paling-150x150.jpg
202 ms
Carpaccio-van-kalfsvlees-op-aardappelsalade-150x150.jpg
203 ms
aardappelchips-met-krab-gember-en-avocado-150x150.jpg
269 ms
d395771085aab05244a4fb8fd91bf4ee-150x150.jpg
270 ms
ddb30680a691d157187ee1cf9e896d03-150x150.jpg
271 ms
4k-eenvoudig-vrolijk-bloemetje.jpg
457 ms
f-logo01_lvbo.gif
278 ms
f-logo02.gif
356 ms
sdk.js
271 ms
bg-text.png
329 ms
arrow02.png
334 ms
none.gif
342 ms
ga.js
98 ms
getAllAppDefault.esi
118 ms
rating_over.gif
304 ms
dropdown.png
306 ms
28A91A_0_0.woff
485 ms
5fdc935e-9e30-442a-bbe9-8d887b858471.woff
410 ms
GTNBLj58pwv6qyDO1RGnXaCWcynf_cDxXwCLxiixG1c.woff
44 ms
pinit_main.js
73 ms
__utm.gif
34 ms
__utm.gif
22 ms
getSegment.php
12 ms
checkOAuth.esi
6 ms
t.dhj
63 ms
74 ms
xd_arbiter.php
236 ms
xd_arbiter.php
450 ms
t.dhj
51 ms
x35248
130 ms
s-3271.xgi
14 ms
pixel
35 ms
hbpix
182 ms
13 ms
xrefid.xgi
7 ms
22 ms
cm
17 ms
13583
20 ms
like.php
52 ms
aardappel.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
aardappel.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
aardappel.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aardappel.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it does not match the claimed English language. Our system also found out that Aardappel.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.
aardappel.be
Open Graph data is detected on the main page of Aardappel. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: