Report Summary

  • 94

    Performance

    Renders faster than
    93% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

Page Load Speed

1.5 sec in total

First Response

256 ms

Resources Loaded

1 sec

Page Rendered

258 ms

sgrillo.net screenshot

About Website

Visit sgrillo.net now to see the best up-to-date Sgrillo content and also check out these interesting facts you probably never knew about sgrillo.net

Personal page of Ricardo Sgrillo

Visit sgrillo.net

Key Findings

We analyzed Sgrillo.net page load time and found that the first response time was 256 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

sgrillo.net performance score

94

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

86/100

25%

SI (Speed Index)

Value2.3 s

98/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value2.3 s

99/100

10%

Network Requests Diagram

sgrillo.net

256 ms

ga.js

18 ms

brasao.jpg

132 ms

Logo_25gry.gif

86 ms

__utm.gif

34 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 18% of them (7 requests) were addressed to the original Sgrillo.net, 13% (5 requests) were made to Pagead2.googlesyndication.com and 11% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (405 ms) relates to the external source Jf.revolvermaps.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 69.2 kB (16%)

Content Size

442.6 kB

After Optimization

373.5 kB

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

HTML Optimization

-68%

Potential reduce by 10.3 kB

  • Original 15.1 kB
  • After minification 13.9 kB
  • After compression 4.8 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 10.3 kB or 68% of the original size.

Image Optimization

-5%

Potential reduce by 16.0 kB

  • Original 334.2 kB
  • After minification 318.2 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. Sgrillo images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 42.8 kB

  • Original 93.4 kB
  • After minification 80.9 kB
  • After compression 50.5 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 42.8 kB or 46% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (59%)

Requests Now

32

After Optimization

13

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

Accessibility Review

sgrillo.net accessibility score

51

Accessibility Issues

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

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

sgrillo.net best practices score

58

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

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

sgrillo.net 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

    N/A

  • Language Claimed

    N/A

  • Encoding

    UNICODE

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sgrillo.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Sgrillo.net main page’s claimed encoding is unicode. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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