Choose the right plan
Swift Performance AI is the best choice to speed up your WordPress sites. There are 4 + 1 available plans:
You can use Swift Performance with Single plan for 1 WordPress site. It can be the right choice if you have only 1 site, or if you would like to test what can Swift Performance AI do (you can upgrade your subscription later).
You can use Swift Performance with Multi plan for up to 5 WordPress sites. Regarding that the Multi plan price is very reasonable, if you have at least 2 sites you should choose Multi plan.
As the plan name suggest this plan is the best for developers, who manage many sites. You can use Developer Plan for up to 100 WordPress sites. If you are an agency, or freelancer, who has few clients you should choose Developer plan.
We created Business plan for professional speed up experts, who doesn't manage the site, but speed up WordPress sites as a service. Business plan can be used on unlimited sites. For this plan monthly subscription is also available, so you can choose the monthly plan with a reasonable monthly fee as well.
Micro license is a special Single license for bloggers and personal sites. Even if your project generates some income you can use Micro license if your project meets the following requirements: Your site may can generate income from ads, but you can’t sell any service/product (including PR articles) on the site. Using Micro license is not allowed for politically active sites.
Install Swift Performance AI
- Login to My account on swiftperformance.io
- On the next screen you will see your subscriptions. Choose any active subscription and click to Manage Subscription
- On the next screen click to Download in Swift Performance AI section (you can still download Swift Performance 2, but it is a different plugin)
- Login to WordPress admin where you would like to install Swift Performance AI
- Go to Plugins < Add new and click to upload plugin
- Select the previously downloaded ZIP file (swift-ai.zip) and click to install
- Now let Swift Performance AI to configurate itself
Caching is one of the core functions of Swift Performance AI. The cache warmer will load all of your pages - when necessary - and save a static version of every pages.
Once a visitor will be served from cache, your server will load this static file, which need much less resources (CPU and memory) and of course it is much faster than generate the page for every visit.
Some managed hosting has their own caching system (which sometimes even faster, but mostly it is better only for the hosting company), so you can disable caching in Swift Performance AI. Otherwise - in the most cases - you should let caching enabled in Swift Performance.
CSS optimization can improve Core Web Vital, it should be always enabled. There are 3 levels of optimization:
- Generate Critical CSS and optimize CSS delivery
- Optimize font delivery
If there are no issues with your fonts, then you should always set it to full optimization
- Offload main thread
- Delay less important scripts
If there are no issues on the site you should set it to maximum level, however in rare cases it can cause issues with some themes/plugins. If you have any issues please open a support ticket, and our developer team will check into it. In these cases as a quick fix you can set the level to medium or you can even temporary disable this feature.
Swift Performance AI will generate optimized WebP version for all images (including third party and background images) on the fly. Optionally you can also enable Optimize Images on Upload. Swift Performance also can use WebP which has been generated by other plugins, so you can switch instantly.
Swift Performance AI can create placeholder for iframes, and lazyload them. In that case on the first load only an optimized screenshot will be loaded instead the heavy iframe, and Swift Performance will load the embedded iframe only when it is necessary.
You can tweak advanced settings if you click "Under the hood" button in Configuration. In most cases you won't need to change these settings, except if you need a quick fix until permanent solution from our dev team.
With this option, you can exclude pages by URL (or URL part). Write one URL (part) per line, then click to update.
Swift Performance AI will detect non-cacheable pages automatically, however regarding that there are over 50 000 WordPress plugins and approximetly 30 000 themes, it can happen that Swift Performance can't detect a non-cacheable page. If you find that there is a plugin or theme related page which always should be excluded, please let us know.
Exclude Post Types
With this option, you can exclude post types. You can select multiple post types.
Just like pages, Swift Performance AI can detect non-cacheable post types automatically as well. However regarding that there are over 50 000 WordPress plugins, it can happen that Swift Performance can't detect a non-cacheable post type. If you find that there is a custom post type which always should be excluded, please let us know.
By default Swift Performance will bypass caching if query string is present in the URL. There are 2 options to overwrite this default behavior:
Ignored query parameters
You can define query parameters which should be ignored. Write one parameter per line. Swift Performance ignores some parameters by default: utm_source, utm_campaign, utm_medium, utm_expid, utm_term, utm_content, fb_action_ids, fb_action_types, fb_source, fbclid, _ga, gclid, age-verified
Allowed query parameters
You can list query parameters which shouldn't be ignored, but should be cached separately. For example if you add "s" parameter, all of your search results pages will be cached separately. Write one parameter per line.
By default Swift Performance will bypass caching if some specific cookies are set. However you can list any cookies here.
If you find that there is a cookie, which always should be bypassed, please let us know.
Usually you won't need to enable GZIP manually, because Swift Performance can detect compression and configure it automatically. However if you have double GZIP issues, then you may need to disable this feature in Swift Performance settings.
With this option you can let Swift Performance to set the expiry headers for different content types. Usually you don't need to disable this, however in some cases (for example if you are using a CDN with own expiry values), it is unnecessary.
Keep Original Headers
Send original headers for cached pages. If you are using a plugin which send custom headers you can keep them for the cached version as well.
Optimize Images on Upload
Swift Performance AI will optimize all images (even third party, and background images) on demand. This means, when the cache warmer cache a page, it will pick up all images and optimize them on the actual page. Therefore you don't really need to optimize images on upload, however it can be useful if you would like to serve optimized images for the first (uncached) pageview.
Swift Performance AI is using the native lazyload for images, but improve it. Automatically detects important images and exclude them from lazyloading. You need disable this feature only if you would like to use a different plugin for lazyloading (not recommended).
Smart Image Sizing
Swift Performance will automatically resize images for every used viewport size, and will use responsive images on every pages (even for logged in visitors). You need disable this feature only if you would like to use a different plugin for responsive images (not recommended).
Swift Performance AI will automatically detect the important images on every pages during the optimization process. These images will be excluded from lazyloading and will be preloaded (using the right responsive size) to improve LCP and FCP scores.
Swift Performance AI can load some part of the page dynamically and load the rest from cache. You can enable fragment caching for Elementor Widgets or Gutenberg Blocks in the editor, and specify shortcodes which should be loaded dynamically.
With this feature Swift Performance will use smart preload technique (based on network bandwidth and device) to speed up the onsite navigation. With preloading important pages before the user navigate the navigation can be nearly instant. It will improve the field data scores, and the user experience as well.
On the system tab you can see your subscription status and disconnect the current site from the subscription.
If you need to add the generated rewrite rules manually, you can download them and also can verify that they work.
You can check the API connection status and reconnect API if it is necessary, and you can also start over the whole setup process. Please note if you restart setup, your current settings will be overwritten.
Swift Performance AI is compatible with most plugins and themes out of box, however there are a few third-party plugins, themes, server software and services which are highly integrated with Swift Performance. Most of them doesn't need any configuration (like Elementor, Slider Revolution, WP Bakery, LiteSpeed, etc.), some others can be configured - if it is necessary.
You can enable autopurge Cloudflare cache, which is recommended if you are using Cloudflare APO, or proxy caching. If you previously used any Cloudflare plugin where your API credentials were set, Swift Performance will find them so you don't need to set them again.
If Cloudflare couldn't be configured automatically you need to choose the authentication mode, and enter Cloudflare e-mail and API password, or Cloudflare API token (recommended).
Once you configured Cloudflare you can enable Proxy caching, which will provide the same performance as Cloudflare APO.
If your site is running on Nginx server you need to add the generated rules manually to Nginx config.
You can find the rewrite rules on Nginx tab under Integrations, copy the rules, add them to config and restart Nginx.
On Nginx integration tab you can also verify that rules are up-to-date and working.
If Swift Performance detects Varnish you can enable Varnish module on Varnish tab under Integrations. Once you enabled it, Swift Performance will manage Varnish cache as well.
There are some specific features which can be enabled for a WooCommerce site. You can manage them on WooCommerce tab under Integrations.
If you have separate single pages for variations you should also prebuild them. For this you need to enable Prebuild Variations feature, so Swift Performance will automatically preload, cache and optimize available variation single pages for all products.
If Checkout Booster is enabled, Swift Performance will preload cart and checkout pages, and force visitors' browser to cache them for a short time. In that way cart and checkout pages can be loaded instantly when your customer navigate to cart/checkout pages.
If you have a multi-currency store, or use visitors' geolocation to calculate VAT on shop/product pages, you can enable Price Fragments feature, to load prices via AJAX, while the rest of the page can be served from cache.
0.3.23 - 2022.11.29.
- [IMPROVE] Iframe optimizer
- [IMPROVE] Jetpack compatibility
0.3.22 - 2022.11.25.
- [IMPROVE] JS Optimization Engine
- [FIX] typo in WooCommerce module
0.3.20 - 2022.11.23.
- [FIX] Elementor double init issue
0.3.19 - 2022.11.22.
- [FIX] source mapping issues in JS engine
0.3.18 - 2022.11.22.
- [FIX] Improve JS engine compatibility
0.3.17 - 2022.11.21.
- [FIX] Minor bugfixes
0.3.16 - 2022.11.21.
- [FIX] Gateway fo Braintree Payments compatibility issue
0.3.15 - 2022.11.21.
- [FIX] Fatal error when $urls empty
0.3.14 - 2022.11.21.
- [RELEASE] Public beta release