Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

mega.es

Mega: equipamiento hidraúlico para industrial y automoción desde 1940

Page Load Speed

4.1 sec in total

First Response

405 ms

Resources Loaded

3.5 sec

Page Rendered

224 ms

About Website

Welcome to mega.es homepage info - get ready to check Mega best content for Iran right away, or after learning these important things about mega.es

En MEGA Diseñamos, construimos y distribuimos equipamientos hidráulicos para automoción e industria. Creamos todas las piezas sensibles nosotros mismos.

Visit mega.es

Key Findings

We analyzed Mega.es page load time and found that the first response time was 405 ms and then it took 3.7 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.es performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value10.4 s

0/100

25%

SI (Speed Index)

Value8.0 s

21/100

10%

TBT (Total Blocking Time)

Value340 ms

74/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value9.4 s

30/100

10%

Network Requests Diagram

mega.es

405 ms

933 ms

gtm.js

66 ms

font-awesome.min.css

410 ms

normalize.min.css

310 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 78% of them (29 requests) were addressed to the original Mega.es, 14% (5 requests) were made to Fonts.gstatic.com and 3% (1 request) 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.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 584.9 kB (33%)

Content Size

1.8 MB

After Optimization

1.2 MB

In fact, the total size of Mega.es main page is 1.8 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. 25% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-95%

Potential reduce by 153.1 kB

  • Original 160.7 kB
  • After minification 68.6 kB
  • After compression 7.6 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 92.1 kB, which is 57% 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.1 kB or 95% of the original size.

Image Optimization

-3%

Potential reduce by 38.3 kB

  • Original 1.1 MB
  • After minification 1.1 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. Mega images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 224.6 kB

  • Original 298.5 kB
  • After minification 282.3 kB
  • After compression 73.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 224.6 kB or 75% of the original size.

CSS Optimization

-87%

Potential reduce by 168.9 kB

  • Original 193.6 kB
  • After minification 164.6 kB
  • After compression 24.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. Mega.es needs all CSS files to be minified and compressed as it can save up to 168.9 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (52%)

Requests Now

29

After Optimization

14

The browser has sent 29 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 10 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

mega.es accessibility score

81

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 input fields do not have accessible names

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

Image elements do not have [alt] attributes

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.

Best Practices

mega.es best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

mega.es SEO score

88

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mega.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Mega.es 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 description is not detected on the main page of Mega. 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: