Report Summary

  • 60

    Performance

    Renders faster than
    76% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

mario.pe

penzi

Page Load Speed

2.4 sec in total

First Response

531 ms

Resources Loaded

1.7 sec

Page Rendered

101 ms

mario.pe screenshot

About Website

Click here to check amazing Mario content for Peru. Otherwise, check out these important facts you probably never knew about mario.pe

Lucharé frontalmente contra la burocracia y la corrupción

Visit mario.pe

Key Findings

We analyzed Mario.pe page load time and found that the first response time was 531 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

mario.pe performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value5.5 s

70/100

10%

Network Requests Diagram

mario.pe

531 ms

font-awesome.min.css

35 ms

all.min.css

153 ms

all.min.js

408 ms

mario-main.png

680 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that 85% of them (11 requests) were addressed to the original Mario.pe, 15% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (680 ms) belongs to the original domain Mario.pe.

Page Optimization Overview & Recommendations

Page size can be reduced by 490.8 kB (41%)

Content Size

1.2 MB

After Optimization

708.2 kB

In fact, the total size of Mario.pe main page is 1.2 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. 30% of websites need less resources to load. Images take 594.6 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 7.3 kB

  • Original 9.5 kB
  • After minification 7.3 kB
  • After compression 2.2 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.2 kB, which is 23% 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 7.3 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 19.2 kB

  • Original 594.6 kB
  • After minification 575.4 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. Mario images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 253.6 kB

  • Original 358.3 kB
  • After minification 358.3 kB
  • After compression 104.7 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 253.6 kB or 71% of the original size.

CSS Optimization

-89%

Potential reduce by 210.7 kB

  • Original 236.6 kB
  • After minification 236.6 kB
  • After compression 25.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. Mario.pe needs all CSS files to be minified and compressed as it can save up to 210.7 kB or 89% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

11

After Optimization

11

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mario. According to our analytics all requests are already optimized.

Accessibility Review

mario.pe accessibility score

100

Accessibility Issues

Best Practices

mario.pe best practices score

83

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

mario.pe SEO score

91

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    ES

  • Encoding

    UTF-8

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