What a fast portfolio is
A portfolio that shows the first image inside a second and finishes a hundred-image gallery in under two, on a phone, on mobile data, however large the exports you upload. It is organised so a couple finds work like their day, and a marketing manager finds work like their brief. Here is how to set one up, in order.
1. Decide the structure before the images
Portfolio organised by type, one section per kind of work you want to be booked for, each with its own enquiry route:
- Wedding photographers: two or three full wedding stories of 60 to 90 images each and a highlights set of about 30. See wedding photographer websites.
- Wedding planners: real weddings as case studies, each with the planning story, 20 to 40 images and supplier credits, with the couple's permission. A wedding planner website sells the planning, so the story matters as much as the pictures.
- Florists: by style and by season, because couples browse by look and seasonality drives price. See florist websites.
- Videographers: by type, weddings, events, commercial, one reel each.
- Commercial photographers: by industry and use. See commercial photographer websites.
- Venues: a gallery per space, plus real events held there.
Write the section list down. Every image you choose goes into one of them.
2. Edit hard
Fewer images, chosen for range. A couple wants to see a whole day told well, not two hundred favourites. Thirty highlights that cover getting ready, ceremony, portraits, details, party and light at different times beat a hundred portraits. Cut anything you would not want to be booked for again.
3. Set up the image pipeline
The site should take your full export and generate what it needs:
- Several widths (roughly 400, 800, 1200, 1600 and 2400 pixels) so a phone downloads the small one and a desktop the large one.
- WebP or AVIF with a JPEG fallback.
- A quality setting around 75 to 82; test against your own export and pick the lowest you cannot tell apart.
- A tiny blurred placeholder so the layout is stable while the image arrives.
- Lazy loading for everything below the first screen, and priority for the first image.
On a framework site this is the image component doing its job. On WordPress it is a properly configured media pipeline plus a CDN. Either way, it is automatic: you upload the export, once.
4. Build the gallery page
A grid or a justified layout in CSS, not a plugin with an animation library. A lightbox that opens the larger size when tapped. No slider on the section landing page; one strong hero image, chosen for that kind of work, then the grid. Each section page carries its from-price, a short paragraph and the Check my date button, so the portfolio and the enquiry are on the same page.
5. Handle video separately
Reels hosted on Vimeo or YouTube, embedded with a poster image you choose, lazy-loaded, never autoplaying. The reel plays when tapped; the page does not wait. One reel per section, not one per project.
6. Name and describe the images
File names and alt text that say what the image is: the venue, the kind of moment, the season. Not IMG_4471. It helps search, it helps accessibility, and it is how a venue's name on your site gets found by the next couple marrying there.
7. Get permission
Client work published with the couple's or client's consent, in the contract or asked afterwards. First names only for couples where allowed, nothing for anyone who declined. Commercial work with the client's sign-off on the case study. The same rule as reviews: real, and with permission.
8. Set up the upload routine
After each wedding or job: choose the images for the section, upload the exports, add the venue and a line of caption, publish. Fifteen minutes. The pipeline handles the rest, so the portfolio stays current without a developer and without a resizing step you will skip in peak season.
9. Measure it
PageSpeed Insights on the busiest gallery page, mobile. Core Web Vitals in Search Console, mobile, Good. Your own phone on mobile data in a car park: first image inside a second, gallery finished inside two. Check again after the season's uploads.
What it looks like when it works
A couple lands from Instagram, sees a full-width image before they have decided to leave, scrolls a whole wedding at a venue like theirs, finds the from-price beneath it, and taps Check my date. That sequence is the portfolio's job, and speed is what allows the rest of it to happen.
Where this sits
The image pipeline, the organisation by type and the upload routine are part of every photography and events website we build, because the portfolio is the product and it has to appear. The section list is yours; making every export fast is the build's.