https://buy-zithromax.online buy kamagra usa https://antibiotics.top buy stromectol online https://deutschland-doxycycline.com https://ivermectin-apotheke.com kaufen cialis https://2-pharmaceuticals.com buy antibiotics online Online Pharmacy vermectin apotheke buy stromectol europe buy zithromax online https://kaufen-cialis.com levitra usa https://stromectol-apotheke.com buy doxycycline online https://buy-ivermectin.online https://stromectol-europe.com stromectol apotheke https://buyamoxil24x7.online deutschland doxycycline https://buy-stromectol.online https://doxycycline365.online https://levitra-usa.com buy ivermectin online buy amoxil online https://buykamagrausa.net

Cache as cache can

So one of my frustrations with Google Plus has been an inability to link to items on my blog from it.  When you do a link, G+ tries to actually load the file (to read the text, grab the images, etc.), unlike putting a link into Twitter or Facebook where it’s … well, just a link.  Which makes G+ more reliable in some ways, but more complicated.  And complications mean more places to break.

Including, for me, the inability to link to posts on my blog from Google Plus.

That led me to think that maybe my blog had some performance/latency problems. So I ran through some performance tools, including Google’s Page Speed  tool. Which then, in looking up some of the advisory tools, led me to the the W3 Total Cache WordPress plugin, which does all sorts of cache-y, performance-improving goodness.

And, it appears, it sped things up enough that I’m able to now post (at least once) from G+.

If you notice something wonky with the performance, images, etc., on the blog, please let me know.

73 view(s)  

5 thoughts on “Cache as cache can”

  1. Not in an automated fashion. The issue here was doing a link back to the blog through the Link function in G+. That seems to work fine for you (having tested it just now).

  2. So while I haven’t ever timed your blog’s load speed before, I’ve often found myself (and gotten into the habit of) clicking onto another tab window to read something else while waiting. This page, at least this morning, loaded quicker than I clicked away onto another tab. 😉

  3. Some experimenting today (and finding and excising some obsolete and nasssty Javascript) leaves me with a blog that is very slow to initial response — 12-15 seconds of “waiting for hill-kleerup.org/blog” followed by a very fast, non-lingering render.

    Need to keep at it.

Leave a Reply

Your email address will not be published. Required fields are marked *