TL;DR. JustinHarris.AI built My Vegas Love Story, a Las Vegas wedding-film brand, a live production splash page: a true-transparent WebGL neon-heart hero that floats on the page, a real freeze-frame poster from the brand's own film, and a frictionless mobile form. It runs on the apex domain and is built to convert on a phone in the first three seconds.
Why a Las Vegas wedding videographer's first surface has to land in three seconds
When a couple is choosing who films their Las Vegas wedding, they are scrolling on a phone, comparing vendors, and giving each one about three seconds before they move on. For a brand-new film brand that first surface is the whole pitch. If it looks like a template, with a stock hero in a dark box and a cramped form, the couple reads cheap and they bounce, and the inquiry that would have become a booking never gets sent. The splash page is not decoration. For a creative brand it is the proof of craft, and it has to do that work in the time it takes to glance at a screen. That is the bar My Vegas Love Story needed its first page to clear: feel premium, feel like this exact brand, and earn the date inquiry on a phone, immediately. The neon heart, the brand's own film footage, and a form that takes seconds to send are all in service of that single three-second test.
What we built: a true-transparent neon-heart hero that floats on the page
The centerpiece is a neon heart, and how it is rendered is the difference between premium and cheap. A normal approach drops a neon video on the page, but the video carries its own dark rectangle, so the heart sits in a visible box and the illusion breaks. We replaced that with a custom rendering component that uses a stacked-alpha video technique: the color and the transparency are packed into a single video and recombined on the graphics processor, so the heart is genuinely transparent. It glows on the page with no box and floats on any background. Behind it runs real footage from the brand's own film, and the very first thing that paints is a real freeze-frame from that same scene, so the page is on-brand before the video has even loaded. When the page opens, the neon sign ignites and the words rise into place in sequence. It reads like a real neon sign, because that is what it is built to be, not a CSS pulse and not a dark-boxed clip.
Built mobile-first: a form that opens as a sheet, not a cramped box
Most couples will see this page on a phone, so the phone experience is the design, not an afterthought. A long inline form crammed into a phone screen is bad user experience, and it is where inquiries go to die. Instead, the mobile hero is a clean single column with one clear button, Start your story, and tapping it opens a full-width form that slides up from the bottom of the screen, the pattern phones use for input. On desktop, where there is room, the form stays inline as a two-column layout. The wedding-date picker is built for the brand and capped to the viewport, so it fits even the smallest 320-pixel phones instead of overflowing the edge. Every detail down to the heart-mark favicon is brand-true. The whole point is to make sending the inquiry feel like nothing, because the easier it is, the more couples actually do it.
How we made sure it loads clean on every phone before it went live
A splash page that looks great in one browser and breaks in another is worse than no page at all, because the couple who hits the broken version is gone for good. So before this page touched the apex domain, it was verified end to end. A browser-based QA agent loaded the real page across Chromium and WebKit, the two engines behind the phones and laptops couples actually use, at three different screen sizes, and returned zero critical issues. A separate cold-read clarity check confirmed that a person seeing the page for the first time understands in five seconds what it is and what to do. And the build itself has a guard: a no-orphan gate runs before every build and fails it if any referenced asset is missing, so a broken image can never reach a couple. The work was reviewed on a staging surface first and only promoted to the apex once it was approved.
Where it runs: live in production on the apex domain
This is not a mockup or a demo. The splash page is live in production on the brand's apex domain, myvegaslovestory.com, served on fast edge infrastructure and returning a healthy response. When a couple submits the inquiry form, it routes straight to the filmmaker's inbox, so a new lead is a message, not a dashboard nobody checks. The same heart-mark favicon carries across the brand's surfaces, so the tab, the bookmark, and the page all read as one brand. It is a small page by design, one screen, one job, and every gram of that screen is built and proven, not assembled from a theme.
Why a custom splash beats a template for a creative brand
A template can get a wedding videographer online, but it cannot make them look like the only choice. The template hero sits in its box, the template form is whatever the theme ships, and the template has no idea that the brand's heart should float and glow. For a creative brand, where the first impression is the product, those differences are the difference between a couple booking a call and a couple scrolling past. This page is custom code on the apex, with a hero rendered on the graphics processor from the brand's own film, a date picker built to fit a phone, a build that refuses to ship a missing asset, and a cross-browser QA sweep across real browsers before launch. It is the first thing a couple sees, done right, the same standard we hold for every brand surface we ship.
Related work
- The Moments guest-upload app for this same wedding brand
- The neon-heart brand identity behind the hero
- AI Managed Services
- See all of our work
Want a first impression that converts on a phone? Get your free AI Audit and we will show you exactly where your current site is losing the inquiry, and the surface that captures it. Get your free AI Audit.