Tools & Wizards About Us
flatster.de screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

flatster.de

Musik suchen, aufnehmen und speichern - flatster

Page Load Speed

3.3 sec in total

First Response

380 ms

Resources Loaded

2.7 sec

Page Rendered

176 ms

flatster.de screenshot

About Website

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

Mit flatster Musik/Playlisten aufnehmen und auf PC/Handy speichern. Vorteil von flatster im Vergleich zu Spotify ist, dass Musik für immer behalten werden kann.

Visit flatster.de

Key Findings

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

flatster.de performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

flatster.de

380 ms

www2.flatster.com

334 ms

flatsterStart.aspx

743 ms

cookieconsent.min.css

103 ms

flatster-1.2.15.min.css

222 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Flatster.de, 81% (25 requests) were made to Flatster.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (743 ms) relates to the external source Flatster.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 22.1 kB (3%)

Content Size

751.7 kB

After Optimization

729.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flatster.de main page is 751.7 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. 25% of websites need less resources to load. Images take 652.0 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 18.5 kB

  • Original 23.8 kB
  • After minification 21.9 kB
  • After compression 5.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 18.5 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 723 B

  • Original 652.0 kB
  • After minification 651.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. Flatster images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 1.2 kB

  • Original 68.3 kB
  • After minification 68.3 kB
  • After compression 67.1 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

-24%

Potential reduce by 1.8 kB

  • Original 7.5 kB
  • After minification 7.5 kB
  • After compression 5.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. Flatster.de needs all CSS files to be minified and compressed as it can save up to 1.8 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (25%)

Requests Now

28

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

flatster.de

flatster.de

380 ms

www2.flatster.com

www2.flatster.com

334 ms

flatsterStart.aspx

flatsterStart.aspx

743 ms

cookieconsent.min.css

cookieconsent.min.css

103 ms

flatster-1.2.15.min.css

flatster-1.2.15.min.css

222 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

421 ms

jquery.inlinefieldlabel.min-1.0.js

jquery.inlinefieldlabel.min-1.0.js

506 ms

jquery.simplemodal.1.4.4.min.js

jquery.simplemodal.1.4.4.min.js

515 ms

jquery.form-validator.min.js

jquery.form-validator.min.js

23 ms

cookieconsent.min.js

cookieconsent.min.js

520 ms

flatster-1.1.9.min.js

flatster-1.1.9.min.js

539 ms

analytics.js

analytics.js

45 ms

pageback2.gif

pageback2.gif

101 ms

flatster.jpg

flatster.jpg

233 ms

gratis.jpg

gratis.jpg

330 ms

flatster2.jpg

flatster2.jpg

504 ms

flatster-Musik-suchen-und-aufnehmen-von-Webradios.jpg

flatster-Musik-suchen-und-aufnehmen-von-Webradios.jpg

408 ms

aufnehmen.jpg

aufnehmen.jpg

410 ms

flatsterTarife.jpg

flatsterTarife.jpg

301 ms

flatsterGratisAufnehmenTesten.jpg

flatsterGratisAufnehmenTesten.jpg

694 ms

events.jpg

events.jpg

402 ms

prepaid.jpg

prepaid.jpg

439 ms

student.jpg

student.jpg

502 ms

top.png

top.png

495 ms

tabs2.png

tabs2.png

497 ms

code.png

code.png

521 ms

go.png

go.png

574 ms

sliderbuttons.png

sliderbuttons.png

562 ms

song_add.gif

song_add.gif

567 ms

collect

collect

13 ms

js

js

79 ms

Accessibility Review

flatster.de accessibility score

74

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.

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 [lang] attribute

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.

Best Practices

flatster.de best practices score

58

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

SEO Factors

flatster.de SEO score

92

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

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flatster.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Flatster.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

flatster.de

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