How Oversized Property Photos Slow Direct Bookings

Accommodation photography helps a guest decide. It also becomes a barrier when a phone must download the photographer’s original files just to show a small room preview.

On one direct booking website we reviewed, individual photos weighed between 2 and 9.5 megabytes. The homepage requested around 31 megabytes of images before it looked finished. Those are observations from that review, not a benchmark for every property website.

Office Wi-Fi can hide the problem. A guest on mobile data may see empty space, partial images or a booking button moving as the page fills in. Their first decision becomes whether to wait.

These are illustrative loading states of the same fictional property. They explain the experience; they are not before-and-after speed measurements.

Google’s Largest Contentful Paint guidance defines a good result as the largest visible image or text appearing within 2.5 seconds for at least 75% of visits. A single fast test on your laptop does not establish that result for real guests.

For an accommodation page, the largest element is often a photograph. If that image starts late or carries several unnecessary megabytes, the guest waits for the very information that makes the property worth booking.

Compression is one part of the fix. Scripts, the server and third-party widgets can also delay the page. Measure the page as a whole rather than treating a smaller image as proof of a faster booking journey.

• Resize photographs for their actual display size. Keep full-resolution originals in your archive, not in every guest’s download.
• Export WebP or AVIF versions and inspect beds, room details and text after compression. The photo still needs to help someone choose.
• Provide smaller versions for smaller screens using responsive image delivery such as srcset and sizes.
• Load the important first-screen image eagerly. Apply high fetch priority to the likely hero image; do not lazy-load it.
• Lazy-load photography farther down the page, and reserve every image’s width and height so content does not jump.
• Check booking widgets and tracking scripts if the page remains slow after the images are right-sized.

A practical image budget depends on the room detail, display size and format. Start by removing unnecessary pixels, then reduce file weight until the visual quality would start to undermine the decision.

Open a property page on your phone using mobile data. Can you understand the room and find availability before scrolling? Does anything jump when the photos arrive?

Ask your developer for the homepage’s transferred image weight, the hero file size and mobile performance results. Compare the same page before and after optimisation. Use real-user data where available; a laboratory test helps diagnose issues but cannot describe every guest’s connection.

Keep the useful photography. Remove the waiting that sits between the guest and the room.