Excessive Bandwidth Usage

[fool]

Hiya!

Good intuition on the cache-control header overriding, though I hope you’ve read this article to be aware that you will basically be unable to update any of your non-html content for repeat visitors, within a month: Better Living Through Caching

I took a quick look at your account’s bandwidth usage and what I found is that as I’m guessing you expected, it is all on the polyglotdeveloper site and production URL.

I also searched over the past hour to understand your highest traffic URL’s (this is the 10 most requested URL’s by count + path), and I can see some problems in them:

487	https://www.thepolyglotdeveloper.com/favicon.png
426	https://www.thepolyglotdeveloper.com/sw.js
346	https://www.thepolyglotdeveloper.com/images/logo-icon.svg
331	https://www.thepolyglotdeveloper.com/css/bundle.min.8f4d2123e610fec4150954b443794414ed1d0f3dce67cef0bb9763880325f490.css
327	https://www.thepolyglotdeveloper.com/media/sponsors/thepolyglotdeveloper/placeholder-inline-1.svg
326	https://www.thepolyglotdeveloper.com/js/bundle.min.9fc1cd0e6f46395694342a05dd6042d29d757af2ee5e765ec3c476a8ea9fca76.js
322	https://www.thepolyglotdeveloper.com/media/authors/nraboy.jpg
322	https://www.thepolyglotdeveloper.com/webfonts/fa-solid-900.woff2
318	https://www.thepolyglotdeveloper.com/webfonts/fa-brands-400.woff2
292	https://www.thepolyglotdeveloper.com/manifest.json

Specifically it seems like you are using hashes in your assets which will make your cache-control headers pointless. These articles have more details on avoiding that pattern:

[Support Guide] Making the most of Netlify's CDN cache

Last reviewed by Netlify Support - August, 2023 Our CDN derives much of its efficiency from files whose checksums don’t change between deploys. For instance, in a blog, you usually write or update one article in one file, while the rest of the content remains unchanged. In this typical use case, we don’t need to re-upload and re-process these files, since our CDN already has them stored - no checksums have changed except the one file. This also means that your visitors’ browsers don’t need to …

and

[Support Guide] Why do I see “Uncaught SyntaxError: Unexpected token <” errors? How can I use chunking or versioning for my assets at Netlify?

Last reviewed by Netlify Support on December 2022 The error Uncaught SyntaxError: Unexpected token < is most commonly caused by your site’s code referring to an asset that is no longer available. Most commonly, this is due to a filename change in assets generated during your build. The same situation happens if you use versioned or chunked javascript where the filename changes with every deploy. Let’s look at an example: A file that was named /assets/main-123abc.js would change to /assets…

The next 10 or so top loads are all font files. While I don’t know what changed from DO, this does all seem like legitimate traffic, though you get about 2400 reqs a day from this service: http://serpstatbot.com/ many of which 404 and serve your 14126 byte 404 page, so you might try lightening up that HTML, but it isn’t the majority cause of your traffic or anything.

Sorry I don’t have more insights but hopefully that helps you diagnose and improve!