News
Meet the Chrome Farm.
Many slim Chromes on one Mac, built for Buoy Optimize on the web. Each idea gets its own Chrome. It's free with a Buoy account.
Use buoy optimize and the chrome farm on our slow lights page.
That's all you ask. You don't pick how many ideas.
Updated October 21, 2026 · by the Buoy team
¼
the memory of a full Chrome
0.4 s
to start one
1 idea
per Chrome
A farm Chrome next to a full one, on our test Mac. See the numbers.
How it works
Many Chromes look. One Chrome times.
Buoy Optimize tries many ideas to make a slow page fast. The farm gives each idea its own Chrome. So your AI checks them all at once.
1
Ideas
Your AI writes down every way it can find to make it faster.
2
Build
It builds the best bets first. Each one is a new copy of the page.
3
Open
Each idea opens in its own Chrome, all at the same time.
4
Look
The AI snaps each Chrome, and you check the looks. An idea that looks wrong is out.
5
Time
The farm pauses the other Chromes. One idea runs alone while it is timed.
6
Again
It keeps what won and tries new ideas. It stops when it can't get faster.
Why time one at a time? All the Chromes share your Mac. While they all run, they fight over it. The others wait a few seconds, with their page still loaded.
Our test round
Six ideas. One clear winner.
We gave six Chromes six ways to draw glowing lights. Then we added lights to each idea until it dropped below 60 frames a second.
| Idea | Most lights at 60 fps |
|---|---|
| WebGL | 368,000 |
| Canvas, one glow picture | 21,000 |
| A div for each light | 4,000 |
| CSS animations | 2,000 |
| SVG blur, canvas shadow | Out: no glow |
With all six running, one idea drew no frames for 4 seconds. Alone, it held 4,000 lights. That's why speed is only timed with the others paused.
Why slim
Real Chrome, minus the window.
The farm runs Chrome without its window. It still draws with your Mac's GPU, like your own Chrome.
| Full Chrome | Farm Chrome | |
|---|---|---|
| Memory with your app open | 918 to 932 MB | 227 to 243 MB |
| Programs running | 7 | 4 |
| Ready to use | 0.6 to 1.3 s | about 0.4 s |
Each Chrome has its own storage and a memory cap. One Chrome can't take down the rest. You can pause the ones you aren't using.
How to start
Set it up once. Then ask.
Run this in your app's folder. It sets up Buoy MCP and the buoy-optimize skill.
$ npx -y @buoy-gg/mcp@latest init
1
Start your app
Run your web app's dev server, like you always do.
2
Get the farm's Chrome
Run
farm chrome setuponce. It's about 100 MB.3
Ask your AI
Name your slow page or component. The AI does the rest.
You need a Mac. The Chrome Farm guide has each step.
Questions