Tools & Wizards About Us
groenaz.de screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

groenaz.de

GröNaZ | A Bad Wolf Production

Page Load Speed

7.8 sec in total

First Response

952 ms

Resources Loaded

6.3 sec

Page Rendered

604 ms

groenaz.de screenshot

About Website

Visit groenaz.de now to see the best up-to-date Groe NaZ content and also check out these interesting facts you probably never knew about groenaz.de

Visit groenaz.de

Key Findings

We analyzed Groenaz.de page load time and found that the first response time was 952 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

groenaz.de performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value110 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.257

48/100

15%

TTI (Time to Interactive)

Value6.4 s

59/100

10%

Network Requests Diagram

groenaz.de

952 ms

www.groenaz.de

3960 ms

style.css

389 ms

miniplayer.css

298 ms

styles.css

205 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 80% of them (24 requests) were addressed to the original Groenaz.de, 7% (2 requests) were made to Apis.google.com and 7% (2 requests) were made to Statistik.groenaz.de. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Groenaz.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 272.3 kB (48%)

Content Size

563.2 kB

After Optimization

291.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Groenaz.de main page is 563.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 242.7 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 29.3 kB

  • Original 39.3 kB
  • After minification 36.3 kB
  • After compression 9.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. 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 29.3 kB or 75% of the original size.

Image Optimization

-12%

Potential reduce by 29.1 kB

  • Original 242.7 kB
  • After minification 213.5 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. Obviously, Groe NaZ needs image optimization as it can save up to 29.1 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

-72%

Potential reduce by 146.1 kB

  • Original 203.0 kB
  • After minification 196.5 kB
  • After compression 56.9 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 146.1 kB or 72% of the original size.

CSS Optimization

-86%

Potential reduce by 67.7 kB

  • Original 78.3 kB
  • After minification 55.7 kB
  • After compression 10.6 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. Groenaz.de needs all CSS files to be minified and compressed as it can save up to 67.7 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (54%)

Requests Now

28

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

groenaz.de

groenaz.de

952 ms

www.groenaz.de

www.groenaz.de

3960 ms

style.css

style.css

389 ms

miniplayer.css

miniplayer.css

298 ms

styles.css

styles.css

205 ms

pagenavi-css.css

pagenavi-css.css

203 ms

jquery.min.js

jquery.min.js

68 ms

jQuery.mb.miniAudioPlayer.min.js

jQuery.mb.miniAudioPlayer.min.js

512 ms

map_overwrite_default_me.js

map_overwrite_default_me.js

291 ms

jquery.fitvids.js

jquery.fitvids.js

302 ms

custom.js

custom.js

302 ms

widgets.js

widgets.js

84 ms

jquery.form.min.js

jquery.form.min.js

239 ms

scripts.js

scripts.js

239 ms

wp-embed.min.js

wp-embed.min.js

239 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

102 ms

socialicons.png

socialicons.png

207 ms

groenaz_logobild_2.png

groenaz_logobild_2.png

207 ms

bottomline.png

bottomline.png

207 ms

posticons.png

posticons.png

205 ms

schwarze_hoffnung_thumb.png

schwarze_hoffnung_thumb.png

206 ms

piraten_dystopie.png

piraten_dystopie.png

206 ms

EdwardSnowden.jpg

EdwardSnowden.jpg

645 ms

sherlock.jpg

sherlock.jpg

623 ms

0zapftis_catcontent.jpg

0zapftis_catcontent.jpg

691 ms

search.png

search.png

303 ms

plusone.js

plusone.js

203 ms

piwik.js

piwik.js

579 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

5 ms

piwik.php

piwik.php

418 ms

Accessibility Review

groenaz.de accessibility score

90

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

groenaz.de best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

groenaz.de SEO score

89

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

High

Tap targets are not sized appropriately

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 Groenaz.de 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 Groenaz.de 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

groenaz.de

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