Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

feg.de

FeG Deutschland | Bund Freier evangelischer Gemeinden KdöR

Page Load Speed

23.2 sec in total

First Response

1.4 sec

Resources Loaded

9.8 sec

Page Rendered

12 sec

feg.de screenshot

About Website

Click here to check amazing FeG content for Germany. Otherwise, check out these important facts you probably never knew about feg.de

Bewegt von Gottes Liebe bauen wir lebendige Gemeinden. Der Bund FeG ist Teil der Vereinigung Evangelischer Freikirchen (VEF) mit dem wesentlichen Merkmal der Freiwilligkeitsgemeinde.

Visit feg.de

Key Findings

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

Performance Metrics

feg.de performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value29.9 s

0/100

25%

SI (Speed Index)

Value26.8 s

0/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value50.9 s

0/100

10%

Network Requests Diagram

feg.de

1379 ms

5q6ll.css

108 ms

5q6ll.css

442 ms

5q6lk.css

313 ms

5q6lk.css

314 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 94% of them (80 requests) were addressed to the original Feg.de, 2% (2 requests) were made to Matomo.feg.de and 1% (1 request) were made to Cdn.podlove.org. The less responsive or slowest element that took the longest time to load (7.4 sec) belongs to the original domain Feg.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 492.5 kB (3%)

Content Size

15.7 MB

After Optimization

15.2 MB

In fact, the total size of Feg.de main page is 15.7 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 15.2 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 217.3 kB

  • Original 242.9 kB
  • After minification 238.1 kB
  • After compression 25.7 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 217.3 kB or 89% of the original size.

Image Optimization

-2%

Potential reduce by 272.5 kB

  • Original 15.2 MB
  • After minification 14.9 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. FeG images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 720 B

  • Original 208.2 kB
  • After minification 208.2 kB
  • After compression 207.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 2.0 kB

  • Original 90.5 kB
  • After minification 90.5 kB
  • After compression 88.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. Feg.de has all CSS files already compressed.

Requests Breakdown

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

Requests Now

83

After Optimization

68

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

Accessibility Review

feg.de accessibility score

88

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

[aria-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

feg.de best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

feg.de SEO score

100

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

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 Feg.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 Feg.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

Open Graph data is detected on the main page of FeG. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: