2.7 sec in total
341 ms
1.9 sec
479 ms
Welcome to mo.be homepage info - get ready to check MO best content for Belgium right away, or after learning these important things about mo.be
MO* Magazine staat voor onafhankelijke journalistiek over wereldnieuws, ontwikkelingssamenwerking, globalisering en de klimaatcrisis. Je kan alle artikels gratis lezen.
Visit mo.beWe analyzed Mo.be page load time and found that the first response time was 341 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
mo.be performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value7.8 s
3/100
25%
Value7.1 s
31/100
10%
Value310 ms
77/100
30%
Value0.317
37/100
15%
Value8.3 s
40/100
10%
341 ms
163 ms
172 ms
168 ms
171 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 95% of them (84 requests) were addressed to the original Mo.be, 3% (3 requests) were made to Google-analytics.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (676 ms) belongs to the original domain Mo.be.
Page size can be reduced by 440.2 kB (43%)
1.0 MB
584.3 kB
In fact, the total size of Mo.be main page is 1.0 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. 50% of websites need less resources to load. Images take 524.5 kB which makes up the majority of the site volume.
Potential reduce by 51.3 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 51.3 kB or 78% of the original size.
Potential reduce by 55.8 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. Obviously, MO needs image optimization as it can save up to 55.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 123.4 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 123.4 kB or 63% of the original size.
Potential reduce by 209.7 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. Mo.be needs all CSS files to be minified and compressed as it can save up to 209.7 kB or 88% of the original size.
Number of requests can be reduced by 29 (37%)
79
50
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
mo.be
341 ms
system.base.css
163 ms
system.messages.css
172 ms
system.theme.css
168 ms
simplenews.css
171 ms
comment.css
173 ms
date.css
173 ms
datepicker.1.7.css
244 ms
entityreference_live_preview.css
250 ms
field.css
251 ms
fitvids.css
250 ms
node.css
251 ms
search.css
251 ms
user.css
327 ms
workflow_admin_ui.css
332 ms
views.css
333 ms
lazyloader.css
336 ms
ctools.css
335 ms
typogrify.css
337 ms
jquery.growl.css
410 ms
addressfield.css
413 ms
eu_cookie_compliance.css
414 ms
mo.css
497 ms
mo-print.css
415 ms
js_G7eUvYnsf51t8bdjvsaGsT0MEnkTEDf5rUvWqlhxdJc.js
584 ms
js_eYtqeAfolcNAQDztCru3ceAhrWGELimEkv-ZBlazmKY.js
492 ms
js_FDUOuuH712vXjCYD-2XUr_ihdXV2Jkn4ODGfAJTC47U.js
516 ms
js_4lET-JuUPpLqsZovy52jwqOYThsn1WM6kSCqbHiF82I.js
516 ms
js_w8Ow5beRU1PL1Eu-gcVg0MT1m0x7DaS1nZxstXDbV-c.js
517 ms
js_paiTaEsc1HNeBS2rkLc1NrprKrFnApv70kuY8awAaTI.js
508 ms
analytics.js
30 ms
Banner_LandofTheEnlightened_MO.png
334 ms
mob-logo.png
154 ms
logo.png
155 ms
zinsou.jpg
336 ms
zelfrijdende_wagen.jpg
153 ms
canis_aureus.jpg
155 ms
electrical_cars.jpg
175 ms
child_marriage_india.jpg
173 ms
2b2cc1a5f2_Urba%2C-Smart-Farm-Gent-8.jpg
252 ms
c8e52f8099_daniel_cohn_bendit.jpg
175 ms
GeertVanIstendael_11.jpg
255 ms
tinehens_1.jpg
258 ms
warda_el-kaddouri_2.jpg
260 ms
tobiasleenaert_600_13.jpg
338 ms
nucleaire_wapens.jpg
339 ms
jan_van_de_poel_0.jpg
342 ms
obama_0.JPG
343 ms
PFA%20plaza_de_mayo.jpg
416 ms
Mauricio%20Macri%20.jpg
417 ms
Brazil%20down%20.jpg
502 ms
linkselente.png
503 ms
algerije-01_0.jpg
423 ms
jaaroverzicht2015_0_0.jpg
425 ms
nergens_thuis.jpg
499 ms
Valerie%20Hopkins%20-%2026%20feb.jpg
500 ms
Petro_Poroshenko_0.JPG
505 ms
paramaribo_woman.jpg
507 ms
1_2_0.jpg
582 ms
Addis%20bouwwerf.jpg
585 ms
soedan_UNDP.jpg
585 ms
MO-collectie-1024.jpg
585 ms
Swing_MO118.jpg
588 ms
11-11-11.jpg
590 ms
broederlijkdelen.png
666 ms
vredeseilanden.png
668 ms
gtm.js
60 ms
zebrastraat.png
648 ms
collect
79 ms
proxima_nova_regular-webfont.woff
620 ms
fairtradebelgium.jpg
524 ms
fos.png
526 ms
collect
12 ms
proxima_nova_bold-webfont.woff
588 ms
proxima_nova_semibold-webfont.woff
666 ms
DroidSerif-Bold-webfont.woff
597 ms
DroidSerif-webfont.woff
676 ms
DroidSerif-Italic-webfont.woff
599 ms
proxima_nova_black-webfont.woff
594 ms
icomoon.woff
591 ms
trias.png
588 ms
planbelgie.png
592 ms
oxfam.png
590 ms
wereldsolidariteit.png
589 ms
mo.png
589 ms
search-icon.png
587 ms
submit-arrow.png
588 ms
discover.png
588 ms
mo.be accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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 IDs are not unique
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
Form elements do not have associated labels
Links do not have a discernible name
mo.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
mo.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
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mo.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 Mo.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.
mo.be
Open Graph description is not detected on the main page of MO. 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: