Something on my site is still loading before people agree

Read your own site: What is held back → Read my site again. Anything found with Held back: No is running early, and one switch fixes it.

If it is something the plugin does not know about, it is listed on the same screen under On your pages, from sites this plugin does not recognise, including an address that a snippet pasted into your page loads (the row says Loaded by a snippet on the page). Pick the kind of cookie it sets and press Hold back, or press Leave it if it has to load, such as a payment form. Hold back holds the script or the snippet back whether it writes the address with a file name, with nothing after the host, with a port, with only a ? or # after the host, or with a name and @ before it. You can also add a rule at the bottom of that screen: part of its address, or a word from inside its snippet. A word from a snippet is kept and looked for exactly as the page's source writes it, a < or an & included; an address is looked for as a browser reads it, per cent codes and all, so there write & where the source has &.

If the screen says your pages were slow to answer and some were not read, the reading stopped after 45 seconds so that it could answer at all. Read your site again when it is quieter. If it could not read any page at all, what was found before is kept, and What is held back says the error it met.

If the tag that loads before people agree is inside Google Tag Manager, the container itself waits for Measurement, as long as its switch is on under What is held back, and then every tag in it can start. To make advertising tags inside it wait for Advertising, see Google Tag Manager in the documentation: it gives two ways, set up in Google Tag Manager, each fired on the trcc_consent event, and the Dashboard shows them too once a reading has found the container. The Dashboard also says when the container is not held back at all.

If What is held back says a page answered with an error, the reading could not read that page. A page in the Trash or kept as a draft answers "not found", and it does not stop the Dashboard saying your site is up to date. A page a security rule or a busy host turns the reading away from is still there for visitors. If an earlier version of the plugin read it, the Dashboard says so until this version can read it: let the reading in (it asks as a visitor who is not signed in, with the user agent Traslatability Cookie Consent scanner), then read your site again.