Tools & Wizards About Us
fst-ev.org screenshot

Report Summary

  • 94

    Performance

    Renders faster than
    93% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

fst-ev.org

FST e.V.: Startseite

Page Load Speed

3.4 sec in total

First Response

276 ms

Resources Loaded

3.1 sec

Page Rendered

94 ms

fst-ev.org screenshot

About Website

Welcome to fst-ev.org homepage info - get ready to check FST E V best content right away, or after learning these important things about fst-ev.org

FST - Freiwillige Selbstkontrolle Telefonmehrwertdienste e.V.

Visit fst-ev.org

Key Findings

We analyzed Fst-ev.org page load time and found that the first response time was 276 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

fst-ev.org performance score

94

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

93/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.069

96/100

15%

TTI (Time to Interactive)

Value2.3 s

99/100

10%

Network Requests Diagram

fst-ev.org

276 ms

www.fst-ev.org

472 ms

stylesheet_d5aac9df8f.css

247 ms

style.css

111 ms

javascript_0b12553063.js

221 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that all of those requests were addressed to Fst-ev.org and no external sources were called. The less responsive or slowest element that took the longest time to load (598 ms) belongs to the original domain Fst-ev.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 32.7 kB (16%)

Content Size

203.1 kB

After Optimization

170.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fst-ev.org main page is 203.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 84.8 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 28.2 kB

  • Original 36.4 kB
  • After minification 34.9 kB
  • After compression 8.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 28.2 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 393 B

  • Original 84.8 kB
  • After minification 84.4 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. FST E V images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 3.1 kB

  • Original 62.5 kB
  • After minification 62.5 kB
  • After compression 59.4 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

-5%

Potential reduce by 1.1 kB

  • Original 19.4 kB
  • After minification 19.4 kB
  • After compression 18.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. Fst-ev.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 13 (50%)

Requests Now

26

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fst-ev.org

fst-ev.org

276 ms

www.fst-ev.org

www.fst-ev.org

472 ms

stylesheet_d5aac9df8f.css

stylesheet_d5aac9df8f.css

247 ms

style.css

style.css

111 ms

javascript_0b12553063.js

javascript_0b12553063.js

221 ms

mootools.js

mootools.js

331 ms

de.js

de.js

359 ms

formcheck.js

formcheck.js

361 ms

formcheck.css

formcheck.css

368 ms

style.min.css

style.min.css

494 ms

blocks.css

blocks.css

380 ms

jquery.min.js

jquery.min.js

550 ms

jquery-migrate.min.js

jquery-migrate.min.js

477 ms

style.css

style.css

479 ms

web.css

web.css

490 ms

blocks.js

blocks.js

505 ms

analytics.js

analytics.js

595 ms

masonry.pkgd.min.js

masonry.pkgd.min.js

598 ms

www.fst-ev.org

www.fst-ev.org

111 ms

logo.jpg

logo.jpg

112 ms

header-img.jpg

header-img.jpg

385 ms

menu-bg.gif

menu-bg.gif

122 ms

searcg-bg.gif

searcg-bg.gif

126 ms

left-menu-bg.gif

left-menu-bg.gif

125 ms

stamp.jpg

stamp.jpg

124 ms

mouse.jpg

mouse.jpg

239 ms

Paragraph_Bleistift_klein_WEB3.JPG

Paragraph_Bleistift_klein_WEB3.JPG

240 ms

arw-pink.gif

arw-pink.gif

122 ms

arrow-down.png

arrow-down.png

221 ms

stamp.jpg

stamp.jpg

124 ms

mouse.jpg

mouse.jpg

110 ms

Paragraph_Bleistift_klein_WEB3.JPG

Paragraph_Bleistift_klein_WEB3.JPG

125 ms

Accessibility Review

fst-ev.org accessibility score

66

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

Form elements do not have associated labels

High

Links do not have a discernible name

High

<object> elements do not have alternate text

Best Practices

fst-ev.org best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

fst-ev.org SEO score

64

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

Document uses plugins

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 Fst-ev.org 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 Fst-ev.org 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

fst-ev.org

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