4.7 sec in total
777 ms
3.2 sec
637 ms
Visit boston.gov now to see the best up-to-date Boston content for United States and also check out these interesting facts you probably never knew about boston.gov
Welcome to the official homepage for the City of Boston.
Visit boston.govWe analyzed Boston.gov page load time and found that the first response time was 777 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
boston.gov performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value6.2 s
11/100
25%
Value3.5 s
88/100
10%
Value1,110 ms
23/100
30%
Value0
100/100
15%
Value9.2 s
32/100
10%
777 ms
70 ms
8 ms
15 ms
14 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Boston.gov, 5% (3 requests) were made to S7.addthis.com and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (777 ms) relates to the external source Cityofboston.gov.
Page size can be reduced by 538.9 kB (69%)
786.5 kB
247.6 kB
In fact, the total size of Boston.gov main page is 786.5 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. 70% of websites need less resources to load. Javascripts take 629.5 kB which makes up the majority of the site volume.
Potential reduce by 120.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. 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 120.0 kB or 76% of the original size.
Potential reduce by 418.8 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 418.8 kB or 67% of the original size.
Number of requests can be reduced by 36 (58%)
62
26
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Boston. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.cityofboston.gov
777 ms
redirect.js
70 ms
reset-fonts-grids.css
8 ms
style.css
15 ms
foresee-trigger.js
14 ms
jquery.js
34 ms
script.js
33 ms
jq.js
42 ms
jquery.galleryview-2.0-pack.js
36 ms
jquery.timers-1.1.2.js
41 ms
jquery.easing.1.3.js
43 ms
galleryview.css
42 ms
addthis_widget.js
42 ms
ga.js
195 ms
bg_page_right.gif
192 ms
bg_page_left.gif
70 ms
bg_hd.jpg
59 ms
home_tcm3-709.jpg
73 ms
masthead.jpg
60 ms
nav_divider.gif
59 ms
bg_right.jpg
59 ms
bg_left.jpg
66 ms
dotted_line_blue.gif
58 ms
smush%20voting%20booth_tcm3-27876.jpg
59 ms
iconexternallink.gif
63 ms
economicequityagenda443_tcm3-52935.png
65 ms
cityscore_binary_443_tcm3-52914.jpg
58 ms
stateofthecity16_tcm3-52831.png
78 ms
VZConcerMapForSlider_tcm3-52653.png
69 ms
Garbage%20Truck%20(443)_tcm3-51603.jpg
63 ms
facebook40_tcm3-19887.png
69 ms
twitter40_tcm3-12370.png
63 ms
instagram40_tcm3-36282.png
65 ms
youtube40.png
65 ms
linkedin40_tcm3-30397.png
68 ms
sub_nav_header_bg_home.gif
69 ms
dotted_line_white.gif
69 ms
onlineservices311_service.png
69 ms
bg_button.gif
68 ms
sub_content_header_bg.gif
71 ms
translate_smushit.gif.png
69 ms
calendar_tcm3-702.gif
69 ms
bg_page_bottom.gif
72 ms
feedbackifylg.png
68 ms
facebook.png
67 ms
twitter.png
64 ms
reddit.png
64 ms
banner_nightpano.jpg
68 ms
fby.js
180 ms
clear.gif
86 ms
inpage_linkid.js
12 ms
__utm.gif
13 ms
vms.js
117 ms
_Incapsula_Resource
113 ms
300lo.json
31 ms
pdf.gif
23 ms
loader.gif
28 ms
foresee-surveydef.js
23 ms
sh.7c7179124ea24ac6ba46caac.html
93 ms
bc.pv
139 ms
_Incapsula_Resource
132 ms
layers.648fb6c882fbeb98be27.js
49 ms
foresee-dhtml.css
22 ms
boston.gov accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[role]s are not contained by their required parent element
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
boston.gov best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
boston.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
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 Boston.gov 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 Boston.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.
boston.gov
Open Graph description is not detected on the main page of Boston. 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: