7.1 sec in total
1.4 sec
5.5 sec
289 ms
Visit palaestra.nl now to see the best up-to-date Palaestra content and also check out these interesting facts you probably never knew about palaestra.nl
Zin om nu eens echt werk van je fitheid te maken? Op onze site nemen we praktische gezondheidstips met je door. Lees snel verder.
Visit palaestra.nlWe analyzed Palaestra.nl page load time and found that the first response time was 1.4 sec and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
palaestra.nl performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value9.4 s
1/100
25%
Value11.9 s
4/100
10%
Value330 ms
76/100
30%
Value0.027
100/100
15%
Value8.3 s
40/100
10%
1358 ms
189 ms
199 ms
398 ms
409 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 50% of them (56 requests) were addressed to the original Palaestra.nl, 29% (33 requests) were made to Static.xx.fbcdn.net and 11% (12 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Palaestra.nl.
Page size can be reduced by 639.7 kB (24%)
2.7 MB
2.0 MB
In fact, the total size of Palaestra.nl main page is 2.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. 65% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 37.9 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 9.4 kB, which is 20% 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 37.9 kB or 81% of the original size.
Potential reduce by 27.6 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. Palaestra images are well optimized though.
Potential reduce by 354.8 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 354.8 kB or 69% of the original size.
Potential reduce by 219.5 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. Palaestra.nl needs all CSS files to be minified and compressed as it can save up to 219.5 kB or 83% of the original size.
Number of requests can be reduced by 59 (56%)
105
46
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Palaestra. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
palaestra.nl
1358 ms
menu-9e68a240d56ab431406dc805226e2964.css
189 ms
grid-responsive.css
199 ms
bootstrap.css
398 ms
master-30b1c5da85885684f54e522f0576c251.css
409 ms
mediaqueries.css
191 ms
djimageslider.css
199 ms
magnific.css
284 ms
jquery.min.js
579 ms
jquery-noconflict.js
290 ms
jquery-migrate.min.js
297 ms
caption.js
377 ms
mootools-core.js
596 ms
core.js
391 ms
mootools-more.js
719 ms
browser-engines.js
490 ms
rokmediaqueries.js
490 ms
rokmediaqueries.js
493 ms
sidemenu.js
606 ms
bootstrap.min.js
607 ms
jquery.easing.min.js
607 ms
slider.js
675 ms
magnific.js
680 ms
magnific-init.js
679 ms
html5fallback.js
685 ms
css
69 ms
paper.png
559 ms
Header_logo.png
193 ms
h_icon_phone_b.png
102 ms
contact_mail_front2.png
106 ms
loader.gif
103 ms
001_ruimte.jpg
280 ms
002_ruiimte.jpg
356 ms
003_ruimte.jpg
355 ms
004_ruimte.jpg
355 ms
005_ruimte.jpg
379 ms
PA-006kl.jpg
556 ms
PA-007kl.jpg
635 ms
PA-008kl.jpg
816 ms
prev.png
454 ms
next.png
476 ms
play.png
554 ms
pause.png
569 ms
printButton.png
655 ms
emailButton.png
655 ms
wifi_logo.png
656 ms
StichtingSFM_logo_150.png
664 ms
header-logo.png
731 ms
Cardio_front.png
759 ms
huiskamer_front.png
759 ms
google_map_PLAATJE.png
757 ms
logo.png
762 ms
Fitvak.png
826 ms
AED.jpg
860 ms
all.js
269 ms
footer.png
823 ms
fontawesome-webfont.woff
824 ms
fontawesome-webfont.woff
824 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
27 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
37 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
48 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
49 ms
123 ms
xd_arbiter.php
214 ms
xd_arbiter.php
421 ms
ping
46 ms
like_box.php
515 ms
410ucuAGgaJ.css
286 ms
tSbl8xBI27R.css
357 ms
Czh0gDTFcBt.css
428 ms
Ek6lpayKeeB.css
567 ms
EoarYgA68t4.css
554 ms
5VZ003vMUZg.css
571 ms
dAhyk4_vXRy.css
492 ms
q68gy-v_YMF.js
622 ms
FJmpeSpHpjS.js
644 ms
0wM5s1Khldu.js
577 ms
1bNoFZUdlYZ.js
643 ms
njO1TPvGzoR.js
643 ms
1QuX41zDRrx.js
652 ms
Oagsvfb4VWi.js
694 ms
LTv6ZK-5zxz.js
889 ms
1FCa-btixu2.js
755 ms
IjqSyiwKeaX.js
691 ms
rBxSIHk4zIe.js
762 ms
n6VgtouijQL.js
698 ms
7BE0CZr3HTs.js
759 ms
pQrUxxo5oQp.js
825 ms
_UYztdBNTjs.js
762 ms
-7JBD_ybv4q.js
957 ms
Kt4tkgSRvHH.js
826 ms
540498_483998528324650_980633344_n.jpg
387 ms
1237_1044104612314036_6661328503584362745_n.jpg
507 ms
12400572_209580672719491_4870973693122053891_n.jpg
625 ms
12509118_129148847462101_5512760221538983752_n.jpg
641 ms
12802940_988243647928468_8503982321739368728_n.jpg
770 ms
11896045_1143125695727364_6900875999288426658_n.jpg
626 ms
11539611_905931282812626_4504030958837260075_n.jpg
585 ms
12871452_1085553748169122_2727668884167047777_n.jpg
605 ms
12419658_1078458182212012_377674042_n.jpg
713 ms
12088227_1074314545959709_6555679607897438018_n.png
903 ms
12402679_1075178652539965_2123115965_n.jpg
768 ms
12720066_1075178135873350_621365777_n.jpg
766 ms
wL6VQj7Ab77.png
74 ms
s7jcwEQH7Sx.png
75 ms
sSwLTfB7PfP.png
77 ms
QDwYpIaRyfG.png
75 ms
l5aPruN9xMM.png
74 ms
K00K-UgnsKu.png
74 ms
b8XhdWI9eAN.js
91 ms
K_65vAc89SX.png
73 ms
I6-MnjEovm5.js
69 ms
palaestra.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.
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
palaestra.nl 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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
palaestra.nl 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 Palaestra.nl 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 Palaestra.nl 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.
palaestra.nl
Open Graph description is not detected on the main page of Palaestra. 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: