Cybrial
Independent design. Ongoing growth.Manchester · Working everywhere

Guide · Building

The Photographs Are the Product: Trade Website Galleries

By Measured 4 October 2026

A customer deciding on a four-figure job looks at your photographs for longer than they read anything you wrote. Most trades then hide them in a gallery nobody opens.

The short answer

Trade photographs sell the work, so take them properly and put them where the decision happens rather than in a separate gallery page. Shoot the same angle before and after, in daylight, with something in frame for scale. Put the photographs on the relevant service and town pages — a driveway photo belongs on the driveways page and on the page for the town it is in, not only in a grid. Then make sure they are not what is making the site slow: resize before upload, serve modern formats at the width actually displayed, set explicit dimensions so the layout cannot jump, and lazy-load everything below the fold. A twenty-seven page site can still render its homepage from eleven requests in 0.68 seconds.

Why your photographs beat your copy

A homeowner choosing a trade is trying to answer one question that no amount of writing settles: will the finished thing look right.

Copy cannot answer it. Testimonials cannot really answer it — they are about the experience of dealing with you, which matters, but not about the result. A photograph of a driveway you laid on a street that looks like theirs answers it instantly and completely.

Stock photography does the opposite. It is recognisable, it is used by three competitors in the same town, and the customer reading it concludes you have nothing of your own to show. That conclusion is usually correct, which is why the instinct is right.

The practical consequence: a trade with a phone and ten minutes at the end of each job has the single most persuasive content asset in their market, and most of them are not collecting it.

Taking them, on site, on a phone

Nobody is suggesting a professional shoot on every job. A modern phone is more than enough. What matters is consistency and a short habit.

  • Shoot the before from a fixed spot, and shoot the after from the same spot. The pair is worth more than either on its own, and it is only a pair if the angle matches. Stand somewhere memorable — the gatepost, the corner of the house.
  • Daylight, and if you can, the same time of day for both. An after shot taken at dusk against a before taken at noon reads as a different property.
  • Get something in frame for scale. A door, a car, a wheelie bin. A driveway photographed with no reference could be any size.
  • Take the wide shot and then two details. The wide shot sells the result; the details — a clean edge, a neat joint, a tidy finish where it meets the step — sell the workmanship, and they are what separates you from the cheaper quote.
  • Take one of the site left tidy. Trades underestimate how much this matters to somebody about to let strangers into their home for a week.
  • Ask the customer before you publish anything identifiable, and keep a note that you did. House fronts are identifiable.

The whole routine adds about five minutes to a job. The output is the content that will still be selling for you in three years.

Put them where the decision happens

The default is a page called Gallery with a grid of sixty thumbnails. It is the least useful possible arrangement.

A grid asks the customer to do the sorting. They wanted to see driveways and they are looking at a patio, a wall, a patio, a driveway, a drain. Most people scroll twice and leave, and the one photograph that would have won the job is at position forty-one.

Photographs should live on the page where the relevant decision is being made:

  • On the service page, so the person reading about resin driveways sees resin driveways.
  • On the town page, so the person in Bury sees work done in Bury. This is also what makes a town page real rather than a template with the name swapped — and it is the difference between a page that helps and a doorway page that hurts the whole site.
  • Next to the enquiry form or the phone number, because the moment of deciding to call is when proof is worth most.
  • In the search result itself, by making sure the right image is the one that gets picked up.

Keep the gallery if you like it, as a browse-everything page. Just stop making it the only place the proof lives.

And caption them. "Block paved driveway with charcoal border, Prestwich, March 2026" does three things a bare image does not: it tells the customer what they are looking at, it tells them it is recent, and it puts the words on the page where they can be found.

The part that makes trade sites slow

Here is where it goes wrong, and it goes wrong on almost every trade site that takes photographs seriously.

A phone photograph is several megabytes. Uploaded as it came off the camera and displayed in a box four hundred pixels wide, the browser still downloads the whole thing. Twelve of those on a page is thirty or forty megabytes over mobile data, at the kerbside, on one bar.

What to do about it, in order of how much it buys you:

  • Resize before upload, or use a platform that generates sized versions automatically. The image should be delivered at roughly the width it is displayed at, not at 4,000 pixels wide.
  • Serve a modern format. WebP or AVIF are a fraction of the size of the same JPEG at the same visible quality, and every current browser handles them.
  • Set explicit width and height on every image. Without them the browser does not know how much space to reserve, so the page reflows as each one arrives — and that is the layout shift that moves your call button out from under a thumb.
  • Lazy-load everything below the fold, so a page with forty photographs only fetches the two the customer can see.
  • Cap how many go on one page. If a service page needs forty images, it probably wants to be three pages.

For a reference point, we publish our own rather than describing what good looks like. The Pro Pave homepage renders from eleven requests, answers in 51 milliseconds, shows content in 0.56 seconds, loads completely in 0.68 seconds, and has a cumulative layout shift of zero — measured on the live site on 4 September 2026 using the browser's own Navigation Timing, Resource Timing and Layout Instability APIs. It is a paving company, so it is an image-led site by nature, across twenty-seven pages.

That zero layout shift is the image discipline showing up as a number. It is what explicit dimensions buy you, and it is the difference between a tap landing on your phone number and landing on whatever moved into its place.

Making them findable

Two small things that cost nothing and are almost universally skipped.

Name the file before you upload it. "block-paved-driveway-prestwich.jpg" is readable by a search engine; "IMG_4417.jpg" is not. It takes two seconds at upload and is impossible to retrofit across four hundred images later.

Write real alt text. Not keyword stuffing — a plain description of what is in the picture, for somebody who cannot see it. "Charcoal block paved driveway with a contrasting border, laid to a semi-detached house in Prestwich." That serves a screen reader user properly, which is the point, and it happens also to tell a search engine what the image is.

Done consistently, a trade with three years of job photographs has hundreds of specifically-described, locally-named images. That is a genuine asset in image search and in AI answers, and it exists purely because somebody spent two seconds per upload.

What to check on your own site

  • Are the photographs yours, or are any of them stock?
  • Do you have before-and-after pairs shot from the same spot?
  • Are photographs on the service and town pages, or only in a gallery?
  • Is there a photograph next to the enquiry form or the phone number?
  • Are they captioned with what, where and when?
  • What does your heaviest page weigh, and how long does it take on mobile data?
  • Are images served at display width, in WebP or AVIF?
  • Does every image have explicit width and height set?
  • Does the layout move as the page loads?
  • Are the filenames descriptive, and does every image have real alt text?
  • Do you have permission to publish anything identifiable, and a note that you asked?

The quickest win on most trade sites is numbers seven and eight together: resize and set dimensions. It is an afternoon, it usually halves the page weight, and it takes the layout shift to zero.

Sources

Everything this page relies on.

  1. Pro Pave performance figures (propavingmanchester.com): 51 ms time to first byte, 0.56 s first contentful paint, 0.68 s full page load, 11 requests to render, 0 cumulative layout shift, across a 27-page image-led site — measured on the live homepage on 4 September 2026 using the browser Navigation Timing, Resource Timing and Layout Instability APIs. Pro Pave is a Cybrial client and the case study is on this site.

  2. Layout shift is measured here as cumulative layout shift, one of Google’s Core Web Vitals; there is a separate guide on this site covering those metrics in full.

  3. Image format and lazy-loading recommendations are general web platform practice rather than a measured claim about your site. No industry averages for page weight are quoted in this guide, because we have not measured one.

Common questions

Questions people actually search for.

Do I need a professional photographer?

No. A modern phone is enough, and the habit matters more than the camera: same spot before and after, daylight, something in frame for scale, a wide shot plus two details, and one of the site left tidy. That is about five minutes a job and it produces content that keeps selling for years.

Is a gallery page a bad idea?

Not bad, just the wrong place for the proof to live. A grid of sixty mixed thumbnails makes the customer do the sorting, and the one photograph that would have won the job is at position forty-one. Put the photographs on the service and town pages where the decision is being made, and keep the gallery as a browse-everything extra.

Will adding lots of photographs slow my site down?

Only if they are handled badly, and usually they are. Resize before upload, serve WebP or AVIF at display width, set explicit width and height, and lazy-load below the fold. The Pro Pave site is a paving company across twenty-seven image-led pages and its homepage still renders from eleven requests in 0.68 seconds, measured 4 September 2026.

Why does setting image dimensions matter so much?

Because without them the browser does not know how much space to reserve, so the page reflows as each image arrives. That is the layout shift that moves your call button out from under a thumb a fraction of a second before it lands. The tap goes somewhere else, the customer rings the next result, and nothing in any report tells you it happened.

Do I need permission to publish photographs of a job?

Ask, and keep a note that you did. A house front is identifiable and a customer who sees their home on a website they did not expect is a complaint you did not need. Most people say yes happily when asked at handover.

What should image filenames and alt text say?

Name the file before upload — "block-paved-driveway-prestwich.jpg", not "IMG_4417.jpg". Write alt text as a plain description for somebody who cannot see the image, which is what it is for; it also tells a search engine what the picture shows. Neither can be retrofitted easily across hundreds of images, so start now.

What does your gallery weigh?

Send me your trade website. I will tell you what the heaviest page weighs, how long it takes on mobile data, whether your images are shifting the layout under somebody’s thumb, and where the photographs should actually be.