Build -
We cut our home page in half, and it got more interesting
Our home page was 26 screens long on a phone. We cut it to 14, swapped paragraphs for two short films, and found that our first film stuttered on slow phones. Here is what we cut, what we built and how we fixed it.
We showed famingu.com to a few people outside the studio and asked them to be blunt. They were. The page had too much to read, it told people what we do instead of showing it, and nothing on it made you stop scrolling. When we measured it, the home page was 26 screens long on a phone. Nobody reads 26 screens.
So we cut it from 13 sections to 7: the opening, the client logos, a short film, three cards for what we do, an AI receptionist section, a row of demos you swipe through, and one section on who builds it and how. Each section now says one thing and gives you one thing to do. On a phone the page went from 26 screens to 14, and on a laptop from 19 to 10.
Nothing was thrown away. The long explanations already lived on the service pages, which are the pages search engines rank for those topics, so the home page now points to them instead of repeating them. The system builder, where you tap your kind of business and see the system we would build, moved to the solutions page.
The first film is a golden thread. As you scroll, one gold thread knotted around the apps a business juggles (WhatsApp, Excel, Tally, a paper diary) pulls itself straight into one clean line. The steps of a customer's journey light up along it: a message at 11:02 pm, the AI reading it, a reply, an order, an invoice, and the owner seeing it all at 9 am. Then a card asks what your business is, builds a sample of your system with your name on it, and opens a real demo workspace.
The second film is night to morning, for the AI receptionist. The clock runs from 11:02 PM to 9:00 AM, the sky turns from night to sunrise, and a web chat, a call and a text get answered while the owner sleeps. At 9 AM there is a short summary, including the one thing that needs a person. On the home page it plays by itself once, in about 12 seconds; on the AI receptionist page it moves as you scroll. It is a made-up business with sample messages, and the page says so, along with the note that text messages to US numbers need A2P 10DLC registration.
Neither film uses an animation library. The thread is drawn on one canvas, everything else only changes position and opacity, and both stop working the moment they leave the screen. People who have turned off motion on their phone see the finished picture instead: the straight thread, the card, and 9:00 AM.
The honest part: the first version of the thread film stuttered. We test with the computer slowed down four times to act like a cheaper phone, and on a laptop-sized screen it dropped up to 19 frames out of 216 while scrolling. The cause was one convenient shortcut. We were setting a single scroll value on the whole film, so the browser recalculated the styles of everything inside it on every frame, including the card and its large glowing shadow. We switched to writing the new values straight onto the four or five elements that actually move, and drew the canvas at a lower resolution on big screens where nobody can tell. Dropped frames went to 0 on a phone-sized screen and 0 to 1 on a laptop.
Where it ended up, on our own machine: the page's own code grew from 6.2 kB to 6.4 kB, Lighthouse scores it 84 to 95 on mobile and 100 on desktop, and nothing on it shifts while it loads. These are local test numbers. The real test is people scrolling it on real phones, which is happening now, and if they find something we will write that up too.
Written by Rushi Prajapati