2.6 sec in total
158 ms
2.2 sec
209 ms
Click here to check amazing Lottery Dc content for United States. Otherwise, check out these important facts you probably never knew about lottery.dc.gov
Visit lottery.dc.govWe analyzed Lottery.dc.gov page load time and found that the first response time was 158 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
lottery.dc.gov performance score
name
value
score
weighting
Value2.0 s
85/100
10%
Value4.1 s
46/100
25%
Value2.7 s
96/100
10%
Value380 ms
70/100
30%
Value0.391
26/100
15%
Value6.6 s
58/100
10%
158 ms
1388 ms
14 ms
38 ms
40 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 92% of them (97 requests) were addressed to the original Lottery.dc.gov, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to Search.usa.gov. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Lottery.dc.gov.
Page size can be reduced by 1.9 MB (63%)
3.0 MB
1.1 MB
In fact, the total size of Lottery.dc.gov main page is 3.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. 65% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 62.8 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 62.8 kB or 80% of the original size.
Potential reduce by 1.3 MB
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. Obviously, Lottery Dc needs image optimization as it can save up to 1.3 MB or 58% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 271.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 271.7 kB or 71% of the original size.
Potential reduce by 266.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. Lottery.dc.gov needs all CSS files to be minified and compressed as it can save up to 266.9 kB or 81% of the original size.
Number of requests can be reduced by 50 (50%)
101
51
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lottery Dc. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 40 to 1 for CSS and as a result speed up the page load time.
lottery.dc.gov
158 ms
lottery.dc.gov
1388 ms
system.base.css
14 ms
system.menus.css
38 ms
system.messages.css
40 ms
system.theme.css
41 ms
book.css
37 ms
comment.css
40 ms
datepicker.1.7.css
37 ms
date_repeat_field.css
43 ms
domain_nav.css
45 ms
field.css
53 ms
node.css
44 ms
search.css
49 ms
user.css
50 ms
views.css
48 ms
ckeditor.css
49 ms
ctools.css
47 ms
flickrgallery.css
51 ms
panels.css
52 ms
rate.css
54 ms
text_resize.css
55 ms
extlink.css
59 ms
jquery.bxslider.css
65 ms
normalize.css
61 ms
alpha-reset.css
59 ms
alpha-mobile.css
58 ms
formalize.css
60 ms
omega-text.css
63 ms
omega-branding.css
62 ms
omega-forms.css
69 ms
global.css
71 ms
dc-agency-omega-alpha-default.css
68 ms
dc-agency-omega-alpha-default-narrow.css
67 ms
alpha-default-narrow-24.css
69 ms
alpha-default-narrow-12.css
72 ms
dc-agency-omega-alpha-default-normal.css
254 ms
analytics.js
45 ms
widgets.js
40 ms
alpha-default-normal-24.css
72 ms
alpha-default-normal-12.css
328 ms
dc-agency-omega-alpha-default-wide.css
44 ms
alpha-default-wide-24.css
155 ms
alpha-default-wide-12.css
45 ms
js_ri60QNjcazMKdlAmWmDsmRb0iKaVkkXUQxH2MsgpmVo.js
66 ms
js_xpcUaefRF16dGRM12CceyhwGxO2jTZMKo_3milCSqpk.js
45 ms
js_Eo5T__k7cT67RdWobG-2b-YrtvQ0lCM-iy2ivBhk9PY.js
47 ms
js_bJIUxb1HbNkjii51G_6fxOWgxFiYpfKVAFuvG8gToH4.js
48 ms
js_hfrjnkr8fZsEgY8zD_n3QiVliRgcBwxFF7xZ3BtvDTM.js
77 ms
js_43n5FBy8pZxQHxPXkf-sQF7ZiacVZke14b0VlvSA554.js
57 ms
dot.png
39 ms
dcgov_logo.jpg
42 ms
search_icon.png
38 ms
dc_home_logo2_small.png
41 ms
search2.png
41 ms
stay-connected-banner-2014-520x250px%20website_IG-01_614x325.jpg
41 ms
DC-Lottery-Retailer-Information_614x325.jpg
40 ms
News_final_614x325.jpg
41 ms
Charitable-Games-Banner-dc.gov_614x325.jpg
44 ms
events_final_614x325.jpg
43 ms
dclotterdotcom_0.jpg
42 ms
DCL1081%20Current%20Promotions%20F%20-%20Web.jpg
41 ms
claim-prize.jpg
41 ms
winners.jpg
47 ms
DCLotteryLogo.jpg
43 ms
facebook.png
43 ms
youtube.png
45 ms
twitter.png
58 ms
wordpress.png
43 ms
rss.png
47 ms
instagram.png
50 ms
linkedin.png
48 ms
feed.png
48 ms
map_icon_footer.png
50 ms
infoCenter_icon_footer.png
48 ms
community_icon_footer.png
54 ms
contact_footer_icon.png
53 ms
BOW14_Winner.png
53 ms
BOW13_final.jpg
54 ms
collect
21 ms
Roboto-Regular.ttf
38 ms
collect
141 ms
remote.loader.js
137 ms
twitter.png
105 ms
facebook.png
104 ms
mobile.png
104 ms
maps.png
106 ms
webcasts.png
103 ms
rss.png
106 ms
data.png
116 ms
subscribe.png
115 ms
more-arrow.png
108 ms
h2stars.png
107 ms
footer-stars-bars.png
108 ms
surveys.js
45 ms
extlink.png
13 ms
bx_loader.gif
20 ms
stay-connected-banner-2014-520x250px%20website_IG-01_614x325.jpg
60 ms
DC-Lottery-Retailer-Information_614x325.jpg
99 ms
News_final_614x325.jpg
76 ms
Charitable-Games-Banner-dc.gov_614x325.jpg
45 ms
events_final_614x325.jpg
64 ms
controls.png
24 ms
sayt_loader.js
10 ms
38 ms
nr-1039.min.js
14 ms
lottery.dc.gov accessibility score
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.
lottery.dc.gov 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
lottery.dc.gov SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 Lottery.dc.gov 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 Lottery.dc.gov 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.
lottery.dc.gov
Open Graph description is not detected on the main page of Lottery Dc. 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: