It turned out one of the team members saved one of the includes for this page as UTF-8 WITH BOM, the BOM is that rogue character that broke the page. Resaving the file with no BOM fixed everything.
I can't tell you how many includes we had to check.