2 sec in total
106 ms
1.2 sec
682 ms
Visit does.dc.gov now to see the best up-to-date Does Dc content for United States and also check out these interesting facts you probably never knew about does.dc.gov
Visit does.dc.govWe analyzed Does.dc.gov page load time and found that the first response time was 106 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.
does.dc.gov performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value4.9 s
29/100
25%
Value5.2 s
60/100
10%
Value1,310 ms
18/100
30%
Value0.229
54/100
15%
Value9.5 s
30/100
10%
106 ms
18 ms
21 ms
19 ms
19 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 89% of them (65 requests) were addressed to the original Does.dc.gov, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (377 ms) relates to the external source Search.usa.gov.
Page size can be reduced by 1.5 MB (69%)
2.2 MB
674.9 kB
In fact, the total size of Does.dc.gov main page is 2.2 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. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 72.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. 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 72.7 kB or 82% of the original size.
Potential reduce by 1.1 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, Does Dc needs image optimization as it can save up to 1.1 MB or 67% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 194.3 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 194.3 kB or 75% of the original size.
Potential reduce by 105.8 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. Does.dc.gov needs all CSS files to be minified and compressed as it can save up to 105.8 kB or 81% of the original size.
Number of requests can be reduced by 22 (31%)
72
50
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Does 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 13 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
does.dc.gov
106 ms
css_pbm0lsQQJ7A7WCCIMgxLho6mI_kBNgznNUWmTWcnfoE.css
18 ms
css_dUnOJK_8pgQfUqgobJgtye11niXZBDnjtqDVPKu3aWM.css
21 ms
css_CEIU8SSM-Ct8QqsEd00WHW8qUwRUnmAhkAxWh5KKGSA.css
19 ms
css_jhjc9dBT43wTvtgjTl2XUf8bMpz9E6K1QyUuYdk83SY.css
19 ms
css_thekgI-Mv6ejuWFZNveyxsj2ID3V5zNbghZsrMrDiLI.css
21 ms
css_Kv3vPHo5Qci1PlJtDoVGhiXRWMB5yBY91jQmt7r_Tr4.css
25 ms
js_xAPl0qIk9eowy_iS9tNkCWXLUVoat94SQT48UBCFkyQ.js
46 ms
js_33P4O9g9azhrgrGIyoSLndda0FsUZlVOgmR9sIRI4_4.js
93 ms
js_4TlrvrKyvJOwImPCk2rfJYSt97fDAnDiMR77Rvrge_w.js
94 ms
js_w8dT5-Azd2mbcE-4f5tuj6dFj9lTTkHKpHc1DXEhlMs.js
97 ms
js_pRbW9lpEy6572VsEn2feCSIUEFFItY4_1z5OJ1Er9XI.js
95 ms
js_43n5FBy8pZxQHxPXkf-sQF7ZiacVZke14b0VlvSA554.js
95 ms
analytics.js
43 ms
widgets.js
33 ms
remote.loader.js
271 ms
dot.png
121 ms
dcgov_logo.jpg
124 ms
search_icon.png
122 ms
dc_home_logo2_small.png
120 ms
search2.png
121 ms
LEAP%20logo.png
135 ms
AJC_Slider.jpg
135 ms
Unemployment%20_Compensation_Slider.jpg
136 ms
UI%20Fraud_slider.jpg
134 ms
youth.jpg
134 ms
uitax_essp_logoFinal_web_0.gif
131 ms
PE_Slider2.jpg
134 ms
doing-business-dc.png
137 ms
jobs-employment.png
139 ms
education-schools.png
164 ms
budget-finance.png
133 ms
more-arrow.png
132 ms
AJC_Inside.jpg
133 ms
white.jpg
134 ms
new_does_logo.jpg
161 ms
facebook.png
160 ms
twitter.png
159 ms
flickr.png
169 ms
feed.png
168 ms
map_icon_footer.png
172 ms
infoCenter_icon_footer.png
171 ms
community_icon_footer.png
171 ms
contact_footer_icon.png
160 ms
BOW14_Winner.png
160 ms
BOW13_final.jpg
161 ms
Roboto-Regular.ttf
158 ms
collect
153 ms
stats.js
377 ms
twitter.png
331 ms
facebook.png
332 ms
mobile.png
333 ms
maps.png
331 ms
webcasts.png
334 ms
rss.png
333 ms
data.png
335 ms
subscribe.png
338 ms
h2stars.png
335 ms
footer-stars-bars.png
335 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
53 ms
extlink.png
46 ms
mailto.png
46 ms
bx_loader.gif
46 ms
LEAP%20logo.png
47 ms
AJC_Slider.jpg
47 ms
Unemployment%20_Compensation_Slider.jpg
48 ms
UI%20Fraud_slider.jpg
64 ms
youth.jpg
55 ms
uitax_essp_logoFinal_web_0.gif
62 ms
PE_Slider2.jpg
63 ms
controls.png
55 ms
surveys.js
49 ms
595971352257032192
210 ms
does.dc.gov accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
does.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
does.dc.gov SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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 Does.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 Does.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.
does.dc.gov
Open Graph description is not detected on the main page of Does 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: