If you choose to disable one of the core technologies of the modern web, you'll just have to take what you can get.
But enough sidetracking, as ekianjo said, using a script to load the font is unnecessarily adding to its fragility and simply fails for those without javascript.
This modern web core technology being a security liability[1], invasive of privacy[2] and the facilitator of modern annoyances that gets in the way of the user, (ads, interstitial space, ...) it is an expected response from the user to disable it or restrict it to the actual domain serving the page.
[1]: http://thehackernews.com/2016/01/javascript-ransomware-malwa... [2]: http://motherfuckingwebsite.com/ and http://bettermotherfuckingwebsite.com/ and http://evenbettermotherfucking.website/
Sometimes a constraint like that can lead you to solutions even better than what you started with.
Or you can write a robust design that starts with radical simplicity that is at least functional, and then progressively enhance the page with whatever features are currently available. The user shouold at least be left with something usable if the Javascript or CSS or font doesn't load.
This modern trend that tries to pretend that the User Agent will always support various features or that they can simply assume that network errors never happen just makes sites look shoddy and unprofessional.