Frequently Asked Questions

Asset Optimization

  • Will combining files break my site?

    Sometimes. Combining CSS/JS can cause layout or JavaScript errors.

    You can use the Exclude CSS/JS fields under:
    WP Speedy → WP Speedy → Asset Optimization

    Test combinations one by one to isolate issues. 

  • What does “Defer JS Interaction” do?

    It defers execution of all JavaScript until the user interacts (scrolls, clicks, etc).

    This improves load speed but can delay essential scripts – use carefully and test your theme. 

  • Does SpeedyGo support Brotli compression?

    Yes, if supported by your server.

    SpeedyGo auto-detects Brotli availability under:

    WP Speedy → WP Speedy → Asset Optimization → Compression

    Fallback to Gzip is automatic. 

Troubleshooting & Compatibility

  • Why aren’t WebP images loading?

    Check the following:

    1. Serve WebP is enabled in WP WebP → General Settings
    2. GD/Imagick shows WebP supported in System Info
    3. .webp files are actually generated (check file paths)
    4. Your CDN supports and serves WebP format 
  • Can I use SpeedyGo with WP Rocket or other caching plugins?

    It is not recommended to use multiple caching plugins together.

    They may:

    • Conflict in how files are minified or cached
    • Purge each other’s cache at the wrong time
    • Cause layout issues or unexpected behavior

    Disable other optimization plugins before enabling SpeedyGo. 

  • Does SpeedyGo work with Elementor, Divi, or page builders?

    Yes, but:

    • You may need to exclude builder-specific JS/CSS from minification
    • Avoid deferring JS if it affects critical builder scripts
    • Use visual testing after enabling optimization features 
  • Is SpeedyGo multisite compatible?

    Yes. SpeedyGo supports WordPress Multisite:

    • Activate network-wide or per site
    • Settings are managed per site 

Support & Help

WebP Optimization

  • Will SpeedyGo delete my original images?

    No. SpeedyGo creates WebP versions alongside your original .jpg or .png files. Your originals remain untouched. 

  • How do I convert existing images?

    Navigate to:

    WP Speedy → Bulk WebP Conversion

    This tool scans your media library and converts all supported images to .webp format. The process supports filtering, retry, and logs. 

  • Can I automatically convert new uploads?

    Yes.

    Enable the “Convert on Upload” toggle under:
    WP Speedy → WP WebP → General Settings 

  • Which formats are supported?

    Supported:

    • JPEG (.jpg, .jpeg)
    • PNG (.png)

    Not supported:

    • SVG, GIF, WebP (already optimized) 
  • How can I change WebP image quality?

    Go to:

    WP Speedy → WP WebP → General Settings → Image Quality

    Use the slider (default is 80). Lower values reduce size, higher values improve quality. 

Installation & Activation

  • Does SpeedyGo work on shared hosting?

    Yes. SpeedyGo works on shared, VPS, or cloud hosting.

    Minimum requirements:

    • PHP 7.2 or higher
    • GD or Imagick with WebP support
    • WordPress 5.0+ 
  • Where do I find the SpeedyGo settings?

    Once activated, SpeedyGo adds its own top-level menu in the WordPress admin sidebar.

    Navigate to:
    WP Admin → WP Speedy

    From there, you can access:

    • Caching & Optimization: WP Speedy → WP Speedy
    • WebP Settings: WP Speedy → WP WebP
    • Bulk Converter: WP Speedy → Bulk WebP Conversion

Caching & Performance

  • What types of caching does SpeedyGo support?

    SpeedyGo offers:

    • Full-page caching
    • Object and transient caching
    • Browser caching (via headers)
    • Mobile-specific caching
    • Scheduled cache expiration
    • Automatic cache preloading and purging
  • Can I cache mobile and desktop versions separately?

    Go to: WP Speedy → WP Speedy → Caching & Preloading → Mobile Caching

    This ensures mobile users receive device-specific cached versions. 

  • How do I exclude URLs from caching?

    Go to:

    WP Speedy → WP Speedy → Caching & Preloading → Exclude URLs 

    Enter each path on a new line, e.g.: 

    /cart

    /checkout

    /my-account