Tools & Wizards About Us
pedroelsner.com screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

pedroelsner.com

Pedro Elsner, Profissional de TI - Consultor Qlikview, Desenvolvedor e Freelancer - São Paulo

Page Load Speed

3.1 sec in total

First Response

504 ms

Resources Loaded

2.3 sec

Page Rendered

355 ms

pedroelsner.com screenshot

About Website

Click here to check amazing Pedro Elsner content for Brazil. Otherwise, check out these important facts you probably never knew about pedroelsner.com

Profissional de TI a mais de 8 anos. Atua como Consultor QlikView e Desenvolvedor Freelancer, participando e contribuindo ativamente para várias comunidades de software livre.

Visit pedroelsner.com

Key Findings

We analyzed Pedroelsner.com page load time and found that the first response time was 504 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

pedroelsner.com performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

71/100

25%

SI (Speed Index)

Value3.5 s

87/100

10%

TBT (Total Blocking Time)

Value1,720 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.028

100/100

15%

TTI (Time to Interactive)

Value7.6 s

47/100

10%

Network Requests Diagram

pedroelsner.com

504 ms

bootstrap.min.css

154 ms

style.css

275 ms

jquery.js

415 ms

jquery-migrate.min.js

290 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 81% of them (47 requests) were addressed to the original Pedroelsner.com, 5% (3 requests) were made to I2.wp.com and 3% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Pedroelsner.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 109.2 kB (11%)

Content Size

1.0 MB

After Optimization

905.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Pedroelsner.com main page is 1.0 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. 40% of websites need less resources to load. Images take 940.0 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 48.0 kB

  • Original 57.9 kB
  • After minification 50.1 kB
  • After compression 9.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 7.8 kB, which is 14% 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 48.0 kB or 83% of the original size.

Image Optimization

-7%

Potential reduce by 61.2 kB

  • Original 940.0 kB
  • After minification 878.9 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. Pedro Elsner images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

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

Requests Breakdown

Number of requests can be reduced by 14 (25%)

Requests Now

56

After Optimization

42

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pedroelsner.com

pedroelsner.com

504 ms

bootstrap.min.css

bootstrap.min.css

154 ms

style.css

style.css

275 ms

jquery.js

jquery.js

415 ms

jquery-migrate.min.js

jquery-migrate.min.js

290 ms

external-tracking.min.js

external-tracking.min.js

294 ms

jquery.js

jquery.js

52 ms

bootstrap.min.js

bootstrap.min.js

296 ms

holder.min.js

holder.min.js

914 ms

jquery-ui-1.8.14.custom.min.js

jquery-ui-1.8.14.custom.min.js

558 ms

jquery-roundabout2.min.js

jquery-roundabout2.min.js

410 ms

jquery.event.drag-2.2.js

jquery.event.drag-2.2.js

526 ms

jquery.event.drop-2.2.js

jquery.event.drop-2.2.js

526 ms

jquery-scrolltofixed-min.js

jquery-scrolltofixed-min.js

555 ms

jquery-masked-input.js

jquery-masked-input.js

556 ms

plusone.js

plusone.js

68 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

310 ms

ga.js

ga.js

95 ms

smallacts-badge-80x15-blue.png

smallacts-badge-80x15-blue.png

84 ms

7e61a375126902f71b00dbba9091f3f2

7e61a375126902f71b00dbba9091f3f2

163 ms

edcc445217b7977fc24be9772491e4e8

edcc445217b7977fc24be9772491e4e8

77 ms

pedroelsner-bgwhite.png

pedroelsner-bgwhite.png

148 ms

presencaDigital-bgwhite.png

presencaDigital-bgwhite.png

230 ms

ico_slideshare.png

ico_slideshare.png

230 ms

ico_github.png

ico_github.png

236 ms

ico_linkedin.png

ico_linkedin.png

285 ms

ico_twitter.png

ico_twitter.png

294 ms

ico_facebook.png

ico_facebook.png

457 ms

ico_rss.png

ico_rss.png

456 ms

skautomotive.png

skautomotive.png

638 ms

2.jpg

2.jpg

582 ms

1.jpg

1.jpg

584 ms

servico_ecommerce-600x225.png

servico_ecommerce-600x225.png

634 ms

servico_hotsites-600x225.png

servico_hotsites-600x225.png

634 ms

servico_seo-600x225.png

servico_seo-600x225.png

770 ms

servico_websites-600x225.png

servico_websites-600x225.png

877 ms

wordpress-madeira-600x225.png

wordpress-madeira-600x225.png

1166 ms

wordpress3-600x225.png

wordpress3-600x225.png

1219 ms

cakephp2-600x225.png

cakephp2-600x225.png

770 ms

github-600x225.png

github-600x225.png

1178 ms

CC88x31.png

CC88x31.png

907 ms

slider-bottom.jpg

slider-bottom.jpg

905 ms

cakephp2-200x200.png

cakephp2-200x200.png

1024 ms

cakephp1-200x200.png

cakephp1-200x200.png

1042 ms

jquery-200x200.png

jquery-200x200.png

1046 ms

qlikview-verde-200x200.png

qlikview-verde-200x200.png

1172 ms

cakephp-200x200.png

cakephp-200x200.png

1179 ms

ico22_slideshare.png

ico22_slideshare.png

1185 ms

ico22_github.png

ico22_github.png

1310 ms

ico22_linkedin.png

ico22_linkedin.png

1259 ms

ico22_twitter.png

ico22_twitter.png

1250 ms

avatar.png

avatar.png

26 ms

ico22_facebook.png

ico22_facebook.png

1251 ms

__utm.gif

__utm.gif

13 ms

avatar.png

avatar.png

5 ms

ico22_rss.png

ico22_rss.png

1229 ms

avatar.png

avatar.png

2 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

49 ms

Accessibility Review

pedroelsner.com accessibility score

91

Accessibility Issues

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

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

pedroelsner.com 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

High

Browser errors were logged to the console

SEO Factors

pedroelsner.com SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

    PT

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pedroelsner.com can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Pedroelsner.com 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

pedroelsner.com

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