Tools & Wizards About Us

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

rt1.de

HITRADIO RT1

Page Load Speed

3.4 sec in total

First Response

509 ms

Resources Loaded

2.8 sec

Page Rendered

75 ms

About Website

Welcome to rt1.de homepage info - get ready to check RT1 best content for Germany right away, or after learning these important things about rt1.de

HITRADIO RT1 ist das moderne Radio für Augsburg Stadt und Land, Memmingen und das Unterallgäu, Nordschwaben und Neuburg-Schrobenhausen,mit der besten Musikmischung aus aktuellen Hits.

Visit rt1.de

Key Findings

We analyzed Rt1.de page load time and found that the first response time was 509 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

rt1.de performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value16.9 s

0/100

10%

TBT (Total Blocking Time)

Value12,240 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.126

83/100

15%

TTI (Time to Interactive)

Value24.3 s

0/100

10%

Network Requests Diagram

rt1.de

509 ms

rt1.imsueden.de

818 ms

Material+Icons:1-11-4

526 ms

Jost:300,300i,400,400i,500,500i,700

622 ms

app.css

247 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Rt1.de, 40% (10 requests) were made to Rt1.imsueden.de and 20% (5 requests) were made to Assets.welocal.world. The less responsive or slowest element that took the longest time to load (876 ms) relates to the external source Assets.welocal.world.

Page Optimization Overview & Recommendations

Page size can be reduced by 397.4 kB (57%)

Content Size

691.3 kB

After Optimization

293.9 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Rt1.de main page is 691.3 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. Javascripts take 271.1 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 215.4 kB

  • Original 252.9 kB
  • After minification 252.7 kB
  • After compression 37.5 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 215.4 kB or 85% of the original size.

JavaScript Optimization

-31%

Potential reduce by 83.0 kB

  • Original 271.1 kB
  • After minification 271.1 kB
  • After compression 188.2 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 83.0 kB or 31% of the original size.

CSS Optimization

-59%

Potential reduce by 99.0 kB

  • Original 167.2 kB
  • After minification 162.5 kB
  • After compression 68.2 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. Rt1.de needs all CSS files to be minified and compressed as it can save up to 99.0 kB or 59% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (91%)

Requests Now

23

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

rt1.de accessibility score

79

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.

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

rt1.de best practices score

75

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

Missing source maps for large first-party JavaScript

SEO Factors

rt1.de SEO score

83

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

High

Tap targets are not sized appropriately

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 Rt1.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 Rt1.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 data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: