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 :)
Ava
npub1f6…azcka
2024-07-23 21:11:49
in reply to nevent1q…mrt9
Author Public Key
npub1f6ugxyxkknket3kkdgu4k0fu74vmshawermkj8d06sz6jts9t4kslazckaPublished at
2024-07-23 21:11:49Event JSON
{
"id": "b4572874bd499cbda71f0a0399cdf5b85ed320f6ea35a48e102c36258dadb840",
"pubkey": "4eb88310d6b4ed95c6d66a395b3d3cf559b85faec8f7691dafd405a92e055d6d",
"created_at": 1721769109,
"kind": 1,
"tags": [
[
"e",
"ad5374fae37b0ab6ad9ca92121043f89d4293e1b8dca9a6c5125fbd992a67de6",
"",
"root"
],
[
"e",
"16df201b01f5d0ef187890eba0f54e32ef42f40184e53b5bfbb46ac35fb8126e",
"",
"reply"
],
[
"p",
"4eb88310d6b4ed95c6d66a395b3d3cf559b85faec8f7691dafd405a92e055d6d"
],
[
"p",
"7cc328a08ddb2afdf9f9be77beff4c83489ff979721827d628a542f32a247c0e"
],
[
"r",
"fonts.googleapis.com"
],
[
"r",
"fonts.gstatic.com"
],
[
"r",
"fonts.googleapis.com"
],
[
"r",
"fonts.gstatic.com"
],
[
"monero",
"8BS6GhcmP9f6G8VTDHRQmKX49xwH4714Z886PXu8q7wdgT7Qi7kMq1qTHXRuFyFNGiVPuYLzU7buQPQ7FRZKL4teB6U9k63",
"1.0"
]
],
"content": "There are a few of ways:\n\n1. 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*\n\n2. Check the code by looking into your _document.js or _app.js files for any \u003clink\u003e tags that reference Google Fonts\n\n3. Review your CSS files for any (@import) *without the parenthesis* for any statements that include Google Fonts.\n\nAnd yes, you can also use uBlock Origin to check for Google fonts as well.\n\nGo 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.\n\nIt'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.\n\nLet me know how you go :)\n",
"sig": "960cfa0ae1410c6d63bd362dea17e91faa4e2a8d3035ee38e36bfc8fa3ec4703e2e704cb66dd13baddf9ba59c26b9d9d4d2450c6246f702439ddd74c7739f0e3"
}