Tools & Wizards About Us
fvee.de screenshot

Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

fvee.de

FVEE | Forschungsverbund Erneuerbare Energien

Page Load Speed

5.1 sec in total

First Response

244 ms

Resources Loaded

4.2 sec

Page Rendered

712 ms

fvee.de screenshot

About Website

Welcome to fvee.de homepage info - get ready to check FVEE best content for Germany right away, or after learning these important things about fvee.de

Der ForschungsVerbund Erneuerbare Energien (FVEE) ist eine bundesweite Kooperation von Forschungsinstituten. Die Mitglieder erforschen und entwickeln

Visit fvee.de

Key Findings

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

Performance Metrics

fvee.de performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

51/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value4.2 s

86/100

10%

Network Requests Diagram

fvee.de

244 ms

fvee.de

437 ms

www.fvee.de

1178 ms

akpc.css

109 ms

sorting.css

526 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that all of those requests were addressed to Fvee.de and no external sources were called. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Fvee.de.

Page Optimization Overview & Recommendations

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

Content Size

10.5 MB

After Optimization

8.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fvee.de main page is 10.5 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. 65% of websites need less resources to load. Images take 10.2 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 140.4 kB

  • Original 169.6 kB
  • After minification 166.9 kB
  • After compression 29.2 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 140.4 kB or 83% of the original size.

Image Optimization

-18%

Potential reduce by 1.9 MB

  • Original 10.2 MB
  • After minification 8.4 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, FVEE needs image optimization as it can save up to 1.9 MB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-11%

Potential reduce by 7.9 kB

  • Original 72.4 kB
  • After minification 72.4 kB
  • After compression 64.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 7.9 kB or 11% of the original size.

CSS Optimization

-14%

Potential reduce by 9.4 kB

  • Original 67.6 kB
  • After minification 67.6 kB
  • After compression 58.2 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. Fvee.de needs all CSS files to be minified and compressed as it can save up to 9.4 kB or 14% of the original size.

Requests Breakdown

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

Requests Now

59

After Optimization

44

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fvee.de

fvee.de

244 ms

fvee.de

fvee.de

437 ms

www.fvee.de

www.fvee.de

1178 ms

akpc.css

akpc.css

109 ms

sorting.css

sorting.css

526 ms

ctf-styles.min.css

ctf-styles.min.css

322 ms

style.css

style.css

331 ms

borlabs-cookie_1_de.css

borlabs-cookie_1_de.css

325 ms

mailin-front.css

mailin-front.css

325 ms

jquery.min.js

jquery.min.js

327 ms

jquery-migrate.min.js

jquery-migrate.min.js

429 ms

mailin-front.js

mailin-front.js

428 ms

ak-mr-8797fe5e6b.css

ak-mr-8797fe5e6b.css

427 ms

jquery.uploader.js

jquery.uploader.js

429 ms

grating.js

grating.js

435 ms

components.js

components.js

648 ms

page.js

page.js

649 ms

jquery.unuglifymail.js

jquery.unuglifymail.js

648 ms

snippet.min.js

snippet.min.js

650 ms

borlabs-cookie.min.js

borlabs-cookie.min.js

651 ms

ctf-sprite.png

ctf-sprite.png

126 ms

theme-logo.svg

theme-logo.svg

125 ms

curve-header.svg

curve-header.svg

128 ms

fvee-header.jpg

fvee-header.jpg

321 ms

fvee-keyvisual-jahrestagung-rgb-2024-website-1.jpg

fvee-keyvisual-jahrestagung-rgb-2024-website-1.jpg

320 ms

Doppelportraet-FVEE-DIR-2024-1.png

Doppelportraet-FVEE-DIR-2024-1.png

1273 ms

fvee-keyvisual-h-jahrestagung-2023-rgb-e1687942423206.jpg

fvee-keyvisual-h-jahrestagung-2023-rgb-e1687942423206.jpg

322 ms

Solar_und_Wind_ZSW-scaled.jpg

Solar_und_Wind_ZSW-scaled.jpg

429 ms

Energiebereitstellung.svg

Energiebereitstellung.svg

215 ms

Systemkomponenten-n.png

Systemkomponenten-n.png

1065 ms

Systemkomponenten.svg

Systemkomponenten.svg

427 ms

Energienutzung-1.png

Energienutzung-1.png

852 ms

Energienutzung.svg

Energienutzung.svg

431 ms

Energiesystemgestaltung.png

Energiesystemgestaltung.png

751 ms

Energiesystemgestaltung.svg

Energiesystemgestaltung.svg

534 ms

th2022-pdf-1.jpg

th2022-pdf-1.jpg

752 ms

th2021_fvee-pdf-1.jpg

th2021_fvee-pdf-1.jpg

1071 ms

th2020-pdf.jpg

th2020-pdf.jpg

1179 ms

Logo_CAE_mit_text_RGB.png

Logo_CAE_mit_text_RGB.png

861 ms

DBFZ_logo.png

DBFZ_logo.png

959 ms

DLR_Logo.svg

DLR_Logo.svg

968 ms

Juelich_fz_logo.svg

Juelich_fz_logo.svg

1066 ms

fraunhofer_iee_logo-1.svg

fraunhofer_iee_logo-1.svg

1075 ms

ieg.svg

ieg.svg

1171 ms

mitgliederlogo-fraunhofer-ise.svg

mitgliederlogo-fraunhofer-ise.svg

1175 ms

Fraunhofer-IWES_logo.svg

Fraunhofer-IWES_logo.svg

1180 ms

GFZ.svg

GFZ.svg

1182 ms

hzb-logo.svg

hzb-logo.svg

1277 ms

ISFH_logo.png

ISFH_logo.png

1280 ms

IZES-Logo-hoch.jpg

IZES-Logo-hoch.jpg

1285 ms

KIT_logo.svg

KIT_logo.svg

1215 ms

3DtBiY5g_400x400.png

3DtBiY5g_400x400.png

1220 ms

WI_Logo_sRGB-1.svg

WI_Logo_sRGB-1.svg

1307 ms

zae_logo-1.png

zae_logo-1.png

1313 ms

Logo_ZSW.svg

Logo_ZSW.svg

1314 ms

Noto+Sans_400_normal.woff

Noto+Sans_400_normal.woff

1319 ms

Noto+Sans_700_normal.woff

Noto+Sans_700_normal.woff

1270 ms

AK-Font-Bold-Rounded.ttf

AK-Font-Bold-Rounded.ttf

1293 ms

AK-Font-Black-Rounded.ttf

AK-Font-Black-Rounded.ttf

1358 ms

AK-Font-Regular-Rounded.ttf

AK-Font-Regular-Rounded.ttf

1302 ms

AK-Font-Bold.ttf

AK-Font-Bold.ttf

1199 ms

AK-Font-Black.ttf

AK-Font-Black.ttf

1199 ms

AK-Font-Regular.ttf

AK-Font-Regular.ttf

1197 ms

theme-logo.svg

theme-logo.svg

1092 ms

Energiebereitstellung.svg

Energiebereitstellung.svg

1166 ms

Systemkomponenten.svg

Systemkomponenten.svg

1176 ms

Energienutzung.svg

Energienutzung.svg

1072 ms

Energiesystemgestaltung.svg

Energiesystemgestaltung.svg

864 ms

curve-footer.svg

curve-footer.svg

770 ms

spinner.gif

spinner.gif

840 ms

Accessibility Review

fvee.de accessibility score

77

Accessibility Issues

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

Form elements do not have associated labels

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.

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

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

Page has valid source maps

SEO Factors

fvee.de 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 Fvee.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 Fvee.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

fvee.de

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