The landing page's floating field moves again when the page loads

What changed for people using Bellwether

• The field waits for the page. On a normal laptop or desktop the field measured its own speed during the busiest second of the page load, judged itself too slow and left a still picture for the whole visit. It now waits until the page has finished loading before it measures.
• A slow start gets another try. If the first measurement is slow, the still picture stays and the field tries again up to three times: after 6, 20 and 60 seconds, or earlier when you return to the tab or resize the window. A machine that keeps failing sees the same still picture throughout.
• Reduced motion is unchanged. If your device asks for reduced motion you get the still picture at once, as before.

What you may notice

• The moving points arrive about five seconds after the landing page opens, two and a half seconds or more later than before. Until then the still picture holds their place, and nothing flashes when they take over.
• A fast machine now gets the whole field. Before, a busy page load could leave it with half of the points for the visit.
• The sign-in page and every screen inside the console look and behave as they did.

Switched on

• Nothing to switch. The change applies to every visit to the landing page from this release.

Known gaps and what’s next

• A machine that cannot draw the field at 24 frames a second keeps the still picture. That is the intended result there.
• When only half of the points are drawn, the field looks sparser than the still picture it replaces. A denser look for it is a design question for a later release.