Frequently Asked Question
override image sizes

The neo Optimize plugin is a WordPress image optimization plugin. It automatically reduces images to the actually needed display size, converts image files to the fast WebP format, and stores optimized copies in the cache. This makes images load faster and your website more performant, which has a positive effect on SEO ranking.

No, your original images remain completely intact. The plugin neo Optimize only creates optimized copies in the cache and serves those on the frontend. The original files in your media library are not overwritten.

Also your WordPress database remains untouched. When loading the website only the image URL on the frontend is replaced by the optimized cache version. If you deactivate or uninstall neo Optimize, everything is back to how it was before.

The retina factor controls the pixel density at which images are generated for high-resolution displays. A higher value can make images appear sharper on Retina displays but also increases file size.

By default, neo Optimize uses a retina factor of 1.5x to improve the rendering of small text, icons, and details in images on Retina displays. In the Pro version you can set the retina factor individually and compare it directly in the preview.

You should clear the cache when you want to regenerate already optimized images with new settings. This applies, for example, to changes in image quality, the retina factor, or the desired image size.

In the settings of neo Optimize you'll find a dedicated Clear cache button for this. After that, the optimized images will be regenerated automatically as soon as they are requested again in the frontend.

For most websites we recommend a WebP quality of 75%. The WebP format is very efficient, so even lower quality settings often still look very good and produce significantly smaller files.

In the settings of neo Optimize you can conveniently choose the quality and directly evaluate it via a preview with file size. This way you quickly find the right balance between high image quality and fast loading times.

Yes, neo Optimize works with all common page builders. These include Bricks, Elementor, Divi, Beaver, Oxygen, Breakdance, and Gutenberg.

For Bricks and Elementor, neo Optimize can automatically read the configured image sizes and use them as the basis for optimization. This ensures the image is cached as close as possible to the actual display size in the frontend.

If a graphic was created with neo Draw, neo Optimize can automatically optimize it when serving it in the frontend. Unnecessary editor data is removed from the served cache version and embedded raster images can be converted to the efficient WebP format.

The original neoDraw file remains fully intact and editable. Visitors receive a leaner, faster version in the frontend while you can continue to work with the editable original drawing in the backend.

No. neo Optimize processes your images directly on your own server. Local server functions like Imagick or PHP GD are used for image optimization. That means you don't need external image services, no credit packages, and no additional cloud processing. This makes optimization particularly privacy-friendly, cost-effective, and independent of external providers.