What the couple sees
They found you on Instagram, tapped the link in your bio, and the site opened in Instagram's browser on mobile data. White screen. A logo. A spinner. They swipe back to Instagram and open the next photographer. Your best work was three seconds from appearing and it never did.
Slow portfolios are the most common failure of creative websites and the first thing a couple notices. The causes are few and all fixable.
Why it is slow
The export was uploaded. A 6000-pixel JPEG at 5 MB, shown in a column 800 pixels wide. Forty of them on the page is 200 MB. The theme did not resize it; it just displayed it smaller.
Everything loads at once. All forty images start downloading the moment the page opens, competing with each other, so the first one arrives no sooner than the last.
The hero is a slider or an autoplaying video. The largest thing on the page, loading five images or a video file before anything else can.
The gallery plugin. Lightboxes, masonry scripts and animation libraries that add a second before the first image is requested.
The hosting. A shared server a continent away from the couple.
1. Resize and compress automatically
The site should generate every size it needs from your upload: a thumbnail, a column width, a full width, each at two pixel densities, in a modern format (WebP or AVIF) with a JPEG fallback, at a quality setting no client will notice. You upload the export once; the build does the rest. A 5 MB export becomes a 150 KB image at the size it is shown, and the forty-image page becomes a few megabytes instead of 200.
This is the single change that matters most, and it has to be automatic. A rule that says "please resize before uploading" is ignored the week before a wedding.
2. Load what is on screen first
The first image, the one visible without scrolling, is prioritised: it is requested first and given a placeholder so the layout does not jump. Everything below the fold is lazy-loaded, requested only as the visitor scrolls towards it. The visitor sees a finished first screen inside a second and never notices the rest loading.
3. Remove the slider and the autoplay
One strong hero image, chosen for the page, or a video embedded with a poster image that plays when tapped. Videographers and DJs and bands: the showreel or the clips hosted on Vimeo or YouTube, the embed lazy-loaded, never autoplaying. The reel plays when asked; the page does not wait for it.
4. Cut the gallery scripts
A grid with a lightbox is a few lines of modern CSS and a small script, not a plugin with its own animation library. Every script that is not needed to show the work is removed.
5. Host it properly, with a CDN
Images served from a content delivery network with edge locations near the visitor, cached, with the right headers. Managed hosting or a framework host does this by default.
6. Edit harder
A full wedding story of eighty images and a highlights set of thirty beats two hundred favourites. Fewer, better, faster. Couples do not scroll to the end of two hundred anyway. For a wedding photographer, one or two full stories plus highlights is the whole portfolio.
Measuring it
Core Web Vitals in Search Console, mobile: Largest Contentful Paint under 2.5 seconds is Google's threshold, and a well-built portfolio comfortably beats it. PageSpeed Insights on the portfolio page, mobile, before and after. And your own phone, private window, mobile data, in a car park: count.
What it does not require
Fewer images than you want. A different platform. Smaller files from you. A portfolio built for speed takes your full exports and makes them fast; that is the whole point of building it rather than templating it.
Where this sits
Automatic compression and sizing, lazy loading and a fast host are the foundation of every photography and events website we build, because nothing else on the site matters if the work does not appear. A slow portfolio is also the most common finding of a diagnosis on an existing creative site, and the fix rarely needs a rebuild.