2.1 sec in total
125 ms
1.4 sec
531 ms
Welcome to comsource.com homepage info - get ready to check Comsource best content right away, or after learning these important things about comsource.com
Serving the needs of homeowner associations, condominium associations and cooperatives throughout the Washington DC, Maryland and Northern Virginia area for over 40 years. Comsource Management is a fu...
Visit comsource.comWe analyzed Comsource.com page load time and found that the first response time was 125 ms and then it took 2 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.
comsource.com performance score
name
value
score
weighting
Value2.8 s
57/100
10%
Value3.0 s
78/100
25%
Value9.8 s
10/100
10%
Value140 ms
95/100
30%
Value0.174
69/100
15%
Value13.0 s
12/100
10%
125 ms
310 ms
22 ms
40 ms
127 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 73% of them (53 requests) were addressed to the original Comsource.com, 19% (14 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (670 ms) belongs to the original domain Comsource.com.
Page size can be reduced by 943.2 kB (8%)
11.8 MB
10.9 MB
In fact, the total size of Comsource.com main page is 11.8 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. 80% 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 11.5 MB which makes up the majority of the site volume.
Potential reduce by 48.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. This page needs HTML code to be minified as it can gain 16.3 kB, which is 29% 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 48.7 kB or 85% of the original size.
Potential reduce by 813.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. Comsource images are well optimized though.
Potential reduce by 55.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 55.4 kB or 24% of the original size.
Potential reduce by 26.1 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. Comsource.com needs all CSS files to be minified and compressed as it can save up to 26.1 kB or 34% of the original size.
Number of requests can be reduced by 29 (53%)
55
26
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Comsource. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
comsource.com
125 ms
comsource.com
310 ms
css
22 ms
css
40 ms
bootstrap.min.css
127 ms
font-awesome.min.css
178 ms
animate.min.css
182 ms
prettyPhoto.css
180 ms
jquery.datetimepicker.css
183 ms
bxslider.css
183 ms
color.css
186 ms
style.css
298 ms
js
61 ms
modernizr.custom.js
241 ms
jquery.min.js
400 ms
imagesloaded.pkgd.min.js
190 ms
jquery-ui.min.js
401 ms
jquery.ui.touch-punch.min.js
192 ms
isotope.pkgd.min.js
401 ms
bootstrap.min.js
402 ms
classie.js
400 ms
waypoints.min.js
401 ms
jquery.countTo.js
402 ms
jquery.prettyPhoto.js
402 ms
wow.min.js
402 ms
jquery.datetimepicker.js
404 ms
placeholders.js
402 ms
jquery.bxslider.min.js
403 ms
owl.carousel.min.js
403 ms
custom.js
403 ms
master.js
444 ms
adally.js
18 ms
logo.png
170 ms
1_sm.png
558 ms
2_sm.png
502 ms
1.png
507 ms
commcondo.jpg
246 ms
home.png
504 ms
finman.jpg
389 ms
trans.jpg
315 ms
aamc-logo.jpg
377 ms
cai_logo.jpg
437 ms
bbb_logo.png
451 ms
3.png
670 ms
4.png
632 ms
blog.png
566 ms
res.png
567 ms
about.jpg
567 ms
stat.jpg
620 ms
boxedb.png
628 ms
01.jpg
628 ms
calltoaction.jpg
632 ms
boxedw.png
563 ms
logo_w.png
567 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISWaA.ttf
31 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSWaA.ttf
31 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojIWWaA.ttf
117 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4OWaA.ttf
32 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf
34 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf
32 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf
34 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf
35 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf
39 ms
fontawesome-webfont.woff
565 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVc.ttf
38 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkaVc.ttf
35 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjaVc.ttf
38 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjaVc.ttf
38 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjaVc.ttf
39 ms
webfont.js
48 ms
bx_loader.gif
447 ms
controls.png
449 ms
css
69 ms
comsource.com 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
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.
comsource.com 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
comsource.com 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
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 Comsource.com 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 Comsource.com 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.
comsource.com
Open Graph description is not detected on the main page of Comsource. 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: