Investigating Inflated Bandwidth Usage After Recent Site Changes

Has anyone encountered issues where the site Bandwith seems inflated? We published some changes two weeks ago and since then we have been using 4x as much bandwidth. Assets are all optimized and the site traffic isn't crazy

15 comments

Matt J.
·
·
Josh C. when you say traffic isn't crazy - are you looking at total hits versus unique? Could be bots/crawlers?
Matt J.
·
·
In the era of AI, there's a lot of web scrapping tools now so I would imagine we'll see bandwidth being eaten up quite a bit as of late
Zac H.
·
·
We were hitting 500gb bandwidth with just 20k visitors - Most of the bandwidth was due to a heavy animation and also, of all things, typography and icon packs. We moved the custom typography and icon packs to cloudflare and wrote a CSS script to load them from there. Saved us 150+gb per month.
🔥1
Matt J.
·
·
ah yeah custom fonts for sure- makes sense
Josh C.
·
·
I think we get about 2.3k per day, and we use 18 GB of bandwidth a day. I'd have to check the total number of unique hits.
Josh C.
·
·
We do use an Adobe font on the site - could that add bandwidth?
Matt J.
·
·
for sure
🙌1
Josh C.
·
·
Thank you for the reply by the way!
Josh C.
·
·
Seeing as I haven't had to pinpoint an issue like this before, how would you go about diagnosing the problem?
Matt J.
·
·
Josh C. I would think something like lighthouse/pagespeed or some audit tool similar to that would give you a breakdown of what is taking up bandwidth. You can do this right in the chrome developer tools (right click inspect). Zac H. do you have any tools you use for this?
Matt J.
·
·
also seems like the network tab has some quick stats too
Matt J.
·
·
Josh C.
·
·
That's where I started, with Lighthouse. I'm just trying to interpret what I am seeing ha! I'll have to dig in some more. Good to know I am on the right track. Thank you!
Zac H.
·
·
We just used the csv that Webflow provide (you can group by usage) and cross referenced it with the network tab in the inspection tool.
Zac H.
·
·
We also set some CMS lists I.e our blog to lazy load - these were originally set to eager and it loaded all 20+ pages of the blog results and their images.