Web Development & Events 2025
Sala Apolo
Symfony platform for Barcelona's iconic concert venue: dynamic schedule, optimized event pages and +30% clicks to ticketing.
- Symfony Development
- UX/UI Design
- Performance Optimization
- CRO
- Ticketing Integration
01The challenge
The challenge
Sala Apolo manages a dynamic schedule with intense traffic spikes when popular concerts are announced or during campaigns. The primary goal is to drive traffic toward ticket purchase (external ticketing) without friction, especially on mobile. The team needs fast publishing for last-minute changes with control and stability.
02The solution
The solution
We developed a Symfony platform with an 'event-first' model: visual calendar, genre and date filters, comprehensive event pages with associated content and consistent CTAs to the ticketing system. We implemented funnel tracking with standard events and prepared performance for demand peaks with a caching strategy, query optimization and compressed assets.
Tech stack
How it's built
Front end
- Twig Front-end templates
Engine
Data
- PostgreSQL Database
- Redis In-memory cache
- Varnish HTTP cache
- Cloudflare CDN & security
03Architecture
How a request flows
-
A concert is announced and the editor publishes the event in Symfony's 'event-first' model, with the full page ready within minutes
-
The traffic spike that follows the announcement first hits Cloudflare and then Varnish, which serves the listings and event pages from cache
-
The visitor filters the listings by genre and date and reaches the event page, with the CTA to the external ticketing system always visible
-
On clicking, the platform records the funnel tracking event and redirects to the external ticketing system
-
The caching strategy and query optimization keep load times low even at peak demand
04Measured impact
Results
- +30% Clicks to ticketing
- +16% Mobile conversion
- 99.97% High-demand uptime
- <2s Load time
Verifiable data
Metrics in detail
- Duration of the platform project (months)
- 7
- Specialists on the project team
- 5
- Cache layers to sustain the spikes after a concert announcement (Cloudflare, Varnish)
- 2
Methodology: Project scope data (2025): duration and team come from the contract; the cache layers, from the deployed architecture. The ticketing clicks, conversion, uptime and load time metrics are in the results section of this case study.
05The process
The process
-
Discovery
User flow analysis and friction point identification
-
Architecture
Event-first model and CMS design
-
UX/UI
Conversion-oriented design toward ticketing
-
Development
Symfony implementation with optimized caching
-
CRO
Funnel tracking and continuous optimization
06Showcase
The platform
Your next project?
Let's talk results
Tell us your challenge. We'll respond within 24h.
Start a conversation- NDA available
- Response <24h
- Phased proposal