Is this solely due to content delivery speeds? Or, was the prior slowness due in part to producing dynamic content? Congrats on the change, getting your page to appear more quickly on the users screen is hugely beneficial.
Most of the content is read-only, so we really had no excuse for it being slow. Previously we relied on .NET object caching which created issues due to the way dependencies were structured. Even if we were to solve that problem (which is solvable), Akamai would have presented a better performance gain to us.