1.8 sec in total
122 ms
1.3 sec
329 ms
Welcome to columbus.gov homepage info - get ready to check Columbus best content for United States right away, or after learning these important things about columbus.gov
Welcome to the new Columbus.gov! We are thrilled to present a revamped digital experience that caters to the needs of all users. Discover a website that offers improved access to valuable information ...
Visit columbus.govWe analyzed Columbus.gov page load time and found that the first response time was 122 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 30% of websites can load faster.
columbus.gov performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value16.5 s
0/100
25%
Value4.6 s
70/100
10%
Value430 ms
65/100
30%
Value0.127
82/100
15%
Value6.6 s
58/100
10%
122 ms
388 ms
56 ms
233 ms
164 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 77% of them (41 requests) were addressed to the original Columbus.gov, 8% (4 requests) were made to Translate.googleapis.com and 6% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (480 ms) belongs to the original domain Columbus.gov.
Page size can be reduced by 149.1 kB (9%)
1.6 MB
1.5 MB
In fact, the total size of Columbus.gov main page is 1.6 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 1.3 MB which makes up the majority of the site volume.
Potential reduce by 55.0 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 19.2 kB, which is 30% 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 55.0 kB or 86% of the original size.
Potential reduce by 93.2 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 820 B
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 83 B
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.gov has all CSS files already compressed.
Number of requests can be reduced by 15 (31%)
49
34
The browser has sent 49 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 8 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
columbus.gov
122 ms
www.columbus.gov
388 ms
ektron.stylesheet.ashx
56 ms
ektron.javascript.ashx
233 ms
main.css
164 ms
main.js
123 ms
gtm.js
177 ms
noisepatternBg.jpg
140 ms
facebook-header-icon.png
149 ms
twitter-header-icon.png
149 ms
youtube-header-icon.png
150 ms
mobile-header-icon.png
149 ms
311logo195pixels.jpg
200 ms
GetGreen_RGB_Icon.jpg
241 ms
311onmobile.png
199 ms
Ginther_smaller.jpg
200 ms
2%20for%20web.jpg
462 ms
scalesofjustice.jpg
274 ms
WarriorWatch.png
250 ms
WarriorWatch_Rotator3.jpg
274 ms
1.jpg
434 ms
AJG-headshot-small.png
349 ms
01527_lr.jpg
358 ms
Alert_LOGO%20white%20to%20grayV2%20for%20home%20page.png
446 ms
mobApp.png
317 ms
ctv.png
371 ms
facebook-footer-icon.png
438 ms
twitter-footer-icon.png
441 ms
youtube-footer-icon.png
443 ms
mobile-footer-icon.png
445 ms
mycolumbus-foo.png
456 ms
ctv-footer-icon.png
455 ms
logo.png
437 ms
search.png
439 ms
sliderShadow.png
442 ms
usWatermark.png
479 ms
usStar.png
474 ms
starRedBg.jpg
480 ms
ufonts.com_gotham_medium-webfont.woff
365 ms
ufonts.com_gotham_book-webfont.woff
378 ms
element.js
91 ms
themes.png
356 ms
analytics.js
58 ms
collect
9 ms
collect
56 ms
translateelement.css
63 ms
main.js
74 ms
collect
24 ms
element_main.js
40 ms
translate_24dp.png
78 ms
l
45 ms
cleardot.gif
56 ms
print.css
54 ms
columbus.gov 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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
columbus.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
columbus.gov SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Columbus.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 Columbus.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.
columbus.gov
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: