Fernside Studio
Background
Archive
Journal Entry

Speed Up Your Photography Website | Image Optimisation UK

Documented
Capacity
10 MIN READ
Domain
Website Performance & Ops

Photography portfolios face a paradox: you need high-quality images to showcase your work, but every extra megabyte costs you mobile visitors. The good news? You can serve gallery-quality images that load in under two seconds. If you optimise correctly.

According to comprehensive website speed research, 53% of mobile visitors abandon sites that take longer than 3 seconds to load. For photographers whose websites are naturally image-heavy, this is the single biggest conversion killer. When page load time increases from 1 to 3 seconds, bounce probability increases by 32%. Every extra second compounds the problem.

Here’s how to speed up your photography portfolio without sacrificing image quality.

The Real Culprit: Uncompressed Exports Straight From Lightroom

A 5MB JPEG from your camera is overkill for web. For web display at 1920px wide, a well-compressed 200-300KB WebP file is visually identical to the human eye. Most photographers upload exports that are 10-20 times larger than necessary, killing load times for zero perceptual benefit.

The mistake happens at export. Lightroom’s default “Export for Web” settings often produce files that are still too large because they prioritise print quality over web performance. You need to optimise specifically for screen display.

Correct export settings for web:

  • Resize to max 2000px on the longest edge (1920px is sufficient for most displays)
  • Export quality at 75-85% (80% is the sweet spot, visually identical, significantly smaller)
  • Convert to WebP or AVIF format (30-50% smaller than JPEG)
  • Strip all EXIF metadata (location, camera settings, copyright info adds kilobytes)

According to research on modern image formats, AVIF produces files roughly 20-50% smaller than WebP at equivalent perceptual quality, depending on the source image. Netflix’s internal benchmarks across a diverse image dataset showed AVIF achieving ~50% better compression than JPG on average.

For photographers, this means you can deliver stunning portfolio images at a fraction of the file size your camera produces.

Lazy Loading: Only Load Images When Visitors Scroll to Them

Most portfolios load 50+ images on page load, even if visitors only see the first six. Lazy loading delays offscreen images until needed. Modern browsers support native lazy loading (loading="lazy"), but photographers should ensure their site builder implements it correctly.

Here’s the difference it makes: without lazy loading, a 30-image portfolio page might load 15MB of data immediately. With lazy loading, only the 6-8 images visible on screen load initially, perhaps 2MB. The remaining images load as visitors scroll, reducing initial load time by 70-80%.

How lazy loading works:

  1. Browser loads only images visible in the viewport
  2. As visitors scroll, images just below the fold begin loading
  3. Offscreen images remain unloaded until needed
  4. Result: faster initial page speed, lower bandwidth consumption, better mobile performance

All modern browsers support native lazy loading. If your website builder doesn’t implement it by default, it’s a red flag that your site infrastructure is outdated.

At Fernside Studio, every photographer website we build includes automatic lazy loading for all portfolio images. It’s not optional. It’s foundational.

Modern Image Formats Cut File Size by 30-50%

WebP and AVIF offer better compression than JPEG with no visible quality loss. Browser support is now universal in 2026. According to browser support statistics from March 2026, WebP has approximately 97% global browser coverage; AVIF has approximately 93%.

The 4-point gap is mostly legacy Android devices and older Safari installations. For the vast majority of your visitors, modern formats deliver identical visual quality at dramatically smaller file sizes.

Format comparison for a typical portfolio image:

  • JPEG (original export): 1.2MB
  • WebP (equivalent quality): 450KB (62% reduction)
  • AVIF (equivalent quality): 280KB (77% reduction)

That’s the same image, visually indistinguishable, at less than a quarter of the file size. Multiply that across a 30-image portfolio and you’ve reduced load time from 36MB to under 9MB, without losing any quality your visitors can actually see.

Technical implementation:

Modern web servers can serve the most efficient format each visitor’s browser supports. Safari gets AVIF, Chrome gets AVIF, legacy browsers fall back to WebP or JPEG. This happens automatically with proper image optimisation infrastructure.

Fernside sites serve images in the most efficient format each browser supports, automatically. You upload once; visitors receive the optimal format for their device.

For more on choosing the right format, see the detailed comparison of WebP vs AVIF.

Use a CDN to Serve Images From the Edge

Images served from a single server in London take longer to reach visitors in Manchester, Glasgow, or internationally. A CDN (Content Delivery Network) caches images closer to the visitor. Cloudflare, for example, serves images from 300+ global locations. This is automatic on Fernside-built sites.

How CDN delivery works:

  1. You upload images to your website (single origin server)
  2. CDN automatically replicates images to hundreds of edge locations worldwide
  3. When a visitor in Edinburgh loads your portfolio, images come from the nearest edge server (likely in the UK)
  4. When a visitor in New York loads your portfolio, images come from a US edge server
  5. Result: dramatically faster delivery regardless of visitor location

According to research on CDN performance benefits, by caching content closer to the user, CDNs significantly reduce the time it takes for websites and apps to load. For photographers who work internationally or want to attract destination wedding clients, this is essential.

Every Fernside Studio site is hosted on Cloudflare Pages, with automatic CDN delivery included. Your images load fast whether visitors are in Birmingham or Brisbane.

Test on Real Mobile Connections, Not Your Studio Wi-Fi

Your portfolio might load instantly on your desktop, but 4G visitors see a different story. According to Google’s Core Web Vitals documentation, sites should aim for Largest Contentful Paint (LCP) of 2.5 seconds or less. For photography websites, the LCP element is typically your hero image. The largest image visible above the fold.

How to test real-world performance:

  1. Google PageSpeed Insights - Free tool that tests mobile and desktop performance with real-world network throttling
  2. WebPageTest - More detailed analysis with customisable test locations and connection speeds
  3. Chrome DevTools Network Throttling - Simulate 3G/4G speeds directly in your browser
  4. Actual device testing - Load your site on your phone with Wi-Fi turned off

Most photographers test only on their studio broadband and are shocked when they see how slowly their portfolio loads on mobile. Test with a mobile profile to simulate real-world conditions.

Performance targets for photography portfolios:

  • LCP under 2.5 seconds on mobile
  • Total page weight under 3MB for initial load (with lazy loading)
  • First Contentful Paint under 1.8 seconds
  • Fully loaded in under 5 seconds on 4G

If your current portfolio fails these benchmarks, it’s costing you bookings. According to conversion rate research, a one-second delay in mobile load times can impact conversion rates by up to 20%.

For more on mobile performance, see our guide on fixing slow website loading times.

What About Cloudflare Image Optimization?

Cloudflare offers automatic image optimisation that resizes, compresses, and serves images in modern formats, all handled at the edge with no manual intervention. This is included with Cloudflare Pages hosting.

How it works:

  • You upload original images (even unoptimised JPEGs)
  • Cloudflare automatically converts to WebP/AVIF based on browser support
  • Images are resized on-demand to match viewport size (mobile visitors don’t download desktop-sized images)
  • Result: optimal delivery with zero manual work

This is one reason we build all photography websites on Cloudflare Pages. The platform handles image optimisation automatically, removing the manual work of exporting multiple formats and sizes.

Common Photography Website Performance Mistakes

Mistake 1: Uploading full-resolution images Your 6000px × 4000px export is unnecessary. No screen displays images that large. Resize to 2000px max and save 80% file size immediately.

Mistake 2: Using JPEG instead of WebP/AVIF JPEG was designed in 1992. Modern formats offer identical quality at half the file size. There’s no reason to use JPEG in 2026.

Mistake 3: No lazy loading Loading 50 images when visitors see 6 wastes bandwidth and kills mobile performance. Implement lazy loading or switch to a platform that does it by default.

Mistake 4: Testing only on fast connections Your studio Wi-Fi is 100x faster than 4G. Test on actual mobile connections to see what clients experience.

Mistake 5: Background images instead of <img> tags CSS background images can’t lazy-load properly and don’t benefit from modern format serving. Use proper <img> tags with lazy loading attributes.

For more performance mistakes, see our article on website performance issues that lose you clients.

If Your Current Portfolio Fails Core Web Vitals, It’s an SEO Penalty

Google uses Core Web Vitals as a ranking signal. Sites that fail LCP, First Input Delay (FID), and Cumulative Layout Shift (CLS) benchmarks rank lower than faster competitors. For photographers competing on local search, “wedding photographer Nottingham” or “portrait photographer , performance is a competitive advantage.

According to Google’s Core Web Vitals guidelines, sites should aim for good scores on at least 75% of page loads. Photography portfolios often fail LCP due to oversized hero images. Fix that, and you improve both user experience and search rankings.

Core Web Vitals benchmarks:

  • LCP (Largest Contentful Paint): Under 2.5 seconds
  • FID (First Input Delay): Under 100 milliseconds
  • CLS (Cumulative Layout Shift): Under 0.1

If your site fails these, it’s not just a performance issue. It’s actively hurting your search visibility.

For more on SEO for photographers, see our photographer website guide.

How Fernside Studio Builds Fast Photography Portfolios

Every photography website we build delivers sub-1-second load times, even with gallery-quality images. Here’s how:

  • Built with Astro, a static site generator optimised for performance
  • Hosted on Cloudflare Pages with automatic CDN delivery
  • Automatic image optimisation to WebP/AVIF with lazy loading
  • Minimal JavaScript. No heavy frameworks, no unnecessary scripts
  • Mobile-first design with responsive images

Our Launch Sprint delivers a custom one-page portfolio in five days for £750 fixed. Includes strategy, design, copy refinement, contact form, analytics, and managed hosting.

For multi-page portfolios with client galleries or booking systems, our Studio Site packages start from £2,400. Every site includes performance optimisation as standard. Not an add-on, but foundational.

Post-launch, we handle updates through ticketed support. If you want to manage your own content, add the Fernside CMS for £29/month.

Ready to Speed Up Your Portfolio?

If your photography website takes longer than 3 seconds to load on mobile, you’re losing bookings. Get in touch and we’ll audit your current performance and show you exactly what needs fixing.

Or start fresh with a purpose-built fast portfolio. Book a Launch Sprint and we’ll deliver a conversion-focused photography website in five days.

Sources

Say hello

Quick intro