Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

espomega.com

Espomega | La seguridad es Nuestra Especialidad | Espomega

Page Load Speed

4.3 sec in total

First Response

179 ms

Resources Loaded

3.8 sec

Page Rendered

330 ms

About Website

Visit espomega.com now to see the best up-to-date Espomega content for Mexico and also check out these interesting facts you probably never knew about espomega.com

Distribuimos los mejores productos para la protección personal. DermaCare - 3M - Steelpro - Ansell entre otros.

Visit espomega.com

Key Findings

We analyzed Espomega.com page load time and found that the first response time was 179 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

espomega.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value20.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value28.2 s

0/100

25%

SI (Speed Index)

Value48.9 s

0/100

10%

TBT (Total Blocking Time)

Value50,990 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.067

97/100

15%

TTI (Time to Interactive)

Value84.0 s

0/100

10%

Network Requests Diagram

espomega.com

179 ms

espomega.mx

101 ms

calendar.css

80 ms

styles-m.css

248 ms

owl.carousel.css

120 ms

Our browser made a total of 121 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Espomega.com, 70% (85 requests) were made to Espomega.mx and 6% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (840 ms) relates to the external source Espomega.mx.

Page Optimization Overview & Recommendations

Page size can be reduced by 732.6 kB (13%)

Content Size

5.5 MB

After Optimization

4.8 MB

In fact, the total size of Espomega.com main page is 5.5 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. Only a small number of websites need less resources to load. Javascripts take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 101.3 kB

  • Original 118.8 kB
  • After minification 96.5 kB
  • After compression 17.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 22.3 kB, which is 19% 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 101.3 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 2.4 MB
  • After minification 2.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. Espomega images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 313.8 kB

  • Original 2.5 MB
  • After minification 2.5 MB
  • After compression 2.2 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 313.8 kB or 13% of the original size.

CSS Optimization

-60%

Potential reduce by 317.6 kB

  • Original 531.1 kB
  • After minification 530.9 kB
  • After compression 213.6 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. Espomega.com needs all CSS files to be minified and compressed as it can save up to 317.6 kB or 60% of the original size.

Requests Breakdown

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

Requests Now

103

After Optimization

51

The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Espomega. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

espomega.com accessibility score

79

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

[role]s do not have all required [aria-*] attributes

High

ARIA IDs are not unique

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.

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

<frame> or <iframe> elements do not have a title

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

espomega.com 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

espomega.com SEO score

89

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

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 Espomega.com 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 Espomega.com 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 Espomega. 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: