4.5 sec in total
1.3 sec
3 sec
194 ms
Click here to check amazing FLAG content. Otherwise, check out these important facts you probably never knew about flag.be
*/
Visit flag.beWe analyzed Flag.be page load time and found that the first response time was 1.3 sec and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
flag.be performance score
name
value
score
weighting
Value9.3 s
0/100
10%
Value14.2 s
0/100
25%
Value13.7 s
2/100
10%
Value220 ms
87/100
30%
Value0.02
100/100
15%
Value20.0 s
2/100
10%
1280 ms
148 ms
225 ms
892 ms
13 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 83% of them (44 requests) were addressed to the original Flag.be, 9% (5 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Flag.be.
Page size can be reduced by 1.2 MB (72%)
1.6 MB
452.5 kB
In fact, the total size of Flag.be main page is 1.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. 45% of websites need less resources to load. CSS take 696.3 kB which makes up the majority of the site volume.
Potential reduce by 20.2 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 20.2 kB or 75% of the original size.
Potential reduce by 23.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. FLAG images are well optimized though.
Potential reduce by 489.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 489.6 kB or 75% of the original size.
Potential reduce by 618.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. Flag.be needs all CSS files to be minified and compressed as it can save up to 618.6 kB or 89% of the original size.
Number of requests can be reduced by 33 (70%)
47
14
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FLAG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
flag.be
1280 ms
wp-emoji-release.min.js
148 ms
styles.css
225 ms
theme.css
892 ms
font-awesome.min.css
13 ms
css
28 ms
jquery-ui-1.11.4.custom.css
745 ms
mediaelementplayer.min.css
660 ms
wp-mediaelement.css
676 ms
wpv-pagination.css
231 ms
frontend-builder-plugin-style.css
592 ms
magnific_popup.css
323 ms
style.css
413 ms
style.css
504 ms
admin-ajax.php
1214 ms
jquery.js
773 ms
jquery-migrate.min.js
747 ms
frontend-builder-global-functions.js
722 ms
jquery.form.min.js
789 ms
scripts.js
798 ms
bootstrap.min.js
944 ms
theme.min.js
819 ms
core.min.js
879 ms
datepicker.min.js
982 ms
mediaelement-and-player.min.js
915 ms
wp-mediaelement.js
929 ms
underscore.min.js
971 ms
wp-util.min.js
1003 ms
backbone.min.js
1019 ms
wp-playlist.js
1031 ms
wpv-pagination-embedded.js
1154 ms
jquery.fitvids.js
1068 ms
waypoints.min.js
1091 ms
jquery.magnific-popup.js
1111 ms
frontend-builder-scripts.js
1225 ms
analytics.js
60 ms
FLAGheader-Burner.jpg
555 ms
FLAG-logo-site.png
166 ms
EASN-Conference-wpcf_1080x216-pad-2599649.jpg
267 ms
Sampe-europe-liege-wpcf_1080x216-pad-2599649.jpg
215 ms
aero-friedrichshaven-vvmg-wpcf_1080x216-pad-2599649.jpg
279 ms
FLAG-member-Xenics-wpcf_150x100.jpg
170 ms
FLAG-member-VUB-wpcf_150x100.jpg
216 ms
FLAG-member-VKI1-wpcf_150x100.jpg
215 ms
FLAG-member-VLOC-wpcf_150x100.jpg
277 ms
FLAG-member-VITO-wpcf_150x100.jpg
273 ms
FLAG-member-unmanned-wpcf_150x100.jpg
306 ms
u-WUoqrET9fUeobQW7jkRT8E0i7KZn-EPnyo3HZu7kw.woff
129 ms
DXI1ORHCpsQm3Vp6mXoaTRa1RVmPjeKy21_GQJaLlJI.woff
130 ms
MTP_ySUJH_bn48VBG8sNSha1RVmPjeKy21_GQJaLlJI.woff
133 ms
k3k702ZOKiLJc3WVjuplzBa1RVmPjeKy21_GQJaLlJI.woff
133 ms
EInbV5DfGHOiMmvb1Xr-hha1RVmPjeKy21_GQJaLlJI.woff
134 ms
collect
79 ms
flag.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
flag.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
flag.be SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flag.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 Flag.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.
flag.be
Open Graph description is not detected on the main page of FLAG. 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: