Tools & Wizards About Us
futureformat.de screenshot

Report Summary

  • 0

    Performance

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

futureformat.de

futureformat DGME® ~ Die Erfolgsgaranten! Seminare, Weiterbildung, Personalentwicklung mit System: Akademie-Programme, TTT, Inhouse-Seminare, Inhouse-...

Page Load Speed

10.8 sec in total

First Response

366 ms

Resources Loaded

8.3 sec

Page Rendered

2.1 sec

futureformat.de screenshot

About Website

Click here to check amazing Futureformat content. Otherwise, check out these important facts you probably never knew about futureformat.de

Herzlich willkommen bei futureformat DGME® ~ Die Erfolgsgaranten! Online- und Präsenzseminare mit System seit 2002

Visit futureformat.de

Key Findings

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

futureformat.de performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.137

79/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

futureformat.de

366 ms

www.seminare-mit-system.de

1229 ms

layout.css

1051 ms

font.css

873 ms

web.css

620 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Futureformat.de, 35% (36 requests) were made to Cdn.website-start.de and 30% (31 requests) were made to Seminare-mit-system.de. The less responsive or slowest element that took the longest time to load (5.2 sec) relates to the external source Seminare-mit-system.de.

Page Optimization Overview & Recommendations

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

Content Size

1.3 MB

After Optimization

942.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Futureformat.de main page is 1.3 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. Images take 877.9 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 86.3 kB

  • Original 106.7 kB
  • After minification 102.1 kB
  • After compression 20.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 86.3 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 17.6 kB

  • Original 877.9 kB
  • After minification 860.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. Futureformat images are well optimized though.

JavaScript Optimization

-81%

Potential reduce by 194.2 kB

  • Original 239.1 kB
  • After minification 157.0 kB
  • After compression 44.8 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 194.2 kB or 81% of the original size.

CSS Optimization

-81%

Potential reduce by 73.6 kB

  • Original 90.4 kB
  • After minification 80.1 kB
  • After compression 16.7 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. Futureformat.de needs all CSS files to be minified and compressed as it can save up to 73.6 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 56 (56%)

Requests Now

100

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

futureformat.de

futureformat.de

366 ms

www.seminare-mit-system.de

www.seminare-mit-system.de

1229 ms

layout.css

layout.css

1051 ms

font.css

font.css

873 ms

web.css

web.css

620 ms

common,socialbookmark,rssaggregator,facebook,twitter,shoppingbasket

common,socialbookmark,rssaggregator,facebook,twitter,shoppingbasket

616 ms

logstate2-css.php

logstate2-css.php

1093 ms

logstate-js.php

logstate-js.php

1261 ms

web.js

web.js

900 ms

web.bundle.js

web.bundle.js

611 ms

common,socialbookmark,rssaggregator,facebook,twitter,shoppingbasket

common,socialbookmark,rssaggregator,facebook,twitter,shoppingbasket

919 ms

839 ms

pfcsupport.js

pfcsupport.js

1179 ms

basic.css

basic.css

1018 ms

web.css

web.css

995 ms

basic.css

basic.css

1115 ms

web.css

web.css

1131 ms

basic.css

basic.css

1118 ms

web.css

web.css

1174 ms

web.css

web.css

1218 ms

InsertWidget.js

InsertWidget.js

580 ms

in.js

in.js

633 ms

8214.js

8214.js

1426 ms

menu_bg.png

menu_bg.png

161 ms

facebook_frontend_icon_frame.png

facebook_frontend_icon_frame.png

236 ms

sub_nav_bg.png

sub_nav_bg.png

151 ms

sub_nav_link.png

sub_nav_link.png

142 ms

sidebar_bg.png

sidebar_bg.png

132 ms

cache_6174146.png

cache_6174146.png

3595 ms

cache_6633394.png

cache_6633394.png

1248 ms

cache_6626152.png

cache_6626152.png

1801 ms

cache_8211466.png

cache_8211466.png

915 ms

DIY_twitter_logo.png

DIY_twitter_logo.png

384 ms

twitter-b.png

twitter-b.png

418 ms

emotionheader3193613.jpg

emotionheader3193613.jpg

1189 ms

logo.jpg

logo.jpg

822 ms

cart.png

cart.png

924 ms

cache_29490799.png

cache_29490799.png

5177 ms

