Automated Spline Scene Performance Scorecards
Every Friday, WebRun checks every published scene in your Spline workspace for its views and average load time, updates each scene's Trello project card with the latest numbers, and posts a ranked scorecard to Microsoft Teams calling out any scene needing optimization.
How do I track weekly views and performance across my published Spline scenes?
WebRun checks every published scene in your Spline workspace each Friday for its views and average load time, updates each scene's Trello project card with the latest numbers, and posts a ranked scorecard to Microsoft Teams, calling out any scene whose load time needs optimization before it affects visitors.
- Every scene's performance is tracked in one weekly scorecard
- Slow-loading scenes get flagged before they hurt conversions
- Performance history builds up on each scene's own card
Built for Web design agencies · product teams · 3D web designers · marketing teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.spline.design/signinin a real browser with your saved login - no setup, no API keys. -
1
Spline - check each scene's views and performance
- Open the workspace and review each published scene
- Note views and average load time for each
- Flag any scene with a load time above target
Done when Every published scene has this week's views and load time recorded.
-
2
Trello - update the project card
trello.com
WebRun updates the project card in Trello. - Update each scene's project card with this week's numbers
- Note any scene flagged for slow load time
- Keep a running history in the card's comments
Done when Every scene's project card reflects this week's performance.
-
3
Microsoft Teams - post the weekly scorecard
microsoft.com
WebRun posts the weekly scorecard to Microsoft Teams. - Post the week's scorecard to the product channel
- Rank scenes by views
- Call out any scene needing optimization
Done when The team has this week's scene scorecard in Teams.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it optimize or edit the scene itself?
No. WebRun only reads views and load time and reports them. Optimizing a scene's performance stays a manual step for the 3D designer.
What counts as a load time above target?
Whatever threshold you set for your project, commonly a couple of seconds on average connections. Scenes above it get flagged for optimization.
Why track this in Trello instead of just Teams?
So each scene has a running history on its own card, useful for seeing whether performance is improving or getting worse over several weeks, not just this one.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.