> 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/review-current-issues-and-bottlenecks.md).

# Review current issues and bottlenecks

An external speed optimisation tool like [http://webpagetest.org](http://webpagetest.org/) will highlight the problems and provide some guidance to mitigate or minimise the impact. Here we’ll cover some general and common issues and how to tackle them in GovCMS.

## First Byte time

The First Byte time indicates that your website takes too much time to render the page. This may be a result of a less than optimal website configuration, low-performant code or lack of caching. Managing website cache may be a relatively easy way to speed up the site.

Before proceeding with website caching, let’s review which caching modules are available in GovCMS. Navigate to the **Extend** page and enter “cache” in the filter field.

![Image of Cache modules](https://3186608908-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LzAsrTcKaHnLDg-7ALW%2Fuploads%2Fgit-blob-0e2d56d1ce38c0ab07996aa45527f10e317e0d61%2F164.png?alt=media)

{% hint style="info" %}
**Note:** GovCMS SaaS does not provide Memcached container and so the Memcache and Memcache Admin modules have to stay disabled.
{% endhint %}

We can safely activate the **Internal Dynamic Page Cache.** The **Internal Page Cache** modules may be left disabled, as the GovCMS hosting platform provides an efficient reverse-proxy cache – a better replacement to this module.

## Enable GovCMS internal cache

{% hint style="danger" %}
**Note!** Before changing configuration of the internal cache in production, an UAT testing has to be conducted to avoid unforeseen rendering problems for dynamic website content.
{% endhint %}

Enable caching of the site by going to **Configuration** → **Development** → **Performance**. Activate CSS and JS aggregation.

This step improves site loading speeds by reducing the number of connections between the client browser and webserver. You can find CSS and JS aggregation settings in the **Bandwidth optimisation** section.

Reassess your site’s performance to estimate the improvements.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://salsa-digital.gitbook.io/govcms-site-builder/unit-10-site-performance/review-current-issues-and-bottlenecks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.