Tools & Wizards About Us
ensys.mx screenshot

Report Summary

  • 74

    Performance

    Renders faster than
    83% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

ensys.mx

Ensys Solutions : Energía Solar, Ingeniería y Desarrollo, Querétaro, México.

Page Load Speed

794 ms in total

First Response

23 ms

Resources Loaded

507 ms

Page Rendered

264 ms

ensys.mx screenshot

About Website

Click here to check amazing Ensys content. Otherwise, check out these important facts you probably never knew about ensys.mx

Servicios para sectores Oil & Gas, Energías Renovables, Ingeniería y Desarrollo e Iluminación LED en Querétaro, México.

Visit ensys.mx

Key Findings

We analyzed Ensys.mx page load time and found that the first response time was 23 ms and then it took 771 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

ensys.mx performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

97/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value1.4 s

100/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value4.4 s

83/100

10%

Network Requests Diagram

ensys.mx

23 ms

estiloensys.css

3 ms

fondo.jpg

349 ms

spacer.gif

450 ms

1.png

12 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 95% of them (56 requests) were addressed to the original Ensys.mx, 3% (2 requests) were made to Static.xx.fbcdn.net and 2% (1 request) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (450 ms) belongs to the original domain Ensys.mx.

Page Optimization Overview & Recommendations

Page size can be reduced by 44.8 kB (9%)

Content Size

489.3 kB

After Optimization

444.5 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Ensys.mx main page is 489.3 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. 25% of websites need less resources to load. Images take 462.4 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 16.2 kB

  • Original 19.9 kB
  • After minification 17.6 kB
  • After compression 3.7 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 2.3 kB, which is 11% 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 16.2 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 22.6 kB

  • Original 462.4 kB
  • After minification 439.8 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. Ensys images are well optimized though.

CSS Optimization

-86%

Potential reduce by 6.0 kB

  • Original 7.0 kB
  • After minification 5.9 kB
  • After compression 1.0 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. Ensys.mx needs all CSS files to be minified and compressed as it can save up to 6.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (22%)

Requests Now

58

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ensys.mx

ensys.mx

23 ms

estiloensys.css

estiloensys.css

3 ms

fondo.jpg

fondo.jpg

349 ms

spacer.gif

spacer.gif

450 ms

1.png

1.png

12 ms

fondoheader.jpg

fondoheader.jpg

17 ms

logo.png

logo.png

15 ms

correoscuro.png

correoscuro.png

12 ms

ensys-facebook.png

ensys-facebook.png

15 ms

ensys-youtube.png

ensys-youtube.png

18 ms

3.png

3.png

18 ms

2.png

2.png

20 ms

fondomenu.png

fondomenu.png

19 ms

sep.png

sep.png

22 ms

principal.png

principal.png

23 ms

nosotros.png

nosotros.png

22 ms

energia-solar.png

energia-solar.png

21 ms

productos.png

productos.png

24 ms

ingenieria.png

ingenieria.png

24 ms

distribuidores.png

distribuidores.png

24 ms

contacto.png

contacto.png

25 ms

4.png

4.png

25 ms

5.png

5.png

26 ms

6.jpg

6.jpg

30 ms

6.png

6.png

26 ms

7.png

7.png

28 ms

8.png

8.png

29 ms

fondotitulo.jpg

fondotitulo.jpg

28 ms

ensys.png

ensys.png

29 ms

9.png

9.png

30 ms

sep.jpg

sep.jpg

30 ms

fizq.png

fizq.png

30 ms

bullet.png

bullet.png

31 ms

ppal2.jpg

ppal2.jpg

32 ms

sistemas-fotovoltaicos-interconexion-cfe.jpg

sistemas-fotovoltaicos-interconexion-cfe.jpg

33 ms

ingenieria-desarrollo.jpg

ingenieria-desarrollo.jpg

33 ms

fder.png

fder.png

32 ms

10.png

10.png

34 ms

like.php

like.php

266 ms

fondofooter.jpg

fondofooter.jpg

31 ms

correoclaro.jpg

correoclaro.jpg

28 ms

contacto.php

contacto.php

28 ms

mitsubishi.jpg

mitsubishi.jpg

28 ms

goodwe.jpg

goodwe.jpg

28 ms

hellermanntyton.jpg

hellermanntyton.jpg

28 ms

geda.jpg

geda.jpg

27 ms

14.png

14.png

27 ms

11.png

11.png

28 ms

12.png

12.png

26 ms

13.png

13.png

25 ms

nIvNRKOdND_.js

nIvNRKOdND_.js

24 ms

GzgedhmzSQa.png

GzgedhmzSQa.png

23 ms

nosotros.png

nosotros.png

19 ms

energia-solar.png

energia-solar.png

3 ms

distribuidores.png

distribuidores.png

4 ms

contacto.png

contacto.png

3 ms

principal.png

principal.png

4 ms

productos.png

productos.png

4 ms

ingenieria.png

ingenieria.png

6 ms

Accessibility Review

ensys.mx accessibility score

62

Accessibility Issues

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

ensys.mx best practices score

75

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

Serves images with low resolution

SEO Factors

ensys.mx SEO score

67

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

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ensys.mx can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ensys.mx 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

ensys.mx

Open Graph description is not detected on the main page of Ensys. 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: