Tools & Wizards About Us
futuresax.de screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

futuresax.de

futureSAX - Innovationsplattform des Freistaates Sachsen

Page Load Speed

11.4 sec in total

First Response

325 ms

Resources Loaded

10.3 sec

Page Rendered

766 ms

futuresax.de screenshot

About Website

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

futureSAX ist die zentrale Anlaufstelle im Gründungs- & Innovationsökosystem Sachsen mit dem Ziel, Innovationen sichtbarer zu machen.

Visit futuresax.de

Key Findings

We analyzed Futuresax.de page load time and found that the first response time was 325 ms and then it took 11.1 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

futuresax.de performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value18.0 s

0/100

10%

TBT (Total Blocking Time)

Value160 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.205

61/100

15%

TTI (Time to Interactive)

Value7.1 s

52/100

10%

Network Requests Diagram

futuresax.de

325 ms

futuresax.de

423 ms

www.futuresax.de

8104 ms

merged-7f4c4d7a33b6fa979c4f531f2b2f2dcb-00221679c3a0fe47bd29c00fcae87342.css

476 ms

merged-2c32d0203b46c4f35ff3aef2877fd428-6657adebb13d59e5e9cb7e93fbbfe4fc.js

193 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 97% of them (35 requests) were addressed to the original Futuresax.de, 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (8.1 sec) belongs to the original domain Futuresax.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 998.8 kB (28%)

Content Size

3.5 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-91%

Potential reduce by 819.7 kB

  • Original 896.0 kB
  • After minification 407.3 kB
  • After compression 76.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. This page needs HTML code to be minified as it can gain 488.7 kB, which is 55% 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 819.7 kB or 91% of the original size.

Image Optimization

-6%

Potential reduce by 136.8 kB

  • Original 2.4 MB
  • After minification 2.2 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. FutureSAX images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 26.7 kB

  • Original 172.4 kB
  • After minification 172.4 kB
  • After compression 145.7 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 26.7 kB or 15% of the original size.

CSS Optimization

-25%

Potential reduce by 15.6 kB

  • Original 63.0 kB
  • After minification 63.0 kB
  • After compression 47.4 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. Futuresax.de needs all CSS files to be minified and compressed as it can save up to 15.6 kB or 25% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

25

After Optimization

25

  • Images
  • JavaScript
  • CSS

The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FutureSAX. According to our analytics all requests are already optimized.

Network Requests Diagram

futuresax.de

futuresax.de

325 ms

futuresax.de

futuresax.de

423 ms

www.futuresax.de

www.futuresax.de

8104 ms

merged-7f4c4d7a33b6fa979c4f531f2b2f2dcb-00221679c3a0fe47bd29c00fcae87342.css

merged-7f4c4d7a33b6fa979c4f531f2b2f2dcb-00221679c3a0fe47bd29c00fcae87342.css

476 ms

merged-2c32d0203b46c4f35ff3aef2877fd428-6657adebb13d59e5e9cb7e93fbbfe4fc.js

merged-2c32d0203b46c4f35ff3aef2877fd428-6657adebb13d59e5e9cb7e93fbbfe4fc.js

193 ms

merged-5d858819d5b1f00ac8d3f41ded0e33bc-a7a814c17876a2f060280b331f353e05.js

merged-5d858819d5b1f00ac8d3f41ded0e33bc-a7a814c17876a2f060280b331f353e05.js

517 ms

gtm.js

gtm.js

205 ms

logo.svg

logo.svg

176 ms

logo-contrast.svg

logo-contrast.svg

179 ms

polygon-pattern-gr.png

polygon-pattern-gr.png

298 ms

linkedin.svg

linkedin.svg

296 ms

youtube.svg

youtube.svg

342 ms

instagram.svg

instagram.svg

390 ms

imagemap-fallback.png

imagemap-fallback.png

859 ms

imagemap.svg

imagemap.svg

395 ms

imagemap-1.svg

imagemap-1.svg

392 ms

imagemap-2.svg

imagemap-2.svg

391 ms

imagemap-3.svg

imagemap-3.svg

435 ms

imagemap-4.svg

imagemap-4.svg

484 ms

imagemap-5.svg

imagemap-5.svg

493 ms

csm_Thumbnail_Innokulturfilm_0ab5dfcbde.jpg

csm_Thumbnail_Innokulturfilm_0ab5dfcbde.jpg

583 ms

polygon-pattern-kl.png

polygon-pattern-kl.png

420 ms

KlavikaBasic-Regular.woff

KlavikaBasic-Regular.woff

522 ms

OpenSans-Light.woff

OpenSans-Light.woff

572 ms

KlavikaBasic-Medium.woff

KlavikaBasic-Medium.woff

594 ms

Custom-Iconfont.woff

Custom-Iconfont.woff

594 ms

OpenSans-Semibold.woff

OpenSans-Semibold.woff

594 ms

OpenSans-Bold.woff

OpenSans-Bold.woff

638 ms

OpenSans-Regular.woff

OpenSans-Regular.woff

678 ms

OpenSans-Regular-Italic.woff

OpenSans-Regular-Italic.woff

678 ms

csm_20230704_gruppe_preistraeger_01_59a3bf6e46.jpg

csm_20230704_gruppe_preistraeger_01_59a3bf6e46.jpg

1012 ms

csm_Startseite10_a94dda276e.jpg

csm_Startseite10_a94dda276e.jpg

629 ms

csm_DSC07796_4762ab85ac.jpg

csm_DSC07796_4762ab85ac.jpg

1014 ms

csm_0CFB36BC-0A52-4378-888C-B1614A78BEEE_10e9ffe34d.jpeg

csm_0CFB36BC-0A52-4378-888C-B1614A78BEEE_10e9ffe34d.jpeg

964 ms

csm_content_herter_0660159966.jpeg

csm_content_herter_0660159966.jpeg

696 ms

sachsen_logo2x.jpg

sachsen_logo2x.jpg

798 ms

Accessibility Review

futuresax.de accessibility score

69

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-*] attributes do not match their roles

High

[role]s are not contained by their required parent element

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

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

futuresax.de SEO score

86

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

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

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

futuresax.de

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