4.5 sec in total
430 ms
3.3 sec
786 ms
Click here to check amazing Carpe content for Belgium. Otherwise, check out these important facts you probably never knew about carpe.be
Gespecialiseerd esthetisch centrum voor zowel gelaat, lichaam als haar in Antwerpen. Bij Carpe Clinic bent u in goede handen.
Visit carpe.beWe analyzed Carpe.be page load time and found that the first response time was 430 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
carpe.be performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value22.6 s
0/100
25%
Value21.7 s
0/100
10%
Value4,560 ms
0/100
30%
Value0.132
81/100
15%
Value33.1 s
0/100
10%
430 ms
569 ms
179 ms
272 ms
452 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that 77% of them (111 requests) were addressed to the original Carpe.be, 7% (10 requests) were made to Lh3.googleusercontent.com and 7% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Carpe.be.
Page size can be reduced by 2.9 MB (55%)
5.2 MB
2.3 MB
In fact, the total size of Carpe.be main page is 5.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 209.3 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 209.3 kB or 86% of the original size.
Potential reduce by 129.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. Carpe images are well optimized though.
Potential reduce by 661.2 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 661.2 kB or 64% of the original size.
Potential reduce by 1.9 MB
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. Carpe.be needs all CSS files to be minified and compressed as it can save up to 1.9 MB or 88% of the original size.
Number of requests can be reduced by 90 (72%)
125
35
The browser has sent 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Carpe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 46 to 1 for CSS and as a result speed up the page load time.
carpe.be
430 ms
carpe.be
569 ms
theme.min.css
179 ms
style.css
272 ms
frontend.css
452 ms
styles.css
455 ms
style.min.css
281 ms
style.min.css
273 ms
if-menu-site.css
282 ms
style.min.css
361 ms
header-footer.min.css
364 ms
all.min.css
552 ms
v4-shims.min.css
464 ms
public.css
541 ms
elementor-icons.min.css
457 ms
frontend.min.css
721 ms
swiper.min.css
545 ms
post-36.css
547 ms
frontend.min.css
911 ms
post-68.css
632 ms
post-11847.css
639 ms
post-62.css
637 ms
post-13855.css
641 ms
post-12141.css
732 ms
post-11927.css
733 ms
post-4796.css
729 ms
post-4412.css
735 ms
ekiticons.css
826 ms
font-awesome.min.css
819 ms
frontend.css
823 ms
style.css
825 ms
chosen.min.css
831 ms
jet-search.css
999 ms
widget-styles.css
1011 ms
responsive.css
922 ms
css
36 ms
fontawesome.min.css
936 ms
solid.min.css
922 ms
js
73 ms
loader.js
39 ms
api.js
34 ms
regular.min.css
917 ms
brands.min.css
834 ms
animations.min.css
783 ms
trustindex-google-widget.css
782 ms
flatpickr.min.css
812 ms
post-4649.css
815 ms
post-4652.css
750 ms
post-7576.css
741 ms
post-4655.css
654 ms
post-4659.css
664 ms
script.min.js
732 ms
jquery.min.js
733 ms
jquery-migrate.min.js
667 ms
imagesloaded.min.js
669 ms
analytify-events-tracking.js
680 ms
underscore.min.js
661 ms
wp-util.min.js
886 ms
chosen.jquery.min.js
885 ms
jet-plugins.js
882 ms
jet-search.js
882 ms
frontend.js
795 ms
scrolldepth.js
793 ms
miscellaneous-tracking.js
834 ms
wp-polyfill-inert.min.js
835 ms
regenerator-runtime.min.js
832 ms
wp-polyfill.min.js
746 ms
hooks.min.js
744 ms
vue.min.js
746 ms
jet-menu-public-scripts.js
847 ms
frontend-script.js
844 ms
widget-scripts.js
755 ms
jquery.sticky.min.js
753 ms
premium-wrapper-link.min.js
754 ms
jquery.smartmenus.min.js
740 ms
flatpickr.min.js
753 ms
webpack-pro.runtime.min.js
755 ms
webpack.runtime.min.js
751 ms
frontend-modules.min.js
711 ms
i18n.min.js
711 ms
frontend.min.js
713 ms
waypoints.min.js
755 ms
core.min.js
756 ms
frontend.min.js
750 ms
elements-handlers.min.js
749 ms
widgets-scripts.js
750 ms
animate-circle.min.js
739 ms
elementor.js
750 ms
frontend.min.js
746 ms
gtm.js
295 ms
ACg8ocK25WOD0ogKbue3CDHIVnWpl5rh0h_jWl4CSpY4yj57=s120-c-rp-mo-br100
317 ms
nl.png
680 ms
fr.png
692 ms
en.png
691 ms
ALV-UjV_rKPm-zDUFk_n2CYJdFLVtpWNbP20HtOe82gIaL4bs0Q=s120-c-rp-mo-br100
387 ms
ACg8ocJSbuy3PezxcCq7yB-XqWBqmg33m8UZ8DxB1-vC6Gma=s120-c-rp-mo-br100
348 ms
ALV-UjUeYVic08JubYZDZywWaA7AFj5s1yZ2lrj41uqc96XcJKU=s120-c-rp-mo-br100
387 ms
ACg8ocI7MgHI1AedEV5USpvKXEbHLZ0imzHJXxEh3WhEQqbu=s120-c-rp-mo-br100
387 ms
ACg8ocKh_OVl5QtODlULtKiW9CzL4MgCJQ8exaTkyCakBj9O=s120-c-rp-mo-br100
407 ms
ACg8ocLIIXEsQc9FTa1OaBx5zS0o9WvNMGg5oFyZqn3Vdz4M=s120-c-rp-mo-br100
386 ms
ACg8ocKICbfwJDBWg2eZD-dRI-D70rK9eAf7GryTUy1blgTC=s120-c-rp-mo-br100
412 ms
ALV-UjX7JKOmBxH4XLwuClYwusa3GHxVUbG7GmjdOlt_nmytTDg=s120-c-rp-mo-br100
461 ms
ALV-UjV9aWsl0qw5QSEkNTP9dG6Kd78CWkKOJONpC2XSGB_M_6Gx=s120-c-rp-mo-br100
462 ms
icon.svg
164 ms
f.svg
63 ms
e.svg
64 ms
carpe_clinic_logo-1-01-1-300x300.jpg
440 ms
carpe_clinic_logo-1-01-1.jpg
509 ms
SDB_6623.jpg
785 ms
carpe_clinic_logo.svg
524 ms
SDB_6588.jpg
655 ms
SDB_6438-150x150.jpg
526 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff
74 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aXx-p7K4GLs.woff
92 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXx-p7K4GLs.woff
130 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aXx-p7K4GLs.woff
150 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXx-p7K4GLs.woff
152 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXx-p7K4GLs.woff
153 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXx-p7K4GLs.woff
152 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aXx-p7K4GLs.woff
153 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aXx-p7K4GLs.woff
150 ms
RWmPoKKX6u8sp8fIWdnDKqDSroEBJmNjCg.woff
150 ms
fa-solid-900.woff
536 ms
fa-solid-900.woff
558 ms
fa-regular-400.woff
576 ms
fa-regular-400.woff
577 ms
eicons.woff
609 ms
fa-brands-400.woff
644 ms
fa-brands-400.woff
656 ms
embed
306 ms
SDB_6916-150x150.jpg
557 ms
SDB_6115-150x150.jpg
590 ms
CarpeFirstShoot_164-150x150.jpg
590 ms
Carpe_vanRiet_-3-1-300x300.jpg
637 ms
Carpe_Solange-Lintermans_-3-1-300x300.jpg
639 ms
Carpe_SilvieVanEycken_-5-300x300.jpg
593 ms
Carpe_Karolien-Stevens_-4-1-300x300.jpg
575 ms
leen-steyaert-1-300x292.jpg
589 ms
carpe_clinic_logo.svg
637 ms
FIT_CombiLogo_1line-1024x75.jpg
649 ms
js
31 ms
search.js
6 ms
geometry.js
8 ms
main.js
16 ms
carpe.be accessibility score
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-*] attributes do not match their roles
ARIA IDs are not unique
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
carpe.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
Page has valid source maps
carpe.be 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
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Carpe.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 Carpe.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.
carpe.be
Open Graph data is detected on the main page of Carpe. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: