> For the complete documentation index, see [llms.txt](https://support.mgwebdev.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.mgwebdev.eu/documentation/guides/performance-optimization.md).

# Performance optimization

Our goal is to deliver sites that work faster on average. 

#### Quick wins you can do

* Compress images before uploading it to the server (target <100Kb; use Webp format whenever possible).
* Enable lazy-loading for images/offscreen content.
* Minimize third-party scripts and trackers.

#### Advanced Tips

* Use CDN for static assets (can be done on request, billed yearly)
* Optimize fonts: Subset and preload only critical ones.
* Browser caching: Already set up server-side for repeat visitors.

#### Tools to monitor & improve

* Google PageSpeed Insights
* GTmetrix
* Lighthouse (built into Chrome DevTools)

We perform regular audits as part of maintenance. You can request a free performance check.


---

# 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://support.mgwebdev.eu/documentation/guides/performance-optimization.md?ask=<question>&goal=<endgoal>
```

`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.