Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

mega.be

Le fournisseur d'énergie - électricité et gaz - juste moins cher | Mega

Page Load Speed

4.3 sec in total

First Response

281 ms

Resources Loaded

3.4 sec

Page Rendered

682 ms

mega.be screenshot

About Website

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.be

Key Findings

We 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.

Performance Metrics

mega.be performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value9.4 s

31/100

10%

Network Requests Diagram

mega.be

281 ms

mega.be

359 ms

www.mega.be

1331 ms

gtm.js

84 ms

gtm.js

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 Optimization Overview & Recommendations

Page size can be reduced by 239.9 kB (47%)

Content Size

506.0 kB

After Optimization

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.

HTML Optimization

-89%

Potential reduce by 237.4 kB

  • Original 265.4 kB
  • After minification 196.7 kB
  • After compression 28.0 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.

Image Optimization

-1%

Potential reduce by 2.4 kB

  • Original 240.3 kB
  • After minification 237.9 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.

CSS Optimization

-15%

Potential reduce by 42 B

  • Original 286 B
  • After minification 286 B
  • After compression 244 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.

Requests Breakdown

Number of requests can be reduced by 24 (35%)

Requests Now

68

After Optimization

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.

Accessibility Review

mega.be accessibility score

69

Accessibility Issues

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

High

[aria-*] attributes do not have valid values

High

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

High

Buttons do not have an accessible name

High

Form elements do not have associated labels

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

mega.be best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

High

Page has valid source maps

SEO Factors

mega.be SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    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.

Social Sharing Optimization

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: