Thanks for the feedback.  I fixed the focus issue, and I&#x27;ll look into the keystroke&#x2F;mouse handling.<p>As for load times, I never stated that the initial load time was fast - I said that the latency was low.  As you say, combining the JS into the actual HTML file would improve it even further.<p>Yes, the server doesn&#x27;t support gzip yet, but will soon.  It&#x27;s basically our &quot;here&#x27;s a web server to get you started&quot; web server that we include with the product, but you can use any web server that you want.  We actually didn&#x27;t even plan on including one, but you know how plans go..... :-)<p>The JSON isn&#x27;t cacheable, exactly, because it&#x27;s the result of a database query.  So, the response time you&#x27;re seeing includes setup&#x2F;teardown time for the database connection, etc.  Again, this isn&#x27;t production-level stuff here, just a one-off coded to show something in particular.<p>As for the loading of the &quot;United States&quot;: the server request is actually very fast, but the loading of the JSON takes some time.  We do custom JSON parsing in order to validate the JSON properly and allow for missing column values.  We investigated the built-in JSON parsing, but we are still left with the same issues in terms of finding whether certain column values exist in the resultant JS objects, and would end up using almost twice as much memory because the resultant JS objects would still need to be copied into different target structures.