Tools & Wizards About Us
marioguerra.mx screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    40% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

marioguerra.mx

Psicoterapeuta, coach y cursos de desarrollo personal - Mario Guerra

Page Load Speed

896 ms in total

First Response

100 ms

Resources Loaded

696 ms

Page Rendered

100 ms

marioguerra.mx screenshot

About Website

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

Mario Guerra es Psicoterapeuta, Life & Business Coach y también es experto en pérdidas, docente y conferencista en temas relacionados con el desarrollo humano.

Visit marioguerra.mx

Key Findings

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

Performance Metrics

marioguerra.mx performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value8.8 s

15/100

10%

TBT (Total Blocking Time)

Value2,340 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.187

65/100

15%

TTI (Time to Interactive)

Value15.0 s

8/100

10%

Network Requests Diagram

marioguerra.mx

100 ms

www.marioguerra.mx

99 ms

bt

85 ms

require.min.js

39 ms

main-r.min.js

45 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 8% of them (3 requests) were addressed to the original Marioguerra.mx, 74% (29 requests) were made to Static.parastorage.com and 13% (5 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (419 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.1 MB (77%)

Content Size

2.8 MB

After Optimization

639.3 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Marioguerra.mx main page is 2.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 30.7 kB

  • Original 39.1 kB
  • After minification 38.9 kB
  • After compression 8.4 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 30.7 kB or 78% of the original size.

JavaScript Optimization

-77%

Potential reduce by 2.1 MB

  • Original 2.7 MB
  • After minification 2.7 MB
  • After compression 629.1 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 2.1 MB or 77% of the original size.

CSS Optimization

-77%

Potential reduce by 5.8 kB

  • Original 7.5 kB
  • After minification 6.0 kB
  • After compression 1.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. Marioguerra.mx needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (73%)

Requests Now

37

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

marioguerra.mx

marioguerra.mx

100 ms

www.marioguerra.mx

www.marioguerra.mx

99 ms

bt

bt

85 ms

require.min.js

require.min.js

39 ms

main-r.min.js

main-r.min.js

45 ms

viewer.css

viewer.css

56 ms

dynamicmodel

dynamicmodel

31 ms

c8562f_6946cb5b14515556542a61bcbb05fb57_528.json.z

c8562f_6946cb5b14515556542a61bcbb05fb57_528.json.z

206 ms

c8562f_bff26184bb5dbc71c6d6e7bed7e4306d_528.json.z

c8562f_bff26184bb5dbc71c6d6e7bed7e4306d_528.json.z

419 ms

ugc-viewer

ugc-viewer

87 ms

ugc-viewer

ugc-viewer

90 ms

bt

bt

91 ms

skins.min.js

skins.min.js

191 ms

components.min.js

components.min.js

186 ms

utils.min.js

utils.min.js

83 ms

core.min.js

core.min.js

81 ms

react-with-addons.min.js

react-with-addons.min.js

53 ms

lodash.min.js

lodash.min.js

39 ms

TweenMax.min.js

TweenMax.min.js

189 ms

layout.min.js

layout.min.js

187 ms

tpa.min.js

tpa.min.js

83 ms

fonts.min.js

fonts.min.js

82 ms

animations.min.js

animations.min.js

84 ms

swfobject.min.js

swfobject.min.js

84 ms

mousetrap.min.js

mousetrap.min.js

178 ms

tweenEngine.min.js

tweenEngine.min.js

178 ms

DrawSVGPlugin.min.js

DrawSVGPlugin.min.js

180 ms

react-dom.min.js

react-dom.min.js

177 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

178 ms

widgets.min.js

widgets.min.js

178 ms

experiment.js

experiment.js

179 ms

render.min.js

render.min.js

179 ms

wixappsCore.min.js

wixappsCore.min.js

182 ms

wixappsClassics.min.js

wixappsClassics.min.js

183 ms

wixappsBuilder.min.js

wixappsBuilder.min.js

179 ms

zepto.min.js

zepto.min.js

183 ms

color.min.js

color.min.js

182 ms

react-dom-server.min.js

react-dom-server.min.js

185 ms

bt

bt

182 ms

Accessibility Review

marioguerra.mx accessibility score

80

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 match their roles

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

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

Heading elements are not in a sequentially-descending order

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

marioguerra.mx SEO score

77

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

Links do not have descriptive text

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

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

marioguerra.mx

Open Graph data is detected on the main page of Mario Guerra. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: