Thank you very much for a compelling response!
I’ve realized I could just compare the CF X vs SBCF http access reports by using the GTmetrix compare tool. So i did it.
The culprit turned out to be Google Maps api which is quite heavy and slow. The paid WP theme that I’m using does not support defining map markers via coordinates so it stupidly does geocoding EACH TIME a page is loaded. Sadly, I’ve run out of support on that theme so I cannot make a feature request.
Now, interesting thing is that enabling SBCF ‘JS-script free’ form in the middle of the page in question somehow prevents 18 geocoding requests from being sent. Which results (surprise!) in a much faster page – and a blank map which I did not notice as it is located within a modal window.
Now, replacing SBCF with CF X somehow causes those geocoding requests to fire off which makes the page ‘slow’.
Just out of curiosity, what do you think could cause this behaviour?
Meanwhile I guess I will switch back to CF X and look for alternative map solutions….
