How to fix the delay when receiving data of HC-05?

Hi everyone, my device sends data via HC-05, but its delay is long, the data uploaded on the app was slow, which caused my data test results to be problem.
How to fix this?
here time Clock in my aia:

What is the time between transmissions from the HC05?

Maybe the HC05 is a firehose?

Not enough information. We can't see anything except your words that it's too slow... we need blocks with which you receive data and the program code with which you send them.

After a period of time I disconnect the bluetooth, the data is transferred to the app, realtime is delay

It is better for the AI2 Clock Timer to run faster (less ms) than the transmitting device, to avoid backlogs.

Here is standard Delimiter advice to insure you receive complete messages:

Please see the Delimiter article in FAQ

Be sure to use println() at the end of each message to send from the sending device, to signal end of message. Do not rely on timing for this, which is unreliable.

In the AI2 Designer, set the Delimiter attribute of the BlueTooth Client component to 10 to recognize the End of Line character.
Also, return data is not immediately available after sending a request,
you have to start a Clock Timer repeating and watch for its arrival in the Clock Timer event. The repeat rate of the Clock Timer should be faster than the transmission rate in the sending device, to not flood the AI2 buffers.

In your Clock Timer, you should check

  Is the BlueTooth Client still Connected?
  Is Bytes Available > 0?
     IF Bytes Available > 0 THEN
       set message var  to BT.ReceiveText(-1) 

This takes advantage of a special case in the ReceiveText block:

Receive text from the connected Bluetooth device. If numberOfBytes is less than 0, read until a delimiter byte value is received.

If you are sending multiple data values per message separated by | or comma, have your message split into a local or global variable for inspection before trying to select list items from it. Test if (length of list(split list result) >= expected list length) before doing any select list item operations, to avoid taking a long walk on a short pier. This bulletproofing is necessary in case your sending device sneaks in some commentary messages with the data values.

Post the blocks that process the incoming AI2 data, so we can look for inefficiencies.