Photography portfolio website - a gallery that does not kill your speed

A photographer’s website has one job: show the photos well enough that someone writes an enquiry, and get there before they get bored of waiting. Everything else - the fashionable scroll effect, the animated menu, the background music - is an add-on that hurts more often than it helps. A good portfolio has three layers: photos prepared technically so they are sharp and light at the same time, a layout that leads from the homepage to a specific project, and a short path to the enquiry form.

Below I go through it in order: what to do with the photos before you upload them, how to arrange the gallery, what to show right at the top, and what to build the whole thing on.

What a photographer’s site is actually supposed to do

A portfolio site is not an album, it is a sales tool. An album shows everything you have ever done. A portfolio shows what you want to do next, in a quantity small enough that the viewer gets through all of it without losing their way.

That gives you four jobs the site has to do, in order:

1. Say what you specialise in within the first few seconds - weddings, interiors, product, corporate reportage, business portraits
2. Show proof - a handful of your best projects, each one a coherent story rather than a pile of loose frames
3. Answer the questions that will come up in the email anyway - what the package covers, rough price brackets, available dates, the area you work in
4. Give an easy way to make contact - a form with 4-5 fields, with email and phone visible without hunting

If the site only does point two, you get compliments, not bookings.

Why photographers’ galleries load slower than anything else

Because the files land there straight out of the export, at print sizes. A retouched frame out of the camera can weigh several megabytes. Thirty of those on the homepage is a few dozen megabytes that a phone on LTE drags down over long seconds - and for all that time the visitor is looking at white rectangles.

The most common causes I see when diagnosing photography sites:

Important: this is not a choice between “fast” and “beautiful”. A photo scaled to screen size and saved in a good format looks identical on a monitor to the original. The difference shows up only in file weight.

How to prepare photos so they are sharp and light

This list handles most of the problem before anyone touches the code:

1. Set one maximum size - a long edge of 2000-2560 px is enough for 4K screens in full-screen preview
2. Export at quality 75-85 instead of 100 - in that range you cannot see the difference, and the file shrinks several times over
3. Convert to WebP or AVIF - every current browser supports them, and older ones get JPEG as a fallback
4. Generate thumbnails - the grid gets a 600-900 px version, the full file only after a click
5. Turn on lazy loading for everything below the first screen, but not for the lead image - that one is meant to appear instantly
6. Save in sRGB - other profiles can render with shifted colour in the browser
7. Name the files like a human - wedding-session-krakow-12.jpg, not DSC_0917.jpg

You can check the result yourself, without a specialist: go to PageSpeed Insights, enter the address and look at the mobile score and at LCP, the time until the largest element appears. How to read those numbers and what not to take too seriously, I laid out in the step-by-step mini speed audit - the method is the same for a store and for a portfolio.

A gallery layout that holds up

A three-level structure works well, because it lets you show a lot without drowning anyone on arrival:

• Level 1 - homepage: 6-9 lead images, each leading to a category or a specific project
• Level 2 - category or project: 12-24 photos from one session, arranged as a story, with a short intro (who, where, what the goal was)
• Level 3 - full-screen preview: zoom on click, navigation by arrows and swipe, exit with Esc

An even grid (uniform frames) looks calmer and handles a mix of portrait and landscape better than a masonry layout. Keep vertical photos in a single column on mobile. For large sets, load further batches with a “Show more” button instead of automatically on scroll - autoloading breaks the footer and makes it harder to reach the contact section.

The order of your work: what people see in the first seconds

The first three photos decide whether someone stays. So the order is set not chronologically but around the client you want to win.

• Want to shoot product photography for stores? Packshots go at the top, not an outdoor wedding shoot from two years ago
• Doing several things at once? Split it into separate sections with their own entry points instead of mixing everything into one stream
• Cut anything that is merely “quite good” - a portfolio is judged by its weakest photo, not its best
• Add two sentences of context to every project; that is the only text search engines have a chance of understanding, because they cannot read the image itself

