Website for a photographer: an online portfolio that sells

A photographer without a website is like a restaurant without a sign. Instagram is great for building an audience, but the website is what turns followers into clients. Why? Because the site is where you put pricing, the contact form, the full portfolio, and SEO. Instagram doesn’t rank for “wedding photographer Krakow” — your website does.

What separates a good photographer’s site from a bad one?

Most photographers’ sites share one cardinal mistake: they load too slowly. A gallery of 50 full-resolution images is megabytes of data — a customer on a phone will not wait 10 seconds for it to load. A good photographer’s site combines:

• Fast loading (lazy loading, WebP, compression) — PageSpeed 90+
• Aesthetic design matched to the photography style
• Clear navigation by category
• Transparent pricing and a simple contact form
• Local SEO so you can win clients from Google

The structure of an ideal photographer’s portfolio

1. Homepage — first impression

The homepage is your portfolio condensed to its essence. Pick 15–20 best images representing your style — don’t show everything, only the top 5%. Clients book a style they have already seen, not one that might emerge. One strong full-width hero image, a few category galleries, a clear contact CTA.

2. Categories — one page per type of photography

Every specialisation should be its own subpage with its own gallery and copy:

• Wedding photography: description of the style (reportage, classic, fine art), what’s in the package, sample albums, delivery time
• Portrait photography: individual, couples, family, newborn sessions
• Business photography: headshots, corporate events, products, real estate
• Reportage photography: christenings, communions, birthdays

Why separate subpages? Because you can rank independently for “wedding photographer Wroclaw” and “newborn photographer Wroclaw” — these are different phrases with different clients.

3. Pricing — don’t hide it

The single most-asked question of a photographer: “how much?”. If there’s no price list on the site, the customer assumes it’s too expensive and keeps looking. The price list doesn’t have to be down to the zloty — ranges (e.g. “from 1,500 PLN”) are enough, and they discourage clients shopping for a 300 PLN photographer while attracting those for whom quality matters.

4. About me — a story, not a CV

Clients also choose a photographer based on personality — especially for wedding and portrait work, where they spend a whole day with you. An authentic story (what drew you to photography, what your style is, what you enjoy about the work) is more persuasive than a list of certifications. Add a good photo of yourself — a human face builds trust.

5. Client reviews and FAQ

A few quotes from happy clients (with consent), with first name and session type. An FAQ answering questions like: do you deliver raw RAW files? How long does it take to receive the photos? Can we have multiple outfit changes? Are you available on weekends? What if the weather is bad?

6. Contact form — simple, but with context

Minimal form: name, email, phone, session date, session type, additional notes. Optional: budget (helps avoid mismatched inquiries). Answer inquiries within 24 hours — clients book a photographer for a specific date and send inquiries to several people in parallel.

SEO for a photographer — being visible in Google

Key phrases:

• “wedding photographer [city]” — the most popular, fierce competition
• “newborn photographer [city]” — less competition, higher conversion
• “photo session [city]”
• “[specialisation] photographer price [city]”
• “christening photographer [city]”
• “business photographer [city]”

Blogs are very effective for photographers: “how to prepare for a portrait session”, “what to wear for a wedding session”, “top 10 photo session locations in [city]” are articles that drive traffic and build authority.

Technical requirements — lazy loading and compression

A photographer’s site without image optimisation is a performance disaster. Key techniques:

• WebP format: 30% smaller file size than JPEG at the same quality
• Lazy loading: images load only as the user scrolls to them — the page loads 3–5× faster
• CDN: images served from servers geographically close to the user
• Dimensions: for a 1920px-wide screen, 1200px width with proper compression is enough

A photographer’s site built in Next.js with the Image component applies all these optimisations automatically. A PageSpeed score of 95+ is achievable even with large galleries.