Tools & Wizards About Us
rtf1.de screenshot

Report Summary

  • 2

    Performance

    Renders faster than
    20% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

rtf1.de

RTF.1 Regionalfernsehen

Page Load Speed

4 sec in total

First Response

865 ms

Resources Loaded

2.3 sec

Page Rendered

857 ms

rtf1.de screenshot

About Website

Visit rtf1.de now to see the best up-to-date RTF 1 content for Germany and also check out these interesting facts you probably never knew about rtf1.de

Fernsehen fuer die Region Neckar-Alb

Visit rtf1.de

Key Findings

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

rtf1.de performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value16.2 s

0/100

10%

TBT (Total Blocking Time)

Value15,640 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.166

1/100

15%

TTI (Time to Interactive)

Value25.2 s

0/100

10%

Network Requests Diagram

rtf1.de

865 ms

mootools.js

861 ms

mootools-more.js

248 ms

rtf1.css

305 ms

jwplayer.js

411 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 56% of them (52 requests) were addressed to the original Rtf1.de, 8% (7 requests) were made to Googleads.g.doubleclick.net and 6% (6 requests) were made to I1.ytimg.com. The less responsive or slowest element that took the longest time to load (865 ms) belongs to the original domain Rtf1.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 605.9 kB (41%)

Content Size

1.5 MB

After Optimization

861.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 82.1 kB

  • Original 99.4 kB
  • After minification 90.5 kB
  • After compression 17.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 82.1 kB or 83% of the original size.

Image Optimization

-31%

Potential reduce by 290.5 kB

  • Original 939.3 kB
  • After minification 648.8 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. Obviously, RTF 1 needs image optimization as it can save up to 290.5 kB or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-53%

Potential reduce by 211.5 kB

  • Original 402.5 kB
  • After minification 353.5 kB
  • After compression 190.9 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 211.5 kB or 53% of the original size.

CSS Optimization

-82%

Potential reduce by 21.8 kB

  • Original 26.6 kB
  • After minification 21.4 kB
  • After compression 4.8 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. Rtf1.de needs all CSS files to be minified and compressed as it can save up to 21.8 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (27%)

Requests Now

90

After Optimization

66

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rtf1.de

rtf1.de

865 ms

mootools.js

mootools.js

861 ms

mootools-more.js

mootools-more.js

248 ms

rtf1.css

rtf1.css

305 ms

jwplayer.js

jwplayer.js

411 ms

jquery.min.js

jquery.min.js

77 ms

mediaboxAdv.js

mediaboxAdv.js

308 ms

mediaboxBlack.css

mediaboxBlack.css

348 ms

script_dropdown-menu.js

script_dropdown-menu.js

406 ms

cookieconsent.latest.min.js

cookieconsent.latest.min.js

28 ms

adsbygoogle.js

adsbygoogle.js

5 ms

default.jpg

default.jpg

27 ms

bg_site.jpg

bg_site.jpg

139 ms

header_spring_7.jpg

header_spring_7.jpg

242 ms

header_logo.png

header_logo.png

137 ms

search_button.jpg

search_button.jpg

138 ms

button_nachtimcarre.jpg

button_nachtimcarre.jpg

239 ms

button_hbw.jpg

button_hbw.jpg

106 ms

startseite_symbol_video.png

startseite_symbol_video.png

237 ms

startseite_symbol_information.png

startseite_symbol_information.png

239 ms

startseite_symbol_werbung.png

startseite_symbol_werbung.png

240 ms

startseite_symbol_film.png

startseite_symbol_film.png

239 ms

startseite_symbol_post.png

startseite_symbol_post.png

335 ms

startseite_symbol_jobs.png

startseite_symbol_jobs.png

336 ms

sp_box_img_werbung.jpg

sp_box_img_werbung.jpg

410 ms

getimage.php

getimage.php

524 ms

arrow_2056ae.png

arrow_2056ae.png

358 ms

banner_kleidermueller.jpg

banner_kleidermueller.jpg

356 ms

getimage.php

getimage.php

469 ms

getimage.php

getimage.php

549 ms

getimage.php

getimage.php

551 ms

getimage.php

getimage.php

580 ms

wetter_starkbewoelkt.png

wetter_starkbewoelkt.png

512 ms

wetter_schnee.png

wetter_schnee.png

579 ms

sp_logo_bweins.jpg

sp_logo_bweins.jpg

631 ms

sp_logo_rtf3.jpg

sp_logo_rtf3.jpg

634 ms

sp_logo_prometheus.jpg

sp_logo_prometheus.jpg

709 ms

sp_logo_rik-rt.jpg

sp_logo_rik-rt.jpg

710 ms

sp_logo_rik-tue.jpg

sp_logo_rik-tue.jpg

794 ms

sp_logo_rik-et.jpg

sp_logo_rik-et.jpg

793 ms

sp_logo_rik-zol.jpg

sp_logo_rik-zol.jpg

810 ms

sp_logo_landschaft.jpg

sp_logo_landschaft.jpg

811 ms

sp_logo_buchtipps.jpg

sp_logo_buchtipps.jpg

811 ms

sp_logo_werbung.jpg

sp_logo_werbung.jpg

812 ms

sp_logo_mitschnitt.jpg

sp_logo_mitschnitt.jpg

812 ms

sp_logo_jobs.jpg

sp_logo_jobs.jpg

812 ms

0.gif

0.gif

841 ms

default.jpg

default.jpg

29 ms

default.jpg

default.jpg

32 ms

default.jpg

default.jpg

29 ms

default.jpg

default.jpg

30 ms

default.jpg

default.jpg

30 ms

all.js

all.js

32 ms

ga.js

ga.js

31 ms

bg_main.jpg

bg_main.jpg

833 ms

__utm.gif

__utm.gif

25 ms

272 ms

widgets.js

widgets.js

9 ms

xd_arbiter.php

xd_arbiter.php

46 ms

xd_arbiter.php

xd_arbiter.php

85 ms

ca-pub-5016613802279223.js

ca-pub-5016613802279223.js

121 ms

zrt_lookup.html

zrt_lookup.html

65 ms

show_ads_impl.js

show_ads_impl.js

64 ms

bg_mediathek_item.jpg

bg_mediathek_item.jpg

781 ms

intro_list_top.jpg

intro_list_top.jpg

780 ms

intro_list_sub.jpg

intro_list_sub.jpg

778 ms

bg_news.jpg

bg_news.jpg

776 ms

jwpsrv.js

jwpsrv.js

318 ms

ads

ads

336 ms

arrow_08246d.png

arrow_08246d.png

708 ms

bg_mediathek.jpg

bg_mediathek.jpg

708 ms

osd.js

osd.js

5 ms

ads

ads

526 ms

bg_sp_box_right.jpg

bg_sp_box_right.jpg

695 ms

ads

ads

425 ms

ads

ads

445 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

28 ms

bg_footer1.jpg

bg_footer1.jpg

633 ms

ads

ads

357 ms

follow_button.6a78875565a912489e9aef879c881358.de.html

follow_button.6a78875565a912489e9aef879c881358.de.html

17 ms

jot

jot

129 ms

like.php

like.php

282 ms

m_js_controller.js

m_js_controller.js

25 ms

abg.js

abg.js

41 ms

favicon

favicon

117 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

114 ms

nessie_icon_thin_arrow_big_white.png

nessie_icon_thin_arrow_big_white.png

32 ms

s

s

20 ms

x_button_blue2.png

x_button_blue2.png

8 ms

16910508652739014568

16910508652739014568

118 ms

MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js

MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js

34 ms

qbEHJxuVK5u.js

qbEHJxuVK5u.js

116 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

112 ms

Accessibility Review

rtf1.de accessibility score

63

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

rtf1.de best practices score

83

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

SEO Factors

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rtf1.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 Rtf1.de main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

rtf1.de

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