The Heavy Website Epidemic: How Unoptimised Images Are Costing Irish Businesses Mobile Performance

Images slow down a website when they are too large, poorly compressed, loaded too early or served in the wrong format for the user’s device. On mobile, this creates longer loading times, heavier data usage and weaker first impressions before the customer can act.

Images are usually among the heaviest assets on a page. A single homepage banner can be larger than the rest of the page combined. If a site uses several large images, the browser must download, decode and display each one before the page feels complete.

This matters because mobile visitors are less patient. They may be on a 4G or 5G connection, inside a building, travelling between areas or using an older device. A page that feels acceptable on a fast office connection can feel slow in real customer conditions.

The common image problems we see include:

• Uploading original camera images directly into WordPress
• Using PNG files where WebP or JPEG would be more suitable
• Serving desktop-sized images to mobile users
• Loading every image immediately instead of using lazy loading
• Using large sliders that add weight without improving conversions
• Relying on image plugins without checking the final page output

For SMEs, this is not just a design issue. It affects enquiries, bookings, checkout confidence and trust.

Unoptimised images affect Core Web Vitals by delaying the main visual content, shifting layouts as images appear and increasing the amount of work the browser must complete. The biggest impact is usually on LCP, especially when the largest visible element is a hero image.

Core Web Vitals are Google’s performance signals for user experience. For image-heavy websites, the most relevant are:

• LCP, Largest Contentful Paint: How quickly the main visible content loads.
• CLS, Cumulative Layout Shift: Whether page elements move unexpectedly while loading.
• INP, Interaction to Next Paint: How quickly the page responds when users interact.

Large images can hurt LCP because the browser has to fetch and render the main visual element before the page feels ready. If the homepage hero image is too heavy, the user waits longer for the page to appear complete.

Images can also affect CLS when width and height are not properly defined. This causes text, buttons or forms to jump as the image loads. On mobile, even a small layout shift can make the page feel unstable.

Then there is the infrastructure layer. TTFB, or Time to First Byte, measures how quickly the server starts responding. If TTFB is already weak, heavy images make the experience worse. You cannot out-optimise a slow server, but you also cannot expect good hosting to rescue badly prepared media.

Good performance needs both sides working together: efficient content and strong infrastructure.

Mobile performance matters because many customers first discover local Irish businesses on phones, not desktop computers. If a page is slow, awkward or unreliable on mobile, the business may lose enquiries before the visitor reads the offer or reaches the contact form.

This is especially important for service-led SMEs. A customer searching for a plumber, solicitor, accountant, clinic, restaurant, tradesperson or online store is often ready to act. They want to compare options quickly, check trust signals and make contact.

Slow pages create commercial friction:

• Fewer completed enquiry forms
• Lower confidence in checkout pages
• Higher bounce rates from mobile search
• More abandoned service pages
• Poorer user experience before the sales conversation begins
• Extra time spent by staff and developers investigating speed issues

There is also a compliance and governance angle. GDPR does not require every Irish business to use a specific image format, but performance work should still be done carefully. Some optimisation tools, external CDNs and tracking-heavy media plugins may involve data processing, logs or third-country transfers. SMEs should understand what tools are being added, where data may pass and who is responsible for the setup.

That is why speed should not be treated as a cosmetic fix. It is part of operating a dependable business website.

You can improve website speed on mobile by reducing image weight, serving the correct image size, using modern formats, enabling caching and making sure the hosting environment responds quickly. The best results come from fixing both the page assets and the infrastructure behind them.

A practical image optimisation process should include:

• Resize images before upload so they match the real display area.
• Use WebP or AVIF where suitable, with fallbacks where needed.
• Compress images without making them visibly poor.
• Avoid oversized sliders and unnecessary decorative images.
• Set image width and height to reduce layout shift.
• Use lazy loading for images below the first screen.
• Keep the first visible image as light and efficient as possible.
• Review mobile performance, not just desktop scores.

The first screen matters most. If the hero section is slow, everything feels slow. Businesses often spend time optimising images deep inside blog posts while ignoring the largest homepage image, service-page banner or WooCommerce product image.

Hosting also matters. Caching, server response, DNS resolution, storage performance and database speed all influence how quickly the browser receives the page in the first place. If the server is slow to respond, image optimisation helps but does not solve the full problem.

This is where Core Web Vitals hosting becomes relevant. Hosting should support performance rather than become the ceiling that limits it.