Tools & Wizards About Us

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

fuechse.berlin

FÜCHSE BERLIN | Hier ist unser Revier | DAIKIN Handball-Bundesliga

Page Load Speed

7.6 sec in total

First Response

366 ms

Resources Loaded

6.8 sec

Page Rendered

498 ms

About Website

Welcome to fuechse.berlin homepage info - get ready to check Fuechse best content for Germany right away, or after learning these important things about fuechse.berlin

Die Offizielle Webseite der Füchse Berlin - hier finden Sie alle Informationen rund um den Handballverein Füchse Berlin.

Visit fuechse.berlin

Key Findings

We analyzed Fuechse.berlin page load time and found that the first response time was 366 ms and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

fuechse.berlin performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value31.2 s

0/100

25%

SI (Speed Index)

Value13.7 s

2/100

10%

TBT (Total Blocking Time)

Value12,020 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.157

74/100

15%

TTI (Time to Interactive)

Value43.0 s

0/100

10%

Network Requests Diagram

fuechse.berlin

366 ms

home.html

687 ms

gtm.js

64 ms

uc.js

41 ms

googlefonts.css

281 ms

Our browser made a total of 217 requests to load all elements on the main page. We found that 56% of them (121 requests) were addressed to the original Fuechse.berlin, 23% (49 requests) were made to I.ytimg.com and 8% (18 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Fuechse.berlin.

Page Optimization Overview & Recommendations

Page size can be reduced by 959.7 kB (14%)

Content Size

6.9 MB

After Optimization

6.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fuechse.berlin main page is 6.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. Only a small number of websites need less resources to load. Images take 5.7 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 121.4 kB

  • Original 143.8 kB
  • After minification 139.7 kB
  • After compression 22.4 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 121.4 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 187.0 kB

  • Original 5.7 MB
  • After minification 5.5 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. Fuechse images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 424.2 kB

  • Original 827.4 kB
  • After minification 769.6 kB
  • After compression 403.2 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 424.2 kB or 51% of the original size.

CSS Optimization

-85%

Potential reduce by 227.1 kB

  • Original 266.3 kB
  • After minification 211.2 kB
  • After compression 39.1 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. Fuechse.berlin needs all CSS files to be minified and compressed as it can save up to 227.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 64 (31%)

Requests Now

209

After Optimization

145

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

fuechse.berlin accessibility score

84

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

fuechse.berlin best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

fuechse.berlin SEO score

91

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

Image elements do not have [alt] attributes

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fuechse.berlin 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 Fuechse.berlin main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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