Why Your Cleaning Website Images Are Slowing Everything Down

A homeowner taps your cleaning website from Google. The page starts loading. The header appears. Then a white rectangle sits where the hero image should be — for two seconds, three seconds, four seconds. When it finally loads, the text below jumps down as the image pushes everything into place. By then, she’s already tapped the back button.

That hero image was probably a JPEG straight from a phone camera. 3-5 MB of uncompressed pixels, served at 4000 pixels wide to a screen that’s 375 pixels wide. It’s the most common performance problem we found across 837 cleaning company websites audited in 43 cities and 11 states — and it’s entirely preventable.

The average cleaning website in our dataset scores 38 out of 100. Unoptimized images are a leading contributor to that score. This post covers what’s going wrong with images on cleaning websites, exactly how much it costs in speed and lost visitors, and how to fix it without losing visual quality.

Images are the heaviest assets on most cleaning websites

A typical cleaning company homepage contains five to fifteen images: a hero banner, team photos, before-and-after galleries, trust badges, service icons, and maybe a background image or two. On most sites we audited, those images account for 60-80% of the total page weight.

Here’s why that matters. A page weight of 2 MB is considered acceptable for a modern website. Many cleaning websites we audited had page weights of 8-15 MB — almost entirely because of images. When the page is eight times heavier than it should be, load times scale proportionally.

On a broadband desktop connection at 100 Mbps, a 10 MB page takes about a second. On a mobile LTE connection at 15 Mbps — common for the majority of visitors who will never see your desktop site — that same page takes 5-6 seconds. Google’s research shows 53% of mobile visitors leave after 3 seconds. Half your visitors are gone before the page finishes loading, and images are the reason.

The four image problems we see on every other cleaning site

Across 837 audits, the same image optimization failures appeared repeatedly. Most cleaning websites have all four.

Problem 1: No format conversion

The most common image formats on cleaning websites are JPEG and PNG. These are decades-old formats that prioritize compatibility over efficiency. Modern formats — WebP and AVIF — deliver the same visual quality at 25-50% smaller file sizes.

A hero image that weighs 2 MB as a JPEG can weigh 800 KB to 1 MB as WebP, and 500-700 KB as AVIF. Across five to ten images per page, format conversion alone can cut page weight by 40-60%. Every modern browser supports WebP. AVIF support covers Chrome, Firefox, and Safari.

Yet the vast majority of cleaning websites still serve JPEG and PNG exclusively. Many website builders default to these formats, and owners don’t know to change them.

Problem 2: No compression

Even within JPEG format, there’s a massive quality-to-size range. A photo at 100% quality might weigh 4 MB. The same photo at 80% quality weighs 1.2 MB — and the visual difference is imperceptible to human eyes. At 60% quality, it weighs 600 KB and still looks good on a web page.

Most cleaning websites serve images at maximum quality because that’s what the camera or phone produced. Nobody ran the files through a compressor. Nobody asked whether a 4 MB photo looks meaningfully better than a 1 MB version. The answer is almost always no — not on a screen, not at web dimensions, and certainly not as a background image behind semi-transparent text.

Problem 3: No responsive sizing

A hero image displayed at full width on a 1920-pixel desktop monitor needs to be roughly 1920 pixels wide. On a phone at 375 pixels wide, that same image only needs to be 750 pixels wide (for retina displays). Serving the 1920-pixel version to a phone wastes 75% of the file on pixels that never get displayed.

HTML supports responsive images through the srcset attribute, which lets you specify different image files for different screen sizes. The browser picks the appropriate one automatically. Most cleaning websites don’t use this attribute. They serve one image size to every device.

The numbers compound quickly. A 1920-pixel JPEG at 3 MB becomes a 750-pixel WebP at 150 KB. That’s a 95% reduction in file size with zero visible quality loss. Multiply that saving across every image on the page.

Problem 4: No lazy loading

Lazy loading tells the browser to skip downloading images that aren’t visible on screen yet. The hero image loads immediately because the visitor sees it first. The team photo halfway down the page waits until the visitor scrolls near it. The before-and-after gallery at the bottom waits until the visitor reaches the bottom.

Without lazy loading, the browser downloads every image on the page at once — including images the visitor may never scroll to see. On a page with ten images, six of which are below the fold, lazy loading can reduce initial page weight by 60% or more.

Implementing lazy loading is a single HTML attribute: loading="lazy" on each image tag. The hero image should not be lazy loaded (it needs to appear immediately), but everything else below the fold should be.

Before-and-after galleries are the worst offenders

Cleaning companies love before-and-after photos — and they should. They’re powerful trust signals. But galleries are where image optimization failures compound most severely.

A typical before-and-after gallery contains 8-20 image pairs. If each image is an uncompressed JPEG at 2-3 MB, the gallery alone weighs 32-60 MB. Without lazy loading, the browser tries to download all of them when the page loads, even though the gallery might be at the bottom of the page.

