rhein-zeitung.de

rhein-zeitung.de is SSL secured

Free website and domain report on rhein-zeitung.de

Last Updated: 31st August, 2021 Update Now
Overview

Snoop Summary for rhein-zeitung.de

This is a free and comprehensive report about rhein-zeitung.de. The domain rhein-zeitung.de is currently hosted on a server located in Germany with the IP address 185.132.224.41, where the local currency is EUR and German is the local language. Our records indicate that rhein-zeitung.de is owned/operated by Mittelrhein-Verlag GmbH. Rhein-zeitung.de is expected to earn an estimated $19 USD per day from advertising revenue. The sale of rhein-zeitung.de would possibly be worth $13,733 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Rhein-zeitung.de receives an estimated 6,596 unique visitors every day - a huge amount of traffic! This report was last updated 31st August, 2021.

About rhein-zeitung.de

Site Preview: rhein-zeitung.de rhein-zeitung.de
Title: Rhein Zeitung online
Description: Rhein-Zeitung
Keywords and Tags: general news, news, popular
Related Terms: aargauer zeitung, aargauer zeitung aboservice, aargauer zeitung fc aarau, aargauer zeitung freiamt, az online aargau zeitung, blick zeitung, hannover zeitung archiv, immobilien zeitung, psd bank rhein ruhr, rhein erft
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

3/5 (Great!)

Valuation

$13,733 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 70,586
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 6,596
Monthly Visitors: 200,761
Yearly Visitors: 2,407,540
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $19 USD
Monthly Revenue: $572 USD
Yearly Revenue: $6,861 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: rhein-zeitung.de 16
Domain Name: rhein-zeitung 13
Extension (TLD): de 2

Page Speed Analysis

Average Load Time: 1.63 seconds
Load Time Comparison: Faster than 57% of sites

PageSpeed Insights

Avg. (All Categories) 91
Performance 90
Accessibility 97
Best Practices 87
SEO 83
Progressive Web App 100
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.rhein-zeitung.de/
Updated: 31st August, 2021

1.41 seconds
First Contentful Paint (FCP)
82%
13%
5%

0.00 seconds
First Input Delay (FID)
99%
1%
0%

Simulate loading on desktop
90

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for rhein-zeitung.de. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.9 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 1.1 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Max Potential First Input Delay — 50 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.9 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://rhein-zeitung.de/
http/1.1
0
296.63100000471
374
0
301
text/html
https://www.rhein-zeitung.de/
http/1.1
297.66500019468
1190.7220000867
51718
144954
200
text/html
Document
https://www.rhein-zeitung.de/pu_rz/assets/js/consentscript.js?v=202106
http/1.1
1208.4510000423
1878.9880000986
2179
4224
200
text/javascript
Script
https://www.rhein-zeitung.de/pu_rz/scripts/jquery.3.5.1.js
http/1.1
1208.9210001286
1971.7310001142
31302
89475
200
text/javascript
Script
https://www.rhein-zeitung.de/cms_media/minify/6/styles/style_421.css
http/1.1
1209.3150001019
2072.5520001724
46169
231432
200
text/css
Stylesheet
https://www.rhein-zeitung.de/cms_media/minify/6/javascript/javascript_175.js
http/1.1
1210.4110000655
2062.5880002044
45931
169549
200
text/javascript
Script
https://www.rhein-zeitung.de/cms_media/module_img/39/19501_1294_org_titelseite.jpg
http/1.1
2073.6310000066
2486.2290001474
366
0
301
text/html
https://www.rhein-zeitung.de/cms_media/module_img/3914/1957289_1_headerlogoxl_rhein-zeitung.png
http/1.1
2074.8550000135
2837.0690001175
13365
13020
200
image/png
Image
https://www.rhein-zeitung.de/pu_rz/images/teaser/placeholderalpha.png
http/1.1
2124.2380000185
2455.3370000795
1279
957
200
image/png
Image
https://www.googletagmanager.com/gtm.js?id=GTM-NPWD2W
h2
2125.3300001845
2139.6090001799
50499
162024
200
application/javascript
Script
https://www.rhein-zeitung.de/pu_rz/assets/login/?t=0.3205345200306444
http/1.1
2125.9010001086
2923.4060000163
1318
1577
200
text/html
Script
https://www.rhein-zeitung.de/cms_media/module_img/3980/1990024_1_org_bergeundmeer.png
http/1.1
2126.1670000385
2740.7820001245
410
0
301
text/html
https://www.rhein-zeitung.de/pu_rz/images/wetter/svg/wolkig.svg
http/1.1
2126.2990001123
2457.3560000863
1425
2163
200
image/svg+xml
Image
https://www.rhein-zeitung.de/pu_rz/images/wetter/svg/heiter.svg
http/1.1
2126.5500001609
2456.857000012
1425
2163
200
image/svg+xml
Image
https://www.rhein-zeitung.de/cms_media/module_img/3950/1975229_1_bubbleimagelink_AdobeStock_181021829.jpeg
http/1.1
2126.942000119
2742.2700000461
9070
8725
200
image/jpeg
Image
https://www.rhein-zeitung.de/cms_media/module_img/3950/1975153_1_bubbleimagelink_AdobeStock_53996005.jpeg
http/1.1
2127.1770000458
2613.8970002066
21433
21087
200
image/jpeg
Image
https://cdn.privacy-mgmt.com/wrapperMessagingWithoutDetection.js
h2
2127.3450001609
2141.9830000959
45035
155326
200
application/javascript
Script
https://www.rhein-zeitung.de/pu_rz/images/icons/assets_ico.png
http/1.1
2138.6950002052
2738.9730000868
9906
9582
200
image/png
Image
https://www.rhein-zeitung.de/pu_rz/images/icons/magnify.png
http/1.1
2140.5500001274
2764.0880001709
1546
1223
200
image/png
Image
data
2183.023000136
2183.215000201
0
338
200
image/svg+xml
Image
data
2206.2420002185
2206.370000029
0
43
200
image/gif
Image
data
2206.6310001537
2206.7560001742
0
26
200
image/gif
Image
https://projekt.rhein-zeitung.de/mrv/hul/hochwasser/
http/1.1
2210.7090000063
2891.4930000901
1238
2674
200
text/html
Fetch
data
2221.8120000325
2221.966000041
0
636
200
image/svg+xml
Image
https://cdn.privacy-mgmt.com/wrapper/tcfv2/v1/gdpr/native-message?requestUUID=f4887ae9-fa0d-4544-89cf-4a49d480fc67&hasCsp=true&env=prod&consentLanguage=browserDefault&body=%7B%22accountId%22%3A1724%2C%22requestUUID%22%3A%22f4887ae9-fa0d-4544-89cf-4a49d480fc67%22%2C%22propertyHref%22%3A%22https%3A%2F%2Fwww.rhein-zeitung.de%2F%22%2C%22euconsent%22%3Anull%2C%22meta%22%3A%22%7B%5C%22mmsCookies%5C%22%3A%5B%5D%2C%5C%22resolved%5C%22%3Anull%7D%22%2C%22clientMMSOrigin%22%3A%22https%3A%2F%2Fconsent.rhein-zeitung.de%22%2C%22targetingParams%22%3Anull%2C%22campaignEnv%22%3A%22prod%22%2C%22pubData%22%3A%7B%7D%7D
h2
2328.330000164
2356.958999997
651
0
200
text/plain
Preflight
https://cdn.privacy-mgmt.com/wrapper/tcfv2/v1/gdpr/native-message?requestUUID=f4887ae9-fa0d-4544-89cf-4a49d480fc67&hasCsp=true&env=prod&consentLanguage=browserDefault&body=%7B%22accountId%22%3A1724%2C%22requestUUID%22%3A%22f4887ae9-fa0d-4544-89cf-4a49d480fc67%22%2C%22propertyHref%22%3A%22https%3A%2F%2Fwww.rhein-zeitung.de%2F%22%2C%22euconsent%22%3Anull%2C%22meta%22%3A%22%7B%5C%22mmsCookies%5C%22%3A%5B%5D%2C%5C%22resolved%5C%22%3Anull%7D%22%2C%22clientMMSOrigin%22%3A%22https%3A%2F%2Fconsent.rhein-zeitung.de%22%2C%22targetingParams%22%3Anull%2C%22campaignEnv%22%3A%22prod%22%2C%22pubData%22%3A%7B%7D%7D
h2
2357.6940000057
2574.4520002045
17138
457239
200
application/json
XHR
https://analytics.rhein-zeitung.de/matomo.js
http/1.1
2393.0450000335
3087.9830000922
63199
62877
200
application/javascript
Script
https://www.rhein-zeitung.de/pu_rz/images/icons/sudoku_white.png
http/1.1
2465.4750002082
2847.6290002
1231
909
200
image/png
Image
https://www.rhein-zeitung.de/cms_media/module_img/39/19501_3025_org_titelseite.jpg
http/1.1
2486.6470000707
2945.1830000617
18192
17846
200
image/jpeg
Image
https://www.rhein-zeitung.de/pu_rz/ajax/regiomap.html
http/1.1
2529.0780002251
3199.4730001315
3468
11068
200
text/html
XHR
https://www.rhein-zeitung.de/cms_media/module_img/4623/2311564_1_mrvlargeteaser_253901453.jpg
http/1.1
2546.1530000903
3119.8140000924
63761
63415
200
image/jpeg
Image
https://www.rhein-zeitung.de/cms_media/module_img/4623/2311799_1_mrvmediumteaser_image_17af6b0784aa295e.jpg
http/1.1
2546.4440002106
3388.0670000799
40390
40044
200
image/jpeg
Image
https://www.rhein-zeitung.de/cms_media/module_img/2101/1050829_1_mrvmediumteaser_Kommentarfoto_Manfred_Ruch.jpg
http/1.1
2547.3680000287
2913.8629999943
11630
11284
200
image/jpeg
Image
https://www.rhein-zeitung.de/cms_media/module_img/4623/2311796_1_mrvsmallteaser_image_4e8a98034702354e.jpg
http/1.1
2547.5180000067
3311.1720001325
23924
23578
200
image/jpeg
Image
https://www.rhein-zeitung.de/cms_media/module_img/4623/2311695_1_mrvsmallteaser_image_6ad6df75f380be39.jpg
http/1.1
2548.0510001071
3007.4760001153
22930
22584
200
image/jpeg
Image
https://www.rhein-zeitung.de/cms_media/module_img/3980/1990024_2_org_bergeundmeer.png
http/1.1
2741.7500000447
2850.1360001974
2919
2576
200
image/png
Image
https://projekt.rhein-zeitung.de/rzlayout/helftunsleben/hullogo.png
http/1.1
2895.7530001644
3189.0430001076
6166
5821
200
image/png
Image
https://analytics.rhein-zeitung.de/matomo.php?action_name=www.rhein-zeitung.de%2FRhein-Zeitung&idsite=1&rec=1&r=308421&h=1&m=13&s=28&url=https%3A%2F%2Fwww.rhein-zeitung.de%2F&_id=&_idn=1&_refts=0&send_image=0&cookie=1&res=800x600&pv_id=13gTck&pf_net=0&pf_srv=894&pf_tfr=0&pf_dm1=1258
3112.7379999962
3115.0520001538
0
0
-1
Ping
https://www.rhein-zeitung.de/pu_rz/images/regiomap/regiomap_blank.png
http/1.1
3210.0570001639
3596.7780000065
1371
1048
200
image/png
Image
https://www.rhein-zeitung.de/pu_rz/images/regiomap/regiomap_locations.png
http/1.1
3210.5220002122
3597.3930000328
17014
16689
200
image/png
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1231.119
11.24
1243.196
5.258
1248.798
5.53
2110.404
12.008
2122.53
44.344
2166.896
21.751
2188.727
13.777
2202.653
8.878
2211.906
20.199
2244.872
6.293
2251.191
43.964
2299.94
9.679
2309.913
54.043
2364.013
14.633
2388.693
42.082
2430.873
23.712
2458.946
5.475
2466.787
18.553
2486.121
32.011
2529.565
23.621
2558.543
6.584
2576.755
10.286
2614.658
20.943
2895.534
7.627
2931.833
16.251
2952.369
8.449
3045.756
8.095
3130.742
19.808
3158.372
17.414
3236.555
10.372
3349.974
15.664
3426.288
17.148
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Rhein-zeitung.de should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images — Potential savings of 30 KiB
Images can slow down the page's load time. Rhein-zeitung.de should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.rhein-zeitung.de/cms_media/module_img/4623/2311796_1_mrvsmallteaser_image_4e8a98034702354e.jpg
23578
10632
https://www.rhein-zeitung.de/cms_media/module_img/4623/2311695_1_mrvsmallteaser_image_6ad6df75f380be39.jpg
22584
10184
https://www.rhein-zeitung.de/cms_media/module_img/3914/1957289_1_headerlogoxl_rhein-zeitung.png
13020
9762
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Rhein-zeitung.de should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Rhein-zeitung.de should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Rhein-zeitung.de should consider minifying JS files.
Reduce unused CSS — Potential savings of 39 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Rhein-zeitung.de should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.rhein-zeitung.de/cms_media/minify/6/styles/style_421.css
46169
39744
Reduce unused JavaScript — Potential savings of 94 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.rhein-zeitung.de/cms_media/minify/6/javascript/javascript_175.js
45931
37534
https://analytics.rhein-zeitung.de/matomo.js
63199
37031
https://cdn.privacy-mgmt.com/wrapperMessagingWithoutDetection.js
45035
21700
Efficiently encode images — Potential savings of 8 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.rhein-zeitung.de/cms_media/module_img/39/19501_3025_org_titelseite.jpg
17846
8554
Serve images in next-gen formats — Potential savings of 11 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.rhein-zeitung.de/cms_media/module_img/39/19501_3025_org_titelseite.jpg
17846
11750
Enable text compression — Potential savings of 41 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://analytics.rhein-zeitung.de/matomo.js
62877
42475
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Rhein-zeitung.de should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://rhein-zeitung.de/
190
https://www.rhein-zeitung.de/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Rhein-zeitung.de should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 13 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://cdn.privacy-mgmt.com/wrapperMessagingWithoutDetection.js
12985
https://www.rhein-zeitung.de/cms_media/minify/6/javascript/javascript_175.js
45

Diagnostics

Avoids enormous network payloads — Total size was 615 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.rhein-zeitung.de/cms_media/module_img/4623/2311564_1_mrvlargeteaser_253901453.jpg
63761
https://analytics.rhein-zeitung.de/matomo.js
63199
https://www.rhein-zeitung.de/
51718
https://www.googletagmanager.com/gtm.js?id=GTM-NPWD2W
50499
https://www.rhein-zeitung.de/cms_media/minify/6/styles/style_421.css
46169
https://www.rhein-zeitung.de/cms_media/minify/6/javascript/javascript_175.js
45931
https://cdn.privacy-mgmt.com/wrapperMessagingWithoutDetection.js
45035
https://www.rhein-zeitung.de/cms_media/module_img/4623/2311799_1_mrvmediumteaser_image_17af6b0784aa295e.jpg
40390
https://www.rhein-zeitung.de/pu_rz/scripts/jquery.3.5.1.js
31302
https://www.rhein-zeitung.de/cms_media/module_img/4623/2311796_1_mrvsmallteaser_image_4e8a98034702354e.jpg
23924
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Rhein-zeitung.de should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.2 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.rhein-zeitung.de/
249.239
14.042
4.018
https://www.rhein-zeitung.de/cms_media/minify/6/javascript/javascript_175.js
173.435
53.772
3.41
https://cdn.privacy-mgmt.com/wrapperMessagingWithoutDetection.js
74.874
66.849
3.044
Unattributable
73.164
4.47
0.304
https://www.googletagmanager.com/gtm.js?id=GTM-NPWD2W
64.643
57.777
3.975
Minimizes main-thread work — 0.7 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
276.059
Rendering
139.857
Style & Layout
128.293
Other
120.618
Parse HTML & CSS
50.661
Script Parsing & Compilation
19.931
Garbage Collection
5.413
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 36 requests • 615 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
36
629972
Image
19
268977
Script
7
239463
Document
1
51718
Stylesheet
1
46169
Other
8
23645
Media
0
0
Font
0
0
Third-party
4
113323
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
50499
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
img
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://cdn.privacy-mgmt.com/wrapperMessagingWithoutDetection.js
1096
54
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Speed Index — 2.0 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 1.5 s
The timing of the largest text or image that is painted.

Diagnostics

Serve static assets with an efficient cache policy — 3 resources found
Rhein-zeitung.de can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://analytics.rhein-zeitung.de/matomo.js
0
63199
https://projekt.rhein-zeitung.de/rzlayout/helftunsleben/hullogo.png
0
6166
https://cdn.privacy-mgmt.com/wrapperMessagingWithoutDetection.js
3600000
45035

Opportunities

Reduce initial server response time — Root document took 890 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.rhein-zeitung.de/
894.046
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoid an excessive DOM size — 1,575 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
1575
Maximum DOM Depth
19
Maximum Child Elements
25
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://www.rhein-zeitung.de/cms_media/module_img/3980/1990024_1_org_bergeundmeer.png
97

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of rhein-zeitung.de. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Rhein-zeitung.de may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
87

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that rhein-zeitung.de should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
SWFObject
core-js
core-js-global@3.6.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://rhein-zeitung.de/
Allowed

Audits

Displays images with incorrect aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
URL Aspect Ratio (Displayed) Aspect Ratio (Actual)
https://www.rhein-zeitung.de/pu_rz/images/regiomap/regiomap_blank.png
300 x 458 (0.66)
244 x 334 (0.73)
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for rhein-zeitung.de. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of rhein-zeitung.de on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
robots.txt is not valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
100

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of rhein-zeitung.de. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Registers a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of rhein-zeitung.de on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest has a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 88
Performance 64
Accessibility 97
Best Practices 87
SEO 93
Progressive Web App 100
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.rhein-zeitung.de/
Updated: 31st August, 2021

1.55 seconds
First Contentful Paint (FCP)
81%
15%
4%

0.03 seconds
First Input Delay (FID)
94%
5%
1%

Simulate loading on mobile
64

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for rhein-zeitung.de. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Total Blocking Time — 190 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Cumulative Layout Shift — 0
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Rhein-zeitung.de should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Rhein-zeitung.de should consider serving more appropriate-sized images.
Defer offscreen images — Potential savings of 35 KiB
Time to Interactive can be slowed down by resources on the page. Rhein-zeitung.de should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.rhein-zeitung.de/cms_media/module_img/3950/1975153_1_bubbleimagelink_AdobeStock_53996005.jpeg
21087
21087
https://www.rhein-zeitung.de/cms_media/module_img/3950/1975229_1_bubbleimagelink_AdobeStock_181021829.jpeg
8725
8725
https://projekt.rhein-zeitung.de/rzlayout/helftunsleben/hullogo.png
5821
5821
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Rhein-zeitung.de should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Rhein-zeitung.de should consider minifying JS files.
Efficiently encode images — Potential savings of 8 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.rhein-zeitung.de/cms_media/module_img/39/19501_3025_org_titelseite.jpg
17846
8554
Serve images in next-gen formats — Potential savings of 11 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.rhein-zeitung.de/cms_media/module_img/39/19501_3025_org_titelseite.jpg
17846
11750
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Rhein-zeitung.de should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://rhein-zeitung.de/
630
https://www.rhein-zeitung.de/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Rhein-zeitung.de should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 13 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://cdn.privacy-mgmt.com/wrapperMessagingWithoutDetection.js
12985
https://www.rhein-zeitung.de/cms_media/minify/6/javascript/javascript_175.js
45

Diagnostics

Avoids enormous network payloads — Total size was 484 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://analytics.rhein-zeitung.de/matomo.js
63199
https://www.rhein-zeitung.de/
51719
https://www.googletagmanager.com/gtm.js?id=GTM-NPWD2W
50499
https://www.rhein-zeitung.de/cms_media/minify/6/styles/style_421.css
46169
https://www.rhein-zeitung.de/cms_media/minify/6/javascript/javascript_175.js
45931
https://cdn.privacy-mgmt.com/wrapperMessagingWithoutDetection.js
45035
https://www.rhein-zeitung.de/pu_rz/scripts/jquery.3.5.1.js
31302
https://www.rhein-zeitung.de/cms_media/module_img/4623/2311799_1_mrvsmallteaser_image_17af6b0784aa295e.jpg
30039
https://www.rhein-zeitung.de/cms_media/module_img/4623/2311564_1_mrvsmallteaser_253901453.jpg
28163
https://www.rhein-zeitung.de/cms_media/module_img/3950/1975153_1_bubbleimagelink_AdobeStock_53996005.jpeg
21433
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Rhein-zeitung.de should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 1.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.rhein-zeitung.de/
929.484
99.332
15.956
https://www.rhein-zeitung.de/cms_media/minify/6/javascript/javascript_175.js
642.816
209.068
12.804
https://cdn.privacy-mgmt.com/wrapperMessagingWithoutDetection.js
300.62
266.732
12.78
Unattributable
245.692
16.352
1.06
https://www.googletagmanager.com/gtm.js?id=GTM-NPWD2W
222.708
196.788
14.624
https://www.rhein-zeitung.de/pu_rz/assets/js/consentscript.js?v=202106
192.972
86.74
6.136
https://www.rhein-zeitung.de/pu_rz/scripts/jquery.3.5.1.js
98.832
80.532
6.94
https://analytics.rhein-zeitung.de/matomo.js
64.4
57.36
4.944
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 30 requests • 484 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
30
496060
Script
7
239463
Image
14
138532
Document
1
51719
Stylesheet
1
46169
Other
7
20177
Media
0
0
Font
0
0
Third-party
4
113322
Minimize third-party usage — Third-party code blocked the main thread for 70 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
50499
67.38
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
img
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 12 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://cdn.privacy-mgmt.com/wrapperMessagingWithoutDetection.js
3935
219
https://www.googletagmanager.com/gtm.js?id=GTM-NPWD2W
4215
132
https://cdn.privacy-mgmt.com/wrapperMessagingWithoutDetection.js
4604
82
https://www.rhein-zeitung.de/pu_rz/scripts/jquery.3.5.1.js
3150
74
https://www.rhein-zeitung.de/pu_rz/assets/js/consentscript.js?v=202106
2533
71
https://www.rhein-zeitung.de/
1795
69
https://analytics.rhein-zeitung.de/matomo.js
5877
64
https://www.googletagmanager.com/gtm.js?id=GTM-NPWD2W
4154
61
https://www.rhein-zeitung.de/cms_media/minify/6/javascript/javascript_175.js
4372
59
https://www.rhein-zeitung.de/cms_media/minify/6/javascript/javascript_175.js
3881
54
https://www.rhein-zeitung.de/cms_media/minify/6/javascript/javascript_175.js
3830
51
https://www.rhein-zeitung.de/cms_media/minify/6/javascript/javascript_175.js
3780
50
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://rhein-zeitung.de/
http/1.1
0
373.70100000408
375
0
301
text/html
https://www.rhein-zeitung.de/
http/1.1
374.66100003803
1258.2120000152
51719
144954
200
text/html
Document
https://www.rhein-zeitung.de/pu_rz/assets/js/consentscript.js?v=202106
http/1.1
1277.6080000331
1949.8630000162
2179
4224
200
text/javascript
Script
https://www.rhein-zeitung.de/pu_rz/scripts/jquery.3.5.1.js
http/1.1
1277.8490000055
2061.2060000421
31302
89475
200
text/javascript
Script
https://www.rhein-zeitung.de/cms_media/minify/6/styles/style_421.css
http/1.1
1278.3400000189
1783.2490000292
46169
231432
200
text/css
Stylesheet
https://www.rhein-zeitung.de/cms_media/minify/6/javascript/javascript_175.js
http/1.1
1278.7039999967
2137.0170000009
45931
169549
200
text/javascript
Script
https://www.rhein-zeitung.de/cms_media/module_img/39/19501_1294_org_titelseite.jpg
http/1.1
2072.329000046
2531.7270000232
366
0
301
text/html
https://www.rhein-zeitung.de/cms_media/module_img/3914/1957289_1_headerlogos_rhein-zeitung.png
http/1.1
2151.1720000417
2536.8040000321
6306
5962
200
image/png
Image
https://www.rhein-zeitung.de/pu_rz/images/teaser/placeholderalpha.png
http/1.1
2170.5420000362
2825.0129999942
1279
957
200
image/png
Image
https://www.googletagmanager.com/gtm.js?id=GTM-NPWD2W
h2
2171.2699999916
2193.8760000048
50499
162024
200
application/javascript
Script
https://www.rhein-zeitung.de/pu_rz/assets/login/?t=0.8692270720565298
http/1.1
2171.5970000369
2681.0750000295
1318
1577
200
text/html
Script
https://www.rhein-zeitung.de/cms_media/module_img/3980/1990024_1_org_bergeundmeer.png
http/1.1
2172.0550000318
2852.5810000137
410
0
301
text/html
https://www.rhein-zeitung.de/pu_rz/images/wetter/svg/wolkig.svg
http/1.1
2173.0050000479
2802.2830000264
1425
2163
200
image/svg+xml
Image
https://www.rhein-zeitung.de/pu_rz/images/wetter/svg/heiter.svg
http/1.1
2173.265999998
2822.6730000461
1425
2163
200
image/svg+xml
Image
https://www.rhein-zeitung.de/cms_media/module_img/3950/1975229_1_bubbleimagelink_AdobeStock_181021829.jpeg
http/1.1
2173.4760000254
2842.1560000279
9070
8725
200
image/jpeg
Image
https://www.rhein-zeitung.de/cms_media/module_img/3950/1975153_1_bubbleimagelink_AdobeStock_53996005.jpeg
http/1.1
2173.8910000422
2914.5850000205
21433
21087
200
image/jpeg
Image
https://cdn.privacy-mgmt.com/wrapperMessagingWithoutDetection.js
h2
2174.4690000196
2198.9429999958
45035
155326
200
application/javascript
Script
https://www.rhein-zeitung.de/pu_rz/images/icons/magnify.png
http/1.1
2178.1980000087
2513.701000018
1546
1223
200
image/png
Image
data
2222.012000042
2222.1610000124
0
338
200
image/svg+xml
Image
data
2257.3080000002
2257.4270000332
0
43
200
image/gif
Image
data
2257.8010000288
2257.9010000336
0
26
200
image/gif
Image
https://projekt.rhein-zeitung.de/mrv/hul/hochwasser/
http/1.1
2287.8950000159
2987.9130000481
1238
2674
200
text/html
Fetch
data
2302.285999991
2302.4720000103
0
636
200
image/svg+xml
Image
https://cdn.privacy-mgmt.com/wrapper/tcfv2/v1/gdpr/native-message?requestUUID=605ae323-3b05-4a97-814b-4514449b6921&hasCsp=true&env=prod&consentLanguage=browserDefault&body=%7B%22accountId%22%3A1724%2C%22requestUUID%22%3A%22605ae323-3b05-4a97-814b-4514449b6921%22%2C%22propertyHref%22%3A%22https%3A%2F%2Fwww.rhein-zeitung.de%2F%22%2C%22euconsent%22%3Anull%2C%22meta%22%3A%22%7B%5C%22mmsCookies%5C%22%3A%5B%5D%2C%5C%22resolved%5C%22%3Anull%7D%22%2C%22clientMMSOrigin%22%3A%22https%3A%2F%2Fconsent.rhein-zeitung.de%22%2C%22targetingParams%22%3Anull%2C%22campaignEnv%22%3A%22prod%22%2C%22pubData%22%3A%7B%7D%7D
h2
2394.8910000036
2458.191999991
651
0
200
text/plain
Preflight
https://cdn.privacy-mgmt.com/wrapper/tcfv2/v1/gdpr/native-message?requestUUID=605ae323-3b05-4a97-814b-4514449b6921&hasCsp=true&env=prod&consentLanguage=browserDefault&body=%7B%22accountId%22%3A1724%2C%22requestUUID%22%3A%22605ae323-3b05-4a97-814b-4514449b6921%22%2C%22propertyHref%22%3A%22https%3A%2F%2Fwww.rhein-zeitung.de%2F%22%2C%22euconsent%22%3Anull%2C%22meta%22%3A%22%7B%5C%22mmsCookies%5C%22%3A%5B%5D%2C%5C%22resolved%5C%22%3Anull%7D%22%2C%22clientMMSOrigin%22%3A%22https%3A%2F%2Fconsent.rhein-zeitung.de%22%2C%22targetingParams%22%3Anull%2C%22campaignEnv%22%3A%22prod%22%2C%22pubData%22%3A%7B%7D%7D
h2
2458.6320000235
2621.9109999947
17137
457239
200
application/json
XHR
https://analytics.rhein-zeitung.de/matomo.js
http/1.1
2480.8000000194
3152.172000031
63199
62877
200
application/javascript
Script
https://www.rhein-zeitung.de/pu_rz/images/icons/sudoku_white.png
http/1.1
2511.9460000424
3188.1050000084
1231
909
200
image/png
Image
https://www.rhein-zeitung.de/cms_media/module_img/39/19501_3025_org_titelseite.jpg
http/1.1
2532.0480000228
3273.1849999982
18192
17846
200
image/jpeg
Image
https://www.rhein-zeitung.de/cms_media/module_img/3980/1990024_2_org_bergeundmeer.png
http/1.1
2853.237000003
3237.2939999914
2919
2576
200
image/png
Image
https://www.rhein-zeitung.de/cms_media/module_img/4623/2311564_1_mrvsmallteaser_253901453.jpg
http/1.1
2954.7970000422
3337.0030000224
28163
27817
200
image/jpeg
Image
https://www.rhein-zeitung.de/cms_media/module_img/4623/2311799_1_mrvsmallteaser_image_17af6b0784aa295e.jpg
http/1.1
2955.0400000298
3433.4760000347
30039
29693
200
image/jpeg
Image
https://projekt.rhein-zeitung.de/rzlayout/helftunsleben/hullogo.png
http/1.1
2991.6300000041
3658.8789999951
6167
5821
200
image/png
Image
https://analytics.rhein-zeitung.de/matomo.php?action_name=www.rhein-zeitung.de%2FRhein-Zeitung&idsite=1&rec=1&r=876216&h=1&m=14&s=0&url=https%3A%2F%2Fwww.rhein-zeitung.de%2F&_id=&_idn=1&_refts=0&send_image=0&cookie=1&res=360x640&pv_id=wESxpe&pf_net=0&pf_srv=885&pf_tfr=0&pf_dm1=1241
3172.8790000197
3175.5370000028
0
0
-1
Ping
https://www.rhein-zeitung.de/cms_media/module_img/2101/1050829_1_mrvsmallteaser_Kommentarfoto_Manfred_Ruch.jpg
http/1.1
3686.3810000359
4070.7040000125
9337
8992
200
image/jpeg
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
1296.555
10.839
1308.301
5.912
1314.518
5.464
1819.088
12.043
2104.019
18.385
2184.721
25.05
2209.791
9.915
2219.998
20.066
2240.08
35.595
2278.984
5.932
2293.915
25.626
2320.011
8.129
2330.26
27.108
2357.668
10.009
2373.975
54.762
2428.834
15.255
2448.598
34.346
2483.355
32.93
2522.188
12.368
2534.871
29.609
2566.816
7.581
2659.198
20.421
2861.417
18.207
2985.438
6.28
3025.681
12.892
3192.257
15.909
3373.23
13.768
3469.571
14.628
4108.418
17.85
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Metrics

Time to Interactive — 5.0 s
The time taken for the page to become fully interactive.

Other

Max Potential First Input Delay — 220 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 3.1 s
The time taken for the primary content of the page to be rendered.

Opportunities

Reduce unused CSS — Potential savings of 39 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Rhein-zeitung.de should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.rhein-zeitung.de/cms_media/minify/6/styles/style_421.css
46169
39787
Reduce unused JavaScript — Potential savings of 94 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.rhein-zeitung.de/cms_media/minify/6/javascript/javascript_175.js
45931
37442
https://analytics.rhein-zeitung.de/matomo.js
63199
37031
https://cdn.privacy-mgmt.com/wrapperMessagingWithoutDetection.js
45035
21700
Enable text compression — Potential savings of 41 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://analytics.rhein-zeitung.de/matomo.js
62877
42475
Preload Largest Contentful Paint image — Potential savings of 210 ms
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.rhein-zeitung.de/cms_media/module_img/4623/2311564_1_mrvsmallteaser_253901453.jpg
210

Diagnostics

Serve static assets with an efficient cache policy — 3 resources found
Rhein-zeitung.de can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://analytics.rhein-zeitung.de/matomo.js
0
63199
https://projekt.rhein-zeitung.de/rzlayout/helftunsleben/hullogo.png
0
6167
https://cdn.privacy-mgmt.com/wrapperMessagingWithoutDetection.js
3600000
45035
Minimize main-thread work — 2.8 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
1015.56
Style & Layout
558.248
Other
470.336
Rendering
455.776
Parse HTML & CSS
174.66
Script Parsing & Compilation
76.052

Metrics

First Contentful Paint — 3.1 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 6.0 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 5.7 s
The timing of the largest text or image that is painted.

Opportunities

Reduce initial server response time — Root document took 880 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://www.rhein-zeitung.de/
884.53

Diagnostics

Avoid an excessive DOM size — 1,607 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
1607
Maximum DOM Depth
18
Maximum Child Elements
25
Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL Failing Elements
https://www.rhein-zeitung.de/cms_media/module_img/3980/1990024_1_org_bergeundmeer.png

Other

First Contentful Paint (3G) — 6185 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
97

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of rhein-zeitung.de. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Rhein-zeitung.de may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
87

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that rhein-zeitung.de should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
SWFObject
core-js
core-js-global@3.6.1
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://rhein-zeitung.de/
Allowed

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://www.rhein-zeitung.de/cms_media/module_img/4623/2311564_1_mrvsmallteaser_253901453.jpg
340 x 191
420 x 236
680 x 382
93

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for rhein-zeitung.de. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of rhein-zeitung.de on mobile screens.
Document uses legible font sizes — 97.27% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
.teaser__meta
2.44%
11.84px
.weatherbox__temprature, .weatherbox__day
0.29%
11.2px
97.27%
≥ 12px
Tap targets are sized appropriately — 100% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.

Crawling and Indexing

robots.txt is not valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
100

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of rhein-zeitung.de. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Registers a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of rhein-zeitung.de on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest has a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 185.132.224.41
Continent: Europe
Country: Germany
Germany Flag
Region:
City:
Longitude: 9.491
Latitude: 51.2993
Currencies: EUR
Languages: German

Web Hosting Provider

Registration

Domain Registrant

Private Registration: No
Name:
Organization: Mittelrhein-Verlag GmbH
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness: 90/100
WOT Child Safety: 92/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: *.rhein-zeitung.de
Issued By: Thawte RSA CA 2018
Valid From: 9th June, 2020
Valid To: 12th September, 2022
Subject: CN = *.rhein-zeitung.de
O = Mittelrhein-Verlag GmbH
L = Koblenz
S = DE
Hash: 9ad428f5
Issuer: CN = Thawte RSA CA 2018
OU = www.digicert.com
O = DigiCert Inc
S = US
Version: 2
Serial Number: 18936682042343492673740464695035877877
Serial Number (Hex): 0E3F128234739C0331B26969BCB8D9F5
Valid From: 9th June, 2024
Valid To: 12th September, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:A3:C8:5E:65:54:E5:30:78:C1:05:EA:07:0A:6A:59:CC:B9:FE:DE:5A
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://cdp.thawte.com/ThawteRSACA2018.crl

Certificate Policies: Policy: 2.16.840.1.114412.1.1
CPS: https://www.digicert.com/CPS
Policy: 2.23.140.1.2.2

Authority Information Access: OCSP - URI:http://status.thawte.com
CA Issuers - URI:http://cacerts.thawte.com/ThawteRSACA2018.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
Timestamp : Jun 9 08:45:11.288 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:E7:03:89:3F:D3:96:C0:CE:EF:E4:FD:
E9:89:CD:D7:95:5A:57:27:C5:7B:69:8E:DC:B3:49:8B:
52:B8:4C:EB:68:02:21:00:D6:71:4B:7C:CF:CA:B3:80:
F2:84:75:A4:07:0F:A1:E7:E4:FB:BE:4F:C0:34:A3:1D:
3D:2D:CE:E2:C5:37:A8:F7
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 22:45:45:07:59:55:24:56:96:3F:A1:2F:F1:F7:6D:86:
E0:23:26:63:AD:C0:4B:7F:5D:C6:83:5C:6E:E2:0F:02
Timestamp : Jun 9 08:45:11.324 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:D1:EE:00:CD:E4:83:6A:94:70:14:05:
F2:76:91:77:C4:42:CE:7B:73:38:C5:97:CF:2B:83:FF:
06:06:09:17:54:02:20:1C:6F:8C:A5:ED:9C:B3:07:DD:
D9:8E:75:C1:57:10:40:AF:71:27:C2:3E:24:0D:0C:A1:
09:D3:D4:B9:82:94:BD
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 51:A3:B0:F5:FD:01:79:9C:56:6D:B8:37:78:8F:0C:A4:
7A:CC:1B:27:CB:F7:9E:88:42:9A:0D:FE:D4:8B:05:E5
Timestamp : Jun 9 08:45:11.400 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:89:A5:52:66:56:EE:C4:6A:F9:54:DE:
FD:73:F1:FC:FF:6B:7F:FA:40:FB:D9:40:3C:44:5D:AE:
2B:4C:95:01:6F:02:20:12:41:7B:38:50:0B:5C:D5:AC:
E4:FE:54:45:72:8C:5F:55:FE:3A:8B:66:7A:FB:0A:2B:
FB:41:F8:E6:7C:4F:13
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 41:C8:CA:B1:DF:22:46:4A:10:C6:A1:3A:09:42:87:5E:
4E:31:8B:1B:03:EB:EB:4B:C7:68:F0:90:62:96:06:F6
Timestamp : Jun 9 08:45:11.225 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:BF:CD:F5:A7:43:BF:E2:BF:65:6D:C0:
8E:0F:19:51:88:F9:CC:4F:70:BF:D7:67:69:6C:F1:5E:
0B:18:0B:A7:87:02:20:5C:99:97:5A:B2:D6:FE:62:C3:
30:6C:CF:F0:F0:CC:04:0A:91:56:44:93:A6:82:5C:AC:
07:65:8F:20:45:F3:C8
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:rhein-zeitung.de
DNS:*.rhein-zeitung.de
Technical

DNS Lookup

A Records

Host IP Address Class TTL
rhein-zeitung.de. 185.132.224.41 IN 21600

NS Records

Host Nameserver Class TTL
rhein-zeitung.de. ns-a.ktk.de. IN 21600
rhein-zeitung.de. ns-b.ktk.io. IN 21600
rhein-zeitung.de. ns-c.ktk.de. IN 21600

MX Records

Priority Host Server Class TTL
30 rhein-zeitung.de. mx-a.ktk.de. IN 21600
30 rhein-zeitung.de. mx-b.ktk.de. IN 21600

SOA Records

Domain Name Primary NS Responsible Email TTL
rhein-zeitung.de. ns-a.ktk.de. hostmaster.noc.ktk.de. 21600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0, proxy-revalidate
expires: 28th July, 1997
Content-Type: text/html; charset=utf-8
Date: 31st August, 2021
pragma: no-cache
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
strict-transport-security: max-age=600
Age: 69
Via: 1.1 varnish
Connection: keep-alive

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: ns-a.ktk.de
ns-b.ktk.io
ns-c.ktk.de
Full Whois: % Restricted rights.
%
% Terms and Conditions of Use
%
% The above data may only be used within the scope of technical or
% administrative necessities of Internet operation or to remedy legal
% problems.
% The use for other purposes, in particular for advertising, is not permitted.
%
% The DENIC whois service on port 43 doesn't disclose any information concerning
% the domain holder, general request and abuse contact.
% This information can be obtained through use of our web-based whois service
% available at the DENIC website:
% http://www.denic.de/en/domains/whois-service/web-whois.html
%
%

Domain: rhein-zeitung.de
Nserver: ns-a.ktk.de
Nserver: ns-b.ktk.io
Nserver: ns-c.ktk.de
Status: connect
Changed: 2017-02-03T10:31:24+01:00

Nameservers

Name IP Address
ns-a.ktk.de 212.7.160.5
ns-b.ktk.io 5.231.198.203
ns-c.ktk.de 212.7.160.11
Related

Subdomains

Domain Subdomain
archiv

Similar Sites

Domain Valuation Snoop Score
$31,070,054 USD 4/5
$41,733 USD 3/5
0/5
0/5
0/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address