Seems mostly like images, however, there is one that doesn’t seem to be an image, e.g. the third from the bottom.
I’m wondering if the VPS that you indicated above that you use, is actually too “low end” to cope with the traffic that your websites are receiving, and that it would be the major reason to the issues you face.
Assuming that your website is about a Greek radio station:
When I tried loading the second image from the bottom of your list, e.g. “
/wp-content/uploads/2022/10/24s4lesb10.jpg”, I had to hit your image several times from my end, before I received the “CF-Cache-Status” header with “HIT”, and this image contains a “
Last-Modified” header indicate that the image file was last updated on
Sat, 01 Oct 2022 10:31:01 GMT, which matches the time (/2022/10/) from the path of the file.
When I loaded your front page, I saw 128 requests, where many of them were image files. Although the majority seemed to retrieve the “CF-Cache-Status” header with “HIT”, we had another one called “
/wp-content/uploads/2023/12/velopoulos_grafeia_07_12.jpg”, which retrieved a “CF-Cache-Status” of “REVALIDATED”.
All your images seems to have a
Cache-Control header, but shared for all of them, are that they are indicating that it should be cached only for 14400 seconds (4 hours).
There are however images being loaded, where the “
Last-Modified” header indicate that the image file was last updated in November, such as e.g.
/wp-content/uploads/2023/10/3c5140b26e.jpg that was updated on
Wed, 22 Nov 2023 23:17:25 GMT, but still only contains that
Cache-Control header, that is requesting it to be cached only for 14400 seconds (4 hours).
So I would possibly move on with what I said above:
As mentioned above, having to hit the image multiple times to retrieve “CF-Cache-Status” header with “HIT”, tells me that e.g. Tiered Cache is turned off for your zone.
If you’re enabling Tiered Cache, that alone should be able to reduce the amount of queries that the the Cloudflare network ends up on requesting from your server.
The reduction of requests will however be limited to the
Cache-Control header, that you have set, so for the file mentioned above that was updated on
Sat, 01 Oct 2022 10:31:01 GMT, Cloudflare would still be requesting (e.g. refreshing the cache, seeing whether it is still valid) after the time of 14400 seconds (4 hours), or if you have traffic on the site 24/7, then a roughly 6 times per day.
If your visitors end up on reaching Cloudflares locations in Hong Kong, São Paulo, and Amsterdam, it would be be 6 times per day for each of these locations, meaning 18 times per day, in this example with, where Tiered Cache is disabled. Enabling it could reduce this to the above mentioned 6 times per day.
Imagine 200 Cloudflare locations worldwide, all having to request your image, because your visitors are reaching 200 different Cloudflare locations. Now, you would have 200 * 6, or 1200 requests for the same image file per day, assuming that we’re looking at the worst scenario possible.
As the first mentioned file above hasn’t been updated in more than a year, I would say that is quite a static file, so upgrading the
Cache-Control header to something like 86400 seconds (1 day), 604800 seconds (1 week), 2592000 seconds (30 days), or even 31536000 seconds (365 days / 1 year), would likely help a lot to reduce the queries (and thereby the load) that your VPS receives.
Maybe there is even a chance, that you could avoid blocking traffic at all, solely by looking at improving your cache settings.