> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/sustainability-best-practices/frontend/frontend.md).

# Frontend Overview

Here you can learn about how to optimize assets, implement a mobile-first strategy and other suggestions.

In this section, you can find some tips to optimize your website's performance and reduce its carbon footprint:

## [Page Weight Budget](/sustainability-best-practices/frontend/page-weight-budgets.md)

Minimize the data transfer to access your web page as it has a big impact on carbon emissions.

## [Image Optimization](/sustainability-best-practices/frontend/image-optimisation.md)

Optimize images before uploading to a web page and make use of different file formats.

## [Asset Optimization](/sustainability-best-practices/frontend/assets-optimisation.md)

Improve website performance by optimizing fonts, minifying assets and cache static assets.

## [Limit use of 3rd parties](/sustainability-best-practices/frontend/limit-use-of-3rd-parties.md)

To avoid excessive HTTP requests and potential data sharing, limit the use of third-party resources on websites.

## [Lazyload Resources](/sustainability-best-practices/frontend/lazy-load-resources.md)

Optimize the loading of web pages by using Lazyload resources.

## [Mobile First](/sustainability-best-practices/frontend/mobile-first.md)

Prioritize mobile-first design experiences focusing on a clean and efficient design. It can help reduce website energy consumption and promote sustainability.


---

# 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://docs.umbraco.com/sustainability-best-practices/frontend/frontend.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.