3 ms·
Those tips are obviously worthwhile, but doesn't address massive scale for heavily dynamic sites. These should definitely be at the beginning of any optimizati
by bmelton 16y ago
Those tips are obviously worthwhile, but doesn't address massive scale for heavily dynamic sites. These should definitely be at the beginning of any optimization checklist for sure.
One thing I found interesting was his remark this:
Google Analytics failed to detect the surge: page load time was so high that visitors were closing the page before analytics could load.
He then remarks that it took Analytics 15 hours to detect the spike, but isn't that true of all Analytics instances? I'm not sure if the author is mistaking Google Analytics' delayed reporting as a fault or if I'm missing something.
- JoachimSchipper 16y agoThese tips are for people getting slashdotted, not people building the next Google. Your average blog simply isn't "heavily dynamic", and if you're building Google/Facebook/... there are better resources. Google Analytics is Javascript-based and thus vulnerable to people closing the page before it loads. It's actually near-realtime, but just doesn't work if you're having this problem. I'd imagine watching free Apache instances/threads, outgoing bandwidth or probably even the Apache logs would be more useful.
- jedsmith 16y ago> Google Analytics is Javascript-based and thus vulnerable to people closing the page before it loads. And people with Javascript disabled, which is a startling number. The disparity between reported views in Analytics and what I can observe from my Web server logs is amazingly large.
- JoachimSchipper 16y agoAre you sure those aren't bots? Analytics packages vary widely in their ability to filter out bots.
- jedsmith 16y agoBots have Javascript disabled too. :) You're right, of course. I considered it and started grepping them out, but got bored and did something else interesting. From a casual glance, there were a lot more Mozilla UAs than reported views, though.
- rsloan 16y agoWhile the reason Google Analytics failed at this has already been explained, GA Ecommerce tracking is near real-time, but not error corrected. Data in other parts can take several hours to show up, Google says to wait 24 hours for data to be complete and error corrected. Omniture SiteCatalyst is near-real time. I don't know if they do some error correction later like GA does for Ecommerce data.
- joelhaasnoot 16y agoGA data is delayed by a day, but if you adjust the date range manually, you can see the data that has come in so far. Not guaranteed to be complete, but some data.
- pdenya 16y agoGoogle Analytics updates hourly, reporting gives you only full days by default but you can see data much more up to date than that.