This is usually a problem with the presence of a flash of loose content ( FOUC ) .
In particular, this is what Paul Ireland calls a flash of untrue text ( FOUT ) :
In Firefox , basically the text is in webfont by default until the custom font is ready

Webkit takes a very different approach and is very intentional. They think it's best to keep the text invisible until the font is ready. Thus, there is no moment when the text starts flashing in its updated self.

In other words, this issue is not easy to overcome.
You can try to minimize the impact of:
- Using gzip to compress a file so that it loads faster
- Use caching so that the client can use an existing copy rather than grab a new one.
The hard approach was to wait for the page to be displayed to the user until everything was displayed, but I would highly recommend against this. The user is very intolerant of the initial loading times, but is much more forgiving when it comes to providing additional content.
source share