The component-by-component migration of a program from untyped to typed can trigger unintended performance degradations. When such a degradation occurs, typing well-chosen components can lessen the cost of type enforcement, while typing poorly chosen components can exacerbate it. In this talk, I examine whether off-the-shelf profiling tools deliver information that helps programmers navigate these migration choices effectively in Typed Racket.