Afraid not to my knowledge, Google seems the have moved away from webfont.js, I would recommend switching to “aggregate & preload fonts” instead.
hope this helps,
frank
Thank you for your quick reply. We will keep it as it is for now as when aggregating and preloading the Google Page Speed Score drops by 15 points.
Kristina
So if the score is 15 points lower, what are the differences in lab data/ opportunities/ diagnostics?
This is with loading fonts asynchronously (I have Google Page Speed in local language so the translations might not be 100% accurate):
Mobile score: 53
First contentful paint: 2 seconds
First purposeful paint: 2.1 seconds
Speed index: 6.3 seconds
First processor idle: 7.8 seconds
Time till interactive: 8.7 seconds
Max first input delay: 610 ms
Opportunities:
Decrease server response time (TTFB) :1.53s
Remove render blocking resources: 0.94s (Autoptimize css, scss and jquery)
Remove unused css: 0.3s (Autoptimize css)
Diagnostics:
Ensure text remains visible during webfont loaad (all Google fonts and one another)
There are other points but these do not change with font load change.
Combine fonts and preload in header:
Mobile score: 40
First contentful paint: 4.1 seconds
First purposeful paint: 4.2 seconds
Speed index: 6.7 seconds
First processor idle: 7.8 seconds
Time till interactive: 8.5 seconds
Max first input delay: 620 ms
Opportunities:
Decrease server response time (TTFB) :1.33s
Remove render blocking resources: 0.9s (Autoptimize css, scss and jquery)
Remove unused css: 0.45s (Autoptimize css)
Diagnostics:
Ensure text remains visible during webfont loaad (one theme font)
Any ideas? I do not have any caching plugin enabled yet.
might be the display:swap when preloaded slows the first paint down (although I don’t see how it could be 2s), but that’s just a guess … guess it’s webfont.js for you 😉
OK, we will leave it as it is for now, thank you.
