Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

favelawatchblog.com

Live aus der Favela

Page Load Speed

10.9 sec in total

First Response

542 ms

Resources Loaded

6.2 sec

Page Rendered

4.1 sec

favelawatchblog.com screenshot

About Website

Welcome to favelawatchblog.com homepage info - get ready to check Favela Watchblog best content right away, or after learning these important things about favelawatchblog.com

Visit favelawatchblog.com

Key Findings

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

Performance Metrics

favelawatchblog.com performance score

0

Network Requests Diagram

favelawatchblog.com

542 ms

339 ms

css

363 ms

338 ms

344 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Favelawatchblog.com, 27% (27 requests) were made to Favelawatchblog.files.wordpress.com and 10% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Re-publica.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 855.5 kB (22%)

Content Size

3.9 MB

After Optimization

3.1 MB

In fact, the total size of Favelawatchblog.com main page is 3.9 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. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 67.7 kB

  • Original 88.7 kB
  • After minification 86.5 kB
  • After compression 21.0 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 67.7 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 11.9 kB

  • Original 2.8 MB
  • After minification 2.8 MB

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. Favela Watchblog images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 542.5 kB

  • Original 748.6 kB
  • After minification 622.3 kB
  • After compression 206.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 542.5 kB or 72% of the original size.

CSS Optimization

-82%

Potential reduce by 233.3 kB

  • Original 284.1 kB
  • After minification 281.6 kB
  • After compression 50.8 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. Favelawatchblog.com needs all CSS files to be minified and compressed as it can save up to 233.3 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (46%)

Requests Now

82

After Optimization

44

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

SEO Factors

favelawatchblog.com SEO score

0

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

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