7.1 sec in total
421 ms
5.7 sec
1 sec
Visit lotterien.at now to see the best up-to-date Lotterien content for Austria and also check out these interesting facts you probably never knew about lotterien.at
Entdecke die Welt der Österreichischen Lotterien ➜ offizielle Website ✓ alle Lotteriespiele ✓ Ziehungen ✓ Gewinnabfragen ✓ u.v.m.
Visit lotterien.atWe analyzed Lotterien.at page load time and found that the first response time was 421 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
lotterien.at performance score
name
value
score
weighting
Value2.6 s
64/100
10%
Value14.2 s
0/100
25%
Value9.5 s
12/100
10%
Value2,030 ms
7/100
30%
Value0.008
100/100
15%
Value20.4 s
2/100
10%
421 ms
698 ms
20 ms
302 ms
817 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 93% of them (100 requests) were addressed to the original Lotterien.at, 3% (3 requests) were made to App.usercentrics.eu and 3% (3 requests) were made to Api.usercentrics.eu. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Lotterien.at.
Page size can be reduced by 1.2 MB (37%)
3.2 MB
2.0 MB
In fact, the total size of Lotterien.at main page is 3.2 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. 60% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 116.9 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 37.4 kB, which is 27% 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 116.9 kB or 86% of the original size.
Potential reduce by 1.1 MB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, Lotterien needs image optimization as it can save up to 1.1 MB or 38% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 0 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 9 (31%)
29
20
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lotterien. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
lotterien.at
421 ms
www.lotterien.at
698 ms
common.js
20 ms
common.js
302 ms
lotterien.min.css
817 ms
modernizr.min.js
316 ms
loader.js
23 ms
vendor.min.js
715 ms
lotterien.min.js
1053 ms
common.js
366 ms
@http-reporting
1281 ms
@http-reporting
1278 ms
piwik.js
277 ms
cor1kj.js
668 ms
@http-reporting
1420 ms
@http-reporting
1436 ms
@http-reporting
1435 ms
@http-reporting
1545 ms
general@2x.13.png
1066 ms
logo-print.jpg
455 ms
csm_headerbild-lotterien-app-test_NEW_076850356b.jpg
753 ms
lotto.svg
698 ms
loader-small.gif
1066 ms
games@2x.13.png
1310 ms
euromillionen.svg
510 ms
Rubbellos-Gipfelstuermer-632x265.jpg
753 ms
klassenlotterie-632x265.jpg
1176 ms
glueckspost-632x265.jpg
1595 ms
Lotterien-Stories-lotterien.at.jpg
1249 ms
bundle_legacy.js
68 ms
@http-reporting
1493 ms
@http-reporting
1550 ms
playsponsible-logo.svg
1543 ms
St100100-Rg.woff
1546 ms
St100100-Bd.woff
1676 ms
St100100-Blk.woff2
1610 ms
St100100-BlkIt.woff
1611 ms
fa-solid-900.woff
1808 ms
fa-regular-400.woff
1587 ms
fa-brands-400.woff
1808 ms
piwik.php
1675 ms
@http-reporting
1541 ms
@http-reporting
1561 ms
@http-reporting
1617 ms
languages.json
130 ms
de.json
115 ms
1px.png
77 ms
translations-de.json
71 ms
@http-reporting
691 ms
@http-reporting
731 ms
@http-reporting
731 ms
@http-reporting
730 ms
@http-reporting
974 ms
@http-reporting
777 ms
@http-reporting
875 ms
@http-reporting
854 ms
@http-reporting
855 ms
@http-reporting
853 ms
@http-reporting
901 ms
@http-reporting
1002 ms
@http-reporting
1054 ms
uct
218 ms
@http-reporting
977 ms
@http-reporting
975 ms
@http-reporting
975 ms
@http-reporting
1216 ms
@http-reporting
1119 ms
@http-reporting
1167 ms
@http-reporting
1168 ms
@http-reporting
1166 ms
@http-reporting
1167 ms
@http-reporting
1297 ms
@http-reporting
1335 ms
@http-reporting
1320 ms
@http-reporting
1331 ms
@http-reporting
1323 ms
@http-reporting
1389 ms
@http-reporting
1454 ms
@http-reporting
1495 ms
@http-reporting
1504 ms
@http-reporting
1501 ms
@http-reporting
1487 ms
@http-reporting
1545 ms
@http-reporting
1626 ms
@http-reporting
1659 ms
@http-reporting
1657 ms
@http-reporting
1660 ms
@http-reporting
1663 ms
@http-reporting
1718 ms
@http-reporting
1785 ms
@http-reporting
1809 ms
@http-reporting
1818 ms
@http-reporting
1832 ms
@http-reporting
1831 ms
@http-reporting
1875 ms
@http-reporting
1946 ms
@http-reporting
1939 ms
@http-reporting
1984 ms
@http-reporting
1986 ms
@http-reporting
1985 ms
@http-reporting
2051 ms
@http-reporting
2105 ms
@http-reporting
2145 ms
@http-reporting
2143 ms
@http-reporting
2150 ms
@http-reporting
2151 ms
@http-reporting
2208 ms
print.min.css
1844 ms
lotterien.at 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-hidden="true"] elements contain focusable descendents
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
<frame> or <iframe> elements do not have a title
lotterien.at 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
lotterien.at 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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lotterien.at 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 Lotterien.at main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
lotterien.at
Open Graph description is not detected on the main page of Lotterien. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: