Tools & Wizards About Us
mobile.playhugelottos.com screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    70% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

Page Load Speed

2.1 sec in total

First Response

225 ms

Resources Loaded

1.7 sec

Page Rendered

143 ms

mobile.playhugelottos.com screenshot

About Website

Click here to check amazing Mobile Playhugelottos content for Canada. Otherwise, check out these important facts you probably never knew about mobile.playhugelottos.com

Visit mobile.playhugelottos.com

Key Findings

We analyzed Mobile.playhugelottos.com page load time and found that the first response time was 225 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

mobile.playhugelottos.com performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.156

74/100

15%

TTI (Time to Interactive)

Value6.1 s

63/100

10%

Network Requests Diagram

mobile.playhugelottos.com

225 ms

mobile.playhugelottos.com

730 ms

mobile_device.css

74 ms

jquery.fancybox.css

141 ms

jquery.min.js

268 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 85% of them (55 requests) were addressed to the original Mobile.playhugelottos.com, 6% (4 requests) were made to Google-analytics.com and 5% (3 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (730 ms) belongs to the original domain Mobile.playhugelottos.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 367.9 kB (68%)

Content Size

544.1 kB

After Optimization

176.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mobile.playhugelottos.com main page is 544.1 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. Javascripts take 422.7 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 45.2 kB

  • Original 50.9 kB
  • After minification 32.0 kB
  • After compression 5.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 19.0 kB, which is 37% 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 45.2 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 8 B

  • Original 3.6 kB
  • After minification 3.6 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. Mobile Playhugelottos images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 265.7 kB

  • Original 422.7 kB
  • After minification 396.3 kB
  • After compression 157.0 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 265.7 kB or 63% of the original size.

CSS Optimization

-85%

Potential reduce by 56.9 kB

  • Original 66.8 kB
  • After minification 47.8 kB
  • After compression 9.9 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. Mobile.playhugelottos.com needs all CSS files to be minified and compressed as it can save up to 56.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (66%)

Requests Now

62

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mobile.playhugelottos.com

mobile.playhugelottos.com

225 ms

mobile.playhugelottos.com

mobile.playhugelottos.com

730 ms

mobile_device.css

mobile_device.css

74 ms

jquery.fancybox.css

jquery.fancybox.css

141 ms

jquery.min.js

jquery.min.js

268 ms

jquery.simplemodal.js

jquery.simplemodal.js

193 ms

jquery.mousewheel-3.0.6.pack.js

jquery.mousewheel-3.0.6.pack.js

211 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

210 ms

prototype.js

prototype.js

300 ms

globalinit.js

globalinit.js

211 ms

jquery.common.js

jquery.common.js

256 ms

jquery.easing.js

jquery.easing.js

299 ms

jquery.plugin.js

jquery.plugin.js

300 ms

jquery.countdown.js

jquery.countdown.js

300 ms

ball_select_new.js

ball_select_new.js

334 ms

jquery.scrollTo.js

jquery.scrollTo.js

349 ms

jquery.dimensions.js

jquery.dimensions.js

355 ms

CustomEasySlider.js

CustomEasySlider.js

355 ms

carousel.js

carousel.js

353 ms

jquery.cookie.js

jquery.cookie.js

353 ms

moment.min.js

moment.min.js

393 ms

basket.js

basket.js

428 ms

jquery.json-2.2.min.js

jquery.json-2.2.min.js

432 ms

jquery.popup_window.js

jquery.popup_window.js

431 ms

chat_popup.js

chat_popup.js

431 ms

snap.js

snap.js

430 ms

right.png

right.png

183 ms

ru.png

ru.png

206 ms

pl.png

pl.png

214 ms

sv.png

sv.png

211 ms

pt.png

pt.png

212 ms

de.png

de.png

212 ms

cz.png

cz.png

246 ms

ro.png

ro.png

269 ms

es.png

es.png

279 ms

fr.png

fr.png

278 ms

hu.png

hu.png

280 ms

en.svg

en.svg

282 ms

super_ena_max_logo.svg

super_ena_max_logo.svg

311 ms

usa_powerball_logo.svg

usa_powerball_logo.svg

332 ms

euro_jackpot_logo.svg

euro_jackpot_logo.svg

346 ms

super_ena_lotto_logo.svg

super_ena_lotto_logo.svg

361 ms

uk_lottery_logo.svg

uk_lottery_logo.svg

356 ms

oz_lotto_logo.svg

oz_lotto_logo.svg

365 ms

usa_mega_millions_logo.svg

usa_mega_millions_logo.svg

374 ms

la_primitiva_logo.svg

la_primitiva_logo.svg

389 ms

oz_powerball_logo.svg

oz_powerball_logo.svg

403 ms

euro_millions_logo.svg

euro_millions_logo.svg

406 ms

german_lotto_logo.svg

german_lotto_logo.svg

409 ms

super_lotto_plus_logo.svg

super_lotto_plus_logo.svg

410 ms

gtm.js

gtm.js

73 ms

ga.js

ga.js

38 ms

analytics.js

analytics.js

84 ms

el_gordo_logo.svg

el_gordo_logo.svg

394 ms

france_loto_logo.svg

france_loto_logo.svg

401 ms

mega_sena_logo.svg

mega_sena_logo.svg

414 ms

loteria_nacional_extra_logo.svg

loteria_nacional_extra_logo.svg

417 ms

open.png

open.png

417 ms

__utm.gif

__utm.gif

15 ms

analytics_debug.js

analytics_debug.js

58 ms

collect

collect

75 ms

collect

collect

36 ms

collect

collect

37 ms

collect

collect

60 ms

collect

collect

62 ms

Accessibility Review

mobile.playhugelottos.com accessibility score

65

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Links do not have a discernible name

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

mobile.playhugelottos.com best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

mobile.playhugelottos.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document doesn't use legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobile.playhugelottos.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Mobile.playhugelottos.com 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

mobile.playhugelottos.com

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