2.7 sec in total
360 ms
2.1 sec
302 ms
Visit columbus.co now to see the best up-to-date Columbus content for United States and also check out these interesting facts you probably never knew about columbus.co
Visit columbus.coWe analyzed Columbus.co page load time and found that the first response time was 360 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
columbus.co performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value8.3 s
2/100
25%
Value5.7 s
52/100
10%
Value120 ms
97/100
30%
Value0.201
62/100
15%
Value7.9 s
43/100
10%
360 ms
332 ms
136 ms
135 ms
136 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 84% of them (49 requests) were addressed to the original Columbus.co, 12% (7 requests) were made to Columbuscommunications.com and 2% (1 request) were made to Yui.yahooapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Columbus.co.
Page size can be reduced by 267.7 kB (11%)
2.5 MB
2.3 MB
In fact, the total size of Columbus.co main page is 2.5 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. 35% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 17.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 17.7 kB or 77% of the original size.
Potential reduce by 99.6 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. Columbus images are well optimized though.
Potential reduce by 109.9 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 109.9 kB or 70% of the original size.
Potential reduce by 40.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. Columbus.co needs all CSS files to be minified and compressed as it can save up to 40.5 kB or 81% of the original size.
Number of requests can be reduced by 19 (34%)
56
37
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Columbus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
columbus.co
360 ms
mootools-core.js
332 ms
core.js
136 ms
caption.js
135 ms
system.css
136 ms
general.css
136 ms
reset-min.css
8 ms
main.css
190 ms
subpage.css
261 ms
960_24_col.css
267 ms
typography.css
266 ms
jquery.jscrollpane.css
267 ms
jquery.fancybox-1.3.4.css
324 ms
jquery.min.js
32 ms
jquery.nicescroll.js
393 ms
main.js
395 ms
jquery.mousewheel.js
396 ms
jquery.jscrollpane.min.js
399 ms
jquery.jscrollpane.lozenge.css
452 ms
jquery.fancybox-1.3.4.pack.js
459 ms
jquery.easing.1.3.js
525 ms
cloud-carousel.1.0.5.js
528 ms
system.css
181 ms
bg_image.png
813 ms
article_watch.png
298 ms
c&w_logo.png
303 ms
header_bg.png
196 ms
searchButton.png
132 ms
columbus_logo.png
200 ms
menu_image_01.png
138 ms
menu_image_02.png
136 ms
menu_image_03.png
269 ms
menu_image_04.png
270 ms
menu_image_05.png
269 ms
transp_white.png
325 ms
prev2.png
334 ms
next2.png
398 ms
map_rect2.jpg
784 ms
cInternational_rect.png
666 ms
flow_carousel.png
589 ms
cNetworks_rect.png
732 ms
cBusiness_rect.png
795 ms
articles_bg.png
923 ms
whats_new_bg.png
931 ms
bg_main.png
1130 ms
bg_main_inner2.png
916 ms
bg_main_line.png
921 ms
quick_facts_bg.png
995 ms
footer_bg.png
1052 ms
footer_li_bg.png
1051 ms
MEF-logo.png
1052 ms
article_talk.png
276 ms
article_click.png
275 ms
article_capacity.png
272 ms
article_data.png
275 ms
article_solutions.png
276 ms
map_thumb2.jpg
599 ms
vistasansot-med-webfont.woff
1131 ms
columbus.co accessibility score
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
<object> elements do not have alternate text
columbus.co 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
columbus.co 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
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 Columbus.co 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 Columbus.co 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.
columbus.co
Open Graph description is not detected on the main page of Columbus. 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: