Tools & Wizards About Us
rodrigoghedin.com.br screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

rodrigoghedin.com.br

Rodrigo Ghedin

Page Load Speed

1 sec in total

First Response

334 ms

Resources Loaded

586 ms

Page Rendered

114 ms

rodrigoghedin.com.br screenshot

About Website

Welcome to rodrigoghedin.com.br homepage info - get ready to check Rodrigo Ghedin best content right away, or after learning these important things about rodrigoghedin.com.br

Página pessoal de Rodrigo Ghedin, comunicólogo (UEM) e editor do Manual do Usuário.

Visit rodrigoghedin.com.br

Key Findings

We analyzed Rodrigoghedin.com.br page load time and found that the first response time was 334 ms and then it took 700 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

rodrigoghedin.com.br performance score

0

Network Requests Diagram

rodrigoghedin.com.br

334 ms

59 ms

59 ms

gprofiles.js

103 ms

wpgroho.js

53 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Rodrigoghedin.com.br, 35% (8 requests) were made to S1.wp.com and 13% (3 requests) were made to 0.gravatar.com. The less responsive or slowest element that took the longest time to load (334 ms) belongs to the original domain Rodrigoghedin.com.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 244.6 kB (62%)

Content Size

395.0 kB

After Optimization

150.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rodrigoghedin.com.br main page is 395.0 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. 35% of websites need less resources to load. Javascripts take 300.8 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 11.3 kB

  • Original 17.2 kB
  • After minification 16.4 kB
  • After compression 5.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. 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 11.3 kB or 66% of the original size.

Image Optimization

-3%

Potential reduce by 1.8 kB

  • Original 63.0 kB
  • After minification 61.3 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. Rodrigo Ghedin images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 219.9 kB

  • Original 300.8 kB
  • After minification 249.5 kB
  • After compression 80.9 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 219.9 kB or 73% of the original size.

CSS Optimization

-83%

Potential reduce by 11.6 kB

  • Original 14.0 kB
  • After minification 12.1 kB
  • After compression 2.4 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. Rodrigoghedin.com.br needs all CSS files to be minified and compressed as it can save up to 11.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (53%)

Requests Now

17

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rodrigoghedin.com.br

rodrigoghedin.com.br

334 ms

59 ms

59 ms

gprofiles.js

gprofiles.js

103 ms

wpgroho.js

wpgroho.js

53 ms

68 ms

725X1342.skimlinks.js

725X1342.skimlinks.js

140 ms

w.js

w.js

41 ms

merriweather.css

merriweather.css

11 ms

cropped-2015-07-16-19-40-51.jpg

cropped-2015-07-16-19-40-51.jpg

74 ms

wordpress.png

wordpress.png

66 ms

23 ms

hovercard.css

hovercard.css

39 ms

services.css

services.css

62 ms

Noticons.svg

Noticons.svg

8 ms

BaABdRAi2AAAA

BaABdRAi2AAAA

6 ms

merriweather-bold-webfont.ttf

merriweather-bold-webfont.ttf

11 ms

merriweather-regular-webfont.ttf

merriweather-regular-webfont.ttf

12 ms

merriweather-light-webfont.ttf

merriweather-light-webfont.ttf

23 ms

g.gif

g.gif

27 ms

g.gif

g.gif

27 ms

g.gif

g.gif

25 ms

cropped-2015-07-16-19-40-51.jpg

cropped-2015-07-16-19-40-51.jpg

31 ms

SEO Factors

rodrigoghedin.com.br SEO score

0

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rodrigoghedin.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Rodrigoghedin.com.br 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

rodrigoghedin.com.br

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