The problem
A real-estate portfolio site that worked on a MacBook — and only on a MacBook. 70% of inbound traffic was leaving.
Rebuilt the site from a four-perspective audit (founder / developer / client / marketer). 32 KB total, zero JavaScript, lead capture survives the mobile viewport every visit.
Market context: Real estate · long consideration window · mobile-dominant traffic · multi-region buyer base · trust-sensitive purchase.
Duration · Audit + rebuild cycle
See the live buildThe result · in numbers
32 KB
Total file weight
0
JavaScript
763
Lines of code · self-contained
4
Audit perspectives applied before rebuild
The brief
What the client actually needed.
A regional real-estate portfolio site that, on the surface, looked finished. The brief was to "make it look more premium." The real brief was different — the site worked on a MacBook and only on a MacBook. Roughly 70% of real-estate inbound traffic in this region is on mobile. The visible defects were the symptom; the architecture was the cause.
The problem
What was broken — in numbers.
The site looked premium on the desktop preview the founder was using to review the work. The buyer never saw the desktop preview.
- Mobile media queries
- Inadequate
- Lead-capture survival on small screens
- Broken
- Load weight before audit
- Heavy for the value delivered
- Real-estate mobile traffic share (region)
- ~70%
The approach
What we did. Why.
Four perspectives applied to the same site — founder, developer, client, marketer. Each lens caught issues invisible to the others.
- Founder lens — does this convert a mobile-first real-estate buyer into a site-visit booking?
- Developer lens — is the architecture serving the goal, or is the goal serving the architecture?
- Client lens — does this look like the kind of agency I want representing my property portfolio?
- Marketer lens — would I run paid traffic to this site and trust the funnel?
The execution
Inside the work.
Zero-JS rebuild
The previous build used JavaScript for layouts, image carousels, and viewport detection. Each library added weight, each added a failure point. The rebuild used pure HTML and CSS — semantic structure, grid + flexbox layouts, no client-side rendering. File weight dropped to 32 KB. The site loads on a Lucknow 4G connection inside a second.
Mobile-first viewport discipline
Every layout was designed at 375 px first, then progressively enhanced for larger screens. Lead-capture form survives every screen size — no horizontal scroll, no field cut-off, no CTA hidden below an over-tall hero image.
The outcome
What moved. And why.
A site that does its job on the device the buyer actually uses.
- 32 KB total, zero JavaScript — the load isn’t a failure point
- Lead capture survives the mobile viewport every visit
- Critical analysis document published alongside — the audit discipline becomes part of the deliverable
What didn’t work
Every honest case study has one. This builds more trust than ten testimonials.
The original "make it look more premium" framing was the wrong brief — chasing visual premium-ness on a site that wasn’t functional on mobile would have spent the budget on the wrong problem. We re-scoped the engagement to "make it work for the buyer first, then make it premium." That re-scope was a Clarity-Call conversation that could have been faster if we’d set the expectation upfront.
Real-estate site working on a MacBook and only on a MacBook? Bring it to the Clarity Call.
Book the Clarity Call
Bring one problem.
Leave with one framework.
The Clarity Audit is how every Clicknify engagement starts. 30 minutes, live, with the Founder. We diagnose one thing — a stuck channel, a leaky funnel, a brand decision that keeps slipping — and leave you with the framework to fix it. Yours to keep, regardless.
- 30 minutes · live diagnostic
- One channel, one funnel, or one brand decision
- Yours to keep — no pitch unless you ask for one
- Founder on every call
Ashwani Srivastava, Founder, on every call. Responses within 2 hours during IST business hours · same-day for international enquiries.