2.2 sec in total
86 ms
2 sec
64 ms
Visit afldc.org now to see the best up-to-date Afl DC content and also check out these interesting facts you probably never knew about afldc.org
In addition to serving as the representative entity in our nation's capital of the international Chabad-Lubavitch movement - and thus being directly responsible
Visit afldc.orgWe analyzed Afldc.org page load time and found that the first response time was 86 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
afldc.org performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value3.3 s
69/100
25%
Value7.0 s
32/100
10%
Value1,100 ms
23/100
30%
Value0.004
100/100
15%
Value19.2 s
2/100
10%
86 ms
30 ms
66 ms
72 ms
57 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Afldc.org, 26% (18 requests) were made to Static.parastorage.com and 18% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Static.wixstatic.com.
Page size can be reduced by 758.9 kB (60%)
1.3 MB
507.9 kB
In fact, the total size of Afldc.org main page is 1.3 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. 45% of websites need less resources to load. HTML takes 740.5 kB which makes up the majority of the site volume.
Potential reduce by 593.5 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 593.5 kB or 80% of the original size.
Potential reduce by 13.0 kB
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. Afl DC images are well optimized though.
Potential reduce by 152.4 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 152.4 kB or 38% of the original size.
Number of requests can be reduced by 11 (22%)
50
39
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Afl 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 as a result speed up the page load time.
www.jewishwashington.com
86 ms
minified.js
30 ms
focus-within-polyfill.js
66 ms
polyfill.min.js
72 ms
thunderbolt-commons.d1a46914.bundle.min.js
57 ms
main.e312dfc9.bundle.min.js
206 ms
main.renderer.1d21f023.bundle.min.js
56 ms
lodash.min.js
53 ms
react.production.min.js
204 ms
react-dom.production.min.js
227 ms
siteTags.bundle.min.js
225 ms
wix-perf-measure.umd.min.js
226 ms
c6e038_374d0c684b7542c085b0a573543343ba~mv2.png
388 ms
bundle.min.js
229 ms
c6e038_d84d58c0aee94e60877e3952c5b01b43~mv2.png
347 ms
c6e038_664ce4443160441db0435fbf9d635224~mv2.jpg
380 ms
c6e038_7e2bcba9795d4d36bb27106885e55c0d~mv2_d_6301_4201_s_4_2.jpg
401 ms
c6e038_8b8b1296923948d7b2fd00ffc8202d17~mv2_d_4288_2848_s_4_2.jpg
472 ms
c6e038_a283632d446d467fbbdf94d9423306a8~mv2.jpg
402 ms
c6e038_8781312f0f4243ef8ffb71f56aba790c~mv2.jpg
558 ms
c6e038_d21db1e546404aac83d42608a82fcf91~mv2.jpg
629 ms
c6e038_31f82d2d8b894b82a6f41772031bc1f6~mv2.jpg
508 ms
c6e038_07a4d71530e0460ea68f2f48986e4f9b~mv2.jpg
659 ms
c6e038_fdc3ae3640c3432a81ce37e5ab1896db~mv2.jpg
623 ms
c6e038_5c802e2861094fc0a08c63ab5a8b62c6~mv2.jpg
618 ms
c6e038_0c64a90002d24517b9465d81404a0a61~mv2_d_4288_2848_s_4_2.jpg
804 ms
c6e038_b50ff31edac9482da10563495a435b24~mv2.jpg
713 ms
c6e038_832e57f35fcd4d1cbb802e4143d90f91~mv2.webp
773 ms
c6e038_545229f4d40d49d0a89fb3a8d96d1d15~mv2.jpg
774 ms
c6e038_a9833babc8ee48a6860d2adb3abd4a5a~mv2_d_2100_1509_s_2.jpg
857 ms
c6e038_d58f4d0446d4457788a4111fda0f8111~mv2_d_2304_1728_s_2.jpg
928 ms
c6e038_d3b45be474fb4e2e995b1978d4ab99a8~mv2.jpg
985 ms
c6e038_c7a7b00eec6f4464bc60ab7206fed7de~mv2.jpg
987 ms
c6e038_5dc65e8f24e847dca21d1d4bef84d200~mv2.jpg
1116 ms
c6e038_71c9cb9d658a47a48cead18d97fa4bd8~mv2.jpg
980 ms
c6e038_fee964a18f9e49ea978d8c7f3f1940cf~mv2_d_3906_1536_s_2.jpg
1123 ms
JLI_edited.png
1054 ms
Navy%20and%20blue%20logo_edited.png
1219 ms
CGI_edited.png
1200 ms
c6e038_0744b6ccbbbb4164a7cfa4b0cf02bfde~mv2.png
1205 ms
CSCG-Logo_edited.png
1286 ms
cyp-mark-cropped_edited.png
1320 ms
c6e038_6037d080b11e410183f3d772199897d4~mv2.png
1378 ms
c6e038_f59d76929fcd4c3da5f6062a65959891~mv2_d_1534_1859_s_2.png
1389 ms
Untitled%20design%20(1)_edited.png
1210 ms
c6e038_6037810d421b423fbf4cf6e3f8c0dbfe~mv2_d_3800_4000_s_4_2.png
1438 ms
c6e038_11311ed8767e4943a22db8a9a7475c22~mv2.png
1435 ms
908c4810-64db-4b46-bb8e-823eb41f68c0.woff
39 ms
61bd362e-7162-46bd-b67e-28f366c4afbe.woff
5 ms
118 ms
109 ms
112 ms
110 ms
110 ms
107 ms
147 ms
146 ms
145 ms
143 ms
142 ms
134 ms
deprecation-en.v5.html
7 ms
bolt-performance
35 ms
deprecation-style.v5.css
6 ms
right-arrow.svg
27 ms
WixMadeforDisplay_W_Bd.woff
6 ms
WixMadeforText_W_Bd.woff
4 ms
WixMadeforText_W_Rg.woff
6 ms
afldc.org 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.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
afldc.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
afldc.org SEO score
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 Afldc.org 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 Afldc.org 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.
afldc.org
Open Graph data is detected on the main page of Afl DC. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: