Actually, it is one of the leading causes of issues here… Blynk, and other IoT based applications that need exactly timed processes do not work well with standard Arduino style “Run everything fast as possible in the main loop, except when we want to wait, which then stops everything else as well” coding practice.
Unlearn old ways and look to the separate timed functions that more advanced programming uses.
Blynk functions and commands, properly utilised, can and will run as fast as the minimum network lag will allow… I have pushed limits inside a Local network with Local Server to the low ~15ms between groups of Blynk.virtualWrite() commands…