Mistake: redirect chain too long, traffic leaks at each hop

Mistake: redirect chain too long, traffic leaks at each hop

Failure mode: source then tracker then cloaker then prelander then offer then network redirect. Every hop adds latency and a chance for the user to bounce. Mobile users on slow connections drop before the offer loads.

Fix — checklist:
— Count your hops. More than 3 redirects before the landing page is a problem. Aim for 2.
— Collapse hops where possible: a direct (meta-refresh-free) 302 beats a JS redirect that waits on script load.
— Move prelanders to direct-link serving instead of an extra tracker redirect when the source allows it.
— Measure hop latency with a header tool; flag any single hop over 300ms.
— Kill any hop that exists only for legacy reasons no one remembers.

Verify: time the full chain from click to offer-loaded. Under 1.5s on a throttled 3G profile is the target.

Save this SOP. Run this before every launch.