03 / Website for a video production brand
Cammanvideo
A website that sells video services the way good video looks: an impressive showcase of work combined with fast loading and a deliberate path to contact.
- Client
- Cammanvideo, an independent video production brand
- Services
- Websites
Homepage — opening section with featured video work
1920×1080 px, AVIF/WebP
Overview
A video brand faces one fundamental problem with its website: it has to prove quality through imagery, yet it cannot afford a page that takes ten seconds to load. For Cammanvideo I built a site that reconciles both demands. The portfolio plays like a showreel, and the page opens fast on a phone and a weak connection too.
Visual impact alone was not the goal, though. The site had to work as a sales tool: show clearly what services the brand offers, build credibility with real productions, and lead visitors toward an enquiry rather than just pleasant scrolling.
I ran the whole project in direct contact with the brand's owner — from defining the structure and how the work should be presented, through implementation, to launch and the SEO foundations. No intermediaries, no decisions relayed through other people.
Challenge
The core tension in this project was media versus performance. Video and large frames are the product here, so they could not simply be stripped down — and at the same time a slow page drives visitors away and hurts search rankings. The media layer had to be engineered, not just styled.
The second challenge was structure. A good-looking page does not generate enquiries by itself: a visitor has to grasp within seconds what the brand does, see proof of quality, and know what the next step is. All of that while the visual identity stays consistent on every page.
My role
I was responsible for the entire technical delivery: information architecture, front-end implementation, media optimization, SEO foundations and the production launch. [TO BE PROVIDED: authorship of the visual design — my own design or collaboration with a designer].
Decisions were made in one-on-one conversations with the brand's owner, on working versions of the site that could be clicked through and commented on, rather than on mockups and slide decks.
Solution
A structure built for enquiries
I designed the page hierarchy around a single path: a strong opening with the best production, a clear presentation of services, proof of quality, and a distinct call to contact. Every page has a defined next step, so a visitor never hits a dead end.
Presenting the video work
The portfolio is built on carefully chosen stills rather than dozens of embedded players. Video loads only when the user explicitly asks for it — browsing the work stays smooth, and the page does not carry the weight of every player at once on first load.
Performance despite heavy media
Images are served in modern formats (AVIF/WebP), sized for the actual screen and loaded only when needed. The page content renders statically, so the first view never waits on a backend — a simple architecture that is fast by construction.
Responsive design and brand consistency
The site was built mobile-first, because a large share of a video audience arrives on a phone. Colors, typography and spacing are defined as brand tokens used by every component, so the visual identity is identical on the homepage, in the portfolio and in the footer.
SEO foundations and handover
The site has correct semantic structure, metadata for search engines and social sharing, and a sitemap. After launch I handed the owner the full set of access credentials along with instructions for making changes. [TO BE PROVIDED: how content is managed — a CMS or updates in code].
Technology stack
Front end
- TypeScript
- React
- Next.js
Media and performance
- AVIF/WebP
- Responsive images
- Lazy loading
SEO and sharing
- JSON-LD (Schema.org)
- Open Graph
- XML sitemap
Deployment
- Git
- [DO UZUPEŁNIENIA / TO BE PROVIDED: hosting produkcyjny / production hosting]
Engineering decisions
- 01
Stills instead of embedded players: video loads on demand, not on page entry. That single decision determined the speed of the entire portfolio.
- 02
A static architecture: a marketing site does not need an application server, so there is none. Fewer moving parts that can fail, and a smaller attack surface.
- 03
One primary call to action per page instead of several competing buttons — the path to an enquiry should be obvious, not scattered.
- 04
Media prepared at build time: multiple sizes and formats generated automatically, instead of serving original camera files.
Security & reliability
All traffic runs over HTTPS, and the site sends a set of security headers that shut down the typical attack vectors against websites.
The contact form is protected against spam in a way invisible to humans and collects only the data needed to answer an enquiry, following the principle of data minimization.
The static nature of the site and a short dependency list limit what can be attacked in the first place; dependencies are kept up to date.
Outcome
The brand now presents itself online at the level of its productions — the site itself works as proof of quality before a visitor plays the first video.
The portfolio browses quickly on a phone as well, so heavy media no longer costs the visitors who arrive from social channels.
The owner has a clear path from a visit to an enquiry, plus the full access and knowledge needed to keep the content current.
Gallery
Portfolio grid with production stills
1600×1000 px, AVIF/WebP
Mobile view of the services page
390×844 px, AVIF/WebP
Contact section with the enquiry form
1600×900 px, AVIF/WebP
More work
Let's talk about your project
Happy to walk you through how a similar approach would work in your case — and what I would avoid.
- Phone
- +48 573 021 012