cache_4559799.jpg

cache_4559799.jpg

1071 ms

cache_31672953.jpg

cache_31672953.jpg

1228 ms

cache_29342715.jpg

cache_29342715.jpg

1315 ms

cache_4461334.jpg

cache_4461334.jpg

1424 ms

cache_6655644.jpg

cache_6655644.jpg

1595 ms

thumb_30703339.jpg

thumb_30703339.jpg

1497 ms

thumb_30703340.jpg

thumb_30703340.jpg

1561 ms

thumb_30703341.png

thumb_30703341.png

1648 ms

thumb_30703342.jpg

thumb_30703342.jpg

1721 ms

twitter_frontend_icon_frame.png

twitter_frontend_icon_frame.png

251 ms

xing_frontend_icon_frame.png

xing_frontend_icon_frame.png

385 ms

linkedin_frontend_icon_frame.png

linkedin_frontend_icon_frame.png

287 ms

printer.gif

printer.gif

141 ms

mail.gif

mail.gif

137 ms

logo.gif

logo.gif

146 ms

web.css

web.css

260 ms

order.js

order.js

157 ms

contactData.js

contactData.js

1792 ms

de_DE

de_DE

433 ms

widgets.js

widgets.js

222 ms

fp.js

fp.js

295 ms

basic.css

basic.css

421 ms

web.css

web.css

449 ms

offsite_event.php

offsite_event.php

337 ms

loading-16x16-cc.gif

loading-16x16-cc.gif

166 ms

1074 ms

logo-h.png

logo-h.png

225 ms

loader.gif

loader.gif

211 ms

sdk.js

sdk.js

587 ms

facebook.png

facebook.png

766 ms

twitter.png

twitter.png

769 ms

googleplus.png

googleplus.png

981 ms

futureformat

futureformat

373 ms

secureAnonymousFramework

secureAnonymousFramework

128 ms

bg_body_verlauf.png

bg_body_verlauf.png

898 ms

timeline.0eae788bc4fdbe9cd3e72dca3bc26358.js

timeline.0eae788bc4fdbe9cd3e72dca3bc26358.js

620 ms

button.71000885400e222c3c0eec823f8f93f0.js

button.71000885400e222c3c0eec823f8f93f0.js

612 ms

XsEg9L6Ie5_.jpg

XsEg9L6Ie5_.jpg

608 ms

261 ms

syndication

syndication

440 ms

347685772448653313

347685772448653313

691 ms

clip_viewer.js

clip_viewer.js

392 ms

de_DE

de_DE

352 ms

teamIntroduction.js

teamIntroduction.js

312 ms

linkedInCompany.js

linkedInCompany.js

313 ms

de_DE

de_DE

402 ms

xingShareButton.js

xingShareButton.js

484 ms

share.js

share.js

743 ms

xd_arbiter.php

xd_arbiter.php

402 ms

xd_arbiter.php

xd_arbiter.php

888 ms

tweet_button.fd774b599f565016d763dd860cb31c79.en.html

tweet_button.fd774b599f565016d763dd860cb31c79.en.html

116 ms

proxy.jpg

proxy.jpg

727 ms

proxy.jpg

proxy.jpg

900 ms

proxy.jpg

proxy.jpg

1037 ms

proxy.jpg

proxy.jpg

898 ms

proxy.jpg

proxy.jpg

1061 ms

proxy.jpg

proxy.jpg

993 ms

proxy.jpg

proxy.jpg

994 ms

timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css

timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css

160 ms

timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css

timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css

212 ms

spi-button.css

spi-button.css

599 ms

ff_fb_gross_normal.jpg

ff_fb_gross_normal.jpg

823 ms

syndication_bundle_v1_54a085602387c0466bf99924918f2119d047889b.css

syndication_bundle_v1_54a085602387c0466bf99924918f2119d047889b.css

716 ms

syndication_bundle_v1_54a085602387c0466bf99924918f2119d047889b.css

syndication_bundle_v1_54a085602387c0466bf99924918f2119d047889b.css

767 ms

jot.html

jot.html

59 ms

Accessibility Review

futureformat.de accessibility score

59

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

<frame> or <iframe> elements do not have a title

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

futureformat.de best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

futureformat.de SEO score

92

Search Engine Optimization Advices

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

futureformat.de

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