4.3 sec in total
281 ms
3.4 sec
682 ms
Visit mega.be now to see the best up-to-date Mega content for Belgium and also check out these interesting facts you probably never knew about mega.be
Mega, le fournisseur d'énergie le moins cher de Belgique. Faites des économies sur votre facture d'électricité et de gaz pour particuliers et professionnels !
Visit mega.beWe analyzed Mega.be page load time and found that the first response time was 281 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
mega.be performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value7.1 s
5/100
25%
Value7.2 s
30/100
10%
Value440 ms
64/100
30%
Value0.015
100/100
15%
Value9.4 s
31/100
10%
281 ms
359 ms
1331 ms
84 ms
146 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 92% of them (65 requests) were addressed to the original Mega.be, 4% (3 requests) were made to Blog.mega.be and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Mega.be.
Page size can be reduced by 239.9 kB (47%)
506.0 kB
266.1 kB
In fact, the total size of Mega.be main page is 506.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. HTML takes 265.4 kB which makes up the majority of the site volume.
Potential reduce by 237.4 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 68.7 kB, which is 26% 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 237.4 kB or 89% of the original size.
Potential reduce by 2.4 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. Mega images are well optimized though.
Potential reduce by 42 B
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. Mega.be needs all CSS files to be minified and compressed as it can save up to 42 B or 15% of the original size.
Number of requests can be reduced by 24 (35%)
68
44
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mega. 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 as a result speed up the page load time.
mega.be
281 ms
mega.be
359 ms
www.mega.be
1331 ms
gtm.js
84 ms
gtm.js
146 ms
splide.min.css
176 ms
input.css
279 ms
sendEmail.js
306 ms
productWheel.js
321 ms
callingHomePage.js
319 ms
helpMeChoose.js
321 ms
homepageSwitch.js
271 ms
prixComparaison.js
469 ms
comparaison_concurrents_v4.js
469 ms
icon_error.svg
469 ms
icon_check.svg
470 ms
loader.svg
472 ms
splide.min.js
12 ms
cookiesFunctions.js
373 ms
cookiesModal.js
376 ms
script.js
374 ms
icon_simu.png
193 ms
logo-mega.svg
200 ms
gas_elec.svg
200 ms
client.svg
202 ms
icon_phone.svg
265 ms
subscribe.svg
263 ms
chatIcon.svg
279 ms
icon_elec.svg
295 ms
icon_elec_white.svg
298 ms
icon_gaz.svg
304 ms
icon_gaz_white.svg
374 ms
icon_info.png
375 ms
icon_recall.svg
370 ms
sim_white.svg
386 ms
icon_elecgas_white.svg
388 ms
formPoints.svg
394 ms
megaIllu_connexion.png
719 ms
megaIllu_ampoule_2.png
906 ms
greyBlobHeader.svg
475 ms
headerSection_piggybank_curve.png
650 ms
megaIllu_Pig.jpg
651 ms
piggy_surf_mobile.png
657 ms
megaIllu_piggy_surf_right.png
568 ms
logo-mega-color.svg
652 ms
full_star.svg
740 ms
empty_star.svg
741 ms
marks.svg
742 ms
marks_2.svg
708 ms
half_star.svg
635 ms
headerSection_trophee_m.png
761 ms
megaIllu_trophee_rosace_gardient.png
860 ms
headerSection_move2_m.png
773 ms
moreBlog.svg
685 ms
logo-light.png
722 ms
google-play-badge-FR.png
864 ms
app-store-badge-FR.png
813 ms
icon_instagram_white.svg
804 ms
icon_facebook_white.svg
831 ms
icon_X_white.svg
842 ms
retour-au-concept-ecole-crayon-couleur-fournitures-table-bois-1.jpg
642 ms
tiktok_logo.svg
890 ms
woman-working-environment-projects-portrait_23-2148829274-768x419.jpg
555 ms
Blog_economies.jpg
555 ms
headerSection_cookies_curve.png
937 ms
arrowLi.svg
855 ms
rosace-yellow.svg
852 ms
checkList.svg
841 ms
rosace-greyLight.svg
841 ms
b1.svg
895 ms
blue-circle.svg
841 ms
mega.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 have valid values
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
Buttons do not have an accessible name
Form elements do not have associated labels
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
mega.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Page has valid source maps
mega.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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mega.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 Mega.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.
mega.be
Open Graph data is detected on the main page of Mega. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: