3 ms·
Have an almost-static replacement index ready with just enough stuff for a php "give us your email address and we'll send you invites [and a discount or some ot
by iigs 18y ago
Have an almost-static replacement index ready with just enough stuff for a php "give us your email address and we'll send you invites [and a discount or some other bennie]". No CSS or JS on that alternate universe page. If things get nasty you'll want this to be as few keystrokes as possible, because it's possible to trash interactive response in the shell.
Maybe make a pass through your normal site with YSlow if you haven't already, but your site is super fast right now (2009-01-20 17:20pm PST), which is good news.
Also, if you're concerned about it still and you have another hosting option available, change your index.php to <? header("Location: http://www.temphosting.example.com http://www.temphosting.example.com"); die(); ?>, which is probably the smallest amount of cpu you can involve without getting dns moved.
Good luck.
- danielrhodes 18y agoYSlow only applies to browser rendering and sort of assumes you are able to get the page to the browser in the first place. Somehow I doubt client-side rendering is going to be the bottleneck. ;-)
- aschobel 18y agoIt also looks at if you use a CDN, which may help him.
- iigs 18y agoI was under the impression it checked page retrieval times, which (after subtracting for idle network latency) would reveal which pages were transferring slow because of excess computation or disk use on the server. The idea being if it's slow for one user it's going to be _really_ slow for 1000+. I've not more than installed and tried YSlow once, so I can't say too much about it.
- dkubb 18y agoYSlow's primary purpose is to help you make sure the browser renders each page in the minimum amount of time. However YSlow does not only apply to browser rendering, following 6 of the 13 YSlow rules will result in a reduction of the total work the server must perform for each request.