Trace everything: four times lighter

Every icon and button on Divo’s landing page passes through a pipeline nobody would design on purpose, demonstrated start to finish on camera ▸ 3:56: take the image GPT generated, trim its whitespace borders in Canva so it scales cleanly, stack two copies aligned to summon the “download selection” button (his words: “puros truquitos de Canva”), export at max quality, re-import, then hit the editor’s Trace option to convert the bitmap into an SVG ▸ 4:44.

Why suffer this? Juan opens with the joke, “porque nos gusta complicarnos la vida, no tiene otra explicación” ▸ 5:07, then gives the real one, and it has numbers. SVGs zoom without pixelating, but exporting SVG directly from the design tool produces bloated files; the traced version of the same asset is dramatically smaller ▸ 5:36:

nítido al zoom, liviano al cargar →

The teaching sits in the middle of the tradeoff triangle. They want assets that are crisp at any scale (vector), light enough not to slow the page (traced, not exported), and producible today with free tools (GPT + Canva + a trace button). No single tool offers all three, so the pipeline is the product of refusing to give any of them up, five manual steps per asset, applied to everything, the day before launch.

There’s also a quiet dogfooding note: these hand-traced SVGs are being loaded into Divo canvases, which means Divo’s own launch assets are stress-testing how Divo handles vectors. The pipeline feeds the tool that will someday replace it…