Automatic Platform Optimization for WordPress and static assets

I have a really very dumb question: is APO for WP managing static assets (images, js, css, etc.) caching?

Currently I don’t have any CF page rule for static assets and I noticed the following Requests/Responses (examples):

https://lamiacasaelettrica.com/wp-content/plugins/atomic-blocks/dist/assets/fontawesome/css/all.min.css?ver=1600369782

cf-cache-status: HIT
x-via: speedwp/origin,nohtml

https://lamiacasaelettrica.com/wp-content/plugins/akismet/_inc/form.js?ver=4.1.6

cf-polished: origSize=700
cf-cache-status: HIT
x-via: speedwp/origin,nohtml

https://lamiacasaelettrica.com/wp-content/plugins/wp-appbox/img/googleplay.png

cf-polished: origFmt=png, origSize=3106
cf-cache-status: HIT
x-via: speedwp/origin,nohtml

https://lamiacasaelettrica.com/fonts.gstatic.com/s/opensans/v18/mem5YaGs126MiZpBA-UN7rgOUuhpKKSTjw.woff2

x-via: speedwp/proxy
server: cloudflare

Even no HIT in the last example.

I was expecting to have cf-cache-status: HIT and x-via: speedwp/cache for all static assets.

I wasn’t able to find any CF documentation about x-via: speedwp/* responder header so I am not sure how the system is behaving with static assets.

I wouldn’t worry too much about the x-via header unless you are getting a cf-cache-status: DYNAMIC header.

I see here that you are getting a cf-cache-status: HIT header on all resources, which means they are being cached properly.

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.