Tools & Wizards About Us

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

fiege.de

Cross-sector logistics solutions | FIEGE

Page Load Speed

12.2 sec in total

First Response

333 ms

Resources Loaded

11.5 sec

Page Rendered

423 ms

About Website

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

Our modular solutions for logistics, digital services, real estate and ventures are all driven by one integrated system.

Visit fiege.de

Key Findings

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

Performance Metrics

fiege.de performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

38/100

25%

SI (Speed Index)

Value11.6 s

4/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value11.7 s

18/100

10%

Network Requests Diagram

fiege.de

333 ms

www.fiege.com

755 ms

de

869 ms

css__3xsvr5YskfUQLiaWyEW-VUnyhElmiCOnclxsq1B8uc.css

341 ms

css_mvdgHQIEKoN6oaoU3oJNra1me8h0jUy4CslzmsVd-xI.css

890 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Fiege.de, 76% (47 requests) were made to Fiege.com and 6% (4 requests) were made to App.usercentrics.eu. The less responsive or slowest element that took the longest time to load (8.3 sec) relates to the external source Fiege.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 693.4 kB (7%)

Content Size

9.9 MB

After Optimization

9.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-88%

Potential reduce by 267.8 kB

  • Original 305.5 kB
  • After minification 264.0 kB
  • After compression 37.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. This page needs HTML code to be minified as it can gain 41.5 kB, which is 14% 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 267.8 kB or 88% of the original size.

Image Optimization

-5%

Potential reduce by 425.1 kB

  • Original 9.0 MB
  • After minification 8.6 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. FIEGE images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 255 B

  • Original 555.2 kB
  • After minification 555.2 kB
  • After compression 555.0 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

-0%

Potential reduce by 115 B

  • Original 50.3 kB
  • After minification 50.3 kB
  • After compression 50.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. Fiege.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 7 (12%)

Requests Now

59

After Optimization

52

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

fiege.de accessibility score

85

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

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

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

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

fiege.de SEO score

84

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    DE

  • Encoding

    UTF-8

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