The visitor never sees these images because the page is too slow to keep her around. The gallery that’s supposed to build trust instead destroys performance.

The fix is straightforward: compress and convert every gallery image to WebP, size them appropriately (800-1000px wide is sufficient for a gallery thumbnail), and lazy load all of them. A 50 MB gallery becomes a 2 MB gallery with no visible quality difference.

Stock photos add weight without adding trust

We found that many cleaning websites use large stock photography — staged images of spotless kitchens, smiling families, and generic cleaning products. These images weigh the same as real photos but provide less trust value. A homeowner knows a stock photo when she sees one.

The highest-scoring sites in our data use real photos: actual team members, actual job results, actual equipment. These photos don’t need to be professional-quality. A competent phone photo that shows your team or your work is worth more than a polished stock image of a model pretending to mop.

Real photos also tend to be smaller when properly optimized because they don’t have the artificial sharpness and saturation of stock photography. A quick pass through a compression tool, a conversion to WebP, and they’re ready.

If you do use stock photos, at least make sure they’re optimized. A 5 MB stock photo of a clean kitchen isn’t impressing anyone when the page takes 6 seconds to load because of it.

Logo files are silently bloating every page

Here’s a problem most cleaning company owners don’t think about. Their logo appears on every page — in the header, in the footer, sometimes in the hero section. If the logo file is a PNG at 500 KB, that’s 500 KB added to every single page load across the entire site.

We’ve seen cleaning logos served as:

PNG files at 1-2 MB (the original export from a designer)
JPEG files with white backgrounds (instead of transparency)
SVG files with embedded raster images (defeating the purpose of SVG)

A properly optimized logo should be an SVG (which scales infinitely and weighs 5-20 KB) or a WebP with transparency at the dimensions actually displayed on the page (typically 200-300px wide, weighing 10-30 KB).

Replacing a 1 MB PNG logo with a 15 KB SVG saves 985 KB on every page of your site. For a visitor who browses four pages, that’s nearly 4 MB of savings from a single file replacement.

CLS: the invisible image problem that Google penalizes

Cumulative Layout Shift (CLS) is one of Google’s Core Web Vitals — a metric that measures how much the page layout jumps around while it loads. Images are the primary cause of CLS on cleaning websites.

When an image doesn’t have explicit width and height attributes, the browser doesn’t know how much space to reserve for it. The page renders with text and buttons in their initial positions. Then the image loads, and everything below it shifts downward. The visitor was about to tap the “Book Now” button, but it moved. She accidentally taps a link to the About page instead.

Google’s threshold for good CLS is under 0.1. Many cleaning websites we audited exceed 0.25 — mostly because of images that load without reserved space. The fix is simple: add width and height attributes to every image tag. The browser reserves the correct space before the image downloads, and nothing shifts.

This is especially important for the hero image. If the hero is a large photo that takes 2-3 seconds to load, everything below it will jump when it finally appears. Adding dimensions eliminates the jump entirely, even though the image still takes time to load.

The optimization workflow takes less than an afternoon

You don’t need a developer to fix your images. Here’s the workflow:

Step 1: Audit your current images. Open your website in Chrome, press F12, go to the Network tab, filter by “Img,” and reload the page. You’ll see every image, its file size, and its format. Anything over 200 KB deserves attention. Anything over 1 MB is actively hurting your site.

Step 2: Convert to WebP. Use a free tool like Squoosh (browser-based) or ShortPixel. Upload each image, select WebP as the output format, adjust quality to 75-80%, and download. The visual difference is negligible. The file size difference is dramatic.

Step 3: Resize for the web. No image on your site needs to be wider than 1920 pixels, and most can be 1200 pixels or less. Gallery images can be 800 pixels. If you implement responsive images with srcset, also create mobile variants at 750 pixels.

Step 4: Add lazy loading. Every image below the fold should have loading="lazy". The hero image and anything visible on the first screen should not.

Step 5: Add dimensions. Every image should have width and height attributes matching its aspect ratio. This prevents layout shift.

Optimized images improve everything else on the site

Speed is the gatekeeper for every other metric. When images are optimized and the page loads fast, more visitors see your booking button. More visitors read your pricing. More visitors scroll to your reviews and trust signals. More visitors reach your service pages.

The top 1.3% of cleaning websites in our dataset all load in under 2 seconds. Image optimization is a foundational reason why. These sites use modern formats, proper compression, responsive sizing, and lazy loading — the same techniques available to every cleaning company regardless of budget or technical skill.

The industry average score of 38 out of 100 isn’t a function of bad content or ugly design. It’s a function of heavy, unoptimized assets dragging down sites that could otherwise perform well. Fix the images, and you fix the single biggest bottleneck between your website and your next booked client.

Your before-and-after photos deserve to be seen. Right now, most of them are slowing down the page so much that visitors leave before they get to them. An afternoon of optimization changes that permanently.