Issues with fonts.googleapis.com ?

[RedBar]

Since yesterday, Wednesday, I have been experiencing very slow loading on many sites including WebmasterWorld sometimes up to a minute for each page. Some sites have not loaded at all.

I have narrowed it down to a delay in fonts.googleapis.com, sites like mine that do not use these fonts are fine.

Is anyone else seeing this?

I do know of a friend last night who almost destroyed her Chrome Book she was that frustrated at being unable to use it!

[amiromidi]

No Issue in our region, it might be google server's issue in your region, try to open the same websites via VPN ( Connect to some other area) to check it out

[RedBar]

@ amiromidi - Great suggestion, used TOR browser and connected as normal.

Will advise my ISP.

Thanks

[amiromidi]

welcome buddy, any new issues in GSC (after latest update) ?
it seems some rookies are in control in G

[Sgt_Kickaxe]

They aren't rookies but they are focused on implementing the solutions they want, and it's occasionaly creating problems elsewhere when code is altered. Google is comprised of a lot of teams, each with their own focus, and changes the teams make don't always mesh seemlessly with things other teams are responsible for.

As for the fonts googleapi, the slowdowns are causing another problem which is likely to lead to more slowdowns(code changes) until it's resolved.

Spam blocker users are adding remote fonts to their block lists, either directly, in their lists or by using the "click to block remote fonts" option they all have. Chrome just declared war on spam blockers by unsuporting them(retiring manifest V2) but other browsers are embracing those who wish to use privacy tools so there is a growing rift, leading to different user experiences.

[msn.com...]

As deadline for mandatory code rewrite approaches, Manifest v3 still looks like a step backward. Analysis In January next year, Chrome browser extensions – such as ad blockers and other privacy tools – will stop working if they are reliant on an API called Manifest v2 (MV2)

It might be best just to get out of the way and bring your fonts in house, for now, or only serve font.googleapis to chrome users . Don't build for Google, build for your visitors ~ Google.

[edited by: Sgt_Kickaxe at 7:17 pm (utc) on Sep 28, 2022]

[lucy24]

It might be best just to get out of the way and bring your fonts in house

This.

On a broader scale, anything that involves material that doesn't live on your own site* runs the risk of delay. (For the most dramatic illustration, think of pages whose graphics consist entirely of hotlinks, each from a different place.)

* I was going to say “your own server”, but even if it's a different hostname on the same server, there's still a lookup involved.

[RedBar]

I totally agree lucy, I've only ever used the web safe fonts served in-house. There are some great fonts out there however I need to ensure legibility is paramount for my global site for all my non-first language English readers.