Using Yahoo's YSlow to measure performance

Topics: General, Troubleshooting
Feb 18, 2011 at 3:14 PM

One commonly used tool to measure website performance (speed) is Google's YSlow, available at: http://developer.yahoo.com/yslow/

When I run YSlow against a "vanilla" install of YSlow, it reports a couple of problems:

Grade E on Add Expires headers

There are 4 static components without a far-future expiration date.

and

Grade D on Configure entity tags (ETags)

There are 3 components with misconfigured ETags

Are these in fact issues worth addressing?

 

Coordinator
Feb 18, 2011 at 7:57 PM

Expiration dates on static resources are out of the reach of the application but you can go into IIS configuration and fix them. Same thing for ETags.

Feb 19, 2011 at 1:54 AM
bertrandleroy wrote:

Expiration dates on static resources are out of the reach of the application but you can go into IIS configuration and fix them. Same thing for ETags.

My follow on question then is would this be considered an Orchard "best practice" to do so, or is it not worth the effort?

Coordinator
Feb 19, 2011 at 4:07 AM

It's best practice everywhere. Whether it's worth the effort depends on your traffic.