This warning is due to the fact that the search-insights library sends the event with "nagivator.sendBeacon", a function that makes a request asynchronously without parsing the answer. Chrome raises a CORB warning when the response was going to be delivered to a context that can't handle it.
This is a known issue, but the fix would be a breaking change, so this is currently not something Algolia is actively working on to fix.
