Tools & Wizards About Us

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

player.phonostar.de

phonostar - Radio

Page Load Speed

2 sec in total

First Response

293 ms

Resources Loaded

1.7 sec

Page Rendered

53 ms

About Website

Click here to check amazing Player Phonostar content for Germany. Otherwise, check out these important facts you probably never knew about player.phonostar.de

Visit player.phonostar.de

Key Findings

We analyzed Player.phonostar.de page load time and found that the first response time was 293 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

player.phonostar.de performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value1,770 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.152

75/100

15%

TTI (Time to Interactive)

Value12.7 s

14/100

10%

Network Requests Diagram

player.phonostar.de

293 ms

player.phonostar.de

394 ms

ima3.js

26 ms

metaTag.min.js

422 ms

styles.8620b548680ddd867f49.css

95 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 82% of them (9 requests) were addressed to the original Player.phonostar.de, 9% (1 request) were made to Imasdk.googleapis.com and 9% (1 request) were made to Cdn.stroeerdigitalgroup.de. The less responsive or slowest element that took the longest time to load (660 ms) belongs to the original domain Player.phonostar.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 272.3 kB (39%)

Content Size

699.0 kB

After Optimization

426.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Player.phonostar.de main page is 699.0 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. 15% of websites need less resources to load. Javascripts take 662.4 kB which makes up the majority of the site volume.

HTML Optimization

-44%

Potential reduce by 421 B

  • Original 959 B
  • After minification 936 B
  • After compression 538 B

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 421 B or 44% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 29.9 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.

JavaScript Optimization

-41%

Potential reduce by 271.9 kB

  • Original 662.4 kB
  • After minification 662.4 kB
  • After compression 390.5 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 271.9 kB or 41% of the original size.

CSS Optimization

-0%

Potential reduce by 28 B

  • Original 5.8 kB
  • After minification 5.8 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. Player.phonostar.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 4 (57%)

Requests Now

7

After Optimization

3

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

player.phonostar.de accessibility score

69

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

Best Practices

player.phonostar.de best practices score

75

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

player.phonostar.de SEO score

69

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Player.phonostar.de can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Player.phonostar.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

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