5.6 sec in total
296 ms
5 sec
363 ms
Welcome to loto.fr homepage info - get ready to check LOTO best content right away, or after learning these important things about loto.fr
Vous avez jusqu’au lundi 28 août 2023 20h15 pour jouer en ligne et tenter de remporter le Jackpot LOTO® de 9M€. LOTO®, c'est 3 Tirages par semaine minimum.
Visit loto.frWe analyzed Loto.fr page load time and found that the first response time was 296 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
loto.fr performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value26.0 s
0/100
25%
Value18.0 s
0/100
10%
Value3,990 ms
1/100
30%
Value0.003
100/100
15%
Value35.6 s
0/100
10%
296 ms
707 ms
372 ms
1541 ms
288 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Loto.fr, 65% (34 requests) were made to Media.fdj.fr and 33% (17 requests) were made to Fdj.fr. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Media.fdj.fr.
Page size can be reduced by 882.7 kB (54%)
1.6 MB
756.7 kB
In fact, the total size of Loto.fr main page is 1.6 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. 40% of websites need less resources to load. Javascripts take 851.8 kB which makes up the majority of the site volume.
Potential reduce by 123.5 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 123.5 kB or 83% of the original size.
Potential reduce by 25.2 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. LOTO images are well optimized though.
Potential reduce by 627.9 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 627.9 kB or 74% of the original size.
Potential reduce by 106.0 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. Loto.fr needs all CSS files to be minified and compressed as it can save up to 106.0 kB or 74% of the original size.
Number of requests can be reduced by 16 (34%)
47
31
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LOTO. 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.
loto.fr
296 ms
loto
707 ms
CSS_MINIFY_WEBAPP_15870960418.css
372 ms
JS_MINIFY_DEFAULT_72883850530.js
1541 ms
widget.min.js
288 ms
fdjOfferFull.js
297 ms
hasard_header_auth_logo_11391-1434718849.png
1213 ms
hasard_header_logo_12021-1434718955.png
1215 ms
image_new_161296-1457967682.png
1216 ms
image_new_161169-1456392106.png
1219 ms
image_new_161057-1455720052.png
1219 ms
image_new_160799-1454320094.png
1215 ms
webapp_header_12696-1453200300.jpg
1305 ms
dm_1351072024_loto-tableau-multiple-V3.png
1589 ms
dm_1350913339_CompteDOUBLE-V2.png
1496 ms
dm_1350913259_DUO-V2.png
1495 ms
dm_1350913251_DoubleCHANCE-V2.png
1404 ms
dm_1452080378_historique_loto_new.png
1310 ms
dm_1452080378_historique_loto_old.png
1398 ms
dm_1452080378_historique_superloto_new.png
1404 ms
dm_1452080378_historique_superloto_old.png
1491 ms
imb_footer_11409-1434719274.png
1496 ms
imb_footer_11407-1434719287.png
1498 ms
imb_footer_11408-1434719262.png
1586 ms
imb_footer_14583-1456760878.png
1587 ms
footer_permabarre_11027-1436444106.png
1588 ms
footer_permabarre_on_11027-1436442988.png
1590 ms
footer_permabarre_11028-1436444074.png
1592 ms
footer_permabarre_on_11028-1436443016.png
1679 ms
footer_permabarre_11029-1436444012.png
1680 ms
footer_permabarre_on_11029-1436443031.png
1681 ms
footer_permabarre_11030-1436443937.jpg
1682 ms
footer_permabarre_on_11030-1436443044.jpg
1683 ms
footer_permabarre_11031-1436443888.jpg
1685 ms
footer_permabarre_on_11031-1436443110.jpg
1772 ms
footer_permabarre_11032-1436443813.jpg
1773 ms
footer_permabarre_on_11032-1436443129.jpg
1773 ms
footer_permabarre_11033-1436443755.jpg
1774 ms
footer_permabarre_on_11033-1436443145.jpg
1776 ms
footer_permabarre_11035-1434718679.png
1777 ms
dm_1427205512_ubuntu-regular.woff
1060 ms
dm_1427205512_ubuntu-medium.woff
1059 ms
dm_1427205512_ubuntu-bold.woff
1060 ms
dm_1392299972_jeux.png
1183 ms
fdjAuthenticationWidget.js
967 ms
fdjAuthentication.css
108 ms
require.js
107 ms
require_all.js
95 ms
angular_1.3.0.min.js
283 ms
angular-sanitize.min.js
96 ms
angular-route.min.js
96 ms
fdjAuthenticationDirective.js
286 ms
loto.fr accessibility score
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
Image elements do not have [alt] attributes
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.
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.
loto.fr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
loto.fr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
FR
N/A
ISO-8859-15
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Loto.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Loto.fr main page’s claimed encoding is iso-8859-15. 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.
loto.fr
Open Graph description is not detected on the main page of LOTO. 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: