1.2 sec in total
245 ms
826 ms
118 ms
Click here to check amazing Efb Dc content for United States. Otherwise, check out these important facts you probably never knew about efb.dc.gov
Visit efb.dc.govWe analyzed Efb.dc.gov page load time and found that the first response time was 245 ms and then it took 944 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
efb.dc.gov performance score
name
value
score
weighting
Value2.3 s
73/100
10%
Value3.4 s
68/100
25%
Value2.3 s
98/100
10%
Value90 ms
98/100
30%
Value0.002
100/100
15%
Value4.1 s
86/100
10%
245 ms
38 ms
52 ms
69 ms
268 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 88% of them (45 requests) were addressed to the original Efb.dc.gov, 10% (5 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (275 ms) belongs to the original domain Efb.dc.gov.
Page size can be reduced by 20.8 kB (77%)
26.8 kB
6.1 kB
In fact, the total size of Efb.dc.gov main page is 26.8 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. 45% of websites need less resources to load. HTML takes 26.8 kB which makes up the majority of the site volume.
Potential reduce by 20.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. This page needs HTML code to be minified as it can gain 4.7 kB, which is 17% 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 20.8 kB or 77% of the original size.
Number of requests can be reduced by 19 (46%)
41
22
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Efb 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 9 to 1 for CSS and as a result speed up the page load time.
efb.dc.gov
245 ms
Login.aspx
38 ms
bootstrap.min.css
52 ms
font-awesome.min.css
69 ms
themify-icons.css
268 ms
animate.min.css
65 ms
remoteCSS.css
272 ms
palette.css
275 ms
font.css
70 ms
main.css
94 ms
modernizr.js
91 ms
jquery-1.10.2.min.js
109 ms
bootstrap.min.js
116 ms
jquery.validate.min.js
113 ms
dc2.js
143 ms
WebResource.axd
122 ms
ScriptResource.axd
140 ms
ScriptResource.axd
150 ms
ScriptResource.axd
147 ms
offscreen.js
161 ms
jquery.slimscroll.min.js
171 ms
main.js
164 ms
css
60 ms
DCgovLOGO_ver3.png
35 ms
dcgov_logo.png
22 ms
map_icon_footer.png
39 ms
infoCenter_icon_footer.png
33 ms
community_icon_footer.png
41 ms
contact_footer_icon.png
41 ms
dc_logo_red.png
50 ms
dcgov_logo.png
28 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
38 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
49 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
73 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
77 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
76 ms
themify.woff
72 ms
glyphicons-halflings-regular.woff
38 ms
twitter.png
64 ms
facebook.png
65 ms
mobile.png
64 ms
maps.png
63 ms
webcasts.png
62 ms
rss.png
83 ms
data.png
167 ms
subscribe.png
83 ms
more-arrow.png
99 ms
line_bg.jpg
78 ms
main_stars.jpg
96 ms
h2stars.png
93 ms
Roboto-Regular-webfont.woff
139 ms
efb.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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
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.
efb.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
General
Impact
Issue
Detected JavaScript libraries
efb.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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Efb.dc.gov can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Efb.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.
efb.dc.gov
Open Graph description is not detected on the main page of Efb 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: