InfinitySummer.Web design and development with online booking for a holiday rental company in Gran Canaria.
- booking
- Direct
- Real availability and prices on every page, read from the company's own system
- responsive
- 100%
- Designed mobile first, because that's how guests arrive
- Desktop Lighthouse
- 99
- Desktop, on every page · LCP 0.9 s and CLS 0.001
What was there, and what's there now.
Guests met each property inside a portal, in whatever photo order the listing chose: pages that opened on a bathroom or a kitchen, and no screen of their own where you could see the whole place before deciding.
A website of their own designed mobile first, with a full-screen gallery for every property, real availability and prices on each page and direct booking with the company.
Infinity Summer Canarias manages villas with private pools and apartments across El Salobre, Las Palmas, Arguineguín, San Agustín and Maspalomas. All of it lived inside the portals: guests met the property on someone else's listing, in the photo order the platform chose, with several pages opening on a bathroom or a kitchen, and no screen of their own to see the whole property, the area and how the company treats its guests before deciding. The challenge was to build that screen, make it flawless on mobile, where almost all tourist traffic comes from, and make booking directly with the company as easy as booking on a portal.
We built the website in React and TypeScript with a journey designed from mobile outwards: the area leads to the property, the property to the gallery and the gallery to booking, with no dead ends. Each property page brings together capacity, bedrooms, beds, bathrooms, size and real guest ratings, and the cover photos were hand-picked so each home opens on its pool, terrace or views. We didn't reinvent booking: we integrated the engine the client already used, where their availability and prices live, so guests see the real calendar and prices on every property page, pick their dates on the website and confirm in the company's own system, which keeps working with the tool they know, without duplicating calendars. The blog is managed from a headless CMS the client publishes to.
Four things a template could never deliver.
01Design
An editorial system of big photography and serif headline typography, built for this company and not lifted from a holiday rental theme. Each property's cover was hand-picked: it opens on the pool or the view, never a bathroom.
02Speed
React, TypeScript and Vite with per-route code splitting, WebP photography in three widths with placeholders so nothing jumps while loading, and fonts served from their own domain instead of Google. LCP of 0.9 s and CLS of 0.001.
03Experience
Designed mobile first, because that's how guests arrive: filters by area and capacity, a full-screen gallery you can swipe or navigate by keyboard, and each property's calendar and prices in view on its page, so guests can decide without hunting for them on another website.
04Local SEO
Every property and every area has its own URL with a hand-written title and description, plus structured data and a sitemap generated at build time. Real searches (villa with private pool in Maspalomas, apartment in Las Canteras) land on the right page.
Journey and architecture
We mapped the guest's path (area, property, gallery, booking) and built the URL structure per property and per area from it. Every decision was made looking at mobile first.
Visual system and photography
An editorial language of big photos, with a curated cover for every property. All photography was optimised to WebP in three widths with placeholders so the page doesn't jump while loading.
Development and bookings
React, TypeScript and Vite with per-route code splitting, catalogue filters and a full-screen gallery. Booking integrates with the engine the client already used, so availability and prices aren't duplicated. The blog lives in a headless CMS the client publishes to.
Performance and technical SEO
WebP photography in three widths, self-hosted fonts and a page-weight budget watched on every view. Sitemap and metadata generated at build time, with a dedicated URL per property and per area.
