6.3 sec in total
522 ms
4 sec
1.8 sec
Welcome to seeyouthere.be homepage info - get ready to check See You There best content right away, or after learning these important things about seeyouthere.be
See you there is an independent online magazine seeking out the best of what Belgium has to offer, always on the lookout for new places, interesting people and things to do within the Belgian borders.
Visit seeyouthere.beWe analyzed Seeyouthere.be page load time and found that the first response time was 522 ms 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.
seeyouthere.be performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value9.1 s
1/100
25%
Value9.4 s
12/100
10%
Value0 ms
100/100
30%
Value0.002
100/100
15%
Value14.3 s
9/100
10%
522 ms
1175 ms
70 ms
558 ms
78 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 81% of them (63 requests) were addressed to the original Seeyouthere.be, 9% (7 requests) were made to Use.typekit.net and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Seeyouthere.be.
Page size can be reduced by 1.6 MB (44%)
3.6 MB
2.0 MB
In fact, the total size of Seeyouthere.be main page is 3.6 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. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 161.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 161.0 kB or 84% of the original size.
Potential reduce by 57.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. See You There images are well optimized though.
Potential reduce by 778.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 778.2 kB or 72% of the original size.
Potential reduce by 623.4 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. Seeyouthere.be needs all CSS files to be minified and compressed as it can save up to 623.4 kB or 84% of the original size.
Number of requests can be reduced by 43 (65%)
66
23
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of See You There. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
seeyouthere.be
522 ms
www.seeyouthere.be
1175 ms
js
70 ms
sbi-styles.min.css
558 ms
cpv8zae.css
78 ms
grid-system.css
446 ms
style.css
784 ms
header-layout-centered-menu.css
359 ms
element-post-grid.css
593 ms
responsive.css
475 ms
flickity.css
596 ms
skin-material.css
669 ms
menu-dynamic.css
599 ms
js_composer.min.css
666 ms
salient-dynamic-styles.css
1063 ms
p.css
54 ms
css
34 ms
frontend-gtag.min.js
597 ms
cpv8zae.css
54 ms
style-non-critical.css
363 ms
font-awesome.min.css
428 ms
jquery.fancybox.css
428 ms
core.css
479 ms
slide-out-right-hover.css
480 ms
jquery.min.js
649 ms
jquery-migrate.min.js
539 ms
jquery.easing.min.js
541 ms
jquery.mousewheel.min.js
597 ms
priority.js
599 ms
transit.min.js
650 ms
waypoints.js
653 ms
imagesLoaded.min.js
762 ms
hoverintent.min.js
762 ms
jquery.fancybox.js
969 ms
anime.min.js
767 ms
flickity.js
821 ms
superfish.js
847 ms
init.js
1234 ms
touchswipe.min.js
847 ms
js_composer_front.min.js
968 ms
lottie-player.min.js
1171 ms
nectar-lottie.js
970 ms
sbi-scripts.min.js
969 ms
nectar-delay-javascript.js
1053 ms
forms.js
967 ms
gs_async.js
583 ms
sbi-sprite.png
500 ms
seeyouthere.png
501 ms
closing-1024x683.jpeg
665 ms
20230226_125534-1024x731.jpg
572 ms
schiev2-1024x684.jpeg
499 ms
placeholder.png
614 ms
d
50 ms
d
198 ms
d
201 ms
d
200 ms
d
228 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTD-JqaE0lPZbLXGimS.ttf
262 ms
qkBIXvYC6trAT55ZBi1ueQVIjQTDJp2aE0lPZbLXGimS.ttf
262 ms
icomoon.woff
349 ms
qkBKXvYC6trAT7RQNNK2EG7SIwPWMNlCV3lIb7b1HgGQ0tQ.ttf
299 ms
fontawesome-webfont.svg
465 ms
435249978_974384767541397_4982257587577865588_nfull.jpg
179 ms
434887781_1070435174068844_2757455300481529186_nfull.jpg
228 ms
434845388_434076009008376_3722631360404424124_nfull.jpg
268 ms
434840869_438902188533048_7165795239702976494_nfull.jpg
389 ms
432255962_1576758063156745_7573002061933393542_nfull.jpg
275 ms
402725264_718066640223059_835438253703569247_nfull.jpg
339 ms
379105445_864965968110094_5259428424649313017_nfull.jpg
342 ms
376832978_707870271158784_2474273896645011714_nfull.jpg
379 ms
376057229_847367907104996_817346426956432057_nfull.jpg
395 ms
375447741_843351370488892_772434220801913509_nfull.jpg
405 ms
359235417_1029401221389353_1649391986467672264_nfull.jpg
453 ms
357770169_1435840760533414_5987135767956171064_nfull.jpg
453 ms
345417419_927422338418894_4060206362799713406_nfull.jpg
491 ms
339691810_1183654889017989_918111058517670656_nfull.jpg
509 ms
v1_gs_lib.js
53 ms
fontawesome-webfont.woff
174 ms
seeyouthere.be accessibility score
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
seeyouthere.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
seeyouthere.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Seeyouthere.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 Seeyouthere.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.
seeyouthere.be
Open Graph data is detected on the main page of See You There. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: