Re: [Radiant] How to improve site performance?
Thanks for the tips Charles, Sean, et al. Yeah, I saw mod_deflate in our list of Apache modules, but ahem, I don't see any initialization code so it's definitely on my todo list (as well as concat/minify JS, mod_expires, etc.,etc.) However, I should mention that just setting the radiant cache to 24 hours alone has made a huge impact in perceived performance. So much so, that I can probably punt for a few weeks on some of the other performance related adjustments. Of interesting note (for someone else who may be about to reset the cache) it really seems that the default Radiant caching wasn't happening at all (before I made the change). I'm inclined to say that this was somehow our fault (wish I knew exactly why) and not Radiant's. That being said, after making the appropriate changes to /config/environment.rb in the config after init block (see older post in this thread for exact syntax details) it is definitely kicking in and working great. Of interest: passenger will use the /config/environment.rb file's permissions to start Rails instance(s) as this user, unless, the file is set to root, in which case it will set the rails instance(s) to user nobody. This comes from the Passenger docs. Who cares? Well, we had to chown the /tmp dir recursively to user nobody (the directory that radiant uses to cache). Before doing so, we had http 500 internal server errors. This is more a unix permissions thing than a radiant thing, but it's in the context so I mention it as forewarning. On Sun, Jan 3, 2010 at 6:46 PM, Charles Roper reac...@charlesroper.co.ukwrote: On 29/12/2009 03:16, Rob Levin wrote: Thanks all, you've given me a lot excellent information to work with and I appreciate it! Rob, I've just run YSlow on your site and a suggestion it comes up with is to gzip your content: Compression reduces response times by reducing the size of the HTTP response. Gzip is the most popular and effective compression method currently available and generally reduces the response size by about 70%. Approximately 90% of today's Internet traffic travels through browsers that claim to support gzip. You've got quite a lot of JS and CSS in there, so gzipping could work quite well. YSlow makes several other suggestions that could be worth looking into: https://addons.mozilla.org/en-US/firefox/addon/5369 I've used Heroku for Radiant sites and they employ Varnish, which seems to work exceedingly well for keeping things flying: http://docs.heroku.com/http-caching http://varnish.projects.linpro.no/ Some further good stuff on caching, if you're interested: http://tomayko.com/writings/things-caches-do http://www.mnot.net/cache_docs/ Charles ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to improve site performance?
Of interest: passenger will use the /config/environment.rb file's permissions to start Rails instance(s) as this user, unless, the file is set to root, in which case it will set the rails instance(s) to user nobody. This comes from the Passenger docs. Who cares? Well, we had to chown the /tmp dir recursively to user nobody (the directory that radiant uses to cache). Before doing so, we had http 500 internal server errors. This is more a unix permissions thing than a radiant thing, but it's in the context so I mention it as forewarning. I usually set up an instance as a neutral deploy user, or chown the whole deployment tree to the www-data user (Apache). Although it's slightly harder to execute arbitrary code in a Rails app than a typical PHP app, it's still smart to sandbox when possible. Sean ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to improve site performance?
In addition to mod_deflate, I usually add mod_expires with a far-future default and use the FileETag directive. These will also help with overall load time. If you need Radiant to push out the cached page faster, look into mod_xsendfile, which tells Apache to stream the page from disk instead of through Ruby. Sean On Tuesday, December 29, 2009, Rob Levin roblevinten...@gmail.com wrote: Concerning the setting the timeout link: http://groups.google.com/group/radiantcms/msg/01ac040dbcf76479 I thought I should add (in case someone is following this thread that needs to do this) that you have to put it in the callback block for after radiant has finished it's initialization (at the end of the config/environment.rb file): config.after_initialize do # Timeout cache every 24 hours SiteController.cache_timeout = 24.hours After adding ran script/console to confirm: SiteController.cache_timeout 86400 seconds Also using page speed in addition to yslow. Not yet doing the compression/minification but that's on the todo list. Thanks all for the wonderful suggestions yesterday! Rob John Mohit: make sure you are not serving css and/or js from radiant I have my styles and js in RADIANT_ROOT/public/stylesheet /javascripts respectively. Is that correct? It's my understanding that Apache will serve anything under /public right? that's right page parts Well we are using layouts, snippets, parts, etc., pretty heavily. Is this specific to page parts or are snippets, layouts, etc., also hot spots? they require additional database access. however if your database is properly tuned it's generally not much of an issue. it's just something i've noticed on the few apps i track with new relic rpm; in nearly all of them PagePart#find is the most time consuming transaction except in apps that use paperclipped and in that case Asset#find is the slowest. Here's the live site: http://www.snaplogic.com/ the x-runtime header (for the homepage) says 457ms (which is a pretty insignificant part of your total response time) is spent in the rails process so you're likely going to get much more bang for your buck by starting with generic optimizations rather that digging too deeply into radiant (e.g. reducing use of snippets or page parts). a tool like the yslow addon for firefox might help get you started: https://addons.mozilla.org/en-US/firefox/addon/5369. Thanks for the great help all! On Mon, Dec 28, 2009 at 4:54 PM, john muhl johnm...@gmail.com wrote: oh and i'd think 300-400ms or less spent inside the rails process would be sufficient for all but the most performance critical applications since your web server should be able to serve the rest of your page (static assets, css, js) in less than 100ms On Mon, Dec 28, 2009 at 6:49 PM, john muhl johnm...@gmail.com wrote: some things that come to mind immediately: - make sure you are not serving css and/or js from radiant - make sure you have mod_deflate setup up to compress all text files - avoid excessive use of page parts - avoid using paperclipped or page_attachments for design assets (like your logo or icons or things that don't need to be managed by your content editors) On Mon, Dec 28, 2009 at 6:20 PM, Rob Levin roblevinten...@gmail.com wrote: I've just started working at a place that is using Radiant for it's web site and I've noticed our general pages are usually somewhere around 150kb and take, on my system, around 800ms. FWIW, just now dslreports showed my download speed (on my client box) avg at around 5000Kb. Since it's a small start-up I'm going to be the one to further tune site's performance. That being said, I'm not a sysadmin nor do I have experience in this sort of thing (disclaimer). We are using Radiant version 0.8.1 with Apache/2.0.52 (Red Hat) Server on RH4 (don't ask) and using Passenger with ruby enterprise edition: 1.8.6 (2008-08-11 patchlevel 287) Ruby Enterprise Edition 20090610. We have our own dev server but for production we're using server beach. Looking at our Radiant instance's /config/environment.rb file I noticed the following line so it looks like Radiant caching is on right? config.middleware.use ::Radiant::Cache ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] How to improve site performance?
I've just started working at a place that is using Radiant for it's web site and I've noticed our general pages are usually somewhere around 150kb and take, on my system, around 800ms. FWIW, just now dslreports showed my download speed (on my client box) avg at around 5000Kb. Since it's a small start-up I'm going to be the one to further tune site's performance. That being said, I'm not a sysadmin nor do I have experience in this sort of thing (disclaimer). We are using Radiant version 0.8.1 with Apache/2.0.52 (Red Hat) Server on RH4 (don't ask) and using Passenger with ruby enterprise edition: 1.8.6 (2008-08-11 patchlevel 287) Ruby Enterprise Edition 20090610. We have our own dev server but for production we're using server beach. Looking at our Radiant instance's /config/environment.rb file I noticed the following line so it looks like Radiant caching is on right? config.middleware.use ::Radiant::Cache So my questions are: What would be a checklist of things that may be degrading our site's performance? Besides generally reducing http calls and sizes, what Radiant specific stuff can I do to speed things up? Even links to relevant Radiant docs would be helpful. What would be a good time per size metric to shoot for? Thanks all! ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to improve site performance?
Rob Levin wrote: I've just started working at a place that is using Radiant for it's web site and I've noticed our general pages are usually somewhere around 150kb and take, on my system, around 800ms. FWIW, just now dslreports showed my download speed (on my client box) avg at around 5000Kb. Since it's a small start-up I'm going to be the one to further tune site's performance. That being said, I'm not a sysadmin nor do I have experience in this sort of thing (disclaimer). We are using Radiant version 0.8.1 with Apache/2.0.52 (Red Hat) Server on RH4 (don't ask) and using Passenger with ruby enterprise edition: 1.8.6 (2008-08-11 patchlevel 287) Ruby Enterprise Edition 20090610. We have our own dev server but for production we're using server beach. Looking at our Radiant instance's /config/environment.rb file I noticed the following line so it looks like Radiant caching is on right? config.middleware.use ::Radiant::Cache So my questions are: What would be a checklist of things that may be degrading our site's performance? Besides generally reducing http calls and sizes, what Radiant specific stuff can I do to speed things up? Even links to relevant Radiant docs would be helpful. What would be a good time per size metric to shoot for? Thanks all! Are you trying to reduce the 150KB or the 800ms? If you're after the size, you'll need to look at the content more closely - there are probably stylesheets and JS files that are larger. You may need to minify them - I think the SnS extension (or one of its cousins) does that: http://ext.radiantcms.org/extensions/53-sns If you're after the time, I'm not sure where the time is going - you will probably need to see the logs to see where the time is being spent. Are you using many extensions? Are your pages being populated as a result of many queries (database and/ or HTTP)? Finally, you can change the page caching time to a much larger value compared to the default 5 minutes if your pages can manage it. Remember that a page you edit will be expired from cache when you edit it and all pages are expired from cache when the site basics (snippets, layouts, etc.) are changed [if I remember correctly]. Lastly, others may be able to help a bit more if you point us to the website :D Cheers, Mohit. 12/29/2009 | 8:41 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to improve site performance?
Mohit Sindhwani wrote: Rob Levin wrote: I've just started working at a place that is using Radiant for it's web site and I've noticed our general pages are usually somewhere around 150kb and take, on my system, around 800ms. FWIW, just now dslreports showed my download speed (on my client box) avg at around 5000Kb. Since it's a small start-up I'm going to be the one to further tune site's performance. That being said, I'm not a sysadmin nor do I have experience in this sort of thing (disclaimer). We are using Radiant version 0.8.1 with Apache/2.0.52 (Red Hat) Server on RH4 (don't ask) and using Passenger with ruby enterprise edition: 1.8.6 (2008-08-11 patchlevel 287) Ruby Enterprise Edition 20090610. We have our own dev server but for production we're using server beach. Looking at our Radiant instance's /config/environment.rb file I noticed the following line so it looks like Radiant caching is on right? config.middleware.use ::Radiant::Cache So my questions are: What would be a checklist of things that may be degrading our site's performance? Besides generally reducing http calls and sizes, what Radiant specific stuff can I do to speed things up? Even links to relevant Radiant docs would be helpful. What would be a good time per size metric to shoot for? Thanks all! Are you trying to reduce the 150KB or the 800ms? If you're after the size, you'll need to look at the content more closely - there are probably stylesheets and JS files that are larger. You may need to minify them - I think the SnS extension (or one of its cousins) does that: http://ext.radiantcms.org/extensions/53-sns If you're after the time, I'm not sure where the time is going - you will probably need to see the logs to see where the time is being spent. Are you using many extensions? Are your pages being populated as a result of many queries (database and/ or HTTP)? Finally, you can change the page caching time to a much larger value compared to the default 5 minutes if your pages can manage it. Remember that a page you edit will be expired from cache when you edit it and all pages are expired from cache when the site basics (snippets, layouts, etc.) are changed [if I remember correctly]. Lastly, others may be able to help a bit more if you point us to the website :D ... and I think it's good practice to have your style sheets not stored in the database, save them to the file system directly so that there is no overhead every time a style sheet is requested - but that is a tradeoff between simplicity (you/ your designer can edit it directly through the Radiant interface) and performance (no Radiant involved in serving it up, straight from Apache). Cheers, Mohit. 12/29/2009 | 8:48 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to improve site performance?
some things that come to mind immediately: - make sure you are not serving css and/or js from radiant - make sure you have mod_deflate setup up to compress all text files - avoid excessive use of page parts - avoid using paperclipped or page_attachments for design assets (like your logo or icons or things that don't need to be managed by your content editors) On Mon, Dec 28, 2009 at 6:20 PM, Rob Levin roblevinten...@gmail.com wrote: I've just started working at a place that is using Radiant for it's web site and I've noticed our general pages are usually somewhere around 150kb and take, on my system, around 800ms. FWIW, just now dslreports showed my download speed (on my client box) avg at around 5000Kb. Since it's a small start-up I'm going to be the one to further tune site's performance. That being said, I'm not a sysadmin nor do I have experience in this sort of thing (disclaimer). We are using Radiant version 0.8.1 with Apache/2.0.52 (Red Hat) Server on RH4 (don't ask) and using Passenger with ruby enterprise edition: 1.8.6 (2008-08-11 patchlevel 287) Ruby Enterprise Edition 20090610. We have our own dev server but for production we're using server beach. Looking at our Radiant instance's /config/environment.rb file I noticed the following line so it looks like Radiant caching is on right? config.middleware.use ::Radiant::Cache So my questions are: What would be a checklist of things that may be degrading our site's performance? Besides generally reducing http calls and sizes, what Radiant specific stuff can I do to speed things up? Even links to relevant Radiant docs would be helpful. What would be a good time per size metric to shoot for? Thanks all! ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to improve site performance?
oh and i'd think 300-400ms or less spent inside the rails process would be sufficient for all but the most performance critical applications since your web server should be able to serve the rest of your page (static assets, css, js) in less than 100ms On Mon, Dec 28, 2009 at 6:49 PM, john muhl johnm...@gmail.com wrote: some things that come to mind immediately: - make sure you are not serving css and/or js from radiant - make sure you have mod_deflate setup up to compress all text files - avoid excessive use of page parts - avoid using paperclipped or page_attachments for design assets (like your logo or icons or things that don't need to be managed by your content editors) On Mon, Dec 28, 2009 at 6:20 PM, Rob Levin roblevinten...@gmail.com wrote: I've just started working at a place that is using Radiant for it's web site and I've noticed our general pages are usually somewhere around 150kb and take, on my system, around 800ms. FWIW, just now dslreports showed my download speed (on my client box) avg at around 5000Kb. Since it's a small start-up I'm going to be the one to further tune site's performance. That being said, I'm not a sysadmin nor do I have experience in this sort of thing (disclaimer). We are using Radiant version 0.8.1 with Apache/2.0.52 (Red Hat) Server on RH4 (don't ask) and using Passenger with ruby enterprise edition: 1.8.6 (2008-08-11 patchlevel 287) Ruby Enterprise Edition 20090610. We have our own dev server but for production we're using server beach. Looking at our Radiant instance's /config/environment.rb file I noticed the following line so it looks like Radiant caching is on right? config.middleware.use ::Radiant::Cache So my questions are: What would be a checklist of things that may be degrading our site's performance? Besides generally reducing http calls and sizes, what Radiant specific stuff can I do to speed things up? Even links to relevant Radiant docs would be helpful. What would be a good time per size metric to shoot for? Thanks all! ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to improve site performance?
Mohit: Are you trying to reduce the 150KB or the 800ms? I assume we're going to hopefully improve by reducing the 150kb but I'd still like to proportionally decrease the load time if at all possible. change the page caching time to a much larger value compared to the default 5 minutes if your pages can manage it. Yes, I'm looking in to this. I'm almost positive we're just using the default. I agree that this may help a LOT! Does someone have a working example of setting: ResponseCache.defaults[:expire_time] or whatever? That would be very helpful. John Mohit: make sure you are not serving css and/or js from radiant I have my styles and js in RADIANT_ROOT/public/stylesheet /javascripts respectively. Is that correct? It's my understanding that Apache will serve anything under /public right? make sure you have mod_deflate setup up to compress all text files Yeah, I need to look into this! I do see it listed mod_deflate.so in our modules directory but I have to see if it's been properly loaded, etc. Thanks. page parts Well we are using layouts, snippets, parts, etc., pretty heavily. Is this specific to page parts or are snippets, layouts, etc., also hot spots? Here's the live site: http://www.snaplogic.com/ Thanks for the great help all! On Mon, Dec 28, 2009 at 4:54 PM, john muhl johnm...@gmail.com wrote: oh and i'd think 300-400ms or less spent inside the rails process would be sufficient for all but the most performance critical applications since your web server should be able to serve the rest of your page (static assets, css, js) in less than 100ms On Mon, Dec 28, 2009 at 6:49 PM, john muhl johnm...@gmail.com wrote: some things that come to mind immediately: - make sure you are not serving css and/or js from radiant - make sure you have mod_deflate setup up to compress all text files - avoid excessive use of page parts - avoid using paperclipped or page_attachments for design assets (like your logo or icons or things that don't need to be managed by your content editors) On Mon, Dec 28, 2009 at 6:20 PM, Rob Levin roblevinten...@gmail.com wrote: I've just started working at a place that is using Radiant for it's web site and I've noticed our general pages are usually somewhere around 150kb and take, on my system, around 800ms. FWIW, just now dslreports showed my download speed (on my client box) avg at around 5000Kb. Since it's a small start-up I'm going to be the one to further tune site's performance. That being said, I'm not a sysadmin nor do I have experience in this sort of thing (disclaimer). We are using Radiant version 0.8.1 with Apache/2.0.52 (Red Hat) Server on RH4 (don't ask) and using Passenger with ruby enterprise edition: 1.8.6 (2008-08-11 patchlevel 287) Ruby Enterprise Edition 20090610. We have our own dev server but for production we're using server beach. Looking at our Radiant instance's /config/environment.rb file I noticed the following line so it looks like Radiant caching is on right? config.middleware.use ::Radiant::Cache So my questions are: What would be a checklist of things that may be degrading our site's performance? Besides generally reducing http calls and sizes, what Radiant specific stuff can I do to speed things up? Even links to relevant Radiant docs would be helpful. What would be a good time per size metric to shoot for? Thanks all! ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to improve site performance?
On Mon, Dec 28, 2009 at 7:13 PM, Rob Levin roblevinten...@gmail.com wrote: change the page caching time to a much larger value compared to the default 5 minutes if your pages can manage it. Yes, I'm looking in to this. I'm almost positive we're just using the default. I agree that this may help a LOT! Does someone have a working example of setting: ResponseCache.defaults[:expire_time] or whatever? That would be very helpful. http://groups.google.com/group/radiantcms/msg/01ac040dbcf76479 John Mohit: make sure you are not serving css and/or js from radiant I have my styles and js in RADIANT_ROOT/public/stylesheet /javascripts respectively. Is that correct? It's my understanding that Apache will serve anything under /public right? that's right page parts Well we are using layouts, snippets, parts, etc., pretty heavily. Is this specific to page parts or are snippets, layouts, etc., also hot spots? they require additional database access. however if your database is properly tuned it's generally not much of an issue. it's just something i've noticed on the few apps i track with new relic rpm; in nearly all of them PagePart#find is the most time consuming transaction except in apps that use paperclipped and in that case Asset#find is the slowest. Here's the live site: http://www.snaplogic.com/ the x-runtime header (for the homepage) says 457ms (which is a pretty insignificant part of your total response time) is spent in the rails process so you're likely going to get much more bang for your buck by starting with generic optimizations rather that digging too deeply into radiant (e.g. reducing use of snippets or page parts). a tool like the yslow addon for firefox might help get you started: https://addons.mozilla.org/en-US/firefox/addon/5369. Thanks for the great help all! On Mon, Dec 28, 2009 at 4:54 PM, john muhl johnm...@gmail.com wrote: oh and i'd think 300-400ms or less spent inside the rails process would be sufficient for all but the most performance critical applications since your web server should be able to serve the rest of your page (static assets, css, js) in less than 100ms On Mon, Dec 28, 2009 at 6:49 PM, john muhl johnm...@gmail.com wrote: some things that come to mind immediately: - make sure you are not serving css and/or js from radiant - make sure you have mod_deflate setup up to compress all text files - avoid excessive use of page parts - avoid using paperclipped or page_attachments for design assets (like your logo or icons or things that don't need to be managed by your content editors) On Mon, Dec 28, 2009 at 6:20 PM, Rob Levin roblevinten...@gmail.com wrote: I've just started working at a place that is using Radiant for it's web site and I've noticed our general pages are usually somewhere around 150kb and take, on my system, around 800ms. FWIW, just now dslreports showed my download speed (on my client box) avg at around 5000Kb. Since it's a small start-up I'm going to be the one to further tune site's performance. That being said, I'm not a sysadmin nor do I have experience in this sort of thing (disclaimer). We are using Radiant version 0.8.1 with Apache/2.0.52 (Red Hat) Server on RH4 (don't ask) and using Passenger with ruby enterprise edition: 1.8.6 (2008-08-11 patchlevel 287) Ruby Enterprise Edition 20090610. We have our own dev server but for production we're using server beach. Looking at our Radiant instance's /config/environment.rb file I noticed the following line so it looks like Radiant caching is on right? config.middleware.use ::Radiant::Cache So my questions are: What would be a checklist of things that may be degrading our site's performance? Besides generally reducing http calls and sizes, what Radiant specific stuff can I do to speed things up? Even links to relevant Radiant docs would be helpful. What would be a good time per size metric to shoot for? Thanks all! ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to improve site performance?
Rob, Looking at http://www.snaplogic.com/ the first and biggest thing I would suggest would be to combine your 7 (not including ga_tracker) .js files into one. You could also look into using the google hosted versions of jquery and mootools. -Arthur ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to improve site performance?
Hey Rob - Also think about combining whatever (non-repeating background) images you have into one sprite file, combining CSS and JS files into one file, for each respectively. You're going to see a big hit in perceived speed if you're making that many requests to your web server. Do a fresh request to your site while looking at the Net tab in firebug and you'll see what I mean. - Joel On Mon, Dec 28, 2009 at 9:23 PM, Arthur Gunn art...@gunn.co.nz wrote: Rob, Looking at http://www.snaplogic.com/ the first and biggest thing I would suggest would be to combine your 7 (not including ga_tracker) .js files into one. You could also look into using the google hosted versions of jquery and mootools. -Arthur ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
