6.9 sec in total
1 sec
5.7 sec
184 ms
Welcome to mylotto.co.nz homepage info - get ready to check My Lotto best content for New Zealand right away, or after learning these important things about mylotto.co.nz
Visit mylotto.co.nzWe analyzed Mylotto.co.nz page load time and found that the first response time was 1 sec and then it took 5.9 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.co.nz performance score
name
value
score
weighting
Value7.7 s
0/100
10%
Value23.9 s
0/100
25%
Value19.7 s
0/100
10%
Value3,240 ms
2/100
30%
Value0.764
5/100
15%
Value24.4 s
0/100
10%
1037 ms
606 ms
584 ms
585 ms
593 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 72% of them (42 requests) were addressed to the original Mylotto.co.nz, 12% (7 requests) were made to Pixel.mathtag.com and 3% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Mylotto.co.nz.
Page size can be reduced by 894.1 kB (43%)
2.1 MB
1.2 MB
In fact, the total size of Mylotto.co.nz main page is 2.1 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. Images take 941.0 kB which makes up the majority of the site volume.
Potential reduce by 24.1 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 4.1 kB, which is 13% 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 24.1 kB or 78% of the original size.
Potential reduce by 93.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. My Lotto images are well optimized though.
Potential reduce by 611.7 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 611.7 kB or 67% of the original size.
Potential reduce by 165.1 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.co.nz needs all CSS files to be minified and compressed as it can save up to 165.1 kB or 84% of the original size.
Number of requests can be reduced by 30 (54%)
56
26
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My 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 14 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
mylotto.co.nz
1037 ms
layout.css
606 ms
layout_accountpanel.css
584 ms
layout_accountpanel_user_menu.css
585 ms
layout_accountpanel_myfavourites_menu.css
593 ms
typography.css
603 ms
form.css
608 ms
claim-secondchance.css
774 ms
jquery.jscrollpane.css
775 ms
footer-pages.css
788 ms
prospectHomePage.css
803 ms
game.css
803 ms
game-lotto.css
1209 ms
jquery-1.4.2.min.js
1350 ms
jquery.entwine-dist.js
1198 ms
sitejs.js
1375 ms
custom-select.js
1001 ms
accountSetupDialog.js
1001 ms
homepage.js
1202 ms
prospecthomepage.js
1204 ms
header_logo.png
1589 ms
home-tooltip.png
1440 ms
results-panel-lotto-logo.png
231 ms
results-panel-bonus-logo.png
232 ms
results-panel-powerball-logo.png
336 ms
results-panel-strike-logo.png
377 ms
results-ball-shadow.png
396 ms
ball-shine.png
404 ms
unavailable-panel-bg.png
404 ms
SetWidth996-7.5M.jpg
910 ms
dailyGames.png
772 ms
Keno-double-newsize.png
2778 ms
135K.png
1035 ms
ProximaNova-Reg-webfont.woff
827 ms
ProximaNova-Bold-webfont.woff
791 ms
ga.js
69 ms
gtm.js
109 ms
body-bg.png
1333 ms
menu-sprite.png
1389 ms
play-responsibly.png
819 ms
footer-signup-btn.png
877 ms
social-logos.png
1012 ms
ajax-loader-black.gif
1021 ms
__utm.gif
16 ms
collect
66 ms
buttons.png
996 ms
2343581365.js
324 ms
activityi;src=3741270;type=mylot308;cat=mylot403;ord=6546595167904;~oref=https%3A%2F%2Fmylotto.co.nz%2F
62 ms
js
34 ms
i.js
77 ms
js
46 ms
img
15 ms
iframe
25 ms
img
14 ms
img
36 ms
pixel
38 ms
img
79 ms
inspectlet.js
36 ms
mylotto.co.nz accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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>).
mylotto.co.nz 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
mylotto.co.nz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mylotto.co.nz can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Mylotto.co.nz 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.
mylotto.co.nz
Open Graph description is not detected on the main page of My 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: