In the first Toprova session, 16 sites were reviewed. For 8 of them, the AI agents could not reach a judgement from the screenshots. Two returned an anti-bot page and two were too slow. The other four were stuck on a 3D loading screen. Those sites were not necessarily bad. They were simply empty at the moment the screenshot was taken.

The human jurors open the real site and wait. But not all your visitors are that patient, and neither is your speed score. Here is how to show something straight away.

Content first, 3D second

  • Build the heading, text and navigation in HTML, visible from the first render. The 3D scene is layered in front or behind; it does not replace the page.
  • While loading, show a still image of the scene rather than a progress bar on a black background.
  • Do not cover the whole page with the loading screen. If you keep one, limit it to the 3D area.

Load in stages

  • Start with a lightweight version of the scene, then load detailed models and textures in the background.
  • Only load what is visible. Scenes further down the page wait until the visitor gets close, using IntersectionObserver for example.
  • Compress the geometry of your glTF models with Draco or meshopt. Files become much smaller.
  • Convert your textures to KTX2 (Basis Universal). They stay compressed in graphics memory and reach the GPU faster.

Do not block the interface

A heavy scene can freeze the main thread for several seconds. The page stops responding, and Total Blocking Time, which makes up 30 % of the speed score, shoots up.

  • Initialise WebGL after the first render, not before.
  • Spread heavy work, such as shader compilation, decoding and object creation, across several frames.
  • Where possible, move rendering into a worker with OffscreenCanvas.
  • Keep links and buttons usable throughout loading.

Plan a fallback

  • Check whether WebGL is available. If not, show an image or a video instead, with the same content around it.
  • Think of devices without a powerful graphics card, older phones and power-saving modes. Automated browsers that take screenshots often fall into this group.
  • Respect prefers-reduced-motion: offer a still scene, or very gentle movement, to people who have asked for it.
A good 3D scene enriches a page that already works. It should never be the condition for seeing the page at all.