Concurrent request limit for A-Frame <a-assets> element

The Concurrent Request Ceiling

A-Frame does not have an internal concurrent request limit. Because the <a-assets> element relies on the browser's native loading mechanisms (via Three.js LoaderManager), the maximum number of simultaneous network requests is determined entirely by the browser and the network protocol in use.

Protocol-Based Limits

The behavior differs significantly based on the protocol negotiated between the client and the server:

• HTTP/1.1: Most modern browsers (Chrome, Firefox, Safari, Edge) limit concurrent connections to 6 per origin. If you have 20 textures in your <a-assets> block, the browser will queue them, downloading only 6 at a time.
• HTTP/2 (and HTTP/3): These protocols use multiplexing, allowing many requests over a single TCP connection. While the theoretical limit is much higher, browsers and servers often cap concurrent streams (typically between 100 and several hundred). In practice, this removes the bottleneck for most A-Frame scenes.

A-Frame's Influence and Versioning

A-Frame provides no API to observe, throttle, or increase this limit. This behavior is consistent across A-Frame releases (from 1.x through current versions) because the underlying Three.js loading logic has remained functionally the same regarding network dispatch.

How to Verify and Manage Loads

To determine the actual concurrency in your specific environment, use these steps:

1. Open your browser's Developer Tools (F12) and navigate to the Network tab.
2. Refresh the page and observe the "Waterfall" column.
3. Look for "stair-stepping" patterns: if requests start in groups of 6, you are limited by HTTP/1.1. If they all start nearly simultaneously, you are utilizing HTTP/2 multiplexing.

If you are hitting HTTP/1.1 limits and cannot upgrade your server to HTTP/2, you can bypass the per-origin cap by hosting assets across multiple sub-domains (domain sharding), as the browser maintains a separate connection pool for each unique origin.

Diagnostic Requirement

To provide a more specific recommendation for optimizing your load times, please specify if your assets are served via a CDN or a custom backend, as this determines whether you have control over the protocol (HTTP/2) and compression settings.