Images: why photos slow down practice websites, and how to fix them

Updated November 14, 2026 · 5 min read
Short answer

Images are often the heaviest part of a web page, and practice sites tend to use big ones: the team, the office, the providers. Resize each photo to the size it is shown, save it in a modern format such as WebP or AVIF, give it fixed dimensions, and never lazy load the main photo at the top of the page.

Why photos are so often the problem

Google's image guidance notes that images are often the largest contributor to a page's overall size. On a practice website the pattern is predictable. Someone takes good photos of the new office or the providers, uploads the original files, and the site sends every visitor a photo meant for a billboard.

A photo straight from a modern phone or camera can easily be several megabytes and thousands of pixels wide. A phone screen shows it a few hundred pixels wide. The browser downloads the whole file, then shrinks it. On cellular data that can be the difference between a homepage that appears at once and one that sits blank.

The hero photo at the top of the page is often your Largest Contentful Paint element, the thing Google times. Fixing that one image can move your score more than any other single change.

Find your heaviest images in ten minutes

You do not need special software to find the culprits.

  1. Run your homepage through PageSpeed Insights on mobile and read the diagnostics. Image suggestions, such as sizing images properly or serving them in modern formats, point to specific files.
  2. Note which element is reported as the Largest Contentful Paint. If it is an image, that is your first fix.
  3. In your website editor's media library, look at file sizes. Anything over a few hundred kilobytes deserves a look, and anything measured in megabytes needs fixing.
  4. Check galleries, sliders and before and after pages separately. They often hold the largest collection of oversized files.

Make a list of the page, the image and its current size before anyone starts changing things, so you can measure the improvement.

See your Surge Score in about a minute

Does ChatGPT recommend your practice?

The Surge Score measures five things about your practice website: how often ChatGPT, Gemini and Perplexity recommend you, your PageSpeed, your structured data, your indexing and your reviews, each with its evidence and date. Free.

Right size, right format, right compression

Three changes do most of the work.

  • Right size. Save each image at roughly the width it is displayed, doubled for high resolution screens. A photo shown 500 pixels wide on a phone needs to be about 1,000 pixels wide, not 6,000. Well built sites serve several sizes and let each device pick, which is what the srcset attribute does.
  • Right format. WebP often compresses better than JPEG or PNG and is widely supported. AVIF can be smaller still. Keep PNG for logos and graphics that need transparency or crisp edges.
  • Right compression. Photos tolerate lossy compression well. Compress until you can see a difference, then step back a notch, and always check the result on a real screen, especially skin tones and fine detail.

Squarespace, for example, recommends images of 500 KB or smaller and creates up to seven sized versions of each upload. Your platform may handle part of this; see what your platform does for speed.

The hero photo needs special treatment

The large photo at the top of your homepage and service pages should load first and fast.

  • Do not lazy load it. Lazy loading tells the browser to wait until an image is near the screen. That is right for photos further down and wrong for the one already in view. Google's guidance is explicit: never lazy load your LCP image.
  • Mark it as high priority. Setting the fetchpriority attribute to high tells the browser this image matters most. WordPress has added it automatically to the likely main image since version 6.3.
  • Use a real image element, not a CSS background. Google does not index CSS background images, and the browser discovers them later in the load.
  • Skip the slider. A rotating carousel of five photos loads far more than a single hero for the same space.

One fast, well chosen photo of your real team does more than five slow stock images. See stock photos versus your real providers.

Stop the page from jumping

Images without set dimensions cause layout shift. The browser does not know how tall the image will be, so it lays out the text, then shoves it down when the photo arrives. That is often the exact moment a patient tries to tap your phone number.

The fix is simple: every image gets width and height attributes, or equivalent sizing in the page's styles, so the browser reserves the right space before the file arrives. Many platforms handle this for images added through their editor. Problems tend to come from images pasted into custom code blocks, embedded review widgets and logos added to headers by hand.

Galleries and before and after photos

Dermatology, plastic surgery, med spa and dental practices often have pages with dozens of before and after photos. These can be the heaviest pages on the site.

  • Show small thumbnails and load the full size image only when a patient taps one
  • Lazy load every image below the first screen
  • Compress consistently, so the before and after in each pair look the same quality, which matters for honesty as well as speed
  • Split very large galleries by procedure, which also gives each procedure page a clear focus

These photos also need written patient consent and must follow your state's advertising rules. Speed is the easy part. See testimonials and before and after photos.

Name and describe images for search

While you fix file sizes, fix names and descriptions too. Google recommends short, descriptive file names, so dr-lee-pediatric-exam-room.jpg is better than IMG00023.JPG. Write alt text that describes the image for patients using screen readers, such as "Dr. Lee examining a child's ear in the Elm Street office" for a hypothetical pediatric practice. Google uses alt text along with the page content to understand images, and good alt text is part of making your site accessible.

If your galleries load through JavaScript after the page opens, an image sitemap can help Google find photos it might otherwise miss. See image and video sitemaps.

Checklist

  • The hero image on each key page is a few hundred kilobytes or less
  • Images are saved near their displayed size, not straight from the camera
  • Photos use WebP or AVIF where your platform allows
  • The hero image is not lazy loaded, and images further down are
  • Every image has set dimensions so the page does not jump
  • Galleries show thumbnails first and load full images on tap
  • File names and alt text describe what each photo shows

Frequently asked

Will compressing photos make my practice look less professional?

Not if it is done with care. Modern formats keep photos sharp at a fraction of the original file size, and on a phone screen a well compressed photo usually looks the same as the original. Check skin tones and fine detail before publishing.

Should I convert every image to AVIF?

Not necessarily. WebP is widely supported and a safe default. AVIF can be smaller, but support is less universal, so serve it with a fallback or let your platform choose. Wix, for example, says it converts images to modern formats such as AVIF where possible.

Is lazy loading always a good idea?

For images below the first screen, yes. For the main image at the top of the page, no. Lazy loading that image delays your Largest Contentful Paint, which is the opposite of what you want.

Do I need a developer for this?

Often not for the basics. Resizing and compressing photos before upload is something any staff member can learn. Changing how the template loads the hero image, adding dimensions in custom code or setting up responsive image sizes usually needs whoever built the site.

Sources

  1. Image SEO best practices, Google Search Central
  2. Image performance, web.dev (Google)
  3. Optimize Largest Contentful Paint, web.dev (Google)
  4. Browser-level image lazy loading for the web, web.dev (Google)
  5. Optimize Cumulative Layout Shift, web.dev (Google)
  6. Image performance enhancements in WordPress 6.3, Make WordPress Core
  7. Format and size images for your site, Squarespace Help Center
  8. Site Performance: Best Practices, Wix Help Center
Prefer to talk it through?

Book a strategy call with the team.

Twenty minutes. We'll walk through the specific opportunities in your market and what a MedPracticeGrowth engagement would look like for your practice.

AI patient discovery audit

Is AI recommending you, or your competitor?

See who ChatGPT, Gemini and Perplexity recommend to patients in your area.

Free. Built by physicians.