Luminare Collection curates private villas, concierge services and property advisory across Ibiza, the Balearics and the Greek islands. The product is not a booking engine: clients arrive through relationships, and the most valuable homes — including a private collection that is never openly marketed — are shown, not listed.
We built the platform that carries that collection. The brief was to make eighty-nine individual homes legible across five islands without ever turning the brand into a rental checkout.
The brief
A conventional rental checkout would have pushed the brand the wrong way and made the inventory look smaller than it is. What the collection needed was depth: every home presented on its own terms, with its setting, its layout, its included services and the reasons it was chosen.
At the same time, every route to the business had to stay a conversation. There is no cart anywhere on the site. Contact is an email or a WhatsApp message, and that is deliberate.
What we built
A Next.js front end over headless content, served through Cloudflare, with the collection modelled as first-class pages rather than a filtered database view. Every villa is a real, indexable URL with its own title, meta description and structured data — which is what lets a guest find a villa by name instead of by scrolling a grid.
- 89 villa pages plus collection, concierge, advisory, insights and contact routes — 105 URLs indexed
- A hospitality content model: guests, bedrooms, bathrooms, amenities, house rules and included services
- Enquiry-led conversion: pages carry pricing and availability cues, then hand off to a person
- An editorial layer of destination guides and buyer guidance, because this audience reads before it travels
What we measured
We profiled the five heaviest routes — the homepage, the collection index, a villa page, the concierge page and the insights index — in a plain Chromium instance at 1440 px, cold cache, two runs each.
Server response is the strongest part: 70 ms for the homepage and 177 ms for a villa page. The homepage ships 168 kB of markup compressed to 16.6 kB over the wire, and the image pipeline serves a 300 kB source photograph as 22 kB at 640 px and 123 kB at 1920 px in WebP — roughly four times lighter than the original, on a site whose product is photography. Layout shift stays at or below 0.023 on every page we profiled.
The part worth watching as the collection grows: Largest Contentful Paint sits around two seconds, and the LCP element is the headline text rather than an image or the server, so the wait is render and font timing on a page carrying forty to sixty-six requests. It is a budget to hold, not a problem to fix.