Tools & Wizards About Us
fernandowobeto.com screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

fernandowobeto.com

Fernando Wobeto

Page Load Speed

4.6 sec in total

First Response

282 ms

Resources Loaded

3 sec

Page Rendered

1.3 sec

fernandowobeto.com screenshot

About Website

Welcome to fernandowobeto.com homepage info - get ready to check Fernando Wobeto best content right away, or after learning these important things about fernandowobeto.com

Visit fernandowobeto.com

Key Findings

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

Performance Metrics

fernandowobeto.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.9 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.2 s

100/100

25%

SI (Speed Index)

Value0.9 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.9 s

100/100

10%

Network Requests Diagram

fernandowobeto.com

282 ms

font-awesome.min.css

82 ms

css

71 ms

css

150 ms

animate.css

161 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 30% of them (22 requests) were addressed to the original Fernandowobeto.com, 34% (25 requests) were made to Maps.googleapis.com and 23% (17 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (672 ms) belongs to the original domain Fernandowobeto.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 614.9 kB (50%)

Content Size

1.2 MB

After Optimization

609.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fernandowobeto.com 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. 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 521.1 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 39.9 kB

  • Original 47.4 kB
  • After minification 42.8 kB
  • After compression 7.5 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 39.9 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 12.3 kB

  • Original 419.1 kB
  • After minification 406.8 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. Fernando Wobeto images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 359.9 kB

  • Original 521.1 kB
  • After minification 486.8 kB
  • After compression 161.2 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 359.9 kB or 69% of the original size.

CSS Optimization

-86%

Potential reduce by 202.8 kB

  • Original 236.9 kB
  • After minification 212.0 kB
  • After compression 34.2 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. Fernandowobeto.com needs all CSS files to be minified and compressed as it can save up to 202.8 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (51%)

Requests Now

55

After Optimization

27

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fernandowobeto.com

fernandowobeto.com

282 ms

font-awesome.min.css

font-awesome.min.css

82 ms

css

css

71 ms

css

css

150 ms

animate.css

animate.css

161 ms

bootstrap.min.css

bootstrap.min.css

223 ms

bootstrap-responsive.css

bootstrap-responsive.css

154 ms

style_menu_white.css

style_menu_white.css

157 ms

component.css

component.css

156 ms

jquery.min.js

jquery.min.js

125 ms

jquery.isotope.min.js

jquery.isotope.min.js

151 ms

js

js

207 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

181 ms

jquery.transit.js

jquery.transit.js

196 ms

jquery.scrollTo.js

jquery.scrollTo.js

182 ms

jquery.nav.js

jquery.nav.js

179 ms

jquery.scrolly.js

jquery.scrolly.js

190 ms

JScript.js

JScript.js

204 ms

javascript.js

javascript.js

204 ms

modernizr.custom.js

modernizr.custom.js

211 ms

grid.js

grid.js

672 ms

bg1.jpg

bg1.jpg

178 ms

bottom_arrow.png

bottom_arrow.png

175 ms

me.jpg

me.jpg

177 ms

top_arrow.png

top_arrow.png

159 ms

LgcV55siz7BRNdbO3Huj5g.ttf

LgcV55siz7BRNdbO3Huj5g.ttf

235 ms

AcvTq8Q0lyKKNxRlL28Rn6CWcynf_cDxXwCLxiixG1c.ttf

AcvTq8Q0lyKKNxRlL28Rn6CWcynf_cDxXwCLxiixG1c.ttf

236 ms

81X-1TO5y4aMK2PPy9kFw6CWcynf_cDxXwCLxiixG1c.ttf

81X-1TO5y4aMK2PPy9kFw6CWcynf_cDxXwCLxiixG1c.ttf

235 ms

4GwpJM7qx9X5Obd9KsnKxQ.ttf

4GwpJM7qx9X5Obd9KsnKxQ.ttf

236 ms

zpv3sOKAbMf4wff105oLjw.ttf

zpv3sOKAbMf4wff105oLjw.ttf

237 ms

5pEc4QKTMA2oB4Hi9NkS4w.ttf

5pEc4QKTMA2oB4Hi9NkS4w.ttf

232 ms

obisuY-MenYRAFwd-r2NhfesZW2xOQ-xsNqO47m55DA.ttf

obisuY-MenYRAFwd-r2NhfesZW2xOQ-xsNqO47m55DA.ttf

235 ms

guC5lwT5Dw7anV_xfpCGqw.ttf

guC5lwT5Dw7anV_xfpCGqw.ttf

253 ms

0b3R8ORT0i9mlMGM3BxXF_esZW2xOQ-xsNqO47m55DA.ttf

0b3R8ORT0i9mlMGM3BxXF_esZW2xOQ-xsNqO47m55DA.ttf

241 ms

05xr33FHwecUTIADg28rEfesZW2xOQ-xsNqO47m55DA.ttf

05xr33FHwecUTIADg28rEfesZW2xOQ-xsNqO47m55DA.ttf

223 ms

URSgP3aplSko3CQAzdXHwPesZW2xOQ-xsNqO47m55DA.ttf

URSgP3aplSko3CQAzdXHwPesZW2xOQ-xsNqO47m55DA.ttf

223 ms

Luunk03-uSz9LnB7oNEUuvesZW2xOQ-xsNqO47m55DA.ttf

Luunk03-uSz9LnB7oNEUuvesZW2xOQ-xsNqO47m55DA.ttf

237 ms

T4JvHtpMHbjlr73o1YLMo_esZW2xOQ-xsNqO47m55DA.ttf

T4JvHtpMHbjlr73o1YLMo_esZW2xOQ-xsNqO47m55DA.ttf

219 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

210 ms

common.js

common.js

100 ms

map.js

map.js

166 ms

util.js

util.js

73 ms

onion.js

onion.js

70 ms

openhand_8_8.cur

openhand_8_8.cur

446 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

119 ms

stats.js

stats.js

113 ms

controls.js

controls.js

91 ms

css

css

224 ms

transparent.png

transparent.png

58 ms

google4.png

google4.png

50 ms

mapcnt6.png

mapcnt6.png

119 ms

sv5.png

sv5.png

120 ms

vt

vt

163 ms

vt

vt

150 ms

vt

vt

147 ms

vt

vt

147 ms

vt

vt

180 ms

vt

vt

183 ms

vt

vt

150 ms

vt

vt

170 ms

vt

vt

178 ms

vt

vt

180 ms

vt

vt

184 ms

vt

vt

188 ms

vt

vt

250 ms

vt

vt

249 ms

vt

vt

244 ms

vt

vt

246 ms

tmapctrl4.png

tmapctrl4.png

141 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

100 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

140 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

207 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

208 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

75 ms

Accessibility Review

fernandowobeto.com accessibility score

74

Accessibility Issues

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.

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

fernandowobeto.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

fernandowobeto.com SEO score

92

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

    N/A

  • Encoding

    UTF-8

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

fernandowobeto.com

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