The path to an enquiry, which is the point of all this

The most common portfolio mistake is having no ending. The gallery finishes and the visitor is left alone with the footer. Close it like this:

1. A contact section under every gallery - one sentence and a button, you do not need a full form in every place
2. A form with specific fields: type of job, date, location, rough budget, short description. That way your first reply can be concrete instead of three emails about nothing
3. Price brackets or packages - even rough ones. A site with no price information at all mostly generates enquiries from people who were never going to buy
4. Information about response time - “I reply within 24 hours” works better than a silent form
5. Email and phone as plain text - some people will never use a form

If you sell one specific type of session, sometimes you do not need an elaborate site at all - one well-built offer page with a gallery and a form is enough. When that makes sense and when it does not, I covered in the piece on landing pages and what they cost.

Image rights, SEO and accessibility

Three things that are easy to postpone and then regret:

• Alt text on photos. It is a short description of what is in the frame for people using a screen reader, and incidentally the only information about the image content available to search engines. Digital accessibility rules (the EAA) have applied since June 2025; the scope depends on what you sell and to whom, but text contrast, keyboard navigation and photo descriptions are a minimum worth implementing regardless of obligation
• Watermarks and file metadata. A watermark across the middle of the frame ruins the impression; limiting the size of the public file plus authorship and contact details written into the IPTC metadata is more effective
• Image releases for photos of private individuals and the client’s staff - not having them can come back years later as a demand to take the whole gallery down

If you work in a specific city, your Google Business Profile and your site have to say the same thing (name, address, phone) - a mismatch there quietly costs you positions in the map results. What local visibility is built on, I described in the piece on working with an SEO partner locally or remotely.

What to build the site on

The choice between the first two comes down to how much of your own time you want to spend on it - I broke that down in the piece on using a website builder versus hiring a developer. With the third we move into a project where the gallery, thumbnails and forms are written around your specific way of working, and that is the ground I work on most often as part of building websites.

Where to start if the site already exists

If the portfolio exists and what bothers you is its speed or the lack of enquiries, do not start with a rebuild. I start with a free diagnosis: I look at photo weight, load time on mobile, the layout of the path from homepage to form, and whether the site says what you actually sell. Out of that comes a list of fixes ordered by effect-to-effort - and very often the first two items can be done in a few hours.

When the diagnosis points to bigger work, you get a written quote before the start, with a fixed amount and scope. New sites usually land in the 5,000-10,000 PLN net range (Polish market rates), depending on the number of subpages and what has to happen beyond the gallery. If someone is to watch over updates, backups and speed after launch, there is ongoing technical maintenance - Basic from 1,000, Pro from 2,000 or Premium from 3,500 PLN net per month, depending on how much is going on.

Frequently asked questions

How many photos should a photographer’s portfolio have? 6-9 lead frames on the homepage, 12-24 within a single project. More does not increase your chances of a booking; it lengthens load time and dilutes the impression. Keep the rest of the material in client galleries, outside the public portfolio.

Do photos lose quality after compression? At quality 75-85 with conversion to WebP or AVIF, you cannot see the difference on screen, and the file can weigh several times less. Quality loss only shows up with aggressive downscaling or with repeated re-saving of the same file.

Does a photographer need their own site if they have Instagram? A social profile shows single frames, but it does not lead to an enquiry and it does not belong to you - the rules and the reach change without warning. A site gives you your own address, complete projects, price information and a form. In practice they work best together: the profile attracts, the site closes.

How long does a portfolio site take to build? With the photo material ready and the copy agreed, usually 2-4 weeks from sign-off on the design. The longest part is not the code, it is choosing the photos and writing the text about your offer - which is why I ask for that material at the start, not at the end.

Need something like this on your side? I design and build websites for B2B companies - from scratch or as a rebuild of what already stands. Send me the scope and a quote with a date comes back.