Most heavy pages are not fonts. They are photographs exported at camera resolution into a column that is only a few hundred pixels wide. The browser downloads millions of pixels, then throws most of them away during layout. Compression cannot fully fix a bad export order. Resize first, then compress.
The Image Resizer on FreeToolsBox sets the pixel budget. Decide the largest display size you actually need and resize to that width before you worry about encoder settings. Retina layouts may justify 2x assets, but 3x and 4x versions of a blog photograph are rarely earning their bytes.
After the pixel budget is set, the Image Compressor decides how much quality you can surrender. JPEG remains the workhorse for photographs. WebP often wins on weight for the same perceived quality when browsers support it. PNG still wins for UI chrome, screenshots with sharp text, and anything that needs a clean alpha channel.
Browser compression is honest about one limit: it re-encodes pixels you already have. It cannot invent detail that a noisy phone sensor never captured. Start from the best master you own, resize once, and avoid repeated open-and-save cycles in lossy formats.
Format conversion is a separate job from compression. The Image Format Converter exists for the moment you need WebP for the web, JPEG for email, or PNG for a transparent logo. Conversion without resizing is how people ship a large WebP that is still the wrong dimensions.
Favicons are a special case of the same discipline. A 4000-pixel PNG forced into a browser tab is wasted work. Use the Favicon Generator and ship a small icon that still reads as your mark at 16 and 32 pixels.
Perceptual quality matters more than a single numeric quality score. Zoom to 100% on a typical device. Check faces, text overlays, and large flat gradients — those areas show artefacts first.
Accessibility and performance meet in the middle. Lighter images improve load time on slow networks. They also reduce data costs for mobile users. Compressing well is a product decision, not only a Lighthouse score chase.
When you hand assets to a CMS, keep a clean master offline and publish derivatives. Re-compressing an already compressed CMS download is how quality dies across redesigns.
A practical workflow: export or upload the master, run the resizer to the target width, compress with a conservative quality setting, then spot-check on phone and laptop. If the page still feels heavy, look for the next largest image rather than punishing the logo that is already small.
FreeToolsBox keeps these utilities in the browser so your unpublished photographs and client assets do not need to sit on a random server for a one-off export.
Sharp sites feel intentional. Soft, bloated images feel accidental. Resize, choose the right format, compress once, and move on.