Currently, avatar performance rank can be affected by bounding box size in a way that appears inconsistent when avatars use different default/import scales.
Two avatars can have the same effective in-world size, mesh complexity, materials, textures, physics, and runtime behavior, but receive different performance rankings because one has a different default scale or authored scale. In that case, the bounding box metric is not measuring actual runtime impact consistently.
Reproduction steps
  1. Take the same avatar with identical meshes, materials, textures, shaders, and physbones.
  2. Upload one version at a normal avatar height (~1.5m).
  3. Upload another version scaled to ~15m height.
  4. Scale both avatars to the same effective in-world size during runtime.
  5. Observe that the larger-authored avatar receives a significantly worse performance rank due to bounding box size, despite equivalent effective runtime appearance and behavior.
The bounding box check should ideally normalize the bounds relative to avatar size.
Large bounds can still be a legitimate concern for culling or visibility behavior, but equivalent in-world avatars should not receive different rankings solely because of differing default scale metadata.