How to Standardize Image Optimization Settings Across Every Client Site

If your agency manages more than a handful of WordPress sites, image optimization tends to drift.

One site is on lossy with WebP enabled. Another has AVIF on but no resizing. A third was set up two years ago by someone who left the agency, and nobody remembers what the original configuration was supposed to be.

That drift adds up. Onboarding takes longer. Troubleshooting takes longer. And when a client asks why their images look different from another site you manage, you don’t have a clear answer.

The fix isn’t more documentation. It’s a repeatable system. One ShortPixel setup that works for most client sites, a way to reuse it without manual configuration, and a habit of checking that nothing has changed since you set it up.

Why a standard setup matters

When every client site has different image optimization settings, three things start to break down.

Onboarding. Every new site means starting from defaults and making decisions from scratch. Even with a checklist, it takes longer than it should.

Troubleshooting. When a site has a problem, you can’t compare it against “what it should look like.” You’re inspecting each setting individually instead of spotting deviations from a known baseline.

Handoffs. When work moves between team members, or when an agency takes over an existing site, undocumented configurations become guesswork.

A standard setup, the same defaults applied across most of your portfolio, removes most of that friction. The work happens once, and the rest is replication. This is what makes image optimization manageable at scale.

The default ShortPixel setup

The point of a default setup isn’t to list every option ShortPixel offers. It’s to pick a sensible configuration that fits the majority of client sites, small business sites, blogs, service companies, and basic e-commerce stores, and apply it without thinking. This becomes your agency baseline.

For most agencies, that default looks roughly like this:

• Compression: Glossy — strong savings, visually indistinguishable from the original for typical web content. Good middle ground between Lossy (too aggressive for some sites) and Lossless (leaves savings on the table).
• WebP and AVIF: both enabled — modern browsers get the best format available, older browsers fall back automatically.
• Thumbnail optimization: on — WordPress generates many sized versions of every image. Optimizing only the original misses most of what visitors actually load.
• Resize large uploads: 1920–2560px max width — covers retina displays without storing pixels nobody will ever see.
• Backup originals: on — storage is cheap, regret is expensive.
• Optimize on upload: on — keeps the setup self-maintaining as clients add new content.

These exact values matter less than the fact that they’re chosen deliberately and used consistently. Pick what works for your agency, document it, and move on.

Reuse the setup with Export/Import

This is where the workflow shift happens.

ShortPixel has an Export/Import feature in its settings panel that saves the entire configuration as a file. On a new site, you import that file and the configuration is applied in one step, instead of clicking through every setting manually.

For an agency, the workflow becomes:

1. Configure ShortPixel once on a reference or staging site
2. Export the settings file and store it in a shared location
3. Import the file on every new client site

That single change turns “configure ShortPixel” from a 10-minute task per site into a 30-second one. Across a portfolio of 30 or 50 sites, that’s hours of cumulative time, and more importantly, it removes the room for inconsistency. Nobody forgets a setting if no one has to configure it manually.

The other thing to standardize at the same time is your API key strategy. Use a per-client subaccount or alias instead of dropping your agency master key into every install. This keeps usage tracking clean and lets you revoke access per site without affecting the rest of your portfolio.

When the default setup needs to change

Most sites fit the default. Some don’t, and that’s normal.

Photography portfolios and creative agencies. Photographers will notice aggressive compression. Switch to Lossless or reduce compression aggressiveness, and consider keeping EXIF data if the client cares about copyright metadata or embedded camera information.

WooCommerce stores with high-detail products. For jewelry, watches, fashion, or anything where texture and detail matter, lean toward less aggressive compression. Overcompressed product images quietly hurt conversion.

Real estate galleries. Lots of large images per listing. The default usually works, but verify that the gallery plugin generates the thumbnail sizes you expect and that ShortPixel is catching all of them.

Publishers and news sites. Volume is the issue. The default compression is fine, but CDN integration matters more here because image bandwidth is much higher than on the average site. Also make sure old archived images are processed, not just new uploads.

Premium brands. Have the compression conversation with the client before deciding. Some premium brands would rather pay for the bandwidth than accept any visible degradation on a hero image. Document the decision somewhere it won’t get lost.

The point isn’t to remember exceptions. It’s that you flag them at onboarding, document the deviation from your standard setup, and treat them as deliberate variants instead of accidental drift.

Keeping settings consistent over time

Even with a clean baseline, settings drift over time. This is expected in most agency environments.

A developer logs in to debug something and toggles a setting to test a theory. A client’s marketing person clicks around in the dashboard. A plugin update changes a default. A redesign brings in a new theme that registers different thumbnail sizes. Six months later, nobody remembers why a particular site is configured slightly differently from the rest.

The fix is a periodic check, not strict control.

Schedule a quarterly review. Most agencies already do quarterly site health checks. Add a step where someone opens ShortPixel’s settings, compares them against your reference file, and notes any differences. If a site has drifted, either restore it or document the new state as an intentional exception.

Version your reference file. When you update the agency baseline, save the file with a date or version number. That way, a site that doesn’t match the current baseline isn’t necessarily wrong, it might just be on an older version that hasn’t been migrated yet.

Document exceptions per client. Anything that legitimately deviates from the baseline (the photography client on Lossless, the premium brand with custom compression) belongs in that client’s internal notes. Otherwise, the next person who looks at it will assume it’s drift and “fix” it.

Final checklist

For every new client site, or when auditing an existing one:

• API key uses a per-client subaccount or alias, not the agency master key
• Settings imported from the current agency baseline file
• WebP and AVIF delivery verified on a live page (check dev tools, not just the settings toggle)
• A few key page types tested: homepage, a product or listing page, a blog post
• Cache and CDN cleared after configuration
• Any deviation from the baseline documented in the client’s internal notes

The goal isn’t perfect uniformity across all sites. Some sites genuinely need different settings, and that’s fine. The goal is that every difference is intentional, documented, and recoverable, so that anyone opening a ShortPixel setup six months from now immediately understands what they’re looking at and why.