Timeline for Enabling compression in WARP Framework template
Current License: CC BY-SA 3.0
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Aug 8, 2016 at 16:04 | vote | accept | Gregory | ||
Aug 7, 2016 at 13:11 | comment | added | Gregory | DNS lookup times are negligible, so it's OK. | |
Aug 7, 2016 at 13:06 | comment | added | Neil Robertson | I do the same thing but usually use GTMetrix. Apparently tests are not cached but subsequent tests may run a little faster due to the DNS lookup being cached. | |
Aug 7, 2016 at 12:49 | comment | added | Gregory | I usually go to website speed testing sites like pingdom etc. Let's say, I wanna run two tests. The first with compression enabled and the second with it being disabled, OK? BUT... what about CACHE on pingdom's server? I can't clear it myself on THEIR server, right? So what MIGHT happen is that the second test would come from that server's cache, so the test overall won't be reliable. Or maybe their systems clear their cache after each test, who knows... | |
Aug 7, 2016 at 12:40 | comment | added | Neil Robertson | Good question. I usually err on the side of caution and only enable GZip once. There's no point GZipping twice and this might actually affect performance adversely. | |
Aug 7, 2016 at 12:30 | comment | added | Gregory | The difference is the number of requests. Without it being enabled there was about 120, and with it being enabled around 90. As per page loading times... The improvement is at best around 10-15%. And the last thing I wanna know is this...I know there's an Apache GZip compression (it's not enabled on my server). If I use what I mentioned in my first post, is it best to keep Apache's compression disabled? In other words, what's the difference between Joomla's compression and Apache's compression and how they can or can't co-exist? | |
Aug 7, 2016 at 0:25 | history | answered | Neil Robertson | CC BY-SA 3.0 |