HTTP/3 is faster with some work and help from Cloudflare
How the Uber-bound delivery giant tuned its mobile networking stack to cut latency
When using mobile apps to order food, the time spent navigating the app is considered wasted. At P99 2026 virtual conference, an engineer from Delivery Hero explained how the company migrated most of its user base to HTTP/3, cutting the app's total end-to-end response time by 17%. While HTTP/3 is faster than HTTP/2, it has some slow aspects that need adjustments.
Delivery Hero, a global delivery service, serves 60 million users across Europe, Latin America, Africa, the Middle East, and Asia. The company centralized management of various apps for different regions, each built or acquired. Delivery Hero's engineering team aimed to minimize the impact of varying network connectivity by moving to HTTP/3.
The Internet Engineering Task Force (IETF) introduced HTTP/3 in 2022, replacing the previous TCP with QUIC. QUIC, developed by Google, offers faster performance by not waiting for a signature and reducing the round trips needed for secure connections. Delivery Hero used Cloudflare's content delivery network to serve its global user base, making the transition to HTTP/3 relatively easy.
Most mobile clients supported HTTP/3 out of the box, while Android required additional engineering. However, certain secondary screens experienced latency issues due to Cloudflare's choice of the Cubic congestion control algorithm, which struggled with packet loss. Delivery Hero is collaborating with Cloudflare to resolve this issue.
Written by urgent.news from The Register Science's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
This story
This is one outlet's version. Read the fullest account.
- HTTP/3 is faster with some work and help from Cloudflare theregister.com
