Ana Arabia

We designed and built a fast, responsive landing page with a cinematic hero, layout that mirrors between Arabic and English, and the event details a visitor actually came for.

Web development

Start a project Visit ana-arabia.com

Ana Arabia event landing page designed and built by kaprera — Ana Arabia event landing page, built by kaprera

/ Overview

The challenge

A Riyadh Season event needed one page in Arabic and English that reads on a phone in a queue and looks like it belongs to the event rather than to a template.

The solution

We built it as a single Nuxt 3 page on Firebase: a cinematic hero, the event details a visitor actually came for, and one switch that mirrors the whole layout between Arabic and English without a reload.

/ What we built

Inside the project.

Cinematic hero introducing the Riyadh Season event
Full Arabic/English i18n with instant in-place language switching
Layout mirrors in full between RTL and LTR
Firebase hosting and analytics behind the scenes

/ Specs

Type: Event landing page
Stack: Nuxt 3 + Firebase
Languages: Arabic & English (RTL/LTR)
Scope: Design & development

/ Results

The outcome.

AR/ENFull bilingual support

100%Responsive across devices

<1sHero load time

/ Measured

Numbers anyone can re-run.

Every figure below is a real reading from a standard tool anyone can re-run: Google Lighthouse for speed and quality, the W3C validators for the code itself. Each one says what it means for you in plain language.

Google Lighthouse scores out of 100

86PerformanceHow quickly the page becomes usable. Google scores it out of 100, and 90 or above counts as fast.

96Accessibility A11Y · WCAGHow well the page works for people using a screen reader, a keyboard, or high-contrast settings, checked against the WCAG standard.

100Best practices BPWhether the site follows the modern rules of the web: HTTPS everywhere, safe libraries, and a browser console with nothing thrown into it.

100SEOHow readable the page is to search engines: titles, descriptions, crawlable links and valid robots rules.

Loading & responsiveness Core Web Vitals

1.0 sFirst contentful paint FCPHow long before the visitor sees anything at all. Under 1.8 seconds is the target.

1.4 sLargest contentful paint LCPWhen the main image or headline has finished loading, which is the moment the page looks ready. Google wants this under 2.5 seconds.

0 msTotal blocking time TBTHow long the page ignores taps and clicks because it is still busy loading. Zero means it never freezes on the visitor.

0.03Cumulative layout shift CLSHow much the page jumps around while it loads. Zero means nothing moves under the reader's finger mid-tap.

0 msInteraction to next paint INPHow fast the page answers a tap. It is measured on real visitors over time; the lab stand-in shown here is total blocking time.

Code quality & weight standards, size, dependencies

2 KBHTML, compressed GZIP / BRThe weight of the page's own code as it actually travels over the network. Smaller is cheaper and faster on mobile data.

NoFont preloadWhether the custom typefaces are requested up front, so text never flashes in a fallback font before settling.

6W3C HTML errorsErrors found by the W3C's official markup validator. Zero means the code is standards-clean, which is what keeps a site working through future browsers.

0W3C CSS errorsThe same official check applied to the stylesheets. Invalid CSS is where most cross-browser display bugs begin.

0Third-party originsHow many outside servers the page pulls from. Every one is another company that can slow the page down, break it, or track your visitors.

Measured on the live site at ana-arabia.com with Google Lighthouse 12.8.2 (desktop) and the W3C validators, August 2026.

/ More work