Tools & Wizards About Us
evitra.mx screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

evitra.mx

EVITRA

Page Load Speed

2.1 sec in total

First Response

358 ms

Resources Loaded

1.5 sec

Page Rendered

242 ms

evitra.mx screenshot

About Website

Visit evitra.mx now to see the best up-to-date EVITRA content and also check out these interesting facts you probably never knew about evitra.mx

We show you the way to trace your success

Visit evitra.mx

Key Findings

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

Performance Metrics

evitra.mx performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value24.8 s

0/100

25%

SI (Speed Index)

Value14.9 s

1/100

10%

TBT (Total Blocking Time)

Value90 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value20.7 s

2/100

10%

Network Requests Diagram

evitra.mx

358 ms

e3a6d1bae4.js

195 ms

css

47 ms

plugins-css.css

68 ms

typography.css

128 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 70% of them (54 requests) were addressed to the original Evitra.mx, 27% (21 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Kit.fontawesome.com. The less responsive or slowest element that took the longest time to load (540 ms) belongs to the original domain Evitra.mx.

Page Optimization Overview & Recommendations

Page size can be reduced by 14.6 kB (43%)

Content Size

33.8 kB

After Optimization

19.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Evitra.mx main page is 33.8 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. 45% of websites need less resources to load. CSS take 14.0 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 10.2 kB

  • Original 13.1 kB
  • After minification 8.7 kB
  • After compression 2.9 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 4.4 kB, which is 34% 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 10.2 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 636 B
  • After minification 636 B

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. EVITRA images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 343 B

  • Original 6.1 kB
  • After minification 6.1 kB
  • After compression 5.8 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. This website has mostly compressed JavaScripts.

CSS Optimization

-29%

Potential reduce by 4.0 kB

  • Original 14.0 kB
  • After minification 13.6 kB
  • After compression 9.9 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. Evitra.mx needs all CSS files to be minified and compressed as it can save up to 4.0 kB or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (91%)

Requests Now

53

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

evitra.mx

evitra.mx

358 ms

e3a6d1bae4.js

e3a6d1bae4.js

195 ms

css

css

47 ms

plugins-css.css

plugins-css.css

68 ms

typography.css

typography.css

128 ms

shortcodes.css

shortcodes.css

129 ms

style.css

style.css

414 ms

responsive.css

responsive.css

277 ms

skin-purple.css

skin-purple.css

209 ms

style-customizer.css

style-customizer.css

139 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

317 ms

plugins-jquery.js

plugins-jquery.js

530 ms

custom.js

custom.js

281 ms

app.js

app.js

281 ms

bootstrap.min.css

bootstrap.min.css

293 ms

mega_menu.css

mega_menu.css

214 ms

animate.css

animate.css

233 ms

font-awesome.min.css

font-awesome.min.css

189 ms

bootstrap-datetimepicker.min.css

bootstrap-datetimepicker.min.css

254 ms

dataTables.bootstrap4.min.css

dataTables.bootstrap4.min.css

281 ms

magnific-popup.css

magnific-popup.css

283 ms

mediaelementplayer.css

mediaelementplayer.css

288 ms

owl.carousel.min.css

owl.carousel.min.css

328 ms

slick-theme.css

slick-theme.css

341 ms

themify-icons.css

themify-icons.css

351 ms

fullcalendar.css

fullcalendar.css

352 ms

accordion.css

accordion.css

356 ms

action-box.css

action-box.css

385 ms

blockquote.css

blockquote.css

395 ms

bootstrap-typography.css

bootstrap-typography.css

404 ms

button.css

button.css

416 ms

clients.css

clients.css

415 ms

contact-form.css

contact-form.css

421 ms

countdown.css

countdown.css

448 ms

counter.css

counter.css

457 ms

divider.css

divider.css

468 ms

dropcap.css

dropcap.css

477 ms

feature-text.css

feature-text.css

479 ms

list-style.css

list-style.css

486 ms

nice-select.css

nice-select.css

511 ms

owl-carousel.css

owl-carousel.css

519 ms

page-title.css

page-title.css

530 ms

pie-chart.css

pie-chart.css

540 ms

pricing.css

pricing.css

538 ms

progress-bar.css

progress-bar.css

474 ms

section-title.css

section-title.css

498 ms

social-icons.css

social-icons.css

504 ms

tabs.css

tabs.css

482 ms

team.css

team.css

421 ms

testimonial.css

testimonial.css

403 ms

side-panel.css

side-panel.css

394 ms

onload-modal.css

onload-modal.css

413 ms

loader-02.svg

loader-02.svg

453 ms

logo_evitra.png

logo_evitra.png

427 ms

03.jpg

03.jpg

303 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

84 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

39 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

40 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

40 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

40 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

39 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

34 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

40 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

58 ms

pxiGyp8kv8JHgFVrJJLucHtF.ttf

pxiGyp8kv8JHgFVrJJLucHtF.ttf

57 ms

pxiDyp8kv8JHgFVrJJLmg1hVF9eL.ttf

pxiDyp8kv8JHgFVrJJLmg1hVF9eL.ttf

40 ms

pxiDyp8kv8JHgFVrJJLm21lVF9eL.ttf

pxiDyp8kv8JHgFVrJJLm21lVF9eL.ttf

57 ms

pxiDyp8kv8JHgFVrJJLmr19VF9eL.ttf

pxiDyp8kv8JHgFVrJJLmr19VF9eL.ttf

40 ms

pxiDyp8kv8JHgFVrJJLmy15VF9eL.ttf

pxiDyp8kv8JHgFVrJJLmy15VF9eL.ttf

58 ms

pxiDyp8kv8JHgFVrJJLm111VF9eL.ttf

pxiDyp8kv8JHgFVrJJLm111VF9eL.ttf

58 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

60 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

60 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

59 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

61 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

61 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

60 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

61 ms

Accessibility Review

evitra.mx accessibility score

69

Accessibility Issues

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

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

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

evitra.mx 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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

evitra.mx SEO score

90

Search Engine Optimization Advices

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 Evitra.mx 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 Evitra.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

evitra.mx

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