4.8 sec in total
1.7 sec
2.6 sec
519 ms
Visit wex.be now to see the best up-to-date WEX content for Belgium and also check out these interesting facts you probably never knew about wex.be
✔ Découvrez tous les concerts, spectacles et événements à l'affiche du WEX ✔ Réservez vos tickets et entrées facilement en quelques clics ✔ Billetterie officielle 100% sécurisée
Visit wex.beWe analyzed Wex.be page load time and found that the first response time was 1.7 sec 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.
wex.be performance score
name
value
score
weighting
Value9.9 s
0/100
10%
Value16.9 s
0/100
25%
Value17.1 s
0/100
10%
Value950 ms
29/100
30%
Value0
100/100
15%
Value15.3 s
7/100
10%
1724 ms
192 ms
8 ms
185 ms
23 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 64% of them (41 requests) were addressed to the original Wex.be, 14% (9 requests) were made to Scontent.cdninstagram.com and 5% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Wex.be.
Page size can be reduced by 982.5 kB (34%)
2.9 MB
1.9 MB
In fact, the total size of Wex.be main page is 2.9 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. 40% of websites need less resources to load. HTML takes 1.8 MB which makes up the majority of the site volume.
Potential reduce by 657.6 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 247.2 kB, which is 14% 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 657.6 kB or 37% of the original size.
Potential reduce by 63.0 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. WEX images are well optimized though.
Potential reduce by 188.3 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 188.3 kB or 73% of the original size.
Potential reduce by 73.5 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. Wex.be needs all CSS files to be minified and compressed as it can save up to 73.5 kB or 89% of the original size.
Number of requests can be reduced by 24 (41%)
58
34
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WEX. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
wex.be
1724 ms
stylesheet_combined_382e4cae9981156e304b742dbab911fd.css
192 ms
jquery.min.js
8 ms
paginate.js
185 ms
css
23 ms
tinynav.min.js
186 ms
js
25 ms
fondHome.jpg
649 ms
lignesFond.png
276 ms
logo.png
96 ms
r_tUZNl0G8xCoOmp_JkSConF5uFdDttMLvmWuJdhhgs.ttf
8 ms
qLBu5CQmSMt1H43OiWJ77aCWcynf_cDxXwCLxiixG1c.ttf
8 ms
fND5XPYKrF2tQDwwfWZJI4nF5uFdDttMLvmWuJdhhgs.ttf
12 ms
petitFb.png
141 ms
petitTw.png
167 ms
enVente.png
108 ms
ticket.png
157 ms
pro.png
93 ms
pucePro.png
95 ms
fondNewsletter.jpg
87 ms
newsletterGo.png
93 ms
mailOn.png
133 ms
fbOn.png
167 ms
twitterOn.png
183 ms
liOff.png
184 ms
gpOff.png
275 ms
inOff.png
185 ms
youtubeOn.png
214 ms
topInsta.png
248 ms
pointilles.png
274 ms
annuler.png
229 ms
sepContent.jpg
212 ms
footer.jpg
230 ms
logo-marche.png
265 ms
logo-quartierlatin.png
299 ms
logo-gcpartner.png
301 ms
logo-eventsmania.png
300 ms
logo-awex.png
303 ms
paulus.png
311 ms
logo-mathionn.png
346 ms
logo-idelux.png
390 ms
logo-ftlb.png
390 ms
ardenne.png
391 ms
jquery-embedagram.pack.js
387 ms
widgets.js
154 ms
hotjar-141290.js
94 ms
analytics.js
33 ms
289 ms
left.png
123 ms
bg_buttons.png
126 ms
right.png
125 ms
collect
19 ms
collect
88 ms
modules-043c1e6abe660c48857202e419ff9d8a.js
26 ms
ga-audiences
39 ms
12081230_1070375893026219_674033888_n.jpg
36 ms
12798059_1655771101351353_1855772422_n.jpg
50 ms
12822567_237753859898697_986396374_n.jpg
63 ms
12751381_956733667750369_262201766_n.jpg
49 ms
11349423_673008782841165_1443905752_n.jpg
99 ms
12751362_147199289003229_1528205693_n.jpg
53 ms
924973_229204800759686_754792573_n.jpg
99 ms
12798176_1678515112422703_1828734918_n.jpg
66 ms
12728523_233441160325770_1209960315_n.jpg
115 ms
wex.be accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
wex.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
wex.be SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wex.be can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Wex.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.
wex.be
Open Graph data is detected on the main page of WEX. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: