Hi @javismiles
Yes. It looks like the assets are actually cached. You can check the Disable Cache in Chrome dev tool to see the difference when it is not cached (file size column should show the download size instead of memory cache/disk cache).
but the status is 200, shouldnt it be a different status number if it was really reading it from cache
Status 200 is fine it indicates the cached content is fulfilled in the browser cache. A different status code? Do you mean 304 Not Modified? It involves requests to the backed and backend confirms that the local cached file is not changed.