Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

weblog.greenpeace.org

Making Waves | Greenpeace International

Page Load Speed

10.8 sec in total

First Response

692 ms

Resources Loaded

7.6 sec

Page Rendered

2.5 sec

weblog.greenpeace.org screenshot

About Website

Welcome to weblog.greenpeace.org homepage info - get ready to check Weblog Greenpeace best content for United States right away, or after learning these important things about weblog.greenpeace.org

Updates from the front lines of the Greenpeace planet. Sign up and login to join the conversation.

Visit weblog.greenpeace.org

Key Findings

We analyzed Weblog.greenpeace.org page load time and found that the first response time was 692 ms and then it took 10.1 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

weblog.greenpeace.org performance score

0

Network Requests Diagram

weblog.greenpeace.org

692 ms

461 ms

all.css

73 ms

js-resources.ashx

310 ms

jquery.min.js

41 ms

Our browser made a total of 127 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Weblog.greenpeace.org, 52% (66 requests) were made to Greenpeace.org and 9% (11 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Staticxx.facebook.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.0 MB (41%)

Content Size

4.9 MB

After Optimization

2.9 MB

In fact, the total size of Weblog.greenpeace.org main page is 4.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. 80% 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.4 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 258.0 kB

  • Original 336.5 kB
  • After minification 313.1 kB
  • After compression 78.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 258.0 kB or 77% of the original size.

Image Optimization

-12%

Potential reduce by 272.5 kB

  • Original 2.4 MB
  • After minification 2.1 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. Obviously, Weblog Greenpeace needs image optimization as it can save up to 272.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-64%

Potential reduce by 1.3 MB

  • Original 2.0 MB
  • After minification 1.9 MB
  • After compression 705.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 1.3 MB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 192.7 kB

  • Original 232.5 kB
  • After minification 227.7 kB
  • After compression 39.9 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. Weblog.greenpeace.org needs all CSS files to be minified and compressed as it can save up to 192.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 79 (65%)

Requests Now

122

After Optimization

43

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

SEO Factors

weblog.greenpeace.org SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weblog.greenpeace.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Weblog.greenpeace.org 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 data is detected on the main page of Weblog Greenpeace. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: