2.1 sec in total
557 ms
1.3 sec
212 ms
Welcome to townhallsf.com homepage info - get ready to check Townhallsf best content for United States right away, or after learning these important things about townhallsf.com
Visit townhallsf.comWe analyzed Townhallsf.com page load time and found that the first response time was 557 ms and then it took 1.5 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.
townhallsf.com performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value4.3 s
43/100
25%
Value5.3 s
58/100
10%
Value200 ms
89/100
30%
Value0.005
100/100
15%
Value6.7 s
56/100
10%
557 ms
35 ms
45 ms
53 ms
53 ms
Our browser made a total of 35 requests to load all elements on the main page. We found that 43% of them (15 requests) were addressed to the original Townhallsf.com, 34% (12 requests) were made to Secure.opentable.com and 6% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (557 ms) belongs to the original domain Townhallsf.com.
Page size can be reduced by 742.9 kB (67%)
1.1 MB
363.2 kB
In fact, the total size of Townhallsf.com main page is 1.1 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. 60% of websites need less resources to load. Javascripts take 711.8 kB which makes up the majority of the site volume.
Potential reduce by 31.9 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 31.9 kB or 83% of the original size.
Potential reduce by 2.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. Townhallsf images are well optimized though.
Potential reduce by 495.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 495.4 kB or 70% of the original size.
Potential reduce by 213.6 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. Townhallsf.com needs all CSS files to be minified and compressed as it can save up to 213.6 kB or 82% of the original size.
Number of requests can be reduced by 17 (55%)
31
14
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Townhallsf. 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 from 7 to 1 for CSS and as a result speed up the page load time.
townhallsf.com
557 ms
A.libraries,,_gantry,,_css,,_grid-responsive.css+templates,,_gantry,,_css-compiled,,_bootstrap.css,Mcc.2Ivhp5Uvn8.css.pagespeed.cf.VSTYEwtV4T.css
35 ms
A.master-3f9b3006a7cc09dce4e52666572b7f73.css+mediaqueries.css+menu-3646dceb4af2439a7767ea7a2bd35b03.css,Mcc.Bn4EctM1cW.css.pagespeed.cf.iwWaXn3JJW.css
45 ms
jquery.min.js.pagespeed.jm.iDyG3vc4gw.js
53 ms
media,_jui,_js,_jquery-noconflict.js+media,_jui,_js,_jquery-migrate.min.js+media,_system,_js,_caption.js+media,_jui,_js,_bootstrap.min.js+libraries,_gantry,_js,_browser-engines.js+templates,_gantry,_js,_rokmediaqueries.js.pagespeed.jc.n9El_LwS-7.js
53 ms
mootools-core.js+core.js.pagespeed.jc.x86XZnoZG0.js
52 ms
mootools-more.js.pagespeed.jm.-6O1zP2hFm.js
52 ms
rokmediaqueries.js+sidemenu.js.pagespeed.jc.GmWCS8wRTP.js
52 ms
default.aspx
188 ms
css
34 ms
css
46 ms
dc.js
119 ms
xnoise.png.pagespeed.ic.fZk5z0K-7G.png
26 ms
xcookbook-button.png.pagespeed.ic.34WY8OzuhX.png
120 ms
cookbook.jpg.pagespeed.ce.4lXR9Vea_9.jpg
27 ms
xheader.png.pagespeed.ic.CcZkUXDlR4.png
26 ms
xlogo-print.png.pagespeed.ic.8N-juTjfLk.png
25 ms
ot_wide.css
23 ms
jquery-ui-1.8.11.custom.min.js
56 ms
thickbox.js
77 ms
thickbox.css
84 ms
jquery-ui-1.8.5.custom.css
85 ms
background-home.jpg
84 ms
pR0sBQVcY0JZc_ciXjFsKwAUTJOA6-irsSazDq377BE.ttf
72 ms
kH7K4InNTm7mmOXXjrA5v_gg4qM5Rpmu0ASAribBgqE.ttf
72 ms
fontawesome-webfont.woff
110 ms
s62412917166948
61 ms
__utm.gif
29 ms
jquery.scrollTo-min.js
59 ms
loading-animation.gif
32 ms
ba-postmessage.js
32 ms
CookieCheck.aspx
90 ms
ui-bg_flat_75_ffffff_40x100.png
10 ms
ScriptHandler.ashx
106 ms
CookieCheck.aspx
94 ms
townhallsf.com 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
townhallsf.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
townhallsf.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Townhallsf.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 Townhallsf.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.
townhallsf.com
Open Graph description is not detected on the main page of Townhallsf. 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: