No, you can't because when you are uploading a new image ( not replacing it) then magento do that for you ( rename the file name ).
I will recommend you rename image file name if you want it to reflect on browser. But if you dont change file name than it will reflect when CDN cache expire.
I may have a simple solution. At least, the concept below is quite simple:
change the place where store specific config data are stored so that they are separate from the current config. To do this, write an around plugin for the function
clear all the store config data in one script. I would look at customising the ...
if you have 14sec TTFB this is related to your code processing time, check profiler or newrelic,
probably you are trying to load something big on that page.
js bundle is bad
I have created a gulpfile to improve the speed development process.
if you don't need any special tools it should be fine and you can try the "superwatch" task that I created to avoid running an exec command with each new file added :)
I had the same problem when upgrading from 2.3.5-p1 to 2.3.5-p2, even when the deployment included disabling the Magento_GoogleShoppingAds module in config.php.
In my case the solution was to flush Redis cache right before the deployment.
Is this code running on the frontend? If not and it's Admin / CLI / cron, try using \Magento\Store\Model\App\Emulation to emulate being on the store.
$this->appEmulation->startEnvironmentEmulation($storeId, \Magento\Framework\App\Area::AREA_FRONTEND, true);
//Run code to get image here...
The referenceBlock does not support cacheable as an attribute
You have to define cacheable="false" within <block> not <referenceBlock>
The referenceBlock tag does not support the cacheable attribute. Hope this info helps you.
Let me know if you still have any queries.