I don’t know what’s causing the slow publish, but it wouldn’t be the font. When you are using Google Web Fonts, the actual font files are on their server, the only think that get’s added to your site is the little code snippet.
Do you have any huge images that Freeway is scaling down on publish? Oftentimes, this can slow the program to a crawl.
John, as an avid Google font user, I can say unequivocally it’s not the
font or the font code. What it is, I don’t know… I don’t believe anyone can
say definitely. Caleb has a reasonable point about image management, but I
experience extended publish times even with projects that use pass-through
images - where no images are scaled or managed by the app.
My experience with every FWP site I build seems to have some “tipping
point” where the relative complexity exceeds some unknown measure and build
times begin to significantly increase and application response begins to
slow. I have just trained myself to wait for the progress bar to appear and
complete. Often, even the process of “saving” after a publish (which in my
workflow is automatic) presents a progress bar. This is simply the behavior
of the program for anything site-sized.
It’s not popular advice, but I’ve simply tried not to stress over it and be
patient beyond mortal means.