2.8 sec in total
438 ms
2.2 sec
139 ms
Welcome to cafe-uilenstede.nl homepage info - get ready to check Cafe Uilenstede best content right away, or after learning these important things about cafe-uilenstede.nl
Visit cafe-uilenstede.nlWe analyzed Cafe-uilenstede.nl page load time and found that the first response time was 438 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
cafe-uilenstede.nl performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value8.1 s
2/100
25%
Value10.3 s
8/100
10%
Value200 ms
89/100
30%
Value0.033
100/100
15%
Value7.8 s
45/100
10%
438 ms
160 ms
256 ms
369 ms
451 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 31% of them (16 requests) were addressed to the original Cafe-uilenstede.nl, 42% (22 requests) were made to Static.xx.fbcdn.net and 23% (12 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (585 ms) relates to the external source Scontent.xx.fbcdn.net.
Page size can be reduced by 8.4 kB (4%)
206.4 kB
198.0 kB
In fact, the total size of Cafe-uilenstede.nl main page is 206.4 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. 35% of websites need less resources to load. Images take 197.2 kB which makes up the majority of the site volume.
Potential reduce by 5.0 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 5.0 kB or 74% of the original size.
Potential reduce by 1.8 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. Cafe Uilenstede images are well optimized though.
Potential reduce by 626 B
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 626 B or 58% of the original size.
Potential reduce by 1.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. Cafe-uilenstede.nl needs all CSS files to be minified and compressed as it can save up to 1.0 kB or 75% of the original size.
Number of requests can be reduced by 17 (33%)
51
34
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cafe Uilenstede. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
cafe-uilenstede.nl
438 ms
swap-image.js
160 ms
uilenstede.css
256 ms
top_left.jpg
369 ms
logo.jpg
451 ms
top_right.jpg
458 ms
home_highlight.jpg
252 ms
separator.jpg
251 ms
over_ons.jpg
253 ms
events.jpg
395 ms
fotos.jpg
394 ms
aanbod.jpg
401 ms
gastenboek.jpg
512 ms
links.jpg
525 ms
login.jpg
544 ms
likebox.php
378 ms
bottom.jpg
448 ms
kyEKgjk51ZE.css
179 ms
xgj7bXhJNEH.css
223 ms
Czh0gDTFcBt.css
264 ms
N-k91nHCZS2.css
337 ms
6AlVa5wn0Ie.css
297 ms
ZeuPykSxSED.css
345 ms
q68gy-v_YMF.js
377 ms
FJmpeSpHpjS.js
376 ms
0wM5s1Khldu.js
302 ms
1bNoFZUdlYZ.js
341 ms
njO1TPvGzoR.js
356 ms
1QuX41zDRrx.js
409 ms
Oagsvfb4VWi.js
414 ms
LTv6ZK-5zxz.js
498 ms
1FCa-btixu2.js
421 ms
10500274_779096042111211_2999238220752314475_n.jpg
280 ms
safe_image.php
216 ms
40867_158109297543225_4093197_n.jpg
316 ms
12002217_967597963281831_4653532601210792845_n.jpg
356 ms
12342303_10153237070363015_8454535016505550705_n.jpg
392 ms
12313631_986411331415223_6669431337256131987_n.jpg
585 ms
12654609_1682676335348392_956192382721762923_n.jpg
451 ms
1379669_208535869327088_349222527_n.jpg
453 ms
12650833_1628422717419651_6044131502109119214_n.jpg
393 ms
10984617_948056341881846_3603409002749483959_n.jpg
443 ms
10500274_779096042111211_2999238220752314475_n.jpg
466 ms
40867_158109297543225_4093197_n.jpg
492 ms
10409408_779093615444787_6883316722695551399_n.jpg
533 ms
wL6VQj7Ab77.png
62 ms
s7jcwEQH7Sx.png
62 ms
QDwYpIaRyfG.png
61 ms
MiXXTBbOQzg.png
61 ms
K00K-UgnsKu.png
61 ms
I6-MnjEovm5.js
46 ms
pQrUxxo5oQp.js
47 ms
cafe-uilenstede.nl 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.
cafe-uilenstede.nl SEO score
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
NL
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cafe-uilenstede.nl 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 Cafe-uilenstede.nl main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
cafe-uilenstede.nl
Open Graph description is not detected on the main page of Cafe Uilenstede. 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: