14.4 sec in total
5.6 sec
7.9 sec
939 ms
Visit monar.be now to see the best up-to-date Monar content for Belgium and also check out these interesting facts you probably never knew about monar.be
Order your favourite sneakers, streetwear, womenswear and footwear online or pass by one of our stores in Antwerp.
Visit monar.beWe analyzed Monar.be page load time and found that the first response time was 5.6 sec and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
monar.be performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value8.1 s
2/100
25%
Value7.5 s
26/100
10%
Value990 ms
28/100
30%
Value0.11
87/100
15%
Value18.7 s
3/100
10%
5553 ms
409 ms
173 ms
175 ms
713 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 24% of them (10 requests) were addressed to the original Monar.be, 33% (14 requests) were made to Data.static.cityfashion.be and 10% (4 requests) were made to Translate.googleapis.com. The less responsive or slowest element that took the longest time to load (5.6 sec) belongs to the original domain Monar.be.
Page size can be reduced by 725.3 kB (17%)
4.2 MB
3.5 MB
In fact, the total size of Monar.be main page is 4.2 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. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 153.9 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 97.4 kB, which is 59% 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 153.9 kB or 94% of the original size.
Potential reduce by 545 B
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. Monar images are well optimized though.
Potential reduce by 407.9 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 407.9 kB or 59% of the original size.
Potential reduce by 163.0 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. Monar.be needs all CSS files to be minified and compressed as it can save up to 163.0 kB or 84% of the original size.
Number of requests can be reduced by 22 (56%)
39
17
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Monar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.monar.be
5553 ms
jquery.js
409 ms
jquery.cookie.js
173 ms
fancybox.css
175 ms
scripts.js
713 ms
theme.css
823 ms
jquery.fancybox-1.3.0.pack.js
213 ms
js
24 ms
page.js
17 ms
api.js
45 ms
element.js
39 ms
translateelement.css
67 ms
main.js
69 ms
recaptcha__en.js
27 ms
css
73 ms
element_main.js
4 ms
dc.js
57 ms
arrow.png
96 ms
logo.png
96 ms
user.png
156 ms
black-line.png
182 ms
cart.png
239 ms
8c99a3470c1cfd0f398a094f6aaac7cc.jpg
996 ms
cf831199867bc7107c0eb09b7c096097.jpg
993 ms
3149cc8e2e92fd43819d2ed00cc86c74.jpg
788 ms
a6946fedb04f6e00db76573e18766704.jpg
909 ms
39dcd9bf3b3264e97e27db256e250d07.jpg
754 ms
2d78c2e19a48ab5e86cd857deb78b54e.jpg
1008 ms
76d863e82c98004015053d5b48bc78a0.jpg
1166 ms
all.js
25 ms
jquery.lazyload.js
176 ms
font-awesome.min.css
249 ms
jquery-ui.css
246 ms
jquery.dotdotdot.js
185 ms
__utm.gif
17 ms
47 ms
0sTQzbapM8j.js
35 ms
0sTQzbapM8j.js
42 ms
fontawesome-webfont.woff
409 ms
translate_24dp.png
8 ms
l
18 ms
translate_24dp.png
3 ms
monar.be accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
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
Image elements do not have [alt] attributes
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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a valid value for its [lang] attribute.
monar.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
Missing source maps for large first-party JavaScript
monar.be SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Monar.be can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Monar.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.
monar.be
Open Graph data is detected on the main page of Monar. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: