3 ms·

Being on Dreamhost without the option to move in the limited time, these are your options that I can personally think of: - Cache the hell out of everything.

Being on Dreamhost without the option to move in the limited time, these are your options that I can personally think of: - Cache the hell out of everything. - Fix links to broken JS includes. On http://store.wonderwarp.com http://store.wonderwarp.com you link to https://store.wonderwarp.com/mint/?js https://store.wonderwarp.com/mint/?js which does not exist and wastes valuable processing time only to error out. - Pack and minimize your CSS/JS files, even just temporarily. If you are dead sure this is going to be a lot of people, every small bit of saved bytes helps! That's all I can think of since you've already moved the downloads to S3. Your site is mostly heavy on the static content anyways so not much you can do unless you stripped it down, but I would say keep it as it is because it looks great. Regardless, if your site does go down think of it as a victory. You got so much traffic (and probably sales) to knock you down that you can only become better for the next time you get press. If it's a good product, it will happen again and again :)

drm237 18y ago
If you can, also move all of your static content to S3 including every image, css, and js file. You're currently serving ~47 requests per user to load the home page. If you move all of your static stuff to s3, each client makes 1 maybe 2 requests to your server instead of 47. If you're using apache, any content, including static files, has a huge memory overhead to serve. Also, because you're not setting far-futures expires headers, users have to check for every static item every time just to get a 304 not modified. Last bit of advice, get firebug http://getfirebug.com/ http://getfirebug.com/ and add yslow http://developer.yahoo.com/yslow/ http://developer.yahoo.com/yslow/.
aschobel 18y ago
We have had decent luck with <a href="http://aws.amazon.com/cloudfront/ http://aws.amazon.com/cloudfront/">Amazon's CDN CloudFront</a>. If you already use S3 it is pretty easy to configure CloudFront and make sure your users have a speedy experience.

drm237 18y ago

If you can, also move all of your static content to S3 including every image, css, and js file. You're currently serving ~47 requests per user to load the home page. If you move all of your static stuff to s3, each client makes 1 maybe 2 requests to your server instead of 47. If you're using apache, any content, including static files, has a huge memory overhead to serve. Also, because you're not setting far-futures expires headers, users have to check for every static item every time just to get a 304 not modified. Last bit of advice, get firebug http://getfirebug.com/ http://getfirebug.com/ and add yslow http://developer.yahoo.com/yslow/ http://developer.yahoo.com/yslow/.

aschobel 18y ago

We have had decent luck with <a href="http://aws.amazon.com/cloudfront/ http://aws.amazon.com/cloudfront/">Amazon's CDN CloudFront</a>. If you already use S3 it is pretty easy to configure CloudFront and make sure your users have a speedy experience.