Property & constructionSites that prove the work before the first call, from planning to handover.
Every industry buys differently, so every industry gets its own page.All industries →

Why Your Photography Portfolio Website Is Losing Clients Before It Even Loads

To fix a slow photography portfolio, resize and compress your exports, show fewer images at first and test the site on mobile data.

By Mikkel Calmann, Founder, TypzaUpdated 9 min read

In this article
  1. What "slow" actually means for a portfolio site
  2. The three most common causes on photography sites
  3. How to test your own site honestly
  4. Fixes that don't require touching code
  5. What to ask a developer or platform if you're stuck
  6. Conclusion
  7. FAQ
  8. More insights for photographers

Picture a client who clicks your link on their phone, waits on a blank screen and leaves. Your images never got a chance. Here's how to find what's slowing you down and fix it.

1. What "slow" actually means for a portfolio site

Most photographers think of speed in vague terms: "my site feels a bit sluggish." That's not useful for fixing anything. What matters is a specific number: Largest Contentful Paint, the time it takes for the biggest visible element (usually your hero image) to fully render. Google and most visitors start losing patience past 2.5 seconds. Past 4 seconds, a meaningful share of visitors are gone, and photography sites, because they're built almost entirely around large images, are disproportionately at risk of blowing past that threshold.

The trap is that speed feels fine to you. You've visited your own site a hundred times, your browser has cached everything, and you're testing on a fast connection at your desk. Your actual visitor is often on a phone, on mobile data, clicking through from an Instagram bio link or a Google search, with zero patience and zero loyalty to your brand yet. They have no reason to wait. A slow site doesn't just lose points on a technical audit, it loses the booking before the visitor ever forms an opinion about your photography.

2. The three most common causes on photography sites

Almost every slow photography portfolio traces back to one of three culprits. The first is uncompressed, full-resolution image files being served directly. A photographer exports a gallery from Lightroom at full resolution and drags it straight onto the website, not realizing the browser is now downloading a 12MB file to display something 1200 pixels wide on screen. The second is too many images loading at once, particularly on homepage sliders or grid galleries that try to load everything above and below the fold simultaneously instead of loading images as the visitor scrolls to them.

The third, and the one photographers overlook most, is platform and theme bloat. Heavy animation libraries, autoplay video backgrounds, embedded fonts, and third-party widgets (booking calendars, chat plugins, social feed embeds) all add weight that has nothing to do with your photography and everything to do with slowing it down. Each one individually seems harmless. Stacked together on a template that wasn't built with photographers' image volume in mind, they compound into a site that feels heavy even before a single photo renders.

3. How to test your own site honestly

Run your homepage and your busiest gallery page through Google's PageSpeed Insights or GTmetrix. Look specifically at the mobile score, not desktop, since that's where most of your traffic and most of your friction lives. Note the Largest Contentful Paint time and the total page weight in megabytes. A photography gallery page can reasonably run 3-5MB if images are properly optimized; if you're seeing 15-20MB or more, something in your workflow is exporting files far larger than what the page actually displays.

Also test on an actual phone, on cellular data rather than wifi, ideally somewhere with average signal rather than sitting next to your router. Time it with a stopwatch, not a feeling. If it takes more than three seconds for your hero image to appear, you have a real, measurable problem, and it's costing you enquiries you'll never know you lost, because those visitors don't leave feedback. They just don't come back.

4. Fixes that don't require touching code

Start with export settings. Before any image goes on your site, it should be resized to the actual display dimensions (rarely more than 2000px on the longest edge for a full-width hero) and exported as a compressed JPEG or WebP, not a lossless TIFF or an untouched RAW-derived export. Most photographers can cut file sizes by 70-80% with zero visible quality loss simply by exporting correctly the first time instead of relying on the platform to compress on upload.

Next, reduce how much loads at once. Trim homepage sliders to 5-7 images instead of 15, and make sure your platform lazy-loads images below the fold so the browser only fetches what's currently in view. Audit third-party embeds ruthlessly: does that autoplay background video actually book more shoots, or is it just aesthetic weight slowing down the one page every visitor sees first? Cut anything that isn't earning its place. A tighter, faster gallery of your best 20 images almost always converts better than a slower gallery of 60.

5. What to ask a developer or platform if you're stuck

If you've optimized your own exports and the site still lags, the problem is likely structural: a theme not built for image-heavy layouts, hosting that can't serve media efficiently, or a lack of proper lazy-loading and responsive image sizing (serving a correctly sized image to a phone instead of the same file used on desktop). Ask directly: does this platform serve responsive images automatically, or does every device download the same full-size file? Is there a CDN delivering images from a server close to the visitor? These aren't vanity technical questions, they directly determine whether your galleries feel instant or sluggish.

If you're evaluating a redesign, treat load speed as a non-negotiable requirement stated up front, the same way you'd state your gallery layout preferences. A photography site that looks stunning in a screenshot but takes six seconds to actually load on a phone in the real world is not a finished product. It's a portfolio nobody sees.

Conclusion

Run your homepage through PageSpeed Insights, then open it on your phone with Wi-Fi off. Re-export your heaviest images first, and cut your homepage to your strongest few. Then test again. A fast gallery makes your work feel more premium too.

FAQ

How fast should my photography website load?

Aim for your main image to appear within 2.5 seconds on mobile. That is Google's threshold for a good Largest Contentful Paint, the time it takes for the biggest visible element, usually your hero image, to render. Past 4 seconds, a meaningful share of visitors are gone. Run your homepage and busiest gallery through PageSpeed Insights or GTmetrix, and look at the mobile score and total page weight.

Do I need to sacrifice image quality for speed?

Usually not. The most common cause of slow galleries is serving full-resolution files, such as a 12MB Lightroom export displayed 1200 pixels wide. Resize to the actual display size, rarely more than 2000px on the longest edge for a full-width hero, and export as compressed JPEG or WebP. The post says most photographers can cut file sizes by 70 to 80% with no visible quality loss.

Is Squarespace fast enough for photography portfolios?

It can be, but speed depends on how any site is built rather than the platform alone. The post points to platform and theme bloat: heavy animation libraries, autoplay video backgrounds, embedded fonts and third-party widgets. If you've fixed your exports and the site still lags, ask whether the platform serves responsive images automatically and lazy-loads images below the fold, so phones get a correctly sized file.

How many images should be on my homepage?

Fewer than you think. The post suggests trimming homepage sliders to 5 to 7 images instead of 15, then linking to full galleries. Make sure images below the fold lazy-load so the browser only fetches what is in view. A properly optimized gallery page can reasonably run 3 to 5MB, while 15 to 20MB or more means something is wrong.

Should I use a gallery plugin or a built-in feature?

Built-in gallery features are usually the safer choice. Third-party widgets and plugins, such as booking calendars, chat plugins and social feed embeds, add weight that has nothing to do with your photography. Each seems harmless alone, but stacked on a template not built for them they slow the page. Audit every embed and cut anything that isn't earning its place, including an autoplay background video.

More insights for photographers

All photographers insights

How does your website score?

Enter your address and email. You get scores for speed, search, accessibility and trust in about a minute, and the full report by email.