For a long time, we said that Solitics’ response time was 1.8 seconds.
And to be clear, that number was never the typical experience.
It was the maximum. A worst-case ceiling. Most of the time, the platform responds much faster than that.
Still, it was the number we stood behind.
Recently, we realized something: That sentence was no longer true.
Today, we’re comfortable saying 0.8 seconds instead.
This change wasn’t intentional. But it also wasn’t unintentional.
Built for speed, not for a number
We didn’t run a big ‘let’s-get-faster’ initiative.
There was no dramatic optimisation sprint or single breakthrough moment.
What we did do, from day one, was build Solitics with speed as a first-class principle.
That means:
- Real-time decisions instead of batch logic
- Lightweight architecture instead of layered workarounds.
- Fewer hops, fewer assumptions, fewer ‘we’ll fix it later’ compromises.
Over time, small improvements accumulated:
- Smarter decision paths.
- Faster data access.
- Better prioritisation of what truly needs to happen in real time.
None of these were designed to hit a specific benchmark.
They were designed to make the platform behave the way real user experiences demand.
Eventually, someone asked a simple question:
‘Why are we still saying 1.8?’
So we checked.
Then we checked again.
And that’s how we got here.
Where lightning-fast response time is most relevant
Anonymous visitor engagement
The first seconds of a session are fragile.
If an experience adapts too late, it feels injected — like the system missed its chance.
At 0.8 seconds, interactions appear while intent is still forming. Messages feel native to the page, not layered on top of it.
This isn’t about being faster than ‘pretty fast’.
It’s about being fast enough not to interrupt the moment.
In-session personalisation
Personalisation only works if it stays inside the flow of the session.
Once a response arrives after the user has already moved on, its accuracy becomes irrelevant.
0.8-second reactions keep journeys responsive rather than reactive – adapting in real time instead of commenting on what just happened.
Gamification and micro-interactions
Delight is extremely sensitive to delay.
Rewards, progress updates and feedback loops only work when they feel instant. Even small lags break immersion and remind users there’s a system behind the experience.
0.8-second responses allow the system to disappear. Which is exactly the point.
Speed as a basline
For most platforms, speed is something to optimise.
For Solitics, it’s something to assume.
That’s why the shift from 1.8 to 0.8 happened quietly and why it will probably happen again.
