Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

en.boerse-frankfurt.de

Frankfurt Stock Exchange: Quotes, Charts and News

Page Load Speed

6 sec in total

First Response

802 ms

Resources Loaded

4.8 sec

Page Rendered

372 ms

en.boerse-frankfurt.de screenshot

About Website

Welcome to en.boerse-frankfurt.de homepage info - get ready to check En Boerse Frankfurt best content for Germany right away, or after learning these important things about en.boerse-frankfurt.de

Stock market prices, news and know-how directly from the source: shares, ETFs, funds, commodities, bonds, certificates. Setup watchlist and portfolio.

Visit en.boerse-frankfurt.de

Key Findings

We analyzed En.boerse-frankfurt.de page load time and found that the first response time was 802 ms and then it took 5.2 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

en.boerse-frankfurt.de performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value1,720 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value1

2/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

en.boerse-frankfurt.de

802 ms

basic.js

180 ms

jquery.scrolltabs_PATCHED.js

106 ms

iam.js

410 ms

bfra_adlib_r.js

105 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 21% of them (22 requests) were addressed to the original En.boerse-frankfurt.de, 11% (11 requests) were made to I.ligatus.com and 10% (10 requests) were made to Script.boerse-frankfurt.de. The less responsive or slowest element that took the longest time to load (888 ms) relates to the external source D2.ligatus.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.6 MB (69%)

Content Size

3.8 MB

After Optimization

1.2 MB

In fact, the total size of En.boerse-frankfurt.de main page is 3.8 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. 60% of websites need less resources to load. Javascripts take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 156.8 kB

  • Original 222.1 kB
  • After minification 214.5 kB
  • After compression 65.3 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 156.8 kB or 71% of the original size.

Image Optimization

-15%

Potential reduce by 78.6 kB

  • Original 532.9 kB
  • After minification 454.3 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, En Boerse Frankfurt needs image optimization as it can save up to 78.6 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-78%

Potential reduce by 2.2 MB

  • Original 2.8 MB
  • After minification 2.0 MB
  • After compression 607.6 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 2.2 MB or 78% of the original size.

CSS Optimization

-85%

Potential reduce by 239.8 kB

  • Original 281.6 kB
  • After minification 234.9 kB
  • After compression 41.8 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. En.boerse-frankfurt.de needs all CSS files to be minified and compressed as it can save up to 239.8 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

97

After Optimization

35

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

Accessibility Review

en.boerse-frankfurt.de accessibility score

80

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

Image elements do not have [alt] attributes

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a valid value for its [lang] attribute.

Best Practices

en.boerse-frankfurt.de best practices score

67

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

Missing source maps for large first-party JavaScript

SEO Factors

en.boerse-frankfurt.de SEO score

73

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

High

Image elements do not have [alt] attributes

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

    EN

  • Encoding

    ISO-8859-1

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