In my experience IPFS is only fast when you're using it through something like Cloudflare's IPFS proxy (which is basically a caching proxy). I haven't found IPFS to be actually usable any time I've tried running a node myself. Especially pinning anything beyond the most trivial of examples.
For a start, newer versions of IPFS work much better, but the network still had a significant amount of older nodes making the experience worse for everyone. Luckily, this is changing as of late, it seems.
IPFS shines when it can take advantage of content proximity (i.e. in your LAN, in your node etc.) or when there are few providers for the content within reach, at which point it just works regardless of connectivity to the outside world.
In a general scenario, comparing IPFS-delivery speed with a CDN-backed website is not very fair. Might be slower but offers much more versatility.
1) First it loads it through a proxy, then shows me button to enable a local node
2) When I click that button, I then get a page with "Connection Refused" talking to localhost
3) After a few more seconds, the page reloads I get the actual IPFS page
I am guessing with (2) the local node is being a bit slow to start. (I am using a 2013 MBP.) Ideally it would display some kind of "please wait node starting..." message at (2) rather than a connection refused error
