4 sec in total
846 ms
2.8 sec
389 ms
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.atWe 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.
greenpeace.at performance score
name
value
score
weighting
Value2.4 s
71/100
10%
Value3.4 s
68/100
25%
Value11.0 s
6/100
10%
Value3,530 ms
1/100
30%
Value0.001
100/100
15%
Value47.4 s
0/100
10%
846 ms
20 ms
318 ms
126 ms
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 size can be reduced by 4.5 MB (62%)
7.3 MB
2.8 MB
In fact, the total size of Greenpeace.at main page is 7.3 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.5 MB which makes up the majority of the site volume.
Potential reduce by 55.1 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.
Potential reduce by 2.0 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.
Potential reduce by 4.3 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.
Potential reduce by 110.5 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.
Number of requests can be reduced by 34 (74%)
46
12
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.
greenpeace.at
846 ms
uc.js
20 ms
styles.min.css
318 ms
modernizr-latest.js
126 ms
iframe.js
164 ms
frontend.js
468 ms
main.min.js
413 ms
gtm.js
69 ms
js
43 ms
9251.js
29 ms
destination
158 ms
core.js
23 ms
greenpeace.at.json
126 ms
4f6dac1755531e013a53a30db644f2bf.js
104 ms
site24x7rum-min.js
324 ms
full-logo.svg
166 ms
20240306_sargasso_startseiteheader_16x9_rp.jpg
814 ms
badge.png
167 ms
fbevents.js
30 ms
up_loader.1.1.0.js
27 ms
events.js
56 ms
news1
417 ms
vdf0482f1ea5cf44aed95203ec791b1d
123 ms
main.MTIyYzc3NzllMA.js
26 ms
jquery-1.11.2.min.js
271 ms
jquery.placeholder.min.js
107 ms
frontend.css
305 ms
runtime.js
132 ms
frontend-petitions-js.js
715 ms
css
47 ms
font-awesome.min.css
47 ms
app.css
203 ms
enterprise.js
50 ms
checkoutSecuredFields.1.3.0.min.js
463 ms
app.js
598 ms
campaign.js
793 ms
iframeHeightEmitter.js
120 ms
site24x7rum-min.js
10 ms
down.8baa7757.svg
89 ms
right.687c442b.svg
90 ms
sdk.js
5 ms
work-sans-all-500-normal.74a9761b.woff
227 ms
work-sans-all-400-normal.b58d604e.woff
228 ms
work-sans-all-300-normal.440676d5.woff
228 ms
work-sans-all-200-normal.be814b82.woff
556 ms
work-sans-all-100-normal.0c92cbcd.woff
300 ms
work-sans-all-600-normal.190d751b.woff
415 ms
work-sans-all-700-normal.4b71759e.woff
342 ms
work-sans-all-800-normal.efb9537b.woff
683 ms
work-sans-all-900-normal.c3712c73.woff
410 ms
sdk.js
4 ms
39 ms
recaptcha__en.js
25 ms
gtm.js
105 ms
site24x7rum-min.js
406 ms
secure.svg
87 ms
greenpeace.at accessibility score
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
[role]s are not contained by their required parent element
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
greenpeace.at best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
greenpeace.at SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
DE
DE
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.
greenpeace.at
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: