Webflow handles custom code through a dedicated settings panel rather than a raw file edit, and it applies across your whole site — static pages and CMS-generated Collection pages alike — once you publish.
Every page, including dynamically generated CMS Collection pages — Head Code set in Project Settings is injected at the site template level, not per page.
No meaningfully — the script tag uses defer, so it doesn't block rendering, and the rest of the page is still served through Webflow's own hosting and CDN as normal.
Webflow does support per-page custom code in each page's own settings, but for analytics you generally want the sitewide Project Settings version so you're not repeating it on every page.
No — Webflow's built-in site analytics (where available on your plan) and Orbit read pageviews independently and can run side by side.