Meta tags:
Headings (most frequently used words):
documentation, getting, started, general, optimization, caching, media, cdn, compatibility, tweaks, license, frequently, asked, questions,
Text of the page (most frequently used words):
the (16), you (14), and (13), swift (12), performance (10), cache (10), cpu (10), www (9), will (8), can (8), are (7), settings (7), images (7), usage (7), scripts (6), exclude (6), caching (6), com (6), nginx (5), that (5), rewritecond (5), https (5), see (5), elementor (5), lazyloading (4), should (4), usually (4), size (4), redirect (4), non (4), ssl (4), example (4), htaccess (4), your (4), prebuild (4), more (4), all (3), with (3), clear (3), use (3), disable (3), lazyload (3), not (3), enable (3), optimization (3), them (3), add (3), following (3), happens (3), there (3), pages (3), dynamic (3), some (3), about (3), http_host (3), rewriterule (3), 301 (3), probably (3), rules (3), force (3), speed (3), shared (3), hosting (3), license (3), optimizer (3), changelog (2), install (2), configure (2), helper (2), fastcgi (2), redis (2), when (2), support (2), conflict (2), merge (2), async (2), execute (2), using (2), media (2), missing (2), find (2), but (2), exceptions (2), post (2), types (2), separate (2), steps (2), normal (2), css (2), 200 (2), means (2), have (2), rewriteengine (2), http (2), general (2), tweaks (2), this (2), order (2), these (2), from (2), strange (2), analytics (2), site (2), redirects (2), yoursite (2), webpack (2), pro (2), runtime (2), min (2), animations (2), working (2), limit (2), plugin (2), decrease (2), they (2), time (2), small (2), limited (2), how (2), cdn (2), image (2), server (2), 2026, rights, reserved, made, fevr, supports, properly, necessary, regarding, 3rd, party, may, features, well, recommended, built, any, other, loaded, autoconfig, most, automatically, manually, unnecessary, styles, then, larger, than, very, large, number, part, themes, plugins, creates, javascripts, why, folder, filled, average, cached, page, 400kb, 000, 400, server_port, 443, forwarded, proto, examples, custom, caused, improper, rule, please, remove, insert, urls, url, like, content, desktop, unauthenticated, index, html, both, enabled, elements, simply, need, merging, work, dropdown, menu, warmup, however, easy, solution, keep, under, set, moderate, reduced, wait, bit, between, preloading, 100, temporary, while, generates, once, generated, running, limits, won, let, options, optimizing, process, also, booster, compute, api, avoid, vps, provider, high, frequently, asked, questions, upgrade, generate, new, password, where, invoice, renew, subscription, many, sites, based, browser, language, regular, expressions, constants, contact, form, woocommerce, compatibility, cloudflare, integration, inline, responsive, global, webp, mode, proxy, side, jquery, migrate, push, critical, javascript, bypass, google, debugging, errors, database, heartbeat, control, organizer, cronjobs, activate, uninstall, whitelabel, footprints, config, extra, getting, started, for, documentation, landing, quick, links, knowledge, base,
Text of the page (random words):
swift performance knowledge base quick links changelog landing documentation for swift performance getting started swift performance extra add rules to nginx config whitelabel and footprints install swift performance uninstall swift performance activate your license see more general cronjobs plugin organizer heartbeat control database optimizer debugging errors bypass google analytics optimization javascript optimization critical css server push lazyload scripts disable jquery migrate server side scripts see more caching cache exceptions clear cache prebuild cache dynamic caching proxy caching caching mode see more media webp support image optimizer image optimizer global settings lazyload images force responsive images inline small images see more cdn cloudflare integration cdn settings compatibility woocommerce elementor contact form 7 tweaks constants regular expressions redirect based on browser language license on how many sites can i use swift performance renew your subscription where can i find the invoice how can i generate a new password upgrade license frequently asked questions high cpu usage usually it happens on small vps or limited shared hosting when cpu is limited by the hosting provider to avoid it you should do the following steps enable compute api enable prebuild booster these options will speed up optimizing process and also will decrease cpu usage if your site is running on shared hosting they usually limits the cpu usage cpu time that means they won t let you use the shared cpu all the time 100 cpu usage is temporary it happens while swift generates the cache but once it is generated cpu usage will be about 0 however there is an easy solution to keep cpu usage under the limit you can limit prebuild speed if you set it to moderate or reduced the plugin will wait a bit between preloading pages it will decrease the cpu usage you can configure it in settings caching warmup prebuild speed elementor animations or dropdown menu are not working if merge scripts and async execute is enabled and elementor animations are not working or some elements are simply missing you will probably need to exclude webpack runtime min js from merging in order to work to exclude it in both elementor and elementor pro add the following to exclude scripts webpack pro runtime min js strange redirects if you have strange urls in your analytics or you can see that the site redirects to an url like this https www yoursite com wp content cache yoursite com desktop unauthenticated index html this is probably caused by an improper order of htaccess rules probably you are using a force ssl or force www non www rule in htaccess please remove these rules from htaccess and insert them in settings general tweaks custom htaccess some examples redirect non www to ssl www rewriteengine on rewritecond http_host example com nc rewriterule https www example com 1 l r 301 redirect non ssl to ssl rewritecond https on rewritecond server_port 443 rewritecond http x forwarded proto https rewriterule https http_host 1 r 301 l redirect www to non www rewriteengine on rewritecond http_host www example com nc rewriterule http example com 1 l r 301 cache size the average size of a cached page should be about 200 400kb that means if you have 1 000 pages the normal cache size will be about 200 400 mb if cache size is larger than normal it usually happens if there are a very large number of pages or if there is a dynamic part in js or css some themes plugins creates dynamic javascripts and that is why the folder is filled up clear all cache then do the following steps 1 enable separate styles and separate scripts in optimization settings 2 exclude unnecessary post types autoconfig should find most and exclude them automatically but you can add them manually settings caching exceptions exclude post types missing images if images are not loaded usually it is a conflict with lazyloading if you are using any other lazyloading you should disable it or disable it in swift performance settings media images lazyload images regarding that 3rd party lazyloading may can conflict with merge scripts and async execute features as well it is recommended to use swift performance built in lazyloading fastcgi nginx cache and redis support swift performance supports nginx helper if you install and configure nginx helper properly swift will clear nginx fastcgi and redis when it is necessary changelog 2026 swift performance all rights reserved made with fevr
|
