The complete guide
Website Personalization
What it is, why it works, and where to start.
Learn
Use Cases
How teams use ConversionWax
Guides
Step-by-step setup and strategy
Content Personalization Guide
How to personalize your website
Playbook
Proven plays for every industry
Compare
How we stack up against others
Blog
Personalization tips and platform updates
Help Center
Docs, setup guides, and support
Featured playbook
Ecommerce Personalization Playbook
Geo-targeted offers, BFCM windows, device-specific layouts - copy-paste plays that run themselves.
Optimized Images
Auto-resize for any device
Video Support
Personalized video content
Scheduled Updates
Time-based content automation
By role
Ecommerce Operators
Geo-offers, BFCM, device layouts
Growth Marketers
Campaign pages, UTM matching, A/B
Digital Agencies
Multi-site, version control, team access
New in the platform
AI Image Generation
Generate campaign visuals from a prompt. Saves to your asset library.
Learn more →Real-time personalization hub
Real-Time Website Personalization
One embed across every platform. Geo, UTM, viewport, and schedule rules render in milliseconds.
Platforms
WordPress
Plugin · WordPress.org
Shopify
Real-time personalization
Adobe Commerce
Plugin · Magento personalization
Contentful
Headless CMS personalization
Joomla
Real-time personalization
Sanity
Headless CMS personalization
Native plugins
On WordPress.org
ConversionWax for WordPress
Official plugin: shortcode-based banners, A/B testing, and AI image generation. Defer-loaded, Core Web Vitals friendly.
Get the plugin →Help docs
ConversionWax for Adobe Commerce
Plugin for Adobe Commerce and Magento Open Source. Setup guide and configuration steps.
Read the docs →Asset imports
Just released
Canva → ConversionWax
Import banner designs and hero images from Canva directly into your ConversionWax asset library. Skip the export-upload cycle.
See how it works →Anywhere else
One embed code
If your site can accept a script, ConversionWax works on it. WooCommerce, Webflow, BigCommerce, Squarespace, custom builds.
See setup →Responsive Asset Delivery
Serve the right image format and size for each viewport automatically.
When to Use Responsive Asset Delivery
Serving desktop-sized images to mobile devices wastes bandwidth and kills performance. Responsive asset delivery ensures every visitor gets images optimized for their specific screen-faster loads, better Core Web Vitals, higher conversions.
- ✓ Your mobile pages load slower than desktop
- ✓ Core Web Vitals scores need improvement
- ✓ You have image-heavy landing pages
- ✓ Mobile bounce rates are high due to slow loading
How ConversionWax Implements Responsive Assets
📡 Signals Detected
Viewport width, device pixel ratio, connection speed (when available).
🎨 Variants Delivered
Mobile: Compressed JPEGs or WebP under 100KB. Tablet: Medium-res optimized images. Desktop: Full-resolution assets with optional WebP.
📈 Optimization
Track load times and engagement per asset variant. Identify which image optimizations impact conversions most.
Responsive Asset Use Cases
Mobile-Optimized Hero Images
Before: 2MB hero image loads on mobile over 4G.
After: 80KB compressed WebP loads instantly on any connection.
Portrait vs. Landscape Images
Before: Landscape image cropped awkwardly on mobile.
After: Portrait-oriented image specifically composed for vertical screens.
Product Image Optimization
Before: Same high-res product photos for all devices.
After: Appropriately sized images per viewport with maintained quality.
Video Poster Frames
Before: Heavy video files attempt to load on mobile.
After: Mobile gets optimized poster image; video only loads on desktop/WiFi.
Retina Display Optimization
Before: Blurry images on high-DPI screens.
After: 2x images for retina displays, 1x for standard-automatically selected.
Background Image Swapping
Before: CSS background images same for all devices.
After: Different background images per viewport without CSS changes.
Frequently Asked Questions
Does this replace srcset?
It works alongside srcset. ConversionWax handles content personalization; you can still use native responsive images for basic optimization.
How much faster will my pages load?
Depends on your current setup. Teams typically see 30-60% reduction in image payload for mobile, translating to 1-3 second faster loads.
Do I need to create multiple image versions?
Yes-you upload the variants you want to serve. ConversionWax handles the logic of which to show when.
Will this help Core Web Vitals?
Yes. Smaller images improve LCP (Largest Contentful Paint), a key Core Web Vitals metric.
Can I combine responsive assets with A/B testing?
Yes. Test different image approaches per device to find what converts best.
Does this affect SEO?
Positively. Faster page speeds and better Core Web Vitals improve search rankings.
Related Device Personalization Solutions
Faster Images, Better Conversions
Serve optimized assets for every device automatically.
Start Free Trial