> For the complete documentation index, see [llms.txt](https://salsa-digital.gitbook.io/govcms-site-builder/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://salsa-digital.gitbook.io/govcms-site-builder/unit-10-site-performance/define-goals-and-requirements.md). # Define Goals and Requirements Now that you’ve got your baseline results, you can start setting your goals. Based on the problems outlined in your site’s speed test report, you may target different areas of your website, such as: * Manage website caching - to reduce the **First byte** time and the **Fully loaded** time. * Review and apply better optimised image styles - to reduce the **Bytes in** size of your pages and reduce the **fully loaded** time. * Enable CSS and JS files aggregation - to reduce the number of requests. * Enable browser caching - to reduce the **fully loaded time** and the **bytes in** for consecutive page visits. To further improve **Document complete**, **Start Render** and **First Interactive** times, code changes may have to be applied to the application. It may require you to move some render-blocking CSS and JS files from the \ region to the bottom of the page. Such changes are beyond the scope of this training. Example goals may look like the below: * Reduce the **fully loaded** time to stay under 4.7s per page * Reduce the **Bytes in** below 2MB per page * Minimise the number of requests * Minimise the **First Byte** time As you can see, some of the goals are not quantitative. This is because we can’t guarantee some of the metrics. Instead we target a noticeable improvement. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://salsa-digital.gitbook.io/govcms-site-builder/unit-10-site-performance/define-goals-and-requirements.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.