lottohelden.de

lottohelden.de is SSL secured

Free website and domain report on lottohelden.de

Last Updated: 8th September, 2022 Update Now
Overview

Snoop Summary for lottohelden.de

This is a free and comprehensive report about lottohelden.de. The domain lottohelden.de is currently hosted on a server located in United States with the IP address 104.21.40.46, where the local currency is USD and English is the local language. Lottohelden.de is expected to earn an estimated $35 USD per day from advertising revenue. The sale of lottohelden.de would possibly be worth $25,571 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Lottohelden.de receives an estimated 8,280 unique visitors every day - a huge amount of traffic! This report was last updated 8th September, 2022.

About lottohelden.de

Site Preview: lottohelden.de lottohelden.de
Title: Lottohelden.de: Online Lotto spielen beim Testsieger
Description: Tippen Sie online beim Testsieger: Die beliebtesten Lotterien online ✓ Automatische Auszahlung ✓ Gratistipps für Neukunden ✓ Staatlich lizenziert ✓
Keywords and Tags: gambling, gambling related, popular
Related Terms: auszahlung, euromillionen tippen, gesichtscreme testsieger 2019, lotto tippen, nebenkosten beim hausbau, neukunden, online lotto spielen, probleme beim lernen, testsieger, tippen
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

3/5 (Great!)

Valuation

$25,571 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 48,032
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: 8,280
Monthly Visitors: 252,017
Yearly Visitors: 3,022,200
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $35 USD
Monthly Revenue: $1,066 USD
Yearly Revenue: $12,781 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: lottohelden.de 14
Domain Name: lottohelden 11
Extension (TLD): de 2

Page Speed Analysis

Average Load Time: 2.39 seconds
Load Time Comparison: Faster than 35% of sites

PageSpeed Insights

Avg. (All Categories) 88
Performance 51
Accessibility 95
Best Practices 92
SEO 100
PWA 100
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.lottohelden.de/
Updated: 8th September, 2022

1.38 seconds
First Contentful Paint (FCP)
83%
9%
8%

0.00 seconds
First Input Delay (FID)
92%
3%
5%

Simulate loading on desktop
51

Performance

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

Metrics

First Contentful Paint — 0.8 s
The time taken for the first image or text on the page to be rendered.
Cumulative Layout Shift — 0.022
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

First Meaningful Paint — 0.8 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://lottohelden.de/
http/1.1
0
255.77499999781
735
0
301
text/html
https://lottohelden.de/
http/1.1
256.30599999567
720.99199998775
1132
0
301
text/html
https://www.lottohelden.de/
h2
721.46800000337
960.98499998334
165583
2066402
200
text/html
Document
https://www.lottohelden.de/css/app.76147286.css
h2
996.92999999388
1569.8619999748
30619
194240
200
text/css
Stylesheet
https://www.lottohelden.de/fonts/source-sans-pro-v12-latin-900.d8eab344.woff2
h2
997.3239999963
1549.7209999885
16789
15324
200
font/woff2
Font
https://www.lottohelden.de/fonts/source-sans-pro-v12-latin-900italic.f6a4e055.woff2
h2
997.55800000275
1551.3329999812
16223
14764
200
font/woff2
Font
https://www.lottohelden.de/fonts/source-sans-pro-v12-latin-700.1a4bcb3e.woff2
h2
997.8949999786
1511.1809999798
17221
15764
200
font/woff2
Font
https://www.lottohelden.de/fonts/source-sans-pro-v12-latin-600.c85615b2.woff2
h2
998.19299997762
1533.3140000002
17407
15948
200
font/woff2
Font
https://www.lottohelden.de/fonts/source-sans-pro-v12-latin-regular.899c8f78.woff2
h2
998.36699999287
1539.0749999788
17571
16112
200
font/woff2
Font
https://www.lottohelden.de/css/styles~view-home.cd0d65dc.css
h2
998.66899999324
1189.0389999899
5400
18981
200
text/css
Stylesheet
https://www.lottohelden.de/graphcms/media/resize=w:4560,h:360/output=f:webp/quality=value:35/compress/wtynrjXUR4CIGNGcsRQb
h2
1556.7269999883
2172.2730000038
55812
54106
200
image/webp
Image
https://www.lottohelden.de/js/app.76529d93.js
h2
1573.3299999847
2420.1699999976
484573
1914390
200
application/javascript
Script
https://www.lottohelden.de/js/styles~view-home.196e4f40.js
h2
1590.051999985
2113.0370000028
15001
68737
200
application/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-MVSTVZT
h2
1593.3619999851
1620.0829999871
54878
155925
200
application/javascript
Script
https://www.lottohelden.de/img/logo-regular.86d7fca3.svg
h2
1862.0589999773
1946.146000002
3095
5566
200
image/svg+xml
Image
https://www.lottohelden.de/img/account.fa683246.svg
h2
1862.7599999891
2297.4379999796
1923
1032
200
image/svg+xml
Image
https://www.lottohelden.de/img/checkout.543eabf1.svg
h2
1862.9260000016
2256.7960000015
2647
2567
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.7a6b9aa5.svg
h2
1865.4249999963
2273.6569999834
3553
4664
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.5f8a9423.svg
h2
1866.1139999749
2250.4099999787
4044
5916
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.87bc1b6f.svg
h2
1884.5149999834
2304.4349999982
3975
6174
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.70e26461.svg
h2
1886.8720000028
2332.9289999965
4422
9957
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.052537fc.svg
h2
1887.0689999894
2301.2429999944
3261
7139
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.242942f6.svg
h2
1889.3809999863
2327.9119999788
2913
3145
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.17304717.svg
h2
1890.2639999869
2021.7290000001
7197
12298
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.3aaae90c.svg
h2
1891.2859999982
2354.1689999984
2788
3132
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.a533c16a.svg
h2
1891.7749999964
2291.6259999911
3156
3946
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.5708e307.svg
h2
1892.691999994
2273.4969999874
3531
5545
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.51b01efc.svg
h2
1893.7569999835
2321.3589999941
2704
2693
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.cf8b4abc.svg
h2
1894.0270000021
2046.6339999984
9059
18847
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.34e33ce9.svg
h2
1895.2159999753
2286.5319999983
3576
6806
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.89de42d1.svg
h2
1895.4209999938
2345.1829999976
4132
6169
200
image/svg+xml
Image
https://www.lottohelden.de/img/arrow.7ef576c1.svg
h2
1895.9789999935
2013.3109999879
1681
365
200
image/svg+xml
Image
https://www.lottohelden.de/img/d_w.7453962f.png
h2
1927.8549999872
2311.9169999845
7233
5776
200
image/png
Image
https://www.lottohelden.de/img/flamme.f5217674.svg
h2
1928.1789999804
2324.2179999943
2058
1126
200
image/svg+xml
Image
https://www.lottohelden.de/img/star-gold.f05588dd.svg
h2
1931.316000002
2364.109999995
1598
215
200
image/svg+xml
Image
https://www.lottohelden.de/img/phone.497d0cc1.svg
h2
1933.9959999779
2357.8449999914
2459
2045
200
image/svg+xml
Image
https://www.lottohelden.de/img/mail.f8ff33c3.svg
h2
1934.2369999795
2347.9719999887
1896
834
200
image/svg+xml
Image
https://www.lottohelden.de/img/help.e35f766b.svg
h2
1934.8049999971
2361.264999985
2586
2220
200
image/svg+xml
Image
https://o1010732.ingest.sentry.io/api/6173459/envelope/?sentry_key=3da8cd75a13a433881bcbe05393406c4&sentry_version=7
h2
2644.5200000016
2721.8239999784
453
2
200
application/json
Fetch
https://www.lottohelden.de/css/styles~view-cms-mainteaser~view-home.93b1ab37.css
h2
3156.6799999855
3549.3429999915
12892
92420
200
text/css
Stylesheet
https://www.lottohelden.de/js/styles~view-cms-mainteaser~view-home.7e470bd1.js
h2
3158.7349999754
3559.7169999965
5821
16682
200
application/javascript
Script
https://www.lottohelden.de/graphcms/media/resize=w:4560,h:1600/output=f:webp/quality=value:35/compress/YQ50WFstQxuZ1780H0Er
h2
4440.9480000031
5130.9639999818
114444
112700
200
image/webp
Image
https://www.lottohelden.de/img/certificate.bc83abe0.svg
h2
4445.6519999949
4846.3789999951
1911
852
200
image/svg+xml
Image
https://www.lottohelden.de/img/payout.4ddc6b6c.svg
h2
4446.2269999785
4854.5849999937
1827
672
200
image/svg+xml
Image
https://www.lottohelden.de/img/fees.b852c699.svg
h2
4446.3919999835
4862.1679999924
2201
1626
200
image/svg+xml
Image
https://www.lottohelden.de/img/award.6056c7a4.svg
h2
4446.7139999906
4865.3129999875
1988
931
200
image/svg+xml
Image
https://www.lottohelden.de/graphcms/media/resize=w:720,h:340,fit:crop/output=f:webp/quality=value:35/compress/Jp8IwV6TquHOiVQQLzct
h2
4711.7349999899
5224.2059999844
16223
14526
200
image/webp
Image
https://www.lottohelden.de/graphcms/media/resize=w:720,h:340,fit:crop/output=f:webp/quality=value:35/compress/zuwym1XxS4uOxM15ofMX
h2
4712.4329999788
5124.4109999971
7916
6216
200
image/webp
Image
https://www.lottohelden.de/graphcms/media/resize=w:720,h:340,fit:crop/output=f:webp/quality=value:35/compress/xMX3c1zIRmeWNa72cLAP
h2
4712.6789999893
5200.4190000007
18810
17052
200
image/webp
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)
973.773
32.757
1011.434
15.051
1026.501
15.382
1573.882
14.309
1590.295
260.333
1850.655
30.057
1885.057
34.072
1924.638
37.551
1962.325
15.54
1984.439
13.296
2512.197
682.221
3552.177
6.602
3559.043
9.062
3570.184
873.528
4444.155
23.408
4470.787
215.576
4686.396
13.767
4700.243
9.28
4709.668
5.106
4739.194
5.111
4744.316
49.484
4794.035
17.789
4842.566
6.298
4849.668
5.076
5148.746
5.717
5216.039
90.599
5308.386
5.39
5322.193
5.253
7152.696
15.63
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.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Lottohelden.de should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images — Potential savings of 4 KiB
Images can slow down the page's load time. Lottohelden.de should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.lottohelden.de/graphcms/media/resize=w:720,h:340,fit:crop/output=f:webp/quality=value:35/compress/zuwym1XxS4uOxM15ofMX
6216
4604
Defer offscreen images — Potential savings of 28 KiB
Time to Interactive can be slowed down by resources on the page. Lottohelden.de should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.lottohelden.de/img/logo.cf8b4abc.svg
9059
9059
https://www.lottohelden.de/img/logo.89de42d1.svg
4132
4132
https://www.lottohelden.de/img/logo.34e33ce9.svg
3576
3576
https://www.lottohelden.de/img/logo.5708e307.svg
3531
3531
https://www.lottohelden.de/img/logo.a533c16a.svg
3156
3156
https://www.lottohelden.de/img/logo.3aaae90c.svg
2788
2788
https://www.lottohelden.de/img/logo.51b01efc.svg
2693
2693
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Lottohelden.de should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Lottohelden.de should consider minifying JS files.
Reduce unused CSS — Potential savings of 38 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Lottohelden.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.lottohelden.de/css/app.76147286.css
30619
25832
https://www.lottohelden.de/css/styles~view-cms-mainteaser~view-home.93b1ab37.css
12892
12892
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 240 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.lottohelden.de/
240.508
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Lottohelden.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 0 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://www.lottohelden.de/js/app.76529d93.js
77
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.lottohelden.de/graphcms/media/resize=w:4560,h:1600/output=f:webp/quality=value:35/compress/YQ50WFstQxuZ1780H0Er
0
Avoids enormous network payloads — Total size was 1,142 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.lottohelden.de/js/app.76529d93.js
484573
https://www.lottohelden.de/
165583
https://www.lottohelden.de/graphcms/media/resize=w:4560,h:1600/output=f:webp/quality=value:35/compress/YQ50WFstQxuZ1780H0Er
114444
https://www.lottohelden.de/graphcms/media/resize=w:4560,h:360/output=f:webp/quality=value:35/compress/wtynrjXUR4CIGNGcsRQb
55812
https://www.googletagmanager.com/gtm.js?id=GTM-MVSTVZT
54878
https://www.lottohelden.de/css/app.76147286.css
30619
https://www.lottohelden.de/graphcms/media/resize=w:720,h:340,fit:crop/output=f:webp/quality=value:35/compress/xMX3c1zIRmeWNa72cLAP
18810
https://www.lottohelden.de/fonts/source-sans-pro-v12-latin-regular.899c8f78.woff2
17571
https://www.lottohelden.de/fonts/source-sans-pro-v12-latin-600.c85615b2.woff2
17407
https://www.lottohelden.de/fonts/source-sans-pro-v12-latin-700.1a4bcb3e.woff2
17221
Uses efficient cache policy on static assets — 0 resources found
Lottohelden.de can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
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. Lottohelden.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 — 3 user timings
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
https://www.lottohelden.de/
Mark
1590.026
sentry-tracing-init
Mark
2629.711
app-view-mounted
Mark
4158.005
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 — 49 requests • 1,142 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
49
1168917
Script
4
560273
Image
33
306619
Document
1
165583
Font
5
85211
Stylesheet
3
48911
Other
3
2320
Media
0
0
Third-party
2
55331
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)
54878
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
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
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 — 4 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://www.lottohelden.de/js/styles~view-cms-mainteaser~view-home.7e470bd1.js
2185
437
https://www.lottohelden.de/js/app.76529d93.js
1826
341
https://www.lottohelden.de/
792
260
https://www.lottohelden.de/js/app.76529d93.js
1610
216
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
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 lottohelden.de on mobile screens.
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.

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

Time to Interactive — 2.6 s
The time taken for the page to become fully interactive.
Largest Contentful Paint — 2.3 s
The timing of the largest text or image that is painted.

Other

Reduce unused JavaScript — Potential savings of 204 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.lottohelden.de/js/app.76529d93.js
484573
180861
https://www.googletagmanager.com/gtm.js?id=GTM-MVSTVZT
54878
28214
Avoid multiple page redirects — Potential savings of 340 ms
Redirects can cause additional delays before the page can begin loading. Lottohelden.de should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://lottohelden.de/
190
https://lottohelden.de/
150
https://www.lottohelden.de/
0
Avoid an excessive DOM size — 837 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
837
Maximum DOM Depth
8
21
Maximum Child Elements
14
Reduce JavaScript execution time — 1.7 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.lottohelden.de/js/styles~view-cms-mainteaser~view-home.7e470bd1.js
972.10199999999
773.93399999999
0.37
https://www.lottohelden.de/js/app.76529d93.js
928.148
773.452
27.566
https://www.lottohelden.de/
623.774
27.038
103.474
Unattributable
183.783
6.122
0.295
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
1611.633
Other
263.353
Garbage Collection
222.13
Parse HTML & CSS
188.151
Style & Layout
176.841
Rendering
173.462
Script Parsing & Compilation
139.521

Metrics

Speed Index — 2.9 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 1,010 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).

Audits

Max Potential First Input Delay — 440 ms
Users could experience a delay when interacting with the page.
95

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of lottohelden.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.
`<object>` elements have alternate 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"]`
Lottohelden.de may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Names and labels

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

Best Practices

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

Audits

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
Host allowlists can frequently be bypassed. Consider using CSP nonces or hashes instead, along with 'strict-dynamic' if necessary.
script-src
High
'unsafe-inline' allows the execution of unsafe in-page scripts and event handlers. Consider using CSP nonces or hashes to allow scripts individually.
script-src
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.
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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Preact
10
Vue
core-js
core-js-global@3.24.1; core-js-pure@3.21.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.
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://lottohelden.de/
Allowed

Audits

Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.lottohelden.de/js/app.76529d93.js
100

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for lottohelden.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 lottohelden.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.
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.
robots.txt is 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

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of lottohelden.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.
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 lottohelden.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) 78
Performance 25
Accessibility 95
Best Practices 92
SEO 98
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://www.lottohelden.de/
Updated: 8th September, 2022

1.36 seconds
First Contentful Paint (FCP)
86%
9%
5%

0.04 seconds
First Input Delay (FID)
86%
6%
8%

Simulate loading on mobile
25

Performance

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

Metrics

Cumulative Layout Shift — 0.067
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Lottohelden.de should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images — Potential savings of 15 KiB
Images can slow down the page's load time. Lottohelden.de should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.lottohelden.de/graphcms/media/resize=w:1216,h:1080/output=f:webp/quality=value:35/compress/yFqbNDTRSbOWolhPHw2D
34026
15465
Defer offscreen images — Potential savings of 46 KiB
Time to Interactive can be slowed down by resources on the page. Lottohelden.de should consider lazy-loading offscreen and hidden images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://www.lottohelden.de/img/logo.cf8b4abc.svg
9051
9051
https://www.lottohelden.de/img/logo.17304717.svg
7195
7195
https://www.lottohelden.de/img/logo.70e26461.svg
4422
4422
https://www.lottohelden.de/img/logo.89de42d1.svg
4134
4134
https://www.lottohelden.de/img/logo.34e33ce9.svg
3574
3574
https://www.lottohelden.de/img/logo.5708e307.svg
3533
3533
https://www.lottohelden.de/img/logo.052537fc.svg
3265
3265
https://www.lottohelden.de/img/logo.a533c16a.svg
3152
3152
https://www.lottohelden.de/img/logo.242942f6.svg
2915
2915
https://www.lottohelden.de/img/logo.3aaae90c.svg
2780
2780
https://www.lottohelden.de/img/logo.51b01efc.svg
2693
2693
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Lottohelden.de should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Lottohelden.de should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 220 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.lottohelden.de/
216.415
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Lottohelden.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 0 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://www.lottohelden.de/js/app.76529d93.js
77
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
URL Potential Savings (Ms)
https://www.lottohelden.de/graphcms/media/resize=w:1216,h:1080/output=f:webp/quality=value:35/compress/yFqbNDTRSbOWolhPHw2D
0
Avoids enormous network payloads — Total size was 996 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.lottohelden.de/js/app.76529d93.js
484571
https://www.lottohelden.de/
165832
https://www.googletagmanager.com/gtm.js?id=GTM-MVSTVZT
54879
https://www.lottohelden.de/graphcms/media/resize=w:1216,h:1080/output=f:webp/quality=value:35/compress/yFqbNDTRSbOWolhPHw2D
35758
https://www.lottohelden.de/css/app.76147286.css
30623
https://www.lottohelden.de/graphcms/media/resize=w:1216,h:532/output=f:webp/quality=value:35/compress/90DWkUYIS4eCxY43gKcX
29506
https://www.lottohelden.de/fonts/source-sans-pro-v12-latin-regular.899c8f78.woff2
17575
https://www.lottohelden.de/fonts/source-sans-pro-v12-latin-600.c85615b2.woff2
17403
https://www.lottohelden.de/fonts/source-sans-pro-v12-latin-700.1a4bcb3e.woff2
17233
https://www.lottohelden.de/fonts/source-sans-pro-v12-latin-900.d8eab344.woff2
16785
Uses efficient cache policy on static assets — 0 resources found
Lottohelden.de can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
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. Lottohelden.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 — 3 user timings
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
https://www.lottohelden.de/
Mark
823.074
sentry-tracing-init
Mark
1548.815
app-view-mounted
Mark
2865.375
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 — 45 requests • 996 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
45
1019519
Script
4
560268
Document
1
165832
Image
29
156967
Font
5
85223
Stylesheet
3
48917
Other
3
2312
Media
0
0
Third-party
2
55332
Minimize third-party usage — Third-party code blocked the main thread for 20 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)
54879
16.804
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
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.041033653846154
0.025646033653846
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 — 11 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://www.lottohelden.de/js/styles~view-cms-mainteaser~view-home.7e470bd1.js
9052
1703
https://www.lottohelden.de/js/app.76529d93.js
7559
1343
https://www.lottohelden.de/
2846
1023
https://www.lottohelden.de/js/app.76529d93.js
7140
419
https://www.lottohelden.de/
2640
145
https://www.lottohelden.de/
4046
105
https://www.googletagmanager.com/gtm.js?id=GTM-MVSTVZT
4175
92
https://www.lottohelden.de/js/styles~view-cms-mainteaser~view-home.7e470bd1.js
10755
90
Unattributable
630
62
https://www.lottohelden.de/
2785
61
https://www.lottohelden.de/
3910
56
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
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 lottohelden.de on mobile screens.
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.

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.

Audits

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://lottohelden.de/
http/1.1
0
250.27299998328
740
0
301
text/html
https://lottohelden.de/
http/1.1
250.69899996743
403.56099978089
1119
0
301
text/html
https://www.lottohelden.de/
h2
403.95200019702
619.37699979171
165832
2066402
200
text/html
Document
https://www.lottohelden.de/css/app.76147286.css
h2
662.02799975872
807.73099977523
30623
194240
200
text/css
Stylesheet
https://www.lottohelden.de/fonts/source-sans-pro-v12-latin-900.d8eab344.woff2
h2
662.38400014117
1168.0120001547
16785
15324
200
font/woff2
Font
https://www.lottohelden.de/fonts/source-sans-pro-v12-latin-900italic.f6a4e055.woff2
h2
662.67499979585
1184.0189998038
16227
14764
200
font/woff2
Font
https://www.lottohelden.de/fonts/source-sans-pro-v12-latin-700.1a4bcb3e.woff2
h2
662.97500021756
1271.4929999784
17233
15764
200
font/woff2
Font
https://www.lottohelden.de/fonts/source-sans-pro-v12-latin-600.c85615b2.woff2
h2
663.26700011268
801.83199979365
17403
15948
200
font/woff2
Font
https://www.lottohelden.de/fonts/source-sans-pro-v12-latin-regular.899c8f78.woff2
h2
663.53400005028
1140.1129998267
17575
16112
200
font/woff2
Font
https://www.lottohelden.de/css/styles~view-home.cd0d65dc.css
h2
663.78099983558
786.78099997342
5408
18981
200
text/css
Stylesheet
https://www.lottohelden.de/graphcms/media/resize=w:1216,h:532/output=f:webp/quality=value:35/compress/90DWkUYIS4eCxY43gKcX
h2
821.86299981549
1044.9270000681
29506
27804
200
image/webp
Image
https://www.lottohelden.de/js/app.76529d93.js
h2
822.04699981958
1311.7519998923
484571
1914390
200
application/javascript
Script
https://www.lottohelden.de/js/styles~view-home.196e4f40.js
h2
822.2409998998
1332.2600000538
15007
68737
200
application/javascript
Script
https://www.googletagmanager.com/gtm.js?id=GTM-MVSTVZT
h2
822.45399989188
852.2430001758
54879
155925
200
application/javascript
Script
https://www.lottohelden.de/img/logo-regular.86d7fca3.svg
h2
1085.059999954
1112.9490002058
3095
5566
200
image/svg+xml
Image
https://www.lottohelden.de/img/account.fa683246.svg
h2
1085.5370000936
1560.5060001835
1921
1032
200
image/svg+xml
Image
https://www.lottohelden.de/img/checkout.543eabf1.svg
h2
1085.9889998101
1200.6049999036
2643
2567
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.7a6b9aa5.svg
h2
1087.67599985
1218.5280001722
3559
4664
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.5f8a9423.svg
h2
1088.4190001525
1214.2710001208
4048
5916
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.87bc1b6f.svg
h2
1109.8910002038
1228.8759998046
3963
6174
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.70e26461.svg
h2
1110.2309999987
1519.0050001256
4422
9957
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.052537fc.svg
h2
1110.6540001929
1499.9979999848
3265
7139
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.242942f6.svg
h2
1111.83599988
1232.9890001565
2915
3145
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.17304717.svg
h2
1112.3000001535
1527.77899988
7195
12298
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.3aaae90c.svg
h2
1112.7909999341
1258.4359999746
2780
3132
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.a533c16a.svg
h2
1113.485999871
1249.944999814
3152
3946
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.5708e307.svg
h2
1114.5319999196
1245.3970001079
3533
5545
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.51b01efc.svg
h2
1114.7150001489
1258.2600000314
2702
2693
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.cf8b4abc.svg
h2
1135.9310001135
1259.1019999236
9051
18847
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.34e33ce9.svg
h2
1136.4580001682
1253.2199998386
3574
6806
200
image/svg+xml
Image
https://www.lottohelden.de/img/logo.89de42d1.svg
h2
1136.6420001723
1277.6109999977
4134
6169
200
image/svg+xml
Image
https://www.lottohelden.de/img/d_w.7453962f.png
h2
1166.2929998711
1281.7029999569
7231
5776
200
image/png
Image
https://www.lottohelden.de/img/flamme.f5217674.svg
h2
1167.4640001729
1555.4249999113
2046
1126
200
image/svg+xml
Image
https://www.lottohelden.de/img/star-gold.f05588dd.svg
h2
1171.3840002194
1319.2269997671
1592
215
200
image/svg+xml
Image
https://www.lottohelden.de/img/phone.497d0cc1.svg
h2
1172.3529999144
1583.1699999981
2467
2045
200
image/svg+xml
Image
https://www.lottohelden.de/img/mail.f8ff33c3.svg
h2
1175.0659998506
1312.4649999663
1902
834
200
image/svg+xml
Image
https://www.lottohelden.de/img/help.e35f766b.svg
h2
1175.2809998579
1593.6429998837
2576
2220
200
image/svg+xml
Image
https://o1010732.ingest.sentry.io/api/6173459/envelope/?sentry_key=3da8cd75a13a433881bcbe05393406c4&sentry_version=7
h2
1562.8740000539
1613.1059997715
453
2
200
application/json
Fetch
https://www.lottohelden.de/css/styles~view-cms-mainteaser~view-home.93b1ab37.css
h2
2061.1640000716
2200.9160001762
12886
92420
200
text/css
Stylesheet
https://www.lottohelden.de/js/styles~view-cms-mainteaser~view-home.7e470bd1.js
h2
2062.8769998439
2270.843999926
5811
16682
200
application/javascript
Script
https://www.lottohelden.de/img/certificate.bc83abe0.svg
h2
2911.1919999123
3032.6629998162
1917
852
200
image/svg+xml
Image
https://www.lottohelden.de/img/payout.4ddc6b6c.svg
h2
2911.41099995
3287.9829998128
1829
672
200
image/svg+xml
Image
https://www.lottohelden.de/img/fees.b852c699.svg
h2
2911.7510002106
3095.4220001586
2209
1626
200
image/svg+xml
Image
https://www.lottohelden.de/img/award.6056c7a4.svg
h2
2912.6760000363
3040.5930001289
1982
931
200
image/svg+xml
Image
https://www.lottohelden.de/graphcms/media/resize=w:1216,h:1080/output=f:webp/quality=value:35/compress/yFqbNDTRSbOWolhPHw2D
h2
3125.2979999408
3331.1919998378
35758
34026
200
image/webp
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)
633.304
36.286
669.884
5.38
675.274
15.137
690.422
15.456
811.127
10.36
823.313
255.802
1079.133
27.922
1109.701
15.675
1132.658
24.417
1164.795
52.264
1217.545
22.932
1259.418
11.884
1272.234
11.807
1284.433
9.331
1304.934
5.049
1319.242
15.89
1336.664
5.12
1430
671.627
2133.895
5.644
2203.795
5.589
2209.768
7.714
2276.566
851.509
3128.437
11.246
3151.3
104.669
3256.003
16.5
3283.064
5.343
3309.063
44.981
3355.824
15.863
3378.024
5.027
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

First Contentful Paint — 2.9 s
The time taken for the first image or text on the page to be rendered.

Audits

First Meaningful Paint — 3.0 s
The time taken for the primary content of the page to be rendered.

Other

Reduce unused CSS — Potential savings of 39 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Lottohelden.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.lottohelden.de/css/app.76147286.css
30623
26631
https://www.lottohelden.de/css/styles~view-cms-mainteaser~view-home.93b1ab37.css
12886
12886
Avoid an excessive DOM size — 825 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
825
Maximum DOM Depth
8
21
Maximum Child Elements
14

Metrics

Time to Interactive — 10.6 s
The time taken for the page to become fully interactive.
Speed Index — 7.5 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 4,140 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).
Largest Contentful Paint — 10.0 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 1,700 ms
Users could experience a delay when interacting with the page.

Other

Reduce unused JavaScript — Potential savings of 214 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.lottohelden.de/js/app.76529d93.js
484571
190565
https://www.googletagmanager.com/gtm.js?id=GTM-MVSTVZT
54879
28214
Avoid multiple page redirects — Potential savings of 1,110 ms
Redirects can cause additional delays before the page can begin loading. Lottohelden.de should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://lottohelden.de/
630
https://lottohelden.de/
480
https://www.lottohelden.de/
0
Reduce JavaScript execution time — 6.4 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.lottohelden.de/js/styles~view-cms-mainteaser~view-home.7e470bd1.js
3734.108
2947.66
1.62
https://www.lottohelden.de/js/app.76529d93.js
3153.676
2600.032
125.632
https://www.lottohelden.de/
2176.376
119.248
399.352
Unattributable
610.236
20.532
0.728
https://www.googletagmanager.com/gtm.js?id=GTM-MVSTVZT
162.936
125.48
16.528
Minimize main-thread work — 9.9 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
5819.172
Other
1006.524
Garbage Collection
789.116
Style & Layout
755.124
Parse HTML & CSS
705.548
Script Parsing & Compilation
563.42
Rendering
299.016
First Contentful Paint (3G) — 6090 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
95

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of lottohelden.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.
`<object>` elements have alternate 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"]`
Lottohelden.de may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

Names and labels

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

Best Practices

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

Audits

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
Host allowlists can frequently be bypassed. Consider using CSP nonces or hashes instead, along with 'strict-dynamic' if necessary.
script-src
High
'unsafe-inline' allows the execution of unsafe in-page scripts and event handlers. Consider using CSP nonces or hashes to allow scripts individually.
script-src
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.
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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Preact
10
Vue
core-js
core-js-global@3.24.1; core-js-pure@3.21.1; core-js-pure@3.21.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.
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://lottohelden.de/
Allowed

Audits

Missing source maps for large first-party JavaScript
Consider deploying source maps for added benefits such as the ability to debug while in production.
URL Map URL
https://www.lottohelden.de/js/app.76529d93.js
98

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for lottohelden.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 lottohelden.de on mobile screens.
Document uses legible font sizes — 100% 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
100.00%
≥ 12px

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.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Tap targets are not sized appropriately — 82% 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.
Tap Target Size Overlapping Target
152x22
142x22
138x22
AGB
51x29
100x29

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

Server Location

Server IP Address: 104.21.40.46
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
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: 65/100
WOT Child Safety: 10/100
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 31st May, 2022
Valid To: 31st May, 2023
Subject: CN = sni.cloudflaressl.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: c959965e
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 10468066776216017732567686231450167158
Serial Number (Hex): 07E0138A20C45CFC1BE563E0AC07A776
Valid From: 31st May, 2024
Valid To: 31st May, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

Full Name:
URI:http://crl4.digicert.com/CloudflareIncECCCA-3.crl

Certificate Policies: Policy: 2.23.140.1.2.2
CPS: http://www.digicert.com/CPS

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/CloudflareIncECCCA-3.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : E8:3E:D0:DA:3E:F5:06:35:32:E7:57:28:BC:89:6B:C9:
03:D3:CB:D1:11:6B:EC:EB:69:E1:77:7D:6D:06:BD:6E
Timestamp : May 31 01:06:08.111 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:FD:99:80:14:36:58:7A:FC:29:03:EC:
6B:C9:00:33:C4:2A:00:F5:C3:C4:49:7F:9A:3E:9C:76:
3C:35:1C:45:8D:02:20:01:FA:88:0F:56:B8:E4:18:B7:
07:96:17:C1:1A:62:0E:0D:51:24:94:60:9A:F2:1A:35:
52:BB:95:FD:58:BF:A0
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 35:CF:19:1B:BF:B1:6C:57:BF:0F:AD:4C:6D:42:CB:BB:
B6:27:20:26:51:EA:3F:E1:2A:EF:A8:03:C3:3B:D6:4C
Timestamp : May 31 01:06:08.167 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:01:21:3C:41:10:5A:2A:74:96:15:44:7C:
7C:D0:8A:21:7E:F1:6B:25:39:E5:31:D8:1B:68:70:96:
AE:15:79:C6:02:20:06:4B:FF:C9:A7:23:00:43:D2:D9:
C2:1B:85:61:DC:DC:1F:FB:89:6A:29:55:32:BB:99:70:
53:F9:ED:6C:1A:F8
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
Timestamp : May 31 01:06:08.164 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:09:37:AF:CD:52:16:E1:13:B9:01:96:66:
74:18:09:8D:A0:0F:67:8B:28:2D:0E:76:59:D8:AB:A8:
80:87:1D:F2:02:21:00:F8:55:36:F0:49:D7:90:92:98:
52:A5:C2:85:FD:F9:08:EC:30:79:65:C4:04:7F:98:D5:
37:29:0A:95:FA:1C:8F
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.lottohelden.de
DNS:sni.cloudflaressl.com
DNS:lottohelden.de
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 301 Moved Permanently
Date: 8th September, 2022
Content-Type: text/html
Server: cloudflare
Connection: keep-alive
location: https://www.lottohelden.de/
set-cookie: *
x-delivered-by: fe-production1
CF-Cache-Status: DYNAMIC
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=z9%2FJclgW3xB%2Fqt2053N08ZT1DFK7fv4%2Fvq3mtobP%2F%2FfMv4CW8p%2BVGNcLVVIapAEamrXt1krCvySHIOn2zU%2BKuXcBJKCT0DpeoH%2FZ0ocRCWS7lsl0DCi0KROcrmNta93z3w%3D%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
CF-RAY: 7478624a298e8cb7-EWR
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: linda.ns.cloudflare.com
nitin.ns.cloudflare.com
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: lottohelden.de
Nserver: linda.ns.cloudflare.com
Nserver: nitin.ns.cloudflare.com
Status: connect
Changed: 2021-11-09T10:42:47+01:00

Nameservers

Name IP Address
linda.ns.cloudflare.com 172.64.32.250
nitin.ns.cloudflare.com 173.245.59.215
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Sites hosted on the same IP address

Domain Valuation Snoop Score
$10 USD 1/5