Answers.Body: <p>If you enable <a href="http://buildwithcraft.com/docs/config-settings#devMode" rel="nofollow">devMode</a>, then database profiling information (number of queries, SQL executed, execution time, etc.) as well as PHP script benchmarking information for the request will be output to your browser's console as well as the <code>craft/storage/runtime/logs</code> files.</p>
  
  <blockquote>
    <p>Also, as I understand it, every plugin is loaded on each request</p>
  </blockquote>
  
  <p>Installed and enabled plugins are <em>initialized</em> on every request.  The only time what you are describing is a problem is if a plugin is doing some time/resource intensive operation in it's <code>init()</code> method, which is generally considered bad form.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-10-05T05:45:31.877Z
Answers.Text: Ahh, thank you! I went through and was able to find a few pain points and get the request responsive time down to 400-500ms. I was missing a couple big caching opportunities. This is much better! Great!
Answers.UserDisplayName: Jason D
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-10-05T03:50:57.440Z
Answers.LastActivityDate: 2014-10-05T03:50:57.440Z
Answers.UserDisplayName: Brad Bell
Body: <p>I would like to see how long plugins take to load, as well as other aspects of the page (loops and database requests). </p>
  
  <p>My webpage can take ~2-3 seconds to return the initial request. It seems high and I'd like to figure out how I can optimize it.</p>
  
  <p>Also, as I understand it, every plugin is loaded on each request (even if it's not loaded for that page). Is this true? And if so, why is this the desired behavior? If a plugin is performing poorly it can bring the entire website to a standstill (this just happened to me: <a href="https://craftcms.stackexchange.com/questions/2919/website-taking-30-seconds-to-load/2921#2921">Website taking 30+ seconds to load</a>).</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-10-15T17:59:01.703Z
Comments.Text: Please don't use meta tags.
Comments.UserDisplayName: nicael
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2014-10-17T05:38:08.747Z
Comments.Text: Ah, thanks for letting me know! I didn't realize that tags had a functional purpose (for anyone else who sees this: I had the "feature-request" tag incorrectly on this)
Comments.UserDisplayName: Jason D
Tags: <cache><server><request>
Title: How can I time-profile the page load for a Craft request?
ThreadText: # How can I time-profile the page load for a Craft request?
  
  (Asked by: username_0 on 2014-10-04)
  
  I would like to see how long plugins take to load, as well as other aspects of the page (loops and database requests).
  
  My webpage can take ~2-3 seconds to return the initial request. It seems high and I'd like to figure out how I can optimize it.
  
  Also, as I understand it, every plugin is loaded on each request (even if it's not loaded for that page). Is this true? And if so, why is this the desired behavior? If a plugin is performing poorly it can bring the entire website to a standstill (this just happened to me: [Website taking 30+ seconds to load](https://craftcms.stackexchange.com/questions/2919/website-taking-30-seconds-to-load/2921#2921)).
  
  **Tags:** cache, server, request
  
  > **Comments:**
  > **username_1**: Please don't use meta tags.  
  > **username_0**: Ah, thanks for letting me know! I didn't realize that tags had a functional purpose (for anyone else who sees this: I had the "feature-request" tag incorrectly on this)  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2014-10-05. Score: 4 | Accepted answer
  
  If you enable [devMode](http://buildwithcraft.com/docs/config-settings#devMode), then database profiling information (number of queries, SQL executed, execution time, etc.) as well as PHP script benchmarking information for the request will be output to your browser's console as well as the `craft/storage/runtime/logs` files.
  
  > Also, as I understand it, every plugin is loaded on each request
  
  Installed and enabled plugins are *initialized* on every request. The only time what you are describing is a problem is if a plugin is doing some time/resource intensive operation in it's `init()` method, which is generally considered bad form.
  
  > **Comments:**
  > **username_0**: Ahh, thank you! I went through and was able to find a few pain points and get the request responsive time down to 400-500ms. I was missing a couple big caching opportunities. This is much better! Great!  
  
  ---
  
  