1.8 sec in total
32 ms
1.1 sec
688 ms
Click here to check amazing DC content for United States. Otherwise, check out these important facts you probably never knew about dc.gov
Visit dc.govWe analyzed Dc.gov page load time and found that the first response time was 32 ms and then it took 1.7 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.
dc.gov performance score
name
value
score
weighting
Value1.6 s
95/100
10%
Value9.0 s
1/100
25%
Value4.6 s
70/100
10%
Value770 ms
38/100
30%
Value0.67
8/100
15%
Value11.0 s
21/100
10%
32 ms
88 ms
41 ms
64 ms
112 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 85% of them (115 requests) were addressed to the original Dc.gov, 4% (6 requests) were made to Google.com and 1% (2 requests) were made to Cse.google.com. The less responsive or slowest element that took the longest time to load (269 ms) relates to the external source Platform.twitter.com.
Page size can be reduced by 1.2 MB (52%)
2.4 MB
1.1 MB
In fact, the total size of Dc.gov main page is 2.4 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.9 MB which makes up the majority of the site volume.
Potential reduce by 94.6 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 94.6 kB or 76% 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, DC needs image optimization as it can save up to 1.1 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 33.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. This website has mostly compressed JavaScripts.
Potential reduce by 47.5 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. Dc.gov needs all CSS files to be minified and compressed as it can save up to 47.5 kB or 58% of the original size.
Number of requests can be reduced by 78 (59%)
132
54
The browser has sent 132 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 35 to 1 for JavaScripts and from 45 to 1 for CSS and as a result speed up the page load time.
dc.gov
32 ms
dc.gov
88 ms
system.base.css
41 ms
system.menus.css
64 ms
system.messages.css
112 ms
system.theme.css
93 ms
book.css
80 ms
comment.css
77 ms
datepicker.1.7.css
77 ms
date_repeat_field.css
91 ms
domain_nav.css
99 ms
field.css
96 ms
node.css
101 ms
search.css
99 ms
user.css
108 ms
views.css
112 ms
ckeditor.css
118 ms
ctools.css
125 ms
flickrgallery.css
130 ms
panels.css
133 ms
rate.css
139 ms
text_resize.css
130 ms
extlink.css
135 ms
quicktabs.css
141 ms
basic.css
148 ms
jquery.bxslider.css
152 ms
normalize.css
155 ms
alpha-reset.css
156 ms
alpha-mobile.css
166 ms
formalize.css
156 ms
omega-text.css
162 ms
omega-branding.css
171 ms
omega-forms.css
178 ms
global.css
173 ms
dc-home-omega-alpha-default.css
170 ms
dc-home-omega-alpha-default-narrow.css
176 ms
alpha-default-narrow-24.css
186 ms
cse.js
92 ms
js
116 ms
webReader.js
165 ms
vedd3670a3b1c4e178fdfb0cc912d969e1713874337387
118 ms
alpha-default-narrow-12.css
175 ms
dc-home-omega-alpha-default-normal.css
159 ms
alpha-default-normal-24.css
138 ms
alpha-default-normal-12.css
130 ms
dc-home-omega-alpha-default-wide.css
169 ms
alpha-default-wide-24.css
151 ms
alpha-default-wide-12.css
124 ms
seckit.no_body.css
123 ms
twitterfeed.js
139 ms
jquery.min.js
126 ms
jquery-extend-3.4.0.js
138 ms
jquery-html-prefilter-3.5.0-backport.js
134 ms
jquery.once.js
136 ms
drupal.js
163 ms
jquery.cookie.js
163 ms
jquery.form.min.js
153 ms
ajax.js
147 ms
jquery_update.js
144 ms
progress.js
146 ms
seckit.document_write.js
197 ms
jquery.cookie.js
141 ms
text_resize.js
144 ms
extlink.js
142 ms
quicktabs.js
179 ms
googleanalytics.js
175 ms
jquery.bxslider.js
169 ms
base.js
175 ms
ajax_view.js
169 ms
dcHome.js
169 ms
voc.js
164 ms
jquery.formalize.js
158 ms
omega-mediaqueries.js
158 ms
dc_home_logo2_small.png
156 ms
search2.png
189 ms
dot.png
123 ms
dcgov_logo.jpg
123 ms
mayor-bowser-logo.jpg
124 ms
DPR%20Summer%20Programs%20Rotator.jpg
123 ms
DPRBoostRotator.jpg
123 ms
rotatorSeniorFest_01OntheYard2024.jpg
221 ms
rotatorEarnWith_01DPR2024.jpg
219 ms
WebBanner_0_0_0.png
220 ms
emergency-preparedness.png
222 ms
tickets-fines.png
222 ms
transportation-motor-vehicles.png
223 ms
public-works-sanitation-utilities.png
225 ms
training-professional-certification_0.png
227 ms
official-documents-records.png
224 ms
zero113.jpg
208 ms
311at113.jpg
206 ms
map_icon_footer.png
207 ms
infoCenter_icon_footer.png
206 ms
community_icon_footer.png
206 ms
contact_footer_icon.png
205 ms
BOW14_Winner.png
203 ms
Roboto-Regular.ttf
204 ms
cse_element__en.js
60 ms
default+en.css
86 ms
default.css
93 ms
BOW13_final.jpg
223 ms
h2stars.png
51 ms
more-arrow.png
58 ms
widgets.js
269 ms
x-logo-lightgrey.png
193 ms
facebook.png
192 ms
mobile.png
189 ms
maps.png
190 ms
webcasts.png
189 ms
rss.png
187 ms
data.png
193 ms
subscribe.png
193 ms
line_bg.jpg
195 ms
main_stars.jpg
197 ms
analytics.js
157 ms
async-ads.js
160 ms
branding.png
119 ms
clear.png
68 ms
nav_logo114.png
107 ms
bx_loader.gif
71 ms
DPR%20Summer%20Programs%20Rotator.jpg
107 ms
DPRBoostRotator.jpg
107 ms
rotatorSeniorFest_01OntheYard2024.jpg
101 ms
rotatorEarnWith_01DPR2024.jpg
107 ms
WebBanner_0_0_0.png
159 ms
controls2.png
137 ms
controls.png
136 ms
surveys.js
144 ms
surveys.js
145 ms
collect
53 ms
main.js
65 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
112 ms
collect
105 ms
75 ms
64 ms
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.
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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 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 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.
dc.gov
Open Graph description is not detected on the main page of 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: