Yup. Briefly detailing that first image:
Your page was loaded enough to start requesting tag data at the line with the yellow highlight: that looks like it’s around the 1.5 second mark? You can drill down at get more information if you click on any of the lines and select the Timing tab. For example:
The pink-highlighted lines indicate that you’re using image indicators: we try and pre-load all of the images in an indicate so that there’s no hiccup drawing them later as values change. Those don’t load until the page has rendered though, so it shouldn’t affect the initial load time.
I forgot to mention this, but response parsing time can also have a heavy effect. Again using my New York instance as an example, it takes about 435ms to download the list of pages from the server, but then another 877 ms to parse them all out. (That’s mostly what groov’s doing when it shows “Loading Pages…”.) You can find those details in Chrome’s Performance tab:
All this is to say: yes, we can be faster, and we already know a few places to tackle, we just haven’t gotten the time yet.