5.8 sec in total
198 ms
4.9 sec
703 ms
Welcome to mylotto.ws homepage info - get ready to check Mylotto best content right away, or after learning these important things about mylotto.ws
Forsale Lander
Visit mylotto.wsWe analyzed Mylotto.ws page load time and found that the first response time was 198 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
mylotto.ws performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value32.4 s
0/100
25%
Value14.1 s
1/100
10%
Value7,850 ms
0/100
30%
Value0
100/100
15%
Value35.6 s
0/100
10%
198 ms
382 ms
380 ms
174 ms
188 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Mylotto.ws, 17% (15 requests) were made to S2.thelotter.com and 8% (7 requests) were made to Thelotter.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Sso.thelotter.com.
Page size can be reduced by 1.1 MB (54%)
2.0 MB
929.9 kB
In fact, the total size of Mylotto.ws main page is 2.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 956.4 kB which makes up the majority of the site volume.
Potential reduce by 206.7 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 29.4 kB, which is 12% 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 206.7 kB or 87% of the original size.
Potential reduce by 21.3 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. Mylotto images are well optimized though.
Potential reduce by 683.1 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 683.1 kB or 71% of the original size.
Potential reduce by 202.6 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. Mylotto.ws needs all CSS files to be minified and compressed as it can save up to 202.6 kB or 83% of the original size.
Number of requests can be reduced by 31 (39%)
80
49
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mylotto. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
Default.aspx
198 ms
Default.aspx
382 ms
www.thelotter.com
380 ms
css.axd
174 ms
css.axd
188 ms
css.axd
181 ms
css.axd
151 ms
jquery.min.js
24 ms
jslib.axd
152 ms
jslib.axd
180 ms
angular.min.js
59 ms
angular-animate.min.js
62 ms
jslib.axd
238 ms
WebResource.axd
161 ms
ScriptResource.axd
353 ms
hotjar-32416.js
147 ms
dm.tlo
289 ms
dm.tlo
289 ms
header.png
291 ms
dm.tlo
290 ms
dm.tlo
296 ms
dm.tlo
291 ms
dm.tlo
290 ms
dm.tlo
293 ms
dm.tlo
300 ms
dm.tlo
301 ms
dm.tlo
364 ms
footer.png
392 ms
header.png
228 ms
header.png
220 ms
header.png
220 ms
vpOHcNI3jos
847 ms
modules-043c1e6abe660c48857202e419ff9d8a.js
166 ms
dm.tlo
244 ms
dm.tlo
240 ms
footer.png
906 ms
fbevents.js
140 ms
aef05e22-e1d4-4e59-bc2e-a71c13c26cca.woff
878 ms
analytics.js
167 ms
GetMenuItemsData
816 ms
templates.html
113 ms
templates.html
77 ms
templates.html
69 ms
tag.js
788 ms
979 ms
collect
701 ms
www-embed-player-vflfNyN_r.css
721 ms
www-embed-player.js
743 ms
base.js
795 ms
signinsignup.aspx
1584 ms
gethomepageelementsmodel
959 ms
dm.tlo
146 ms
dm.tlo
120 ms
elements.png
119 ms
loader_red.gif
119 ms
dm.tlo
143 ms
sprite01.png
935 ms
sprite03.png
940 ms
sprite04.png
944 ms
33bb86d1-8adf-454e-aee3-ca1c89445476.woff
171 ms
.jsonp
254 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
99 ms
ad_status.js
144 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
109 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
102 ms
mTag.js
613 ms
ourWinnersSprite.png
177 ms
dm.tlo
57 ms
tlfrm.tlp
559 ms
visit-data
260 ms
225 ms
224 ms
css.axd
69 ms
jslib.axd
30 ms
jslib.axd
26 ms
jslib.axd
65 ms
templates.html
27 ms
getauthenticationmodelsignin
193 ms
27 ms
reponline.gif
46 ms
31 ms
28 ms
dm.tlo
359 ms
dm.tlo
370 ms
dm.tlo
595 ms
dm.tlo
371 ms
lg.php
133 ms
mylotto.ws 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
button, link, and menuitem elements do not have accessible names.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
mylotto.ws best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the notification permission on page load
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
mylotto.ws 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
EN
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mylotto.ws 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 Mylotto.ws main page’s claimed encoding is . 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.
mylotto.ws
Open Graph description is not detected on the main page of Mylotto. 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: