Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 42

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

lotto.be

Lotto - Loterie Nationale Loterij - Website

Page Load Speed

3.7 sec in total

First Response

298 ms

Resources Loaded

3.2 sec

Page Rendered

163 ms

lotto.be screenshot

About Website

Click here to check amazing Lotto content for Belgium. Otherwise, check out these important facts you probably never knew about lotto.be

Tout sur Lotto : résultats, jeu en ligne, montants des gains et plus encore ! Alles over Lotto: resultaten, online spelen, winstbedragen en meer!

Visit lotto.be

Key Findings

We analyzed Lotto.be page load time and found that the first response time was 298 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

lotto.be performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value11.5 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value1,600 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.9 s

17/100

10%

Network Requests Diagram

lotto.be

298 ms

language

142 ms

core.css

515 ms

corporate.css

702 ms

jquery-1.11.0.min.js

81 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 14% of them (3 requests) were addressed to the original Lotto.be, 52% (11 requests) were made to Nlotstaticfilesprod01.blob.core.windows.net and 14% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Nlotstaticfilesprod01.blob.core.windows.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 315.5 kB (52%)

Content Size

610.7 kB

After Optimization

295.1 kB

In fact, the total size of Lotto.be main page is 610.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. CSS take 346.3 kB which makes up the majority of the site volume.

HTML Optimization

-56%

Potential reduce by 4.8 kB

  • Original 8.7 kB
  • After minification 8.3 kB
  • After compression 3.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. 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 4.8 kB or 56% of the original size.

Image Optimization

-3%

Potential reduce by 3.4 kB

  • Original 131.9 kB
  • After minification 128.5 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 images are well optimized though.

JavaScript Optimization

-34%

Potential reduce by 42.3 kB

  • Original 123.8 kB
  • After minification 121.6 kB
  • After compression 81.4 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 42.3 kB or 34% of the original size.

CSS Optimization

-77%

Potential reduce by 264.9 kB

  • Original 346.3 kB
  • After minification 345.9 kB
  • After compression 81.3 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.be needs all CSS files to be minified and compressed as it can save up to 264.9 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (50%)

Requests Now

12

After Optimization

6

The browser has sent 12 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lotto. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

lotto.be accessibility score

42

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Image elements do not have [alt] attributes

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

lotto.be best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

lotto.be SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lotto.be can be misinterpreted by Google and other search engines. Our service has detected that English 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 Lotto.be 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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Lotto. 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: