Tools & Wizards About Us

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

greenpeace.at

Greenpeace Österreich | Greenpeace

Page Load Speed

4 sec in total

First Response

846 ms

Resources Loaded

2.8 sec

Page Rendered

389 ms

About Website

Visit greenpeace.at now to see the best up-to-date Greenpeace content for Austria and also check out these interesting facts you probably never knew about greenpeace.at

Aktuelle Schwerpunkte. Wir sind Greenpeace. Gemeinsam mit Ihnen.

Visit greenpeace.at

Key Findings

We analyzed Greenpeace.at page load time and found that the first response time was 846 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

greenpeace.at performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

68/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value3,530 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value47.4 s

0/100

10%

Network Requests Diagram

greenpeace.at

846 ms

uc.js

20 ms

styles.min.css

318 ms

modernizr-latest.js

126 ms

iframe.js

164 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 13% of them (7 requests) were addressed to the original Greenpeace.at, 32% (18 requests) were made to Engagement.greenpeace.at and 13% (7 requests) were made to Cee.donate.greenpeace.org. The less responsive or slowest element that took the longest time to load (846 ms) belongs to the original domain Greenpeace.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.4 MB (61%)

Content Size

7.2 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Greenpeace.at main page is 7.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. 70% of websites need less resources to load. Javascripts take 6.4 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 55.1 kB

  • Original 65.9 kB
  • After minification 48.4 kB
  • After compression 10.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 17.6 kB, which is 27% 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 55.1 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 2.0 kB

  • Original 423.6 kB
  • After minification 421.6 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. Greenpeace images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 4.3 MB

  • Original 6.4 MB
  • After minification 6.4 MB
  • After compression 2.2 MB

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 4.3 MB or 66% of the original size.

CSS Optimization

-43%

Potential reduce by 110.5 kB

  • Original 254.8 kB
  • After minification 181.6 kB
  • After compression 144.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. Greenpeace.at needs all CSS files to be minified and compressed as it can save up to 110.5 kB or 43% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (74%)

Requests Now

46

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 31 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

greenpeace.at accessibility score

79

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[role]s are not contained by their required parent element

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.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

greenpeace.at 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

greenpeace.at SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

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