VITALIANO: a concept restaurant site where guests choose their exact table

VITALIANO is a fictional Italian restaurant group with three houses, as the site calls its restaurants: Moscow, Saint Petersburg and Sochi, which is due to open in 2027. VITON¹³ built it as a concept to show what a restaurant site can do beyond a menu and a phone number. The site is in English, with the dishes named in Italian.

The site had to answer the questions a guest asks before dinner: what is on the menu and what it costs, what to drink with it, where each house is and where exactly they will sit. Booking had to work as choosing a seat, not as filling in a form.

14 pages: Home, La Carta (the menu), Il Sommelier, Il Tavolo (reservations), booking confirmation, private dining events, Le Case (the houses on a map), Chi siamo (about), careers, contact, a demo account with bookings, a legal notice, privacy and a 404 page. The menu lists 34 dishes and 8 wines with prices; as the cursor moves down the list, a photo of the dish follows it.

Il Tavolo draws a floor plan of each house with 20 tables: window two-tops, the main sala, a communal tavolata, a chef’s counter by the wood oven, a private room and a terrace. Availability changes with the house, date, hour and party size; hovering over a table shows what is special about it, and “Surprise me” picks the best free seat.

Il Sommelier gives every dish and wine a taste profile on four dimensions. The guest sets four sliders and a mood, and the site composes the closest antipasto, main, dessert and glass into a priced menu with a match percentage for each. Dishes chosen on the menu or in the sommelier become a pre-order that travels into the booking and is served when the guest sits down.

The key path runs Menu → Sommelier → Reserve: a guest reads La Carta, lets the sommelier build a dinner, takes that pre-order to Il Tavolo, picks a table and gets a confirmation that also appears in the demo account. Motion sets the pace: a preloader with a counter, olive curtain transitions between pages, headlines revealed line by line, parallax, a pinned horizontal gallery of signature dishes, a hand-drawn ellipse that draws itself, marquees that speed up with scrolling, magnetic stamp-style buttons and a custom cursor.

The site is plain HTML, CSS and JavaScript with no build step. The header, footer and overlays come from one shared script, so every page stays identical; GSAP with ScrollTrigger and Lenis handle animation and scrolling. Bookings and the account are demo state kept in the browser’s localStorage, and nothing is sent anywhere. Photos and video are licensed stock photography and video from Unsplash and Pexels, loaded by direct links from their CDNs.

The concept exists as 14 working pages with 34 dishes, 8 wines, 3 houses and 20 tables on each floor plan. Lighthouse measured the home page on 22 September 2026. On mobile, with default throttling: performance 70, accessibility 94, best practices 77 and SEO 100, with LCP 5.0 s, CLS 0.015 and a 5.4 MB page in 31 requests. On desktop: performance 93, accessibility 94, best practices 77 and SEO 100, with LCP 1.0 s and CLS 0.025.

Checks across the 13 pages rendered in Chrome (the 404 page excluded) found a unique title and exactly one H1 on every page, the lang attribute set to en, layouts that fit a 390 px screen without horizontal scrolling, alt text on 100% of images and 0 broken internal links. Canonical tags, Open Graph tags and structured data are on 0 of 13 pages, and there is no sitemap.xml or robots.txt.

VITALIANO is a concept built by VITON¹³ to show range, not a commissioned project. The restaurant group, its three houses, the people, dishes, prices and addresses are fictional. The site has no domain, no visitors, no search traffic and no bookings: every booking and pre-order is demo state that stays in the browser. Photos and video are licensed stock photography and video from Unsplash and Pexels.

The Lighthouse scores are lab measurements of the home page on one day, not field data from real guests, and a 100 SEO score covers the basics only. The case does not show how booking would work with a real reservation system, kitchen or payment, and it does not prove that the site would bring guests to a restaurant.