> For the complete documentation index, see [llms.txt](https://cmp.docs.sirdata.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cmp.docs.sirdata.net/faq/google/google-pagespeed.md).

# Google PageSpeed

Google PageSpeed indique que le script stub bloque le rendu de la page et que cela a un impact sur le SEO. Est-il possible de le charger en asynchrone ou le mettre dans le footer ?

Le script stub fait partie du standard du *Transparency & Consent Framework*.

Ce script relativement léger permet tout d'abord d'indiquer aux autres scripts de votre site qu'une CMP est installée et qu'ils peuvent intéragir avec elle.

Il permet également aux scripts d'appeler les différentes commandes de la CMP avant que cette dernière ne soit complètement chargée (en asynchrone).

Sans cela, les scripts sur votre site ne pourraient pas interagir avec la CMP, lire les informations de consentement de vos utilisateurs et donc en tenir compte pour leurs traitements.

Pour ces raisons, il est indispensable que ce `stub` soit intégré le plus haut possible dans la balise `<head>` de votre site et toujours de manière synchrone.


---

# 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://cmp.docs.sirdata.net/faq/google/google-pagespeed.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.