7.9 sec in total
318 ms
7.3 sec
275 ms
Visit aspria.be now to see the best up-to-date Aspria content for Belgium and also check out these interesting facts you probably never knew about aspria.be
A country retreat just outside the city with four hectares of leafy gardens, seven tennis courts, two pools and state-of-the-art fitness and spa facilities.
Visit aspria.beWe analyzed Aspria.be page load time and found that the first response time was 318 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
aspria.be performance score
318 ms
583 ms
100 ms
270 ms
309 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 7% of them (4 requests) were addressed to the original Aspria.be, 69% (38 requests) were made to Aspria.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.2 sec) relates to the external source Aspria.com.
Page size can be reduced by 343.7 kB (32%)
1.1 MB
737.5 kB
In fact, the total size of Aspria.be main page is 1.1 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. 20% of websites need less resources to load. Images take 672.7 kB which makes up the majority of the site volume.
Potential reduce by 47.1 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 14.3 kB, which is 25% 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 47.1 kB or 83% of the original size.
Potential reduce by 26.9 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. Aspria images are well optimized though.
Potential reduce by 60.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 60.1 kB or 65% of the original size.
Potential reduce by 209.6 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. Aspria.be needs all CSS files to be minified and compressed as it can save up to 209.6 kB or 81% of the original size.
Number of requests can be reduced by 11 (24%)
46
35
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aspria. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
aspria.be
318 ms
www.aspria.be
583 ms
100 ms
home.aspx
270 ms
home.aspx
309 ms
883 ms
css
26 ms
css
39 ms
css
50 ms
DependencyHandler.axd
1235 ms
DependencyHandler.axd
2735 ms
bootstrap-datepicker-en-GB.js
289 ms
DependencyHandler.axd
705 ms
beacon_call.js
30 ms
conversion_async.js
14 ms
preloader.gif
672 ms
aspria_logo.png
191 ms
aspria_royal_la_rasante_hero_aspria-navi.jpg
287 ms
asp_loi_warm_aspria-navi.jpg
703 ms
aspria_avenue_louise_hero_colour_aspria-navi.jpg
290 ms
hcm_outdoor_night_aspria-navi.jpg
499 ms
aspria_berlin_kudamm_hero_aspria-navi.jpg
387 ms
asp1808155625a_1920x1080_2_aspria-navi.jpg
485 ms
uhl_spa_pool_rot_aspria-navi.jpg
889 ms
han_infinitypool_aspria-navi.jpg
679 ms
aspria_hotel_royal_la_rasante_hero_aspria-navi.jpg
598 ms
aspria_hotel_kudamm_hero_aspria-navi.jpg
699 ms
aspria_hotel_uhl_hero_aspria-navi.jpg
954 ms
aspria_hotel_maschsee_hero_aspria-navi.jpg
1186 ms
bru_avl_woman_180216.jpg
2953 ms
aspria_royal_la_rasante_hero_1_aspria-teaser_720.jpg
1677 ms
aspria_arts_loi_hero_1_aspria-teaser_720.jpg
2456 ms
aspria_avenue_louise_hero_colour_1_aspria-teaser_720.jpg
1919 ms
aspria_harbour_club_hero_1_aspria-teaser_720.jpg
2083 ms
aspria_berlin_kudamm_hero_1_aspria-teaser_720.jpg
2731 ms
aspria_alstertal_hero_1_aspria-teaser_720.jpg
3590 ms
aspria_uhlenhorst_hero_1_aspria-teaser_720.jpg
3133 ms
aspria_maschsee_hero_colour_1_aspria-teaser_720.jpg
3699 ms
elle2.png
2549 ms
gq2.png
2643 ms
european-consumer-choise2.png
2827 ms
condenast-johansens2.jpg
3050 ms
logo_myaspria_white.png
3322 ms
hotel.jpg
3045 ms
fontawesome-webfont.woff
4186 ms
flaticon.woff
3081 ms
1x1.gif
172 ms
beacon
54 ms
analytics.js
50 ms
442 ms
icons.png
1337 ms
linkid.js
6 ms
collect
12 ms
collect
68 ms
216 ms
aspria.be SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aspria.be can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Aspria.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.
aspria.be
Open Graph data is detected on the main page of Aspria. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: