6.6 sec in total
355 ms
5.6 sec
606 ms
Welcome to lotto-berlin.de homepage info - get ready to check LOTTO Berlin best content for Germany right away, or after learning these important things about lotto-berlin.de
Bei uns können Sie LOTTO 6aus49, Eurojackpot, KENO und GlücksSpirale staatlich und sicher spielen - online oder in unseren rd. 1.000 Annahmestellen.
Visit lotto-berlin.deWe analyzed Lotto-berlin.de page load time and found that the first response time was 355 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
lotto-berlin.de performance score
name
value
score
weighting
Value15.9 s
0/100
10%
Value18.2 s
0/100
25%
Value18.4 s
0/100
10%
Value400 ms
68/100
30%
Value0.004
100/100
15%
Value29.9 s
0/100
10%
355 ms
1558 ms
321 ms
482 ms
769 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 90% of them (47 requests) were addressed to the original Lotto-berlin.de, 4% (2 requests) were made to Code.etracker.com and 2% (1 request) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Lotto-berlin.de.
Page size can be reduced by 1.9 MB (55%)
3.5 MB
1.6 MB
In fact, the total size of Lotto-berlin.de main page is 3.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Javascripts take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 436.8 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 229.7 kB, which is 49% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 436.8 kB or 93% of the original size.
Potential reduce by 20.4 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. LOTTO Berlin images are well optimized though.
Potential reduce by 1.5 MB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.5 MB or 77% of the original size.
Potential reduce by 8.9 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Lotto-berlin.de has all CSS files already compressed.
Number of requests can be reduced by 19 (40%)
47
28
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LOTTO Berlin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
lotto-berlin.de
355 ms
www.lotto-berlin.de
1558 ms
321 ms
external.min__6-11-4_20240418134618.css
482 ms
main.min__6-11-4_20240418134618.css
769 ms
jquery.min__5a70534bc497341aeb484139310e927e.js
647 ms
external.min__51dd919d32dbb900797b0adcd475e0cd.js
1290 ms
main.min__8025a1d23dd739444856858cb10f980f.js
3075 ms
broprint.bundle.min.js
594 ms
engine.js
717 ms
util.js
839 ms
widget.min.js
16 ms
InfoController.js
839 ms
moin-loader.js
467 ms
e.js
535 ms
ShoppingBasketController.js
674 ms
TicketManagementController.js
688 ms
GameResultController.js
421 ms
__System.generateId.dwr
821 ms
map.svg
820 ms
dklb_192x192.png
126 ms
t.js
120 ms
PTSans-Regular.woff
787 ms
PTSans-Bold.woff
786 ms
lotto_272x338.jpg
154 ms
www.lotto-berlin.de
1026 ms
_menue-teaser_272x307_n01.jpg
752 ms
icon_arrow_dropdown.png
728 ms
keno2_272x307.jpg
729 ms
glucksspirale_272x307.jpg
730 ms
toto_272x307__1_.jpg
731 ms
OpenSans-Bold.woff
732 ms
240502_hochgewinn_ejp_buehne.jpg
858 ms
231116_trainer_ui_lotto.jpg
678 ms
mannertag_280x180.jpg
621 ms
x50_280x180.jpg
653 ms
valtentins-mutter-frauentag.jpg
653 ms
herzlich_willkommen_280x180.png
653 ms
231114_app_halber_teaser_575x250.jpg
653 ms
231121_newsletter_gelbholz_578x250.jpg
655 ms
kundenservice_585x500.jpg
656 ms
231216_website_kundenkarte_575x250px.jpg
657 ms
gewinnprufung__2_.jpg
784 ms
230704_astagneau1_teaser4.jpg
785 ms
map.svg
1149 ms
InfoController.setDisplayResolution.dwr
538 ms
ajax-loader.gif
176 ms
116 ms
cntcc
566 ms
08015198b4ab2000869687011c1e46e8ef74b964d0bfd854d407c6f0003f8d194f6a74e100bf3ffa
113 ms
08015198b4ab2000869687011c1e46e8ef74b964d0bfd854d407c6f0003f8d194f6a74e100bf3ffa
113 ms
print.min__6-11-4_20240418134618.css
121 ms
lotto-berlin.de accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
lotto-berlin.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
lotto-berlin.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
DE
DE
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lotto-berlin.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Lotto-berlin.de main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
lotto-berlin.de
Open Graph data is detected on the main page of LOTTO Berlin. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: