Performance: Performance Accessibility Best Practices SEO Progressive Web App

7/20/2021
https://www.lotteryusa.com/florida/
54 88 67 93
54 88 67 93
Performance Accessibility Best SEO Progressive

Practices Web App
0–49 50–89 90–100
54
Performance
Metrics
First Contentful Paint 1.7 s Time to Interactive 23.9 s

First Contentful Paint marks the time at Time to interactive is the amount of time it
which the first text or image is painted. takes for the page to become fully interactive.
Learn more. Learn more.
Speed Index 5.4 s Total Blocking Time 1,960 ms

Speed Index shows how quickly the Sum of all time periods between FCP and
contents of a page are visibly populated. Time to Interactive, when task length
Learn more. exceeded 50ms, expressed in milliseconds.
Learn more.
Largest Contentful Paint 1.7 s Cumulative Layout Shift 0.001

Largest Contentful Paint marks the time at Cumulative Layout Shift measures the
which the largest text or image is painted. movement of visible elements within the
Learn more viewport. Learn more.
Values are estimated and may vary. The performance score is calculated directly from these metrics. See calculator.
View Original Trace
1/49
7/20/2021
Opportunities — These suggestions can help your page load faster. They don't directly affect the Performance score.
Opportunity Estimated Savings
Remove unused JavaScript 3.71 s
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.

Show 3rd-party resources (14)
Transfer Potential
URL
Size Savings
/build/vendors.bce9a98c.js (www.lotteryusa.com) 180.8 KiB 133.8 KiB
/core/prebid-analytics-4.40.5.js (a.pub.network) 151.2 KiB 89.7 KiB
…sdkloader/ima3.js (imasdk.googleapis.com) 116.9 KiB 70.8 KiB
/gpt/pubads_impl_202….js?31061848 (securepubads.g.doubleclick.net) 114.7 KiB 65.8 KiB
…pubfig/pubfig.engine.4.13.0.98e43e4….js (a.pub.network) 118.3 KiB 57.5 KiB
…r20190131/show_ads_….js?bust=exp%3D31061746 (pagead2.googlesyndication.com) 90.3 KiB 52.5 KiB
…r20190131/reactive_library_fy2019.js (pagead2.googlesyndication.com) 51.7 KiB 42.2 KiB
/production/vpaid_df75f8b2.js (vpaid.springserve.com) 100.4 KiB 39.6 KiB
…2794/pwt.js (ads.pubmatic.com) 60.1 KiB 35.7 KiB
…playerJS/frstrOSm_2.js (cdn.springserve.com) 91.7 KiB 34.2 KiB
/gtag/js?id=G-R1BKHNRFE9&l=dataLayer&cx=c (www.googletagmanager.com) 49.5 KiB 23.6 KiB
…ld/publishertag.prebid.js (static.criteo.net) 26.7 KiB 22.5 KiB
…js/adsbygoogle.js (pagead2.googlesyndication.com) 47.4 KiB 22.2 KiB
…pubfig/pubfig.messaging.2.1.8.26fd503….js (a.pub.network) 55.1 KiB 22.0 KiB
/gtag/js?id=UA-2571454-1 (www.googletagmanager.com) 39.7 KiB 20.1 KiB
Eliminate render-blocking resources 0.76 s
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical
JS/styles. Learn more.

Transfer Potential
URL
Size Savings
/css?family=… (fonts.googleapis.com) 0.6 KiB 790 ms
2/49
7/20/2021
Remove unused CSS 0.15 s
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce
unnecessary bytes consumed by network activity. Learn more.

Transfer Potential
URL
Size Savings
/build/main.22eb6eb3.css (www.lotteryusa.com) 24.6 KiB 20.4 KiB
.orp-light-player-wrapper { position: relative; width: 100%; height: 100%; background:

#000; ... } ... 11.7 KiB 11.7 KiB
Diagnostics — More information about the performance of your application. These numbers don't directly affect the
Performance score.
Reduce the impact of third-party code

— Third-party code blocked the main thread for 1,660 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to
load third-party code after your page has primarily finished loading. Learn more.

Transfer Main-Thread Blocking

Third-Party
Size Time
Google/Doubleclick Ads 544 KiB 1,337 ms
/gpt/pubads_impl_202….js?31061848 (securepubads.g.doubleclick.net) 115 KiB 1,258 ms

…r20190131/show_ads_….js?
90 KiB 42 ms
bust=exp%3D31061746 (pagead2.googlesyndication.com)
…js/adsbygoogle.js (pagead2.googlesyndication.com) 47 KiB 16 ms
…r20190131/reactive_library_fy2019.js (pagead2.googlesyndication.com) 52 KiB 11 ms
…current/osd.js (www.googletagservices.com) 27 KiB 10 ms
Other resources 212 KiB 0 ms
SpringServer 194 KiB 226 ms
…playerJS/frstrOSm_2.js (cdn.springserve.com) 92 KiB 136 ms

/production/vpaid_df75f8b2.js (vpaid.springserve.com) 100 KiB 89 ms
Pubmatic 60 KiB 55 ms
…2794/pwt.js (ads.pubmatic.com) 60 KiB 55 ms
Google Tag Manager 89 KiB 35 ms
/gtag/js?id=G-R1BKHNRFE9&l=dataLayer&cx=c (www.googletagmanager.com) 49 KiB 35 ms

/gtag/js?id=UA-2571454-1 (www.googletagmanager.com) 40 KiB 0 ms
Other Google APIs/SDKs 323 KiB 2 ms
…sdkloader/vpaid_adapter.js?adtagurl=… (imasdk.googleapis.com) 16 KiB 2 ms

…core/bridge3.472.0_en.html (imasdk.googleapis.com) 190 KiB 0 ms
…sdkloader/ima3.js (imasdk.googleapis.com) 117 KiB 0 ms
3/49
7/20/2021
Transfer Main-Thread Blocking

Third-Party
Size Time
Google Analytics 19 KiB 2 ms
/analytics.js (www.google-analytics.com) 19 KiB 2 ms
Google Fonts 50 KiB 0 ms
…v6/rP2Fp2ywx….woff2 (fonts.gstatic.com) 13 KiB 0 ms

…v6/rP2Cp2ywx….woff2 (fonts.gstatic.com) 12 KiB 0 ms
…v6/rP2Hp2ywx….woff2 (fonts.gstatic.com) 12 KiB 0 ms
…v6/rP2Cp2ywx….woff2 (fonts.gstatic.com) 12 KiB 0 ms
Amazon Ads 37 KiB 0 ms
/aax2/apstag.js (c.amazon-adsystem.com) 33 KiB 0 ms

Other resources 5 KiB 0 ms
Criteo 28 KiB 0 ms
…ld/publishertag.prebid.js (static.criteo.net) 27 KiB 0 ms
Yahoo! 18 KiB 0 ms
/bidRequest?dcn=… (c2shb.ssp.yahoo.com) 6 KiB 0 ms

Rubicon Project 15 KiB 0 ms
Google CDN 11 KiB 0 ms
/mysidia/4661e2b….js?
11 KiB 0 ms
tag=mysidia_one_click_handler_one_afma_2019 (www.gstatic.com)
Quantcast 10 KiB 0 ms
/quant.js (secure.quantserve.com) 9 KiB 0 ms
sovrn 5 KiB 0 ms
/rtb/bid?src=prebid_prebid_4.40.0 (ap.lijit.com) 5 KiB 0 ms
Sharethrough 4 KiB 0 ms
AppNexus 3 KiB 0 ms
Scorecard Research 2 KiB 0 ms
Index Exchange 2 KiB 0 ms
Bidswitch 2 KiB 0 ms
OpenX 1 KiB 0 ms
Dataxu 1 KiB 0 ms
TripleLift 1 KiB 0 ms
Yieldmo 0 KiB 0 ms
Avoid document.write()
4/49
7/20/2021
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of
seconds. Learn more.

Source
zrt_lookup.html:18
zrt_lookup.html:20
frstrOSm_2.js:4
vpaid_df75f8b2.js:1
Image elements do not have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn more

URL Failing Elements
img
…images/logo.f6e4ed52.svg (www.lotteryusa.com)
Minimize main-thread work

— 9.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps
with this. Learn more
Category Time Spent
Script Evaluation 4,697 ms
Other 1,980 ms
Style & Layout 1,605 ms
Rendering 612 ms
Script Parsing & Compilation 259 ms
Parse HTML & CSS 110 ms
Garbage Collection 59 ms
Serve static assets with an efficient cache policy

— 25 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

5/49
7/20/2021
URL Cache TTL Transfer Size
/beacon.js (sb.scorecardresearch.com) None 2 KiB
…js/1?id=… (serving.stat-rock.com) None 0 KiB
/vd/i?event=… (vid-io.springserve.com) None 0 KiB
…sdkloader/vpaid_adapter.js?adtagurl=… (imasdk.googleapis.com) 15 m 16 KiB
/lotteryusa-com/pubfig.min.js (a.pub.network) 30 m 43 KiB
…pubfig/pubfig.engine.4.13.0.98e43e4….js (a.pub.network) 1 h 118 KiB
…pubfig/pubfig.messaging.2.1.8.26fd503….js (a.pub.network) 1 h 55 KiB
…live/omweb-v1.js (pagead2.googlesyndication.com) 1 h 12 KiB
/rules-p-U….js (rules.quantcount.com) 1 h 1 KiB
/analytics.js (www.google-analytics.com) 2 h 19 KiB
/aax2/apstag.js (c.amazon-adsystem.com) 1 d 33 KiB
…ld/publishertag.prebid.js (static.criteo.net) 1 d 27 KiB
/px.gif?ch=1&e=0.800… (ad-delivery.net) 1 d 0 KiB
/favicon.ico?ad=300x250&ad_box_=1&adnet=1&showad=1&size=250x250 (ad.doubleclick.net) 1 d 0 KiB
1 d 2 h 50 m

…2794/pwt.js (ads.pubmatic.com) 60 KiB
23 s
…playerJS/frstrOSm_2.js (cdn.springserve.com) 3 d 92 KiB
…html/interstitial_ad_frame_fy2019.js (tpc.googlesyndication.com) 14 d 8 KiB
…r20110914/abg_lite_fy2019.js (tpc.googlesyndication.com) 14 d 7 KiB
…client/qs_click_protection_fy2019.js (tpc.googlesyndication.com) 14 d 6 KiB
…client/window_focus_fy2019.js (tpc.googlesyndication.com) 14 d 1 KiB
…client/load_preloaded_resource_fy2019.js (tpc.googlesyndication.com) 14 d 1 KiB
/production/vpaid_df75f8b2.js (vpaid.springserve.com) 31 d 100 KiB
/mysidia/4661e2b….js?tag=mysidia_one_click_handler_one_afma_2019 (www.gstatic.com) 90 d 11 KiB
Avoid an excessive DOM size

— 1,799 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Statistic Element Value
Total DOM
1,799
Elements
6/49
7/20/2021
Statistic Element Value
path
Maximum DOM
16
Depth
select#stateSelectNavstate-select-nav.js-input-select.c-
select__list.js-state-dropdown__input
Maximum Child
49
Elements
Reduce JavaScript execution time

— 4.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps
with this. Learn more.

Total CPU Script Script

URL
Time Evaluation Parse
/florida/ (www.lotteryusa.com) 2,365 ms 103 ms 12 ms
/gpt/pubads_impl_202….js?31061848 (securepubads.g.doubleclick.net) 1,851 ms 1,737 ms 17 ms
Unattributable 881 ms 14 ms 0 ms
/build/vendors.bce9a98c.js (www.lotteryusa.com) 650 ms 221 ms 23 ms
…playerJS/frstrOSm_2.js (cdn.springserve.com) 638 ms 474 ms 17 ms
/core/prebid-analytics-4.40.5.js (a.pub.network) 354 ms 98 ms 19 ms
…current/osd.js (www.googletagservices.com) 328 ms 299 ms 5 ms
…sdkloader/ima3.js (imasdk.googleapis.com) 274 ms 195 ms 22 ms
…pubfig/pubfig.engine.4.13.0.98e43e4….js (a.pub.network) 238 ms 198 ms 16 ms
…r20190131/show_ads_….js?
235 ms 157 ms 11 ms
bust=exp%3D31061746 (pagead2.googlesyndication.com)
/production/vpaid_df75f8b2.js (vpaid.springserve.com) 217 ms 145 ms 28 ms
…pubfig/pubfig.messaging.2.1.8.26fd503….js (a.pub.network) 212 ms 187 ms 9 ms
…2794/pwt.js (ads.pubmatic.com) 124 ms 112 ms 7 ms
/lotteryusa-com/pubfig.min.js (a.pub.network) 111 ms 93 ms 6 ms
/gtag/js?id=G-R1BKHNRFE9&l=dataLayer&cx=c (www.googletagmanager.com) 104 ms 94 ms 5 ms
…r20190131/reactive_library_fy2019.js (pagead2.googlesyndication.com) 94 ms 83 ms 6 ms
…sdkloader/vpaid_adapter.js?adtagurl=… (imasdk.googleapis.com) 87 ms 78 ms 5 ms
7/49
7/20/2021
Total CPU Script Script

URL
Time Evaluation Parse
…js/adsbygoogle.js (pagead2.googlesyndication.com) 81 ms 68 ms 5 ms
/gtag/js?id=UA-2571454-1 (www.googletagmanager.com) 65 ms 53 ms 4 ms
/analytics.js (www.google-analytics.com) 61 ms 54 ms 4 ms
/aax2/apstag.js (c.amazon-adsystem.com) 57 ms 39 ms 7 ms
…js/gpt.js (www.googletagservices.com) 51 ms 45 ms 3 ms
Avoid chaining critical requests

— 5 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of
chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Learn more.
Maximum critical path latency: 1,570 ms
Initial Navigation
/florida/ (www.lotteryusa.com)
/css?family=… (fonts.googleapis.com)
…v6/rP2Hp2ywx….woff2 (fonts.gstatic.com) - 80 ms, 11.95 KiB
…v6/rP2Cp2ywx….woff2 (fonts.gstatic.com) - 80 ms, 11.97 KiB
…v6/rP2Cp2ywx….woff2 (fonts.gstatic.com) - 90 ms, 11.88 KiB
…v6/rP2Fp2ywx….woff2 (fonts.gstatic.com) - 80 ms, 12.71 KiB
/sid/json?origin=… (gum.criteo.com) - 610 ms, 0.00 KiB
User Timing marks and measures

— 14 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user
experiences. Learn more.
Name Type Start Time Duration
lteu Measure 2,333.71 ms 0.11 ms
ltpq Measure 2,333.92 ms 0.03 ms
pubfig-init Mark 1,145.65 ms
gpt-tag-load Mark 1,943.03 ms
pubfig-prebid-fsRequestBids Mark 2,033.84 ms
pubfig-prebid-auctionInit Mark 2,099.3 ms
loadStarteventUtils Mark 2,333.72 ms
loadEndeventUtils Mark 2,333.82 ms
loadStartpixelQueue Mark 2,333.93 ms
8/49
7/20/2021
Name Type Start Time Duration
loadEndpixelQueue Mark 2,333.96 ms
pubfig-prebid-auctionEnd Mark 3,079.46 ms
gpt-first-ad-request Mark 3,128.58 ms
pubfig-slotRequested Mark 3,134.46 ms
pubfig-slotRenderEnded Mark 3,620.05 ms
Keep request counts low and transfer sizes small

— 199 requests • 2,112 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Resource Type Requests Transfer Size
Total 199 2,111.9 KiB
Script 48 1,645.4 KiB
Document 10 269.0 KiB
Other 108 66.8 KiB
Image 24 53.3 KiB
Font 4 48.5 KiB
Stylesheet 5 28.9 KiB
Media 0 0.0 KiB
Third-party 184 1,809.6 KiB
Largest Contentful Paint element

— 1 element found
This is the largest contentful element painted within the viewport. Learn More
Element
span.c-result-table__game-name
Avoid large layout shifts

— 3 elements found
These DOM elements contribute most to the CLS of the page.
Element CLS Contribution
9/49
7/20/2021
Element CLS Contribution
li.c-global-header__menu-item
0.001
span.c-result__ball.c-result__ball--fire
0.001
div.c-back-to-top.js-back-to-top
Avoid long main-thread tasks

— 20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more

URL Start Time Duration
/gpt/pubads_impl_202….js?31061848 (securepubads.g.doubleclick.net) 13,813 ms 636 ms
…pubfig/pubfig.engine.4.13.0.98e43e4….js (a.pub.network) 9,228 ms 231 ms
/florida/ (www.lotteryusa.com) 1,200 ms 183 ms
/production/vpaid_df75f8b2.js (vpaid.springserve.com) 21,731 ms 183 ms
/build/vendors.bce9a98c.js (www.lotteryusa.com) 6,228 ms 169 ms
…sdkloader/ima3.js (imasdk.googleapis.com) 24,241 ms 161 ms
/build/vendors.bce9a98c.js (www.lotteryusa.com) 6,903 ms 140 ms
…pubfig/pubfig.messaging.2.1.8.26fd503….js (a.pub.network) 13,449 ms 138 ms
/gpt/pubads_impl_202….js?31061848 (securepubads.g.doubleclick.net) 12,259 ms 132 ms
/core/prebid-analytics-4.40.5.js (a.pub.network) 17,931 ms 126 ms
…2794/pwt.js (ads.pubmatic.com) 6,108 ms 120 ms
…playerJS/frstrOSm_2.js (cdn.springserve.com) 19,499 ms 118 ms
/florida/ (www.lotteryusa.com) 1,032 ms 117 ms
…r20190131/show_ads_….js?bust=exp%3D31061746 (pagead2.googlesyndication.com) 21,914 ms 116 ms
/core/prebid-analytics-4.40.5.js (a.pub.network) 12,159 ms 99 ms
10/49
7/20/2021
URL Start Time Duration
/gtag/js?id=G-R1BKHNRFE9&l=dataLayer&cx=c (www.googletagmanager.com) 4,453 ms 95 ms
…r20190131/reactive_library_fy2019.js (pagead2.googlesyndication.com) 13,359 ms 90 ms
…r20190131/show_ads_….js?bust=exp%3D31061746 (pagead2.googlesyndication.com) 5,757 ms 88 ms
…current/osd.js (www.googletagservices.com) 7,242 ms 88 ms
/lotteryusa-com/pubfig.min.js (a.pub.network) 2,871 ms 82 ms
Avoid non-composited animations

— 112 animated elements found
Animations which are not composited can be janky and increase CLS. Learn more
Element Name
AL
<a href="/alabama/" class="c-state-links__link c-state-links__link--statename" data-
statename="Alabama">
Unsupported CSS Property: color

Unsupported CSS Property: padding-bottom
Unsupported CSS Property: line-height
Unsupported CSS Property: flex-grow
Unsupported CSS Property: font-size
AL
<span class="c-state-links__pin">
Unsupported CSS Property: border-top-left-radius

Unsupported CSS Property: border-bottom-left-radius
Unsupported CSS Property: border-bottom-right-radius
Unsupported CSS Property: border-top-right-radius
Unsupported CSS Property: font-weight
Unsupported CSS Property: background-color
AZ
<a href="/arizona/" class="c-state-links__link c-state-links__link--statename" data-
statename="Arizona">

AZ

11/49
7/20/2021
Element Name

AR
<a href="/arkansas/" class="c-state-links__link c-state-links__link--statename" data-
statename="Arkansas">

AR

CA
<a href="/california/" class="c-state-links__link c-state-links__link--statename" data-
statename="California">

CA

12/49
7/20/2021
Element Name
CO
<a href="/colorado/" class="c-state-links__link c-state-links__link--statename" data-
statename="Colorado">

CO

CT
<a href="/connecticut/" class="c-state-links__link c-state-links__link--statename" data-
statename="Connecticut">

CT

DE
<a href="/delaware/" class="c-state-links__link c-state-links__link--statename" data-
statename="Delaware">

13/49
7/20/2021
Element Name

DE

DC
<a href="/district-of-columbia/" class="c-state-links__link c-state-links__link--statename" data-
statename="District of Columbia">

DC

FL
<a href="/florida/" class="c-state-links__link c-state-links__link--statename" data-
statename="Florida">

FL
14/49
7/20/2021
Element Name

GA
<a href="/georgia/" class="c-state-links__link c-state-links__link--statename" data-
statename="Georgia">

GA

ID
<a href="/idaho/" class="c-state-links__link c-state-links__link--statename" data-statename="Idaho">

ID

15/49
7/20/2021
Element Name
IL
<a href="/illinois/" class="c-state-links__link c-state-links__link--statename" data-
statename="Illinois">

IL

IN
<a href="/indiana/" class="c-state-links__link c-state-links__link--statename" data-
statename="Indiana">

IN

IA
<a href="/iowa/" class="c-state-links__link c-state-links__link--statename" data-statename="Iowa">

16/49
7/20/2021
Element Name

IA

KS
<a href="/kansas/" class="c-state-links__link c-state-links__link--statename" data-statename="Kansas">

KS

KY
<a href="/kentucky/" class="c-state-links__link c-state-links__link--statename" data-
statename="Kentucky">

KY

17/49
7/20/2021
Element Name

LA
<a href="/louisiana/" class="c-state-links__link c-state-links__link--statename" data-
statename="Louisiana">

LA

ME
<a href="/maine/" class="c-state-links__link c-state-links__link--statename" data-statename="Maine">

ME

18/49
7/20/2021
Element Name
MD
<a href="/maryland/" class="c-state-links__link c-state-links__link--statename" data-
statename="Maryland">

MD

MA
<a href="/massachusetts/" class="c-state-links__link c-state-links__link--statename" data-
statename="Massachusetts">

MA

MI
<a href="/michigan/" class="c-state-links__link c-state-links__link--statename" data-
statename="Michigan">

19/49
7/20/2021
Element Name

MI

MN
<a href="/minnesota/" class="c-state-links__link c-state-links__link--statename" data-
statename="Minnesota">

MN

MS
<a href="/mississippi/" class="c-state-links__link c-state-links__link--statename" data-
statename="Mississippi">

MS
20/49
7/20/2021
Element Name

MO
<a href="/missouri/" class="c-state-links__link c-state-links__link--statename" data-
statename="Missouri">

MO

MT
<a href="/montana/" class="c-state-links__link c-state-links__link--statename" data-
statename="Montana">

MT

21/49
7/20/2021
Element Name
NE
<a href="/nebraska/" class="c-state-links__link c-state-links__link--statename" data-
statename="Nebraska">

NE

NH
<a href="/new-hampshire/" class="c-state-links__link c-state-links__link--statename" data-
statename="New Hampshire">

NH

NJ
<a href="/new-jersey/" class="c-state-links__link c-state-links__link--statename" data-statename="New
Jersey">

22/49
7/20/2021
Element Name

NJ

NM
<a href="/new-mexico/" class="c-state-links__link c-state-links__link--statename" data-statename="New
Mexico">

NM

NY
<a href="/new-york/" class="c-state-links__link c-state-links__link--statename" data-statename="New
York">

NY
23/49
7/20/2021
Element Name

NC
<a href="/north-carolina/" class="c-state-links__link c-state-links__link--statename" data-
statename="North Carolina">

NC

ND
<a href="/north-dakota/" class="c-state-links__link c-state-links__link--statename" data-
statename="North Dakota">

ND

24/49
7/20/2021
Element Name

OH
<a href="/ohio/" class="c-state-links__link c-state-links__link--statename" data-statename="Ohio">

OH

OK
<a href="/oklahoma/" class="c-state-links__link c-state-links__link--statename" data-
statename="Oklahoma">

OK

OR
<a href="/oregon/" class="c-state-links__link c-state-links__link--statename" data-statename="Oregon">

25/49
7/20/2021
Element Name

OR

PA
<a href="/pennsylvania/" class="c-state-links__link c-state-links__link--statename" data-
statename="Pennsylvania">

PA

PR
<a href="/puerto-rico/" class="c-state-links__link c-state-links__link--statename" data-
statename="Puerto Rico">

PR
26/49
7/20/2021
Element Name

RI
<a href="/rhode-island/" class="c-state-links__link c-state-links__link--statename" data-
statename="Rhode Island">

RI

SC
<a href="/south-carolina/" class="c-state-links__link c-state-links__link--statename" data-
statename="South Carolina">

SC

27/49
7/20/2021
Element Name

SD
<a href="/south-dakota/" class="c-state-links__link c-state-links__link--statename" data-
statename="South Dakota">

SD

TN
<a href="/tennessee/" class="c-state-links__link c-state-links__link--statename" data-
statename="Tennessee">

TN

TX
<a href="/texas/" class="c-state-links__link c-state-links__link--statename" data-statename="Texas">
28/49
7/20/2021
Element Name

TX

VT
<a href="/vermont/" class="c-state-links__link c-state-links__link--statename" data-
statename="Vermont">

VT

VA
<a href="/virginia/" class="c-state-links__link c-state-links__link--statename" data-
statename="Virginia">

29/49
7/20/2021
Element Name
VA

WA
<a href="/washington/" class="c-state-links__link c-state-links__link--statename" data-
statename="Washington">

WA

WV
<a href="/west-virginia/" class="c-state-links__link c-state-links__link--statename" data-
statename="West Virginia">

WV

30/49
7/20/2021
Element Name

WI
<a href="/wisconsin/" class="c-state-links__link c-state-links__link--statename" data-
statename="Wisconsin">

WI

WY
<a href="/wyoming/" class="c-state-links__link c-state-links__link--statename" data-
statename="Wyoming">

WY

31/49
7/20/2021
Element Name
div
<div class="orp-lp-loader-dot orp-lp-loader-dot-0">
lp-loader-
fade
div
lp-loader-
fade
div
lp-loader-
fade
div
lp-loader-
fade
div
lp-loader-
fade
div
lp-loader-
fade
div
lp-loader-
fade
div
lp-loader-
fade
div
lp-loader-
fade
div
lp-loader-
fade
div
lp-loader-
fade
32/49
7/20/2021
Element Name
div
lp-loader-
fade
div
lp-loader-
fade
div
lp-loader-
fade
div
lp-loader-
fade
div
lp-loader-
fade
Passed audits
(20)
Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to
interactive. Learn more.
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.
Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means
faster downloads and less data consumption. Learn more.
33/49
7/20/2021
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn
more.
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins.
Learn more.
Initial server response time was short

— Root document took 60 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.

URL Time Spent
/florida/ (www.lotteryusa.com) 60 ms
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.
Preload key requests
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn
more.
Use HTTP/2
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and
PNG/WebP for static images instead of GIF to save network bytes. Learn more
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for
modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature
detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn
More
Preload Largest Contentful Paint image
Preload the image used by the LCP element in order to improve your LCP time. Learn more.
Avoids enormous network payloads

— Total size was 2,127 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
34/49
7/20/2021

URL Transfer Size
…core/bridge3.472.0_en.html (imasdk.googleapis.com) 189.9 KiB
/build/vendors.bce9a98c.js (www.lotteryusa.com) 180.8 KiB
/core/prebid-analytics-4.40.5.js (a.pub.network) 151.2 KiB
…pubfig/pubfig.engine.4.13.0.98e43e4….js (a.pub.network) 118.3 KiB
…sdkloader/ima3.js (imasdk.googleapis.com) 116.9 KiB
/gpt/pubads_impl_202….js?31061848 (securepubads.g.doubleclick.net) 114.7 KiB
/production/vpaid_df75f8b2.js (vpaid.springserve.com) 100.4 KiB
…playerJS/frstrOSm_2.js (cdn.springserve.com) 91.7 KiB
…r20190131/show_ads_….js?bust=exp%3D31061746 (pagead2.googlesyndication.com) 90.3 KiB
…2794/pwt.js (ads.pubmatic.com) 60.1 KiB
All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more.
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
88
Accessibility
These checks highlight opportunities to improve the accessibility of your
web app. Only a subset of accessibility issues can be automatically
detected so manual testing is also encouraged.
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.
[aria-hidden="true"] elements contain focusable descendents
Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to
users of assistive technologies like screen readers. Learn more.
35/49
7/20/2021
Failing Elements
li.c-link-scroller__item.c-carousel__item.js-carousel__item
li.o-content-scroller__item
36/49
7/20/2021
Failing Elements
Tables and lists — These are opportunities to improve the experience of reading tabular or list data using assistive technology,
like a screen reader.
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn more.
Failing Elements
dl.c-list-rail
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn
more.
Failing Elements
ul.c-carousel.js-carousel.c-link-scroller__items.js-link-scroller__items.flickity-enabled.is-draggable
ul.o-content-scroller__items.c-carousel.js-carousel.flickity-enabled.is-draggable
List items (<li>) are not contained within <ul> or <ol> parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn
more.
Failing Elements
37/49
7/20/2021
Failing Elements
li.c-link-scroller__item.c-carousel__item.js-carousel__item.is-selected
li.o-content-scroller__item.is-selected
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.
Image elements do not have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt
attribute. Learn more.
Failing Elements
img
<img src="https://vid-io.springserve.com/vd/i?event=player_start&id=638836&undefined…" width="1" height="1">
Additional items to manually check

(10)
— These items address areas which an automated testing tool cannot cover. Learn
more in our guide on conducting an accessibility review.
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more.
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn more.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive
elements. Learn more.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn more.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn more.
38/49
7/20/2021
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn more.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn more.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology.
Learn more.
Passed audits
(24)
[aria-*] attributes match their roles
Each ARIA `role` supports a specific subset of ària-*` attributes. Mismatching these invalidates the ària-*` attributes. Learn
more.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when ària-hidden="true"` is set on the document `<body>`.
Learn more.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions.
Learn more.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.
[aria-*] attributes are valid and not misspelled
39/49
7/20/2021
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who
rely on screen readers. Learn more.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn more.
Definition list items are wrapped in <dl> elements
Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can
properly announce them. Learn more.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page
is relevant to their search. Learn more.
[id] attributes on active, focusable elements are unique
All focusable elements must have a unique ìd` to ensure that they're visible to assistive technologies. Learn more.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn
more.
Heading elements appear in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate
and understand when using assistive technologies. Learn more.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user
chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not
announce the page's text correctly. Learn more.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
Links have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the
navigation experience for screen reader users. Learn more.
40/49
7/20/2021
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a
web page. Learn more.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating
experiences for users who rely on assistive technologies. Learn more.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring `<td>` cells using the `[headers]` attribute only
refer to other cells in the same table may improve the experience for screen reader users. Learn more.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells
may improve the experience for screen reader users. Learn more.
Not applicable
(15)
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more.
button, link, and menuitem elements have accessible names
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for
users who rely on screen readers. Learn more.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable
for users who rely on screen readers. Learn more.
ARIA meter elements have accessible names
ARIA progressbar elements have accessible names
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable
for users who rely on screen readers. Learn more.
ARIA tooltip elements have accessible names
41/49
7/20/2021
ARIA treeitem elements have accessible names
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either
the first, the last, or all of the labels. Learn more.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
<input type="image"> elements have [alt] text
When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand the
purpose of the button. Learn more.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may
create a frustrating or confusing experience. Learn more.
<object> elements have [alt] text
Screen readers cannot translate non-text content. Adding alt text to `<object>` elements helps screen readers convey
meaning to users. Learn more.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn
more.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more.
67
Best Practices
Trust and Safety
Links to cross-origin destinations are unsafe
42/49
7/20/2021
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities.
Learn more.
Failing Anchors
Includes front-end JavaScript libraries with known security vulnerabilities

— 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers.
Learn more.
Library Version Vulnerability Count Highest Severity
Lo-Dash@4.17.20 2 High
General
Registers an unload listener
The ùnload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache.
Consider using the `pagehide` or `visibilitychange` events instead. Learn more

Source
osd.js:6
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser
concerns. Learn more

Source Description
gum.criteo.com/sid/j… Failed to load resource: net::ERR_CONNECTION_RESET

sa.com&cw=1&lsw=1:1
43/49
7/20/2021
Source Description
ReferenceError: googletag is not defined

at
www.lotteryusa.com/:3435 https://www.lotteryusa.com/florida/:3435:5

at

at
Issues were logged in the Issues panel in Chrome Devtools
Issues logged to the Ìssues` panel in Chrome Devtools indicate unresolved problems. They can come from network request
failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more
details on each issue.

Issue type
SameSite cookie
/bidRequest?dcn=… (c2shb.ssp.yahoo.com)
Passed audits
(12)
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content,
where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents
intruders from tampering with or passively listening in on the communications between your app and your users, and is a
prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user
action instead. Learn more.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to
user gestures instead. Learn more.
Allows users to paste into password fields
Preventing password pasting undermines good security policy. Learn more.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
Serves images with appropriate resolution
44/49
7/20/2021
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn
more.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more.
Properly defines charset
A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the
Content-Type HTTP response header. Learn more.
Avoids Application Cache
Application Cache is deprecated. Learn more.
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more.
Name Version
Lo-Dash 4.17.20
core-js-global@3.8.3; core-js-global@3.6.4; core-js-pure@3.15.2; core-js-global@3.8.3; core-js-pure@3.6.4;

core-js
core-js-global@3.8.3
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more.
Page has valid source maps
Source maps translate minified code to the original source code. This helps developers debug in production. In addition,
Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn
more.

URL Map URL
/aax2/apstag.js (c.amazon-adsystem.com) /aax2/apstag.js.map (c.amazon-adsystem.com)
Warning: missing 25 items in `.sourcesContent`
Not applicable
(1)
Fonts with font-display: optional are preloaded
Preload òptional` fonts so first-time visitors may use them. Learn more
93 45/49
7/20/2021
93
SEO
These checks ensure that your page is optimized for search engine results
ranking. There are additional factors Lighthouse does not check that may
affect your search ranking. Learn more.
Content Best Practices — Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt
attribute. Learn more.
Failing Elements
img
<img src="https://vid-io.springserve.com/vd/i?event=player_start&id=638836&undefined…" width="1" height="1">

(1)
— Run these additional validators on your site to check additional SEO best
practices.
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more.
Passed audits
(13)
Has a <meta name="viewport"> tag with width or initial-scale
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page
is relevant to their search. Learn more.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more.
Links have descriptive text
Descriptive link text helps search engines understand your content. Learn more.
Links are crawlable
46/49
7/20/2021
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links
to an appropriate destination, so more pages of the site can be discovered. Learn More
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more.
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or
indexed. Learn more.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region.
Learn more.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more.
Document uses legible font sizes

— 100% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to
have >60% of page text ≥12px. Learn more.

Source Selector % of Page Text Font Size
main.22eb6eb3.css:1 .o-layout 0.00% 0px
Legible text 100.00% ≥ 12px
Document avoids plugins
Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more.
Tap targets are sized appropriately

— 100% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be
easy enough to tap without overlapping onto other elements. Learn more.
Progressive Web App

These checks validate the aspects of a Progressive Web App. Learn more.
Installable
47/49
7/20/2021
Web app manifest or service worker do not meet the installability requirements
— 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to
homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively
prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.
Failure reason
No manifest was fetched
PWA Optimized
Does not register a service worker that controls page and start_url
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add
to homescreen, and push notifications. Learn more.
Redirects HTTP traffic to HTTPS
If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web
features for all your users. Learn more.
Is not configured for a custom splash screen Failures: No manifest was fetched.
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn
more.
Does not set a theme color for the address bar.

Failures: No manifest was fetched,
No `<meta name="theme-color">` tag found.
The browser address bar can be themed to match your site. Learn more.
Content is sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile
screens. Learn more.
Has a <meta name="viewport"> tag with width or initial-scale
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more.
Does not provide a valid apple-touch-icon
For ideal appearance on iOS when users add a progressive web app to the home screen, define an àpple-touch-icon`. It
must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Manifest doesn't have a maskable icon No manifest was fetched
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device.
Learn more.

(3)
— These checks are required by the baseline PWA Checklist but are not
automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
48/49
7/20/2021
Site works cross-browser
To reach the most number of users, sites should work across every major browser. Learn more.
Page transitions don't feel like they block on the network
Transitions should feel snappy as you tap around, even on a slow network. This experience is key to a user's perception of
performance. Learn more.
Each page has a URL
Ensure individual pages are deep linkable via URL and that URLs are unique for the purpose of shareability on social media.
Learn more.
Runtime Settings
URL https://www.lotteryusa.com/florida/
Fetch Time Jul 20, 2021, 8:53 AM GMT+1
Device Emulated Moto G4
Network throttling 150 ms TCP RTT, 1,638.4 Kbps throughput (Simulated)
CPU throttling 4x slowdown (Simulated)
Channel devtools
User agent (host) Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/91.0.4472.124 Safari/537.36
User agent (network) Mozilla/5.0 (Linux; Android 7.0; Moto G (4)) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/90.0.4420.0 Mobile Safari/537.36 Chrome-Lighthouse
CPU/Memory Power 1479
Axe version 4.1.2
Generated by Lighthouse 7.2.0 |

File an issue
49/49

Performance: Performance Accessibility Best Practices SEO Progressive Web App

Uploaded by

Copyright:

Available Formats

Performance: Performance Accessibility Best Practices SEO Progressive Web App

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Performance: Performance Accessibility Best Practices SEO Progressive Web App

Uploaded by

Copyright:

Available Formats

7/20/2021

Performance Accessibility Best SEO Progressive

0–49 50–89 90–100

First Contentful Paint 1.7 s Time to Interactive 23.9 s

Speed Index 5.4 s Total Blocking Time 1,960 ms

Largest Contentful Paint 1.7 s Cumulative Layout Shift 0.001

View Original Trace

Opportunity Estimated Savings

Remove unused JavaScript 3.71 s

/build/vendors.bce9a98c.js (www.lotteryusa.com) 180.8 KiB 133.8 KiB

/core/prebid-analytics-4.40.5.js (a.pub.network) 151.2 KiB 89.7 KiB

…sdkloader/ima3.js (imasdk.googleapis.com) 116.9 KiB 70.8 KiB

/gpt/pubads_impl_202….js?31061848 (securepubads.g.doubleclick.net) 114.7 KiB 65.8 KiB

…pubfig/pubfig.engine.4.13.0.98e43e4….js (a.pub.network) 118.3 KiB 57.5 KiB

…r20190131/show_ads_….js?bust=exp%3D31061746 (pagead2.googlesyndication.com) 90.3 KiB 52.5 KiB

…r20190131/reactive_library_fy2019.js (pagead2.googlesyndication.com) 51.7 KiB 42.2 KiB

/production/vpaid_df75f8b2.js (vpaid.springserve.com) 100.4 KiB 39.6 KiB

…2794/pwt.js (ads.pubmatic.com) 60.1 KiB 35.7 KiB

…playerJS/frstrOSm_2.js (cdn.springserve.com) 91.7 KiB 34.2 KiB

/gtag/js?id=G-R1BKHNRFE9&l=dataLayer&cx=c (www.googletagmanager.com) 49.5 KiB 23.6 KiB

…ld/publishertag.prebid.js (static.criteo.net) 26.7 KiB 22.5 KiB

…js/adsbygoogle.js (pagead2.googlesyndication.com) 47.4 KiB 22.2 KiB

…pubfig/pubfig.messaging.2.1.8.26fd503….js (a.pub.network) 55.1 KiB 22.0 KiB

/gtag/js?id=UA-2571454-1 (www.googletagmanager.com) 39.7 KiB 20.1 KiB

Eliminate render-blocking resources 0.76 s

/css?family=… (fonts.googleapis.com) 0.6 KiB 790 ms

Remove unused CSS 0.15 s

/build/main.22eb6eb3.css (www.lotteryusa.com) 24.6 KiB 20.4 KiB

.orp-light-player-wrapper { position: relative; width: 100%; height: 100%; background:

Reduce the impact of third-party code

Transfer Main-Thread Blocking

Google/Doubleclick Ads 544 KiB 1,337 ms

/gpt/pubads_impl_202….js?31061848 (securepubads.g.doubleclick.net) 115 KiB 1,258 ms

SpringServer 194 KiB 226 ms

…playerJS/frstrOSm_2.js (cdn.springserve.com) 92 KiB 136 ms

Pubmatic 60 KiB 55 ms

…2794/pwt.js (ads.pubmatic.com) 60 KiB 55 ms

Google Tag Manager 89 KiB 35 ms

/gtag/js?id=G-R1BKHNRFE9&l=dataLayer&cx=c (www.googletagmanager.com) 49 KiB 35 ms

Other Google APIs/SDKs 323 KiB 2 ms

…sdkloader/vpaid_adapter.js?adtagurl=… (imasdk.googleapis.com) 16 KiB 2 ms

Transfer Main-Thread Blocking

Google Analytics 19 KiB 2 ms

/analytics.js (www.google-analytics.com) 19 KiB 2 ms

Google Fonts 50 KiB 0 ms

…v6/rP2Fp2ywx….woff2 (fonts.gstatic.com) 13 KiB 0 ms

Amazon Ads 37 KiB 0 ms

/aax2/apstag.js (c.amazon-adsystem.com) 33 KiB 0 ms

Criteo 28 KiB 0 ms

…ld/publishertag.prebid.js (static.criteo.net) 27 KiB 0 ms

Yahoo! 18 KiB 0 ms

/bidRequest?dcn=… (c2shb.ssp.yahoo.com) 6 KiB 0 ms

Rubicon Project 15 KiB 0 ms

Google CDN 11 KiB 0 ms

Quantcast 10 KiB 0 ms

/quant.js (secure.quantserve.com) 9 KiB 0 ms

sovrn 5 KiB 0 ms

/rtb/bid?src=prebid_prebid_4.40.0 (ap.lijit.com) 5 KiB 0 ms