Weave Code
Sulu Image Optimizer Bundle Laravel Package
innomedio/sulu-image-optimizer-bundle
A Sulu CMS bundle for automatic image optimization—compresses and resizes uploaded media to cut file sizes and speed up page loads while preserving visual quality. Integrates with Sulu's media management so images are optimized without extra manual steps.
The Innomedio Sulu Image Optimizer Bundle adds automated image optimization to the Sulu CMS media manager. Uploaded images are compressed and optimized to reduce file size while preserving visual quality, helping deliver faster page loads and better Core Web Vitals without manual processing.
- Automatic compression of uploaded media
- Generates optimized image variants and formats
- Configurable quality and sizing options
- Seamless integration with Sulu’s admin and media workflows
- Reduces storage use and bandwidth
Frequently asked questions about Sulu Image Optimizer Bundle
- Is innomedio/sulu-image-optimizer-bundle a Laravel package?
- No. It is a Symfony bundle built specifically for Sulu CMS, and it hooks into Sulu's media upload pipeline rather than Laravel's filesystem or HTTP layers. It will not work in a standard Laravel application without running Sulu separately or reimplementing the optimization step. For Laravel projects, use a Laravel-native optimizer such as spatie/laravel-image-optimizer or a custom queued job.
- How do I install and register the Sulu image optimizer bundle?
- Install it with Composer, register the bundle in config/bundles.php alongside your Sulu bundles, and set the optimizer options for quality and backends. Because the upstream repository is archived, install from a pinned internal fork rather than the original package. Validate the setup against representative media before enabling it broadly.
- Which Sulu and Symfony versions does this bundle support?
- The bundle was built for Sulu 1.x or 2.x on Symfony, but you must check its composer.json for exact version constraints. The upstream is archived, so there is no compatibility work for newer Sulu or Symfony majors. Treat it as an unproven internal fork and test carefully before any CMS upgrade.
- What image optimization backends does it use?
- The bundle likely relies on CLI binaries such as jpegoptim, pngquant, cwebp, and gifsicle, or on Imagick or GD. The README and code should be audited to confirm which backends are supported and how versions are configured. Your deploy image must include the required binaries and permissions to execute them.
- Does the bundle optimize images synchronously during upload?
- The pipeline semantics are not documented, so you need a code read and a staging test to confirm whether optimization runs synchronously in the upload request or is queued. Synchronous optimization can increase request time and memory use for large images. Set timeouts and memory ceilings and test with oversized files.
- Are original images preserved or overwritten in place?
- This is a critical correctness question that the repository context does not answer. Read the code and test with sample uploads to see whether originals are retained, because originals are needed for re-derivation, CDN workflows, and legal or audit requirements. If the bundle overwrites in place, adjust your storage or backup strategy before production.
- Does it convert images to WebP or AVIF and create responsive renditions?
- Format conversion depends on the configured backend and the bundle's options, so verify WebP or AVIF output explicitly in a test environment. Sulu itself handles image renditions and image-format generation, so confirm how the bundle interacts with that layer. Test transparency, animation, and EXIF-rotated images as well as standard photos.
- Is the bundle maintained and safe to use in production?
- No, the upstream repository is archived, has very low visibility, and shows no evidence of production dependents. There are no security patches, issue triage, or compatibility updates for new Sulu and Symfony majors. Fork the code into an internal namespace, pin it to a commit, add CI, and treat any defects as internal defects.
- How should I test the image optimizer before deploying?
- Build a representative corpus that includes photos, screenshots, transparent PNGs, animated GIFs, CMYK JPEGs, EXIF-rotated images, and oversized TIFF or HEIC files. Compare byte size and visual quality using SSIM or PSNR, and measure request time and memory use. Run the tests in staging with the same binaries and versions as production.
- What are the alternatives to this bundle for Laravel or Sulu?
- For Laravel, use spatie/laravel-image-optimizer or a custom queued optimization job rather than bridging a Symfony bundle into your app. For Sulu, use a maintained image optimizer bundle or your own fork of this one. The key is to keep optimization inside the platform that owns the upload flow.
Weaver
How can I help you explore Laravel packages today?