3.4 sec in total
319 ms
2.6 sec
465 ms
Click here to check amazing Thomas More content for Belgium. Otherwise, check out these important facts you probably never knew about thomasmore.be
De grootste hogeschool van Vlaanderen. Een community van bijna 22.000 studenten, medewerkers en onderzoekers. Professioneel onderwijs van de bovenste plank.
Visit thomasmore.beWe analyzed Thomasmore.be page load time and found that the first response time was 319 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
thomasmore.be performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value22.0 s
0/100
25%
Value10.4 s
8/100
10%
Value5,050 ms
0/100
30%
Value0
100/100
15%
Value23.3 s
1/100
10%
319 ms
323 ms
83 ms
163 ms
164 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 36% of them (45 requests) were addressed to the original Thomasmore.be, 20% (25 requests) were made to Maps.google.com and 7% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Thomasmore.be.
Page size can be reduced by 1.3 MB (23%)
5.4 MB
4.2 MB
In fact, the total size of Thomasmore.be main page is 5.4 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. 80% 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. Images take 3.8 MB which makes up the majority of the site volume.
Potential reduce by 75.5 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 75.5 kB or 80% of the original size.
Potential reduce by 60.5 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. Thomas More images are well optimized though.
Potential reduce by 793.6 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 793.6 kB or 68% of the original size.
Potential reduce by 332.9 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. Thomasmore.be needs all CSS files to be minified and compressed as it can save up to 332.9 kB or 84% of the original size.
Number of requests can be reduced by 49 (44%)
112
63
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thomas More. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
thomasmore.be
319 ms
www.thomasmore.be
323 ms
css_rEI_5cK_B9hB4So2yZUtr5weuEV3heuAllCDE6XsIkI.css
83 ms
css__r408iefJFDp7tkJY64xde0BtyLdHU1-GytpTja6H4w.css
163 ms
css_gEVYQ7WlmawMm-2JLpCTHa4w7PrmUvjmlRfiowN7XFE.css
164 ms
css_x7pGUKrZGgqS2b-SmydcJqPAJLFMXwMc_TS4uEHakiI.css
242 ms
js_P0y9MqqyOiYj_PTAPXWTzkKXPrtw8g8yUbGDzx6eRjM.js
323 ms
js_ZwtHh_UtMhEyIZ7P23uU_tO_tZHXgPG1rk11b_m8s9Y.js
166 ms
js_Jj3cBaR3LcsCKM94chOiZQ2EyCkOPnxjVCMcSnPS8Uk.js
165 ms
js
29 ms
js_0tI_xu2XX4VuqlPffS4jQ-V8WQ-lGDmUrRyeuT70ou0.js
253 ms
js_UmuGfX_FqjU4zpvJoRwmudyLoOlfDmhk-yrAbXGKzLE.js
254 ms
js_0W5psLwMlAn2mINLDw0DqRKeflGqWjwRAlxhvMhy1-Q.js
253 ms
buttons.js
6 ms
conversion.js
14 ms
prum.min.js
47 ms
dc.js
63 ms
logo.png
220 ms
homepage_campagneheaders_explore.jpg
945 ms
homepage_campagneheaders_reveal.jpg
703 ms
homepage_campagneheaders_discover.jpg
825 ms
homepage_campagneheaders_innovate.jpg
782 ms
homepage_campagneheaders_mean.jpg
865 ms
homepage_campagneheaders_create.jpg
1106 ms
homepage_campagneheaders_harvest.jpg
1028 ms
homepage_campagneheaders_inspire.jpg
1187 ms
opleidingen.png
897 ms
infodagen.png
947 ms
campussen.png
982 ms
nieuws.png
1026 ms
stip.png
1031 ms
inschrijven.png
1062 ms
campustoer_vorselaar_website_1.png
1189 ms
gtm.js
174 ms
eEAmKzg9cF4
207 ms
menu-top-divider.png
1092 ms
search-icon-header-with-border.png
1092 ms
twitter-bg.png
1127 ms
header-arrow.png
1171 ms
blue_social.png
1173 ms
news.png
1176 ms
event.png
1208 ms
logos.png
1249 ms
173 ms
texgyreadventor-regular-webfont.woff
1216 ms
loader0.js
171 ms
common.js
117 ms
map.js
118 ms
util.js
118 ms
marker.js
118 ms
overlay.js
114 ms
twitter_feed.php
1169 ms
getAllAppDefault.esi
235 ms
ajax-loader.gif
1141 ms
slider-controls.png
1141 ms
flexslider-icon.woff
1138 ms
__utm.gif
27 ms
www-embed-player-vflQrT_sR.css
109 ms
www-embed-player.js
125 ms
base.js
196 ms
142 ms
ga-audiences
183 ms
infowindow.js
62 ms
onion.js
53 ms
openhand_8_8.cur
96 ms
8306-525-10-5579.js
68 ms
ViewportInfoService.GetViewportInfo
226 ms
stats.js
34 ms
controls.js
35 ms
m1.png
75 ms
gmap-marker.png
1019 ms
transparent.png
92 ms
css
130 ms
c
160 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
60 ms
ad_status.js
90 ms
google4.png
87 ms
getSegment.php
62 ms
checkOAuth.esi
150 ms
mapcnt6.png
58 ms
sv5.png
58 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
75 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
77 ms
tmapctrl.png
24 ms
cb_scout5.png
74 ms
tmapctrl4.png
25 ms
imgs8.png
74 ms
t.dhj
91 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
50 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
51 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
64 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
67 ms
vt
52 ms
vt
46 ms
vt
45 ms
vt
46 ms
vt
44 ms
vt
47 ms
vt
57 ms
vt
57 ms
vt
58 ms
vt
58 ms
vt
60 ms
vt
59 ms
vt
61 ms
vt
60 ms
vt
62 ms
t.dhj
13 ms
AuthenticationService.Authenticate
129 ms
s-3271.xgi
15 ms
pixel
43 ms
6 ms
7 ms
xrefid.xgi
4 ms
hbpix
88 ms
pixel
15 ms
pixel
17 ms
cm
11 ms
2981
18 ms
application2.js
123 ms
tweet-left.png
83 ms
tweet-right.png
85 ms
css_cif6e5gYru_o__yZAMEgyWlutjFU3QgD8C7QR1wVkQc.css
83 ms
storage.html
119 ms
storage.js
29 ms
thomasmore.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.
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
thomasmore.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
thomasmore.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 Thomasmore.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 Thomasmore.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.
thomasmore.be
Open Graph description is not detected on the main page of Thomas More. 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: