ava on Nostr: There are a few of ways: 1. You can inspect the HTML by running your compile in a web ...

There are a few of ways:

1. You can inspect the HTML by running your compile in a web browser, open the developer tools, go to the network tab, reload the page and look for (fonts.googleapis.com) or (fonts.gstatic.com) *without the parenthesis*

2. Check the code by looking into your _document.js or _app.js files for any <link> tags that reference Google Fonts

3. Review your CSS files for any (@import) *without the parenthesis* for any statements that include Google Fonts.

And yes, you can also use uBlock Origin to check for Google fonts as well.

Go to the web page of your (Next.js) application in your browser and open uBlock Origin's Logger. Reload the page and watch for any requests made to (fonts.googleapis.com) or (fonts.gstatic.com). These are the domains used by Google Fonts to serve fornt files.

It's also worth noting that (Next.js) has a built-in feature that automatically optimizes and self-hosts Google Fonts. When you include Google Fonts using the next/font/google import, the fonts are downloaded and served from the same domain as your deployment, eleminating requests to Google's servers.

Let me know how you go :)