<p>If you enable <a href="http://buildwithcraft.com/docs/config-settings#devMode">devMode</a>, you'll get code profiling information (execution times, memory used, stack traces, etc.) that you can use to debug templates with in your browser's console as well as in the <code>craft/storage/runtime/logs</code> folder.</p>

CC BY-SA 3.0
2015-03-23T23:40:10.030Z
There's also the old [Profilr plugin](https://github.com/sathoro/Profilr)... how much of that is redundant with the console log output?
Lindsey D
CC BY-SA 3.0
2015-03-23T23:55:20.083Z
Looks like it's duplicating most of it and just adding a nice UI for it.
Brad Bell
CC BY-SA 3.0
2015-03-23T23:56:05.230Z
Nice UIs are for suckers. ;)
Lindsey D
CC BY-SA 3.0
2015-03-24T22:20:08.767Z
Hahaha, yeah... definitely... *looks around before clicking on the download button*
cballenar
CC BY-SA 3.0
2015-03-23T18:55:23.340Z
2015-03-23T18:55:23.340Z
Brad Bell
<p>I've got a news website built and I am in the process of improving it's performance. What would be the best way to measure the performance of my templates?</p>

<p>I can use Chrome Developer tools to measure how long it takes for the server to respond but is that the best way of doing it or can I do it internally?</p>

<cache><performance><templating>
Measuring Template Performance
# Measuring Template Performance

(Asked by: username_0 on 2015-03-23)

I've got a news website built and I am in the process of improving it's performance. What would be the best way to measure the performance of my templates?

I can use Chrome Developer tools to measure how long it takes for the server to respond but is that the best way of doing it or can I do it internally?

**Tags:** cache, performance, templating

---

## 1 answers

### Answer by username_1 on 2015-03-23. Score: 5 | Accepted answer

If you enable [devMode](http://buildwithcraft.com/docs/config-settings#devMode), you'll get code profiling information (execution times, memory used, stack traces, etc.) that you can use to debug templates with in your browser's console as well as in the `craft/storage/runtime/logs` folder.

> **Comments:**
> **username_2**: There's also the old [Profilr plugin](https://github.com/sathoro/Profilr)... how much of that is redundant with the console log output?  
> **username_1**: Looks like it's duplicating most of it and just adding a nice UI for it.  
> **username_2**: Nice UIs are for suckers. ;)  
> **username_0**: Hahaha, yeah... definitely... *looks around before clicking on the download button*  

---

