3.8 sec in total
255 ms
2.8 sec
735 ms
Visit mcg.be now to see the best up-to-date MCG content and also check out these interesting facts you probably never knew about mcg.be
MCG is your cyber-security partner for securing your business. Our collaboration will enable you to defend yourself against various complex and structured threats and attacks, protecting your servers ...
Visit mcg.beWe analyzed Mcg.be page load time and found that the first response time was 255 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
mcg.be performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value19.1 s
0/100
25%
Value11.0 s
6/100
10%
Value1,360 ms
16/100
30%
Value0.043
99/100
15%
Value20.1 s
2/100
10%
255 ms
480 ms
247 ms
332 ms
367 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 83% of them (52 requests) were addressed to the original Mcg.be, 5% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Api.mapbox.com. The less responsive or slowest element that took the longest time to load (889 ms) belongs to the original domain Mcg.be.
Page size can be reduced by 2.9 MB (37%)
7.7 MB
4.8 MB
In fact, the total size of Mcg.be main page is 7.7 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 5.5 MB which makes up the majority of the site volume.
Potential reduce by 53.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 22.6 kB, which is 35% 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 53.9 kB or 84% of the original size.
Potential reduce by 1.4 MB
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, MCG needs image optimization as it can save up to 1.4 MB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.1 MB
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 1.1 MB or 63% of the original size.
Potential reduce by 301.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. Mcg.be needs all CSS files to be minified and compressed as it can save up to 301.4 kB or 84% of the original size.
Number of requests can be reduced by 14 (26%)
54
40
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MCG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
mcg.be
255 ms
en
480 ms
jquery.fancybox.min.css
247 ms
choices.min.css
332 ms
flickity.min.css
367 ms
lib.min.css
495 ms
css2
40 ms
mapbox-gl.css
32 ms
theme.min.css
696 ms
jquery.min.js
533 ms
uc.js
240 ms
js
84 ms
mapbox-gl.js
17 ms
vendor.min.js
837 ms
theme.min.js
254 ms
site.min.js
291 ms
api.js
41 ms
gtm.js
94 ms
logo-mcg-header.png
125 ms
mcgteamhomeheader.jpg
436 ms
lion%20confiance%20retouch%C3%A9.jpg
178 ms
ours%20responsabilit%C3%A9%20retouch%C3%A9.jpg
125 ms
daleine%20long%20terme%20retouch%C3%A9.jpg
178 ms
oies%20esprit%20%C3%A9quipe%20retouch%C3%A9.jpg
180 ms
Page%201@1x_1.png
433 ms
MCG%20Bonne%20Ann%C3%A9e%20Cybersecurite%202024.jpg
431 ms
MCG%20Matias%20Consulting%20Group%20Cybersecurity%20Budget%202024%20EN.jpg
432 ms
photo-partners-homepage.png
832 ms
sant%C3%A9_1.png
430 ms
industrie.png
512 ms
telecom1.png
512 ms
finance1.png
511 ms
commercial.png
514 ms
haut-tech-copie.png
514 ms
education1.png
590 ms
public1.png
591 ms
autre1.png
593 ms
mcg-2021-2022-simple1.png
600 ms
checkpoint.png
597 ms
cisco.png
676 ms
Ivantinewlogo.png
678 ms
onespan.png
680 ms
boradcaom.png
683 ms
darktrace.png
686 ms
qualis.png
764 ms
ontrack.png
768 ms
fortinet.png
770 ms
baracouda.png
770 ms
voem.png
772 ms
vwave.png
850 ms
redimenssion.png
856 ms
dell.png
866 ms
contact-form-image.png
889 ms
logo-mcg-footer.png
739 ms
nKKZ-Go6G5tXcoaS.ttf
238 ms
nKKU-Go6G5tXcr5aOiWg.ttf
256 ms
nKKU-Go6G5tXcr5KPyWg.ttf
258 ms
Feather.ttf
742 ms
linkedin.svg
769 ms
twitter.svg
767 ms
youtube.svg
767 ms
recaptcha__en.js
69 ms
copyright.svg
551 ms
mcg.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-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
mcg.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
mcg.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
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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 Mcg.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 Mcg.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.
mcg.be
Open Graph data is detected on the main page of MCG. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: