The tags a franchised dealership is not allowed to remove.

Not without checking what the requirement is attached to. A manufacturer program, a certified-program standard or a co-op advertising agreement can make a specific tag a condition, and removing it can put funding or program compliance at risk. Changing when it runs is the available remedy instead.

Almost never. A tracking requirement is usually that sessions and conversions are recorded, not that recording happens before the shopper can see a price. Those are different obligations, and the gap between them is where most of the available improvement on a franchised site sits.

Consent management, and anything a lawyer has told the dealership must appear before other technology runs. That list should be short and written down, because it is the constraint every other loading decision has to work around. Most tags a dealership believes belong on it do not.

By listing every third party loading on a vehicle detail page and asking, for each one, which agreement requires it. A tag everybody believes is mandatory and nobody can point to a document for is a common finding, and it is usually the easiest weight on the site to remove.

Co-op funding can depend on it, which is exactly why the question deserves an answer in writing instead of an assumption in either direction. What such a rule usually requires is that the pixel is present and fires; it rarely specifies a position in the loading order, and that leaves the sequencing available.

Not if it has to be shown before other technology runs, which is often the case for consent. A vendor's full payload and the part that must appear early are frequently separable, though, so the question to ask is which specific component the obligation covers instead of treating the whole vendor as untouchable.

Ask what breaks if it does not, and ask for the answer in writing. A vendor whose script genuinely depends on running first can explain the dependency in a sentence. One who cannot is describing a preference, and a preference is not a requirement the shopper should pay for.

Rarely. They are usually a handful of scripts inside a much larger accumulated stack, and most dealerships find the largest contributors are tools they chose. The mandated ones matter because they are the part that removal advice cannot touch, not because they are the bulk of the weight.

A group faces it repeatedly and inconsistently: different manufacturers impose different requirements, so two rooftops in the same group carry different mandated lists. Documenting the list per rooftop is what makes group-level reporting mean anything, instead of comparing sites under different obligations.

No, and doing so misdiagnoses the site. A mandated tag is neither the platform's doing nor an optional add-on the dealership chose; it is a third category. Separating the three is what makes a platform evaluation honest instead of an argument about whose fault the total is.

Asking is worth doing, though OEMs vary widely in whether and how quickly they respond to that kind of request: in the meantime, changing when the script loads is usually within the dealership's control even when the script itself isn't.

Yes. Google's measurement doesn't distinguish between a script the dealership chose and one the OEM requires: both compete for the same loading time.

Removing one anyway is a decision with real co-op or compliance consequences specific to that dealership's agreement, and it's outside the scope of what a performance recommendation should decide: check with your OEM or co-op contact first.