When we started to plan for Rock, we listed out our high-level goals for the project. One of these was "Speed as a Feature." For us that was more than just words, we wanted it to be real and measurable. One of the first features we added was the page load time in the admin bar. From that moment on speed was put in front of us on every page we loaded. We kept it there, not only as our contract with you, but also so you could measure your custom modifications. Think of the Page Load Time tag as a window into how your site is performing. When you click it, the Page Debug Timings show you a map of everything the server did to build that page. Page Debug Timings When you click the Page Load Time tag, the page will reload to gather the latest data. The Page Debug Timings window then opens, showing you a map of everything the server did to build the page. If a page feels slow, this list helps you find the exact block or database query that is causing the delay. It turns the "invisible" work of your system into a clear trail you can use to make your site faster for everyone. This feature uses the same data gathering system that powers the Observability tools in Rock. It is like having a simplified version of those tools without any of the configuration. The top-level items you see, like PAGE: GET /, are network requests. These represent the initial communication between the person's browser and your server to start loading the page. Each row below those requests is a task trace. This is a list of every specific task the server performed, such as looking up a person or calculating a total. When you click on a trace, the system shows even more detail, like the exact database query or piece of code that ran. If a page feels slow, look for the rows with the largest numbers. These are your bottlenecks. A single task, like BLOCK INIT Reminder Links, might be doing a lot of work behind the scenes (like checking cache) to keep things moving. By finding the specific block taking the most time, you can make changes instead of guessing. When your site is fast, the technology stays out of the way so your team can focus on their work. Now that you know how to find the heavy parts of your pages, you are ready to start tuning.