Description
Make your WordPress site faster, safer and easier to find. Arva SEO – Speed Booster & Security Scanner caches your pages, converts images to WebP and compresses them, scans your files for known malware and security problems, and fixes the PageSpeed and Core Web Vitals problems Google reports, one switch at a time. It also checks your basic SEO, shows which missing pages visitors ask for so you can redirect them, and, if you use no SEO plugin, lets you write SEO titles and descriptions.
Page caching, WebP and local image compression, the security scan, the SEO checklist, the broken-address log, redirects and SEO titles all work without an Arva SEO account. Anything that changes what visitors get starts off, and turning it off puts your pages back. A few features (optimized CSS, cloud image compression and deep scans) need a connection to Arva SEO and use the allowances of your plan; connecting is optional.
PageSpeed fixes you control
Arva SEO → Speed explains each fix and the PageSpeed (Lighthouse) problems it addresses. Every fix starts off. Try mode shows supported changes only to signed-in administrators before you enable them for visitors. Server-level caching and compression instead check the site when enabled.
- Page caching: serve saved HTML without running WordPress, through .htaccess or PHP. Signed-in users, personal pages, carts and checkouts are excluded. Cached pages are cleared when relevant content or settings change.
- Background images: the Speed screen detects Elementor’s native background lazy-loading setting and explains its separate exclusions and JavaScript requirement. Arva SEO does not enable it silently or install a second background loader. Keep hero backgrounds eager and test scrolling and interactive widgets.
- Images and layout: prioritize featured images and the homepage image identified by a connected PageSpeed test; lazy-load images, videos and maps below the first few images; add missing media-library image dimensions and the mobile viewport tag when needed.
- Critical and used CSS: Load styles faster supplies first-screen styles; Remove unused CSS supplies the styles a page uses, with full stylesheets available on interaction. Original stylesheets are measured at phone and computer sizes; matching results are assembled in source order for compatible combined files. With the updated combining behavior approved, unmatched files stay separate so ready neighboring results remain usable. Arva SEO generates these on its servers using your plan’s page optimizations. Choose generation by page type or URL, inline or cached-file used CSS, and an inline or external asynchronous loader. Original styles load until suitable results are ready.
- CSS and JavaScript minification: smaller cached copies of supported local files, plus separate controls for minifying inline style blocks and classic scripts in their existing tags. Unsupported files and code stay unchanged.
- CSS and JavaScript combining: bundle compatible neighboring files in order. Optional inline combining requires approval of an exact public static snippet; a changed snippet stops matching its approval. External combining requires exact approved public HTTPS URLs and background caching. Incompatible scripts, integrity-protected resources and managed critical/used CSS stay separate. Fewer requests do not always improve performance.
- Script loading: defer supported scripts until HTML is parsed, or delay supported independent classic scripts until interaction. Dependencies, consent tools, protected measurement scripts and your exclusions are retained. Changing a public loading mode returns it to preview; enabling it requires checking your important pages.
- Chat and third-party widgets: separately delay supported chat, heatmap and social widgets until interaction. Analytics and consent tools are not selected automatically; you can list additional scripts.
- Fonts: optimize Google Fonts delivery, optionally serve local copies, and apply font-display: swap to supported styles so fallback text can appear while fonts load.
- YouTube facades: show a preview image and load the player when someone presses play.
- Browser caching and compression: checked .htaccess rules for Apache and LiteSpeed, with backups and rollback if the site does not respond normally. Other servers can use the suggested rules.
- WordPress extras: choose whether to remove emoji scripts, embed discovery, visitor Dashicons, jQuery Migrate or unneeded block styles.
- Image optimization: make WebP copies of new or existing uploads while keeping originals. Compress existing Media Library JPEG, PNG and supported WebP images in background batches, or select images with bulk actions. See saved bytes and restore originals when backups were kept. WebP compression is local; optional consented cloud compression sends JPEG/PNG images to Arva SEO and uses your image allowance only when it makes an image smaller.
Use page, script, plugin and element exclusions to leave sensitive parts of your site alone. Defer/delay and CSS delivery leave shop pages alone by default. Turning delivery fixes off restores their normal behavior; image changes have their own restore controls. Theme source files and post content are not rewritten by delivery fixes. Keep backups and test menus, forms, booking flows and checkout before enabling changes for everyone.
When another supported speed plugin handles a job, Arva SEO leaves it to that plugin. Deactivation is offered only as an explicit administrator action. An emergency wp-config.php switch can disable all speed fixes; see the FAQ.
Connected PageSpeed results link to the matching controls. Remote switching is off by default and needs administrator approval. Authorized workspace managers can then request supported changes, subject to the same rules; Defer scripts still requires approval in WordPress. Changes are recorded in Activity.
Cloudflare
Optionally connect a Cloudflare API token on the Speed page, without an Arva SEO account. The token is stored encrypted. The plugin clears Cloudflare’s cached pages when relevant content, delivery settings or optimized assets change, and checks for Rocket Loader conflicts. You can disable duplicate post purges if Cloudflare’s own plugin already handles them.
Security scan and chosen repairs
Arva SEO → Health → Security scans locally in background batches, weekly or when you choose Scan now. No account is required. It checks:
- WordPress core and directory plugins against official WordPress.org checksums, including changed, missing and unexpected files.
- PHP in uploads, disguised code, suspicious patterns in nonofficial files, injected redirects and .htaccess rules.
- Exposed configuration, repository, debug, backup and database files; directory listings; and security-related settings.
- New or changed theme, premium-plugin, must-use-plugin and drop-in files, including selected added-line evidence.
- External scripts loaded by sample pages and where they were added, plus dashboard theme/plugin file edits.
Results explain the finding and suggested action. Nothing is repaired automatically. Choose to restore an official file, quarantine unexpected PHP or disable dashboard file editing; supported repairs can be undone for 30 days. Mark an expected result as trusted until its file changes.
Connected sites can receive updated security patterns, known-malware fingerprints, vulnerability findings from Wordfence Intelligence and optional alerts. Sharing scan evidence requires separate consent. A scan detects known signs of trouble; it cannot prove a site is clean and does not replace a firewall, backups, updates or professional cleanup.
Optional deep scans need separate administrator consent and are started individually. Code files not matched to official copies are sent to Arva SEO for malware checks and deleted when the scan finishes. Configuration secrets, logs, database exports, backups and media are excluded. Deep scans use the service’s applicable allowance.
SEO checklist (no account needed)
Arva SEO → SEO checks ten basics and tells you, in plain words, what passed, what needs attention, why it matters and how to fix it in WordPress: HTTPS, “Discourage search engines” off, readable permalinks, a site title, one home page title of a sensible length, a meta description, no accidental noindex on the home page, a sitemap, a robots.txt that doesn’t block everything, and the share of home page images without alt text (a sample). It reads what WordPress knows and makes one request to your own home page from your own server. Nothing is sent anywhere, and the screen changes nothing on your site.
Broken addresses and redirects (off until you turn them on)
Arva SEO → Redirects can log the missing pages visitors ask for, with only the path (without anything after a question mark), how many times, and the first and last time. It never keeps IP addresses, browsers, referring pages, cookies or user IDs, and keeps at most 1,000 addresses; image, script and font requests and addresses that look like hackers probing are left out. Choose “Redirect this” to send an address to a path on your site or to a full https:// address you type. A redirect is an exact-path rule (301 or 302), up to 500 of them; the plugin refuses loops, a redirect to itself and chains of more than three, and only administrators can make them. Rules can be exported as CSV. Nothing is written to .htaccess. An emergency wp-config.php switch turns redirects and the log off; see the FAQ.
SEO titles and descriptions when you have no SEO plugin (off until you turn it on)
If none of Yoast SEO, Rank Math, All in One SEO, SEOPress or The SEO Framework is active, Arva SEO → SEO can add an “SEO title” and “Meta description” box to posts, pages and products, and two fields for the home page. A page prints a description tag or changes its document title only when you filled one in. If you later install an SEO plugin, this stops at once so a page never gets two. The values are stored on your site only.
Optional Arva SEO connection
Approve the connection on app.arvaseo.com without entering an Arva SEO password in WordPress. Each site receives revocable encrypted credentials.
- Inventory and Website Health: share installed plugin/theme versions and approved health checks for findings, tasks and reports.
- Content delivery: receive drafts, pending-review, scheduled or published posts within your chosen publishing ceiling; Draft only is the default.
- SEO updates: separately allow approved SEO titles and meta descriptions for published posts, pages, products and the homepage in Yoast SEO or Rank Math. Only those fields change; caches are cleared and updates can be undone.
- IndexNow: serve the key supplied by Arva SEO for its supported search-engine notifications.
Review shared fields in Settings → Diagnostics and data sharing. External services, consent requirements and data handling are detailed below and in the FAQ.
External services
Connecting to Arva SEO (https://arvaseo.com) is optional and starts only when an administrator connects the site. Local fixes work without an account. The optional features below contact their listed services only when you enable or use them.
- When connecting: you are sent to app.arvaseo.com to sign in and approve; the plugin then exchanges a one-time code with api.arvaseo.com for this site’s own credentials, and sends the site address, name, WordPress and plugin versions, time zone, environment type, your publishing settings, which of the plugin’s PageSpeed fixes are on, which of the plugin’s update notes applied to this site (their ids and dates) and, for an update to a fix you use, whether it waits for your check, you kept the previous version or visitors get it, which page caches and CDNs the plugin found in front of the site (their names, whether the plugin clears them or you do, how you clear the ones that are yours, when each was last cleared, and how many old generated files are kept because of them), and your data-sharing choice.
- Cache check (once a day, no account needed; the request goes only to your own site): the plugin requests your own homepage from your own server, as a visitor would, without cookies or a login, reads a fixed list of its response headers (for example cf-cache-status, x-litespeed-cache, age and cache-control) and the comments cache plugins leave in the page, and keeps only the names of the caches it found. When the site is connected, those names are sent with the site’s details (see above). Also, when it clears a LiteSpeed server cache from a command line or scheduled task, it asks your site for a page that answers with LiteSpeed’s purge header.
- SEO checklist (no account needed; the request goes only to your own site): when you open Arva SEO → SEO or press Check again, the plugin requests your own home page from your own server, as a visitor would, without cookies or a login, and reads its title, meta description, robots rules and images. Results are kept on your site for 15 minutes. Nothing is sent to Arva SEO or anyone else.
- Links you click: “See every fix in Arva SEO” (arvaseo.com, with utm_source=wordpress-plugin and utm_medium=seo-checklist in the address) and “Write a review” (wordpress.org) are ordinary links. Nothing is requested or sent when they are shown; the review request appears only on this plugin’s own screens, after a security scan has finished or a speed fix has been on for a week, and it keeps your answer on your site only.
- Plugin inventory and Website Health (only if you agree when connecting, or later in Settings → Diagnostics and data sharing): installed plugins and themes with versions and update state, and the results of about 40 health checks (booleans, counts and versions only), including saved database maintenance counts from 2.12.0. Cleanup is started only in WordPress; the app and AI connector read counts but cannot start it. Sent after connecting, twice a day for the inventory and once or twice a day for health checks, after plugin changes, and when you or Arva SEO ask for a recheck.
- Security scan results (off by default, a separate choice): after each scan, when an administrator agreed to share them, each open problem’s kind, severity, a key, the file’s path inside the site and its SHA-256 fingerprint, and for suspicious code the pattern’s name, line and the start of that line, with how many files were checked. Never the files themselves.
- Security feed (only when connected): once a day the plugin downloads Arva SEO’s security feed from api.arvaseo.com (fingerprints of known malware and of files found safe, PHP’s latest versions, new patterns), sending only the version it has.
- Deep scans (off by default, a separate choice, and each one started by an administrator): the code files the security scan couldn’t match to an official copy (the theme, premium and custom plugins, and anything unexpected), with their paths inside the site, SHA-256 fingerprints and sizes, 2 MB each and 50 MB in all at most, sent to api.arvaseo.com to be checked for known malware and deleted as soon as the scan finishes. Never wp-config.php, .env files, logs, database exports, backups or media. The plugin then fetches what was found.
- Content: every 5 minutes the plugin asks api.arvaseo.com for content you sent from Arva SEO, and reports back the post ID, status and link it created.
- Switching fixes from Arva SEO (off by default): when allowed, the plugin asks api.arvaseo.com every 5 minutes (and when Arva SEO signals it) for fixes switched there, and reports back what it did and each fix’s state.
- Signed requests from Arva SEO: api.arvaseo.com may call this site’s …
Installation
- Upload the plugin through Plugins → Add New → Upload Plugin, and activate it.
- Open Arva SEO → Get started, review what is shared, and click Connect to Arva SEO.
- Sign in to Arva SEO, choose the website, and approve. You return to WordPress connected.
- In Arva SEO → Settings, choose the default author and publishing mode.
For reliable scheduled publishing on low-traffic sites, run WP-Cron from a server scheduler (see the administrator guide).
FAQ
Can I combine CSS and JavaScript?
Yes. Arva SEO → Speed has separate Combine CSS and Combine JavaScript controls. Each starts off and has a Try mode visible only to administrators. Compatible neighboring local files are bundled in their existing order. CSS image and font addresses keep working; inline code, asynchronous or module scripts, excluded files and Critical CSS/Remove unused CSS delivery stay separate. Minification remains a separate setting. Fewer requests do not always improve performance, so check your site before enabling a control for visitors.
Does the plugin change my site?
Only in the ways you switch on. PageSpeed fixes change how your pages load, only after you turn each one on, and turning it off undoes it. When a change alters what visitors see, the plugin also clears the page caches it can reach (cache plugins, your host’s cache, Cloudflare) at most every 15 minutes, and once a day it asks your own site for its homepage, as a visitor would, to read its cache headers and find the caches in front of it. Website Health, the security scan and the SEO checklist are read-only: they report, and every finding is a recommendation. Redirects and SEO titles and descriptions change what visitors get only after you turn them on. Arva SEO can only create or update posts it sent, within your publishing mode, and, if you allow it in Settings, change the SEO title and meta description of published content in Yoast SEO or Rank Math.
What happens to the fixes I use when the plugin updates?
Nothing changes silently. An update that only adds an option (off until you turn it on) or only makes a fix do less is applied, and Arva SEO → Speed lists it under “What changed”. An update that could make a page work differently for visitors waits for you: your visitors keep the version you checked, you see the new one while you’re signed in, and the fix shows “Update to check” with three choices: use it for visitors, keep the previous version, or turn the fix off. The earlier version stays at least 90 days. Before it is retired, a connected site is reminded in Arva SEO; when the day comes, the fix goes back to being tried so you can check the new version.
Is the security scan a firewall or a malware cleaner?
No. It finds problems and says what to do, and it doesn’t block traffic or log-in attempts. It can put back official copies of WordPress and plugin files and move PHP out of the uploads folder into quarantine, when you choose to, and each can be undone for 30 days. A hacked theme, a database or passwords still need a clean-up, which your host or developer can help with.
What does a deep scan send?
Only when an administrator has allowed deep scans and starts one: the code files the security scan couldn’t match to an official copy, with their paths inside the site, their SHA-256 fingerprints and sizes. Configuration files, logs, database exports, backups and media are never sent, and the files are deleted on Arva SEO’s servers as soon as the scan finishes.
Does the security scan slow my site down?
It runs in the background in batches of about 20 seconds with pauses in between, reading files only up to 2 MB for patterns, and stops after 150,000 files. You can stop a scan at any time, and turn the weekly scan off in Settings.
What does the security scan send to Arva SEO?
Nothing, unless the site is connected and an administrator ticks “Also share the security scan’s results” when connecting or in Settings → Diagnostics and data sharing. Then it sends each open problem’s kind, severity, the file’s path inside the site and its SHA-256 fingerprint (for suspicious code, the pattern’s name, the line and the start of that line), and how many files the scan checked. The files themselves are never sent.
From 2.7.0, with that consent given again for the new fields (the Health page asks once), it also sends: up to 10 lines added to a file that’s new or changed since the last scan; the host names and addresses of scripts your pages load from other websites, with where each is added (a file and line, a setting’s name or a post’s ID); the kind, path and fingerprint of problems marked as expected; and, when a file is saved with WordPress’s file editor, its path, the time, the username and display name of who saved it, the IP address the request came from (and the one a proxy in front of the site reported) and up to 10 added lines. Until then the results are shared as before, without these.
Can a PageSpeed fix break my site?
Most only add or change attributes on images and links, and visitors see the same page. Defer scripts, Delay chat widgets and trackers, Click-to-play videos and Remove unused WordPress extras can affect how some sites work, so try them first and check your important pages. Page caching and Browser caching and compression change your server’s settings, so they can’t be tried first; they check your site straight away instead (see below). If something stops working, leave that page, script or image alone (see the next question) or turn the fix off on the same page. In an emergency, add define( 'ARVASEO_CONNECTOR_DISABLE_SPEED_FIXES', true ); to wp-config.php to switch every fix off. Arva SEO’s own page cache clears itself when a fix changes, and so do the other caches it can reach (Arva SEO → Speed → Other caches on this site lists them); a cache it can’t reach, such as a host’s CDN, is listed there with how to clear it.
Does it work with Cloudflare?
Yes. In Arva SEO → Speed → Cloudflare, paste a Cloudflare API token with Zone → Zone → Read and Zone → Cache Purge → Purge for your site’s domain (add Zone → Zone Settings → Read so Rocket Loader can be checked). The token is stored encrypted and only ever sent to Cloudflare. If Cloudflare’s own plugin already clears a post’s pages when it changes, switch that part off here; the plugin still clears Cloudflare’s copy when a fix changes.
Can I leave a page, script or image alone?
Yes, in Arva SEO → Speed → Leave things alone:
- Pages: addresses such as
/checkout/or/shop/*, a “Leave this page alone” tick box when you edit a post or page, or Arva SEO in the toolbar while you view any page. Defer scripts also leaves WooCommerce and Easy Digital Downloads cart, checkout and account pages alone unless you untick it. - Scripts (Defer scripts): a script name (handle), part of its file address such as
booking.js, or every script from a plugin you choose. - Images, videos and maps: a CSS class (
.hero-slide), an id (#main-banner) or part of the file address (logo.svg). A block’s Additional CSS class counts for everything inside the block. Lazy-load also respects theskip-lazyandno-lazyclasses other plugins use, and every fix skips an element with thedata-arvaseo-skipattribute. - How many images at the top of each page always load straight away (3 unless you change it).
Are there filters for developers?
arvaseo_connector_speed_fix_applies (bool $applies, string $fix_id) turns a fix off for any condition, arvaseo_connector_defer_script (bool $defer, string $handle, string $src) leaves a script alone, and arvaseo_connector_optimize_element (bool $optimize, string $fix_id, string $tag, array $attributes) leaves an image or frame alone.
Can it make critical CSS or remove unused CSS?
Yes, from 1.6.0, when the site is connected: Load styles faster and Remove unused CSS. Arva SEO loads one page of each type (homepage, page, post, product, category and so on) on its servers, as a phone and as a computer, and sends back each stylesheet’s critical and used CSS. Each page type uses one page optimization of your plan (Free 50 a month, more on paid plans, and an add-on of 15,000). A stylesheet whose contents change makes a new page type; clearing your cache costs nothing. When the month’s page optimizations run out, page types whose styles haven’t changed keep their optimized CSS and the others load their normal stylesheets, never out-of-date CSS.
Can my agency switch the fixes from Arva SEO?
Yes, from 1.7.0, once an administrator ticks “Let Arva SEO switch these fixes” on the Speed page. Arva SEO’s PageSpeed results then show Try it, Turn on and Turn off next to each fix for people who manage the website’s integrations there. Switches are picked up within a minute or two; the rules are the same as in WordPress, and each change is logged with the name of the person who asked. Untick the box to stop it at any time.
Does it cache pages?
Yes, from 2.6.0, with Page caching (off until you turn it on). Each page is saved as ready-made HTML the first time a visitor opens it, and the next visitors get that copy without WordPress running. On Apache and LiteSpeed, rules at the top of .htaccess let the server send it without PHP; the plugin keeps a copy of your .htaccess from before it changed it, which you can download from the Speed page. Elsewhere (nginx, for example) a small advanced-cache.php file sends it before WordPress loads, and the plugin adds define( 'WP_CACHE', true ); to wp-config.php, or tells you the line to add when it can’t.
Turning it on checks your homepage from the server: made once, then served from the cache. If it isn’t, everything is taken out again. Signed-in users, visitors with a comment, password or cart, carts, checkouts and account pages, searches, addresses with a query (tracking ones like utm_source are fine) and pages that set a cookie are never cached, nor pages you leave alone. Saved pages are made again after 10 hours; a post’s pages are cleared when it changes, and every page when your theme, menus, widgets or a fix change, or when you press Clear the cache (also in the toolbar). Cloudflare’s copy is cleared too when it’s connected. After clearing, your main pages are refilled in the background, a few at a time. Turn on “A separate copy for phones” only if your theme sends phones different HTML.
If WP Rocket, W3 Total Cache or another cache plugin is active, Arva SEO leaves page caching to it. If your host caches pages itself (SiteGround, LiteSpeed Cache, WP Engine, Kinsta, Cloudways), that’s kept by default, and you can choose Arva SEO’s instead; the card says how to turn the host’s cache off. Turning it off, deactivating or deleting the plugin removes the rules, the file, the line it added and the saved pages.
Is Browser caching and compression safe?
The rules only use standard Apache settings, wrapped so a server without those modules ignores them. Still, a server that doesn’t allow one of them in .htaccess would answer every page with an error, so the plugin checks your homepage and one of its own files from the server right after adding them, and takes them out again in the same moment if either doesn’t answer normally, or if the check can’t be made. Turning the fix off, deactivating or deleting the plugin, or the wp-config.php switch removes them.
Do the PageSpeed fixes need an Arva SEO account?
No. They work as soon as the plugin is active. Connecting adds which fixes your homepage’s latest PageSpeed test asks for, and before-and-after results in Arva SEO.
Which SEO plugins are supported?
Updates from Arva SEO are written to Yoast SEO and Rank Math. The connector detects which one is active; if both are, choose one in Arva SEO → Settings. Without either, those updates aren’t written. If none of Yoast SEO, Rank Math, All in One SEO, SEOPress or The SEO Framework is active, you can turn on this plugin’s own SEO title and description boxes in Arva SEO → SEO; they are stored on your site and are not shared with Arva SEO.
Can a title or description change be undone?
Yes. The connector sends Arva SEO the previous values with every change, and Undo in Arva SEO writes them back (an empty previous value restores the SEO plugin’s default).
Does the redirect manager use .htaccess?
No. Redirects run inside WordPress, early on the front end, and never in the dashboard, REST requests, AJAX, scheduled tasks or when an administrator previews. Turn “Use redirects” off, delete a rule, or add define( 'ARVASEO_CONNECTOR_DISABLE_REDIRECTS', true ); to wp-config.php to stop them at once; that line also stops the broken-address log.
What does the broken-address log keep?
Only the path of a missing page (without the part after a question mark), how many times it was asked for, and the first and last time. No IP addresses, browsers, referring pages, cookies or user IDs, and nothing is sent anywhere. At most 1,000 addresses are kept; the one not asked for the longest goes first. “Clear the list” empties it.
Can a redirect send visitors to another website?
Only to a full http:// or https:// address that an administrator types in. The address is checked when it is saved and again when it is used; addresses with a user name, spaces, backslashes or other schemes are refused.
What if I disconnect?
Credentials are removed from this site and revoked at Arva SEO, scheduled syncs stop, and earlier findings are shown as stale.
Is it free?
The connector works with every Arva SEO plan, including Free.
What happens when I delete the plugin?
Credentials are always revoked and removed. Settings, logs, delivery records, the broken-address log, redirects, SEO titles and descriptions and the files the PageSpeed fixes made are removed too if you ticked that option in Settings; the plugin clears the caches it can reach first, and the files stay if a cache it can’t clear may still show pages that use them. Posts are never deleted.
Screenshots







Changelog
2.19.0
- New: backups, off until you switch them on in Settings → Backups. Once a week the plugin copies the database and the wp-content folder (uploads, themes and plugins) to Arva SEO’s servers, up to 2 GB. Only the latest weekly copy is kept, and it is replaced only after the new one has arrived complete. Daily backups (the last 7 are kept) come with Arva SEO’s Professional and Business plans, or from a top-up. It needs this site to be connected to Arva SEO.
- New: restore. In Settings → Backups, an administrator picks a backup and confirms. The plugin saves a copy of the current database first, then restores the database and the files. It keeps this plugin and its connection to Arva SEO as they were, never changes files that are not in the backup, refuses a backup made for another website address, and puts the database back if the restore fails part-way. The safety copy is removed after 7 days.
- Backups are made in small steps in the background, so they work on shared hosting. The parts are kept in a private folder under wp-content until they are sent, then deleted. Uninstalling the plugin removes every backup folder.
- Nothing is switched on, off or changed on your website by this update.
2.18.0
- New: an Arva SEO box on the WordPress Dashboard for administrators. It lists up to three things that need you (security problems, speed updates waiting for your check, content that couldn’t be added) and messages from Arva SEO when this site is connected. It reads from Arva SEO once in a while in the background, never while the Dashboard loads. New installs have it on; sites that update keep it off until you turn it on in Settings → Dashboard box. Anyone can hide it with Screen Options, and product news can be hidden one message at a time.
- New: one-click login from Arva SEO, off until you switch it on in Settings → Log in from Arva SEO. It logs in as the administrator who connected the site, only for owners and admins of the Arva SEO workspace. Each login link works once and expires after a minute, and Arva SEO never sees a WordPress password. Every login is listed in Activity.
- Nothing is switched on, off or changed on your website by this update.
2.17.0
- New: one-click login from Arva SEO, off until you switch it on in Settings → Log in from Arva SEO. It logs in as the administrator who connected the site, only for owners and admins of the Arva SEO workspace. Each login link works once and expires after a minute, and Arva SEO never sees a WordPress password. Every login is listed in Activity.
- If that administrator is removed or is no longer an administrator, the button stops working.
- Nothing is switched on, off or changed on your website by this update.
2.16.1
- The SEO checklist now has room on every side of each check, instead of text touching the border.
- On the Content from Arva SEO screen, “Check for content now”, “Change in Settings” and “Allow in Settings” now look like buttons, so they are easy to see.
- Nothing is switched on, off or changed on your website by this update.
2.16.0
- Easier to move around: the eight tabs are now five (Home, Speed, SEO, Health, Settings). Content from Arva SEO sits under Home, Redirects under SEO, and Activity under Settings, each reached from a small second row. Every page keeps its address, so existing links and bookmarks still work.
- New “Find a fix” box on the Speed screen: type a word to see the matching fixes from every section at once.
- Screens use wide displays better (up to 1,480 px instead of 1,180 px).
- The review request and the “fixes changed” notice now appear only on Home instead of on every screen.
- Pages that don’t exist (the made-up addresses scanners and bots try all day) are no longer sent to Arva SEO for optimized CSS, which saved renders and page optimizations.
- Nothing is switched on, off or changed on your website by this update.
2.15.0
- New Arva SEO → SEO screen: ten plain-language checks (HTTPS, search engines allowed, permalinks, site title, home page title, meta description, noindex, sitemap, robots.txt, image alt text) made on your site with one request to your own home page. No account, nothing sent, nothing changed.
- New Arva SEO → Redirects screen, off by default: an optional log of broken addresses (path, count, first and last seen; no IP addresses, browsers, referrers, cookies or users; at most 1,000) and exact-path 301/302 redirects (at most 500, loops and long chains refused, administrators only, CSV export). Not written to .htaccess; ARVASEO_CONNECTOR_DISABLE_REDIRECTS in wp-config.php turns it off.
- New, off by default and only when no SEO plugin is active: SEO title and meta description boxes for posts, pages and products, and home page fields, stored on your site.
- A request for a WordPress.org review appears once, only on this plugin’s own screens and only after a finished security scan or a speed fix that has been on for a week. “Maybe later” hides it for 30 days; “No thanks / I already did” hides it for good. Nothing is tracked or sent.
- New readme: a clearer description and tags for page caching, WebP and image compression, the security scanner, Core Web Vitals and SEO.
- Two small database tables are added for the log and the redirects; they are removed with the plugin’s other data if you chose that in Settings.
2.14.0
- Page caching looks at the homepage twice before it writes anything. When your host, a caching plugin or Cloudflare already answers it, Page caching is refused with wp-config.php, .htaccess and the drop-in untouched.
- After Page caching is taken out, the Activity log says so if the WP_CACHE line it added is still in wp-config.php. A refusal is now explained in a plain sentence instead of a generic line.
- New Website Health check: the homepage is read as visitors get it, and a homepage running without its optimized CSS is reported when the styles fixes are on. A homepage you left alone is not flagged, and a page that can’t be read is reported as unknown.
- New Website Health check: Cloudflare in front of the site without Arva SEO connected to clear it is reported, with the steps to connect it.
2.13.0
- Supported local caches clear before Cloudflare. A new public homepage check observes the current Arva SEO generation separately from purge requests; it does not guarantee every CDN location is current.
- A separate reviewed trial can delay directly embedded LeadConnector chat loaders until interaction. It starts off; consent-managed and unsupported scripts stay unchanged. Check navigation, gallery, testimonials, forms, consent and chat before enabling for visitors.
2.12.1
- CSS sample selection: traversal-like URLs, including encoded query values, are excluded from automatic and manual optimization requests. Existing entries remain as non-actionable diagnostics; ordinary query pages remain supported.
- Keep the latest PageSpeed result visible above the Speed tabs, with better spacing around admin notifications.
- Clearer PageSpeed device choices, comparison mode, allowance and saved result history, with a separate no-cost refresh action.
- Combining leaves stylesheets without a safe matching CSS result in place, so neighboring styles can still use their ready Critical or Unused CSS. Preview the homepage, navigation, gallery and testimonials before using this update for visitors.
- Show Elementor background lazy-loading status and safety guidance without changing builder settings or adding a second loader.
- Clarify original-source CSS generation and source-order bundle assembly.
2.12.0
- Optimized styles are now worked out for each original stylesheet and assembled for combined files. Until you choose, changed stylesheets keep their original styles. One upgrade render per page is free.
- Speed fixes now recognize verified files whose addresses change on every visit. The one-time CSS conversion is free; later content changes follow the normal page optimization allowance.
- While new optimized styles are worked out, pages keep earlier results for stylesheets that did not change. Regenerate keeps the files cached pages use.
- The updated renderer keeps entrance animations across stylesheets and reports first-screen animation waits. Eligible existing results can be refreshed for free.
- New optional HTML minification starts off. It preserves text spacing and protected blocks. Additional HTML comments can be kept in Exclusions.
- The Health page now shows database cleanup counts and WordPress-only maintenance controls. Cleanup requires your choice; weekly cleanup starts off. Existing speed settings stay in effect.
- CSS delivery now records the last check, reports failed readiness messages and pauses repeated source changes locally. Current CSS files are retained during refresh, and cache recovery checks are bounded.
2.11.3
- Improved: Speed settings are organized into CSS and page styling, JavaScript and interactions, Images and media, Fonts, Caching and delivery, Testing and diagnostics, and Exclusions and advanced subtabs.
- Improved: Keyboard navigation, remembered sections, browser history and direct links to existing fixes work across subtabs. Switching sections preserves unsaved form entries.
- Improved: Phones use a compact section chooser. Filters count only the current section and explain when no fixes match. All original controls remain available when scripts or session storage are unavailable.
- Existing optimization choices, quotas, safeguards and visitor output are unchanged.
2.11.2
- New: Run mobile and desktop PageSpeed tests inside WordPress, with one or three runs, visible allowance, saved results and score ranges. Refreshing results never starts a paid test.
- Fix: The Deferred preview list records emitted defer attributes after WordPress resolves dependencies, instead of reporting rejected strategy requests as deferred. Existing jQuery, consent and footer protections remain.
- Improved: CSS, JavaScript, images and fonts have their own groups. CSS progress identifies waiting pages and change-protection pauses; one-page recovery fetches an existing result free or explicitly requests one render without clearing other results.
- Improved: Image progress distinguishes cloud savings, local WebP processing and files checked without a saving. Arva SEO server updates bound slow compression tools and preserve originals.
- New: Shared Critical CSS and Unused CSS quota panel with used/remaining allowance, reset date, stale/exhausted warnings and a read-only refresh. Existing plan limits and CSS generation behavior are unchanged.
- New: Private, administrator-requested CSS and JavaScript inspection with duplicate, delivery, bundle-member and conservative syntax diagnostics.
- Optional separate JavaScript exclusions and reviewed AMD, body CSS and jQuery Migrate trials. Existing settings stay in effect. Trials start off and require a matching signed-in preview plus interaction checks before visitors receive them. Changed exclusion policies return the affected fix to Trying.
- New: Review individual jQuery UMD files for standalone minification, small body stylesheets for full-CSS inlining in place, or jQuery Migrate removal when no queued dependency needs it.
- Safety: Trials start off, require a matching preview and acknowledged checks, keep explicit dependencies, and fall back to original files when source bytes change. Persistent admin warnings explain compatibility risks.
- Preserved: jQuery loading order, consent, integrity, module and unsupported AMD safeguards.
2.11.1
- Fix: Run a new test in Arva SEO opens PageSpeed for the connected website.
- Improved: the latest test’s recommended fixes use the same groups as the fixes below; each status stays beside its fix.
- Fix: Leave scripts alone lists supported scripts in Delayed mode as well as Deferred mode. The list refreshes when you return from the homepage and while the settings tab is visible, without losing unsaved exclusions.
- Improved: the script list distinguishes no supported scripts from a homepage that has not been visited while trying the fix.
2.11.0
- New: updates that change how a fix you use works no longer reach your visitors silently. Visitors keep the version you checked; you see the new one while signed in, and an “Update to check” card on Speed lets you “Use it for visitors”, “Keep the previous version” or “Turn the fix off”. A toolbar item and one notice count them. The earlier version is kept at least 90 days, with a reminder before it is retired.
- New: updating from 2.10.0 keeps what you approved: fixes that are on keep 2.10.0’s Load styles faster, Remove unused CSS and Combine behaviour until you use the update, and choices you had not saved keep the defaults they had. Sites that already ran an earlier 2.10 build keep what it did.
- New: Arva SEO and the AI connector can press “Use it for visitors” where you allow switching fixes remotely (never for Defer scripts). The site’s details sent to Arva SEO say which update notes applied (their ids and dates) and where each update stands (waiting, kept or used).
- Listed under What changed on Speed, for the fixes you use (an update waits for your check only while its fix is on):
- Update to check: With Combine CSS on, optimized styles are now worked out from the combined files your visitors get. Each page type is worked out once again, free.
- Update to check: Optimized styles now also reach stylesheets whose names use capital letters (Elementor’s entrance animations, some Google Fonts) and stylesheets a theme prints more than once, so fewer of them hold the page up.
- Update to check: Files next to one that can’t be combined are now combined around it, in the same order. This applies to stylesheets and scripts.
- Option: New option under Defer scripts: Move jQuery down the page. It’s off until you turn it on.
- Option: New option under Load styles faster: Load icon fonts after the page. It’s off until you turn it on.
- Notice: Arva SEO’s renderer now gets your pages without the WordPress extras you removed, as visitors do.
- Notice: Entrance animations no longer play a second time when the rest of the styles arrive.
- Notice: Old generated files (unused for a week, Google Fonts copies for 30 days) are cleaned up once enough have piled up or a folder is nearly full: the caches are cleared first and the files deleted a day later, never while another cache may still use them. While a cache Arva SEO can’t clear may keep pages, the folders may grow to twice their usual limit.
- Notice: Caches are cleared when compression changes an image.
- Notice: Visitors arriving from Google Ads, Facebook, Mailchimp and similar links get the saved page too.
- Notice: Arva SEO now clears more caches when your pages change, at most every 15 minutes: WP Rocket, W3 Total Cache, WP Super Cache, WP Fastest Cache, Cache Enabler, Hummingbird, Comet Cache, Nginx Helper, WP-Optimize, NitroPack, Proxy Cache Purge, Cloudflare’s official plugin and LiteSpeed’s server cache.
- New: Other caches on this site (Speed). Once a day Arva SEO asks your own homepage for its cache headers, and with your plugins and host it finds the caches in front of your site. It clears those it can and lists those that are yours, with how. “Clear every cache now” is there and in the toolbar; “I’ve cleared it” tells Arva SEO you cleared one of yours. The site’s details sent to Arva SEO name them and how to clear yours (never a page or a visitor).
- New: Hostinger’s CDN, Kinsta, Cloudways’ Varnish, Pantheon, SpinupWP and a few cache plugins are listed as yours to clear, with how.
- Changed: other caches are cleared only for changes visitors see that Arva SEO makes, at most every 15 minutes. Theme, menu and widget changes are left to the cache plugins; saving choices you didn’t change clears nothing.
- Changed: under a cache Arva SEO can’t clear, only files unused for 90 days go, until you press “I’ve cleared it”. Optimized CSS copies are cleaned up too. Cloudflare holds this back only when it keeps your pages and isn’t connected. Deleting the plugin with its data clears the caches it can reach first and keeps the files while one it can’t may still show pages.
- Changed: the list of tracking parameters Page caching ignores is longer (gad_source, hsa_*, mtm_* and more; ref stays), and optimized CSS is noted under the same address. Developers add more with the arvaseo_connector_page_cache_ignored_params filter.
- Changed: with more than 300 page types, the ones seen longest ago lose their optimized CSS first. Results saved by a newer version are kept and not used.
- Fixed: deactivating or deleting the plugin leaves no scheduled job behind.
2.10.8
- Fixed: optimized CSS (Load styles faster and Remove unused CSS) lost rules on some themes, because it was saved with everything from a “<” to the next “>” taken out (since 1.6.0; 2.10.0.1 fixed it for 2.10.0). Media queries written as (width<=1023.98px), which many themes use for their phone menu and header, icons drawn with SVG in data: addresses (menu arrows, form icons) and content:”<” lost their rules, sometimes with the rest of the stylesheet. Optimized CSS is now kept exactly as Arva SEO worked it out; a stylesheet whose CSS contains “</style” or a NUL byte loads as it is.
- Fixed: optimized CSS saved by earlier versions is downloaded again after updating, at no cost and without using page optimizations, at most 10 page types each run, also while both CSS fixes are off. Until then, and when Arva SEO no longer has a page type’s results, it keeps its current CSS. A page type no longer tracked (on sites with more than 300) is downloaded again when a page uses its CSS. A download that brings the same CSS no longer clears page caches.
- Fixed: after a Google Fonts copy failed, downloads already waiting for the same stylesheet tried again that day instead of waiting a day.
2.10.7
- Fixed: on a site with more than 300 page types (an Elementor site with many pages, each with its own stylesheet, or “Generate CSS per URL”), 2.10.3 to 2.10.6 deleted the optimized CSS of the page types noted longest ago, even while pages used them; those pages then lost their optimized CSS, were sent again and pushed out the next ones, over and over, each time using a page optimization. Page types now make room by their last use, and their CSS is kept until no page has used it for 30 days.
- Fixed: optimized CSS that finished while visitors’ pages noted new page types could lose those page types, which then waited until the next uncached visit. A page type marked ready whose CSS file is gone (a host’s clean-up, a migration) is asked for again instead of waiting for good, and CSS files are written in one step.
- Fixed: since 2.10.5, every background change (each compressed image, each Google Fonts copy, each batch of optimized CSS) emptied the whole page cache of WP Rocket, W3 Total Cache, WP Super Cache and the other cache plugins Arva SEO can clear, with their refills. Background changes now clear those caches and the host’s at most once every five minutes, and once more at the end; a change you make clears them straight away.
- Fixed: Page caching refilled 5 pages per background run, and runs only happen when WordPress makes a page, so on a quiet site cleared pages (and their optimized CSS) could wait hours. A run now refills for up to 10 seconds, and pages queued or cleared again during a run are no longer lost.
- Fixed: “Move jQuery down the page” no longer moves it past scripts a consent tool holds back (type=”text/plain”, as Complianz, CookieYes, Cookiebot and others use) that may use jQuery once they’re allowed, or past an external script before it that may add scripts (a consent tool or tag manager from another site, or a site file that adds scripts).
- Changed: when the full stylesheets arrive, only animations whose keyframes came with that stylesheet end at once, and the stylesheets in use are read once instead of at each arrival.
2.10.6
- Fixed: with Load styles faster or Remove unused CSS, an entrance animation that a page’s scripts start as content comes into view (Elementor’s fadeInUp, for one) had no keyframes in the used CSS, so the element appeared without it; then, when the full stylesheets arrived at the visitor’s first scroll, tap or key press, every such animation already on screen played again over content the visitor was reading. Animations that start only because the full styles arrived now end at once; endless animations (spinners) and those already running are left alone. Arva SEO’s servers will also keep these animations in the used CSS.
- Fixed: a background run that fetches optimized CSS and was cut short (a slow download past PHP’s time limit) left the page types it was working on waiting until a page that wasn’t in the page cache was visited, while every visitor got the cached pages without optimized CSS. The next run is now scheduled before the downloads start.
2.10.5
- Changed: moving jQuery out of the head (2.10.3) is now a choice of its own under Defer scripts, “Move jQuery down the page”, off until an administrator turns it on. Updating no longer changes what Defer scripts does on sites where it was already checked and on, and turning the choice on returns Defer scripts to preview until the pages are checked again.
- Fixed: with jQuery moved down, an async script or an inline loader before it in the head (Google Tag Manager’s snippet, whose Custom HTML tags often call jQuery) could run before jQuery and fail with “jQuery is not defined”. jQuery now stays in the head when anything before it may run at a time of its own and use it: an async script, an inline script that adds scripts or mentions jQuery, or an event handler that mentions it. Google’s gtag.js doesn’t count; developers can name others with the arvaseo_connector_script_without_jquery filter.
- Changed: loading icon fonts after the page (2.10.4) is now a choice under Load styles faster and Remove unused CSS, “Load icon fonts after the page”, off until an administrator turns it on, because those icons show a moment later and text next to them can move.
- Fixed: the clean-up of full minified and combined folders (2.10.3) deleted files that pages saved by another cache could still use: WP Super Cache, Cache Enabler, WP Fastest Cache, W3 Total Cache and similar kept serving pages pointing at deleted files until they expired. Those with a documented API (WP Super Cache, W3 Total Cache, WP Rocket, WP Fastest Cache, Cache Enabler, Hummingbird, Comet Cache, Nginx Helper) are now cleared with Arva SEO’s own when every page changes; while any other page cache may keep pages (another cache plugin or advanced-cache.php, Kinsta’s or Cloudways’ server cache, SiteGround’s without its plugin, Cloudflare without the connection) nothing is deleted. Files are kept for a week after their last use instead of a day.
- Fixed: Combine CSS left a whole run of adjacent stylesheets uncombined when one of them couldn’t be combined (WordPress’s block library starts with an @import), while Arva SEO’s renderer got a bundle for the files around it, so the stored optimized CSS matched none of them and they stayed render-blocking on posts. The others are now combined around it, in order.
- Fixed: with Combine CSS on, Arva SEO’s renderer got WordPress’s emoji styles and the other extras that “Remove unused WordPress extras” takes out for visitors, which split its stylesheets differently from visitors’ pages. The renderer now gets the same page.
- Fixed: Faster Google Fonts, “Serve them from your site”, scheduled a download with the full address, cache busters included, so until the first copy was ready a theme adding v=time() scheduled another download on every uncached page view, and each one copied the fonts again and cleared the page caches. One download is scheduled, and a copy that exists is never made again. Copies no page used for 30 days, such as those earlier versions made for each page view, are deleted in the daily maintenance.
2.10.4
- Improved: Load styles faster (and Remove unused CSS) left icon font stylesheets that a theme or widget prints into the page itself, outside WordPress’s styles, holding the page up: Solace Extra’s menu, for example, prints Font Awesome from a CDN for every menu item with a sub-menu, so scripts after it waited for it and its 114 KB font loaded with the first paint. Known icon libraries (Font Awesome, Line Awesome, Bootstrap Icons, Remix Icon, Boxicons, Ionicons, Material Icons and Symbols, Themify, Simple Line Icons) now load once the page has loaded, or at the first interaction if that’s sooner, with a noscript copy. Stylesheets from WordPress’s queue keep the used-CSS delivery; developers can decide per stylesheet with the arvaseo_connector_late_icon_style filter.
- Fixed: Faster Google Fonts, “Serve them from your site”, named each copy after the full address, so a theme that adds v=time() to its Google Fonts addresses (Solace does) got a new copy on every page view: the copy was never used, a new download was scheduled each time, and each finished copy cleared the page caches again. Cache busters (v, ver) no longer name copies; existing copies keep their names.
- Fixed: css2 Google Fonts addresses naming several families shared a copy with an address naming only their last family, because repeated family= parameters were collapsed. They now get their own copy.
2.10.3
- Fixed: optimized (used/critical) CSS never applied to stylesheets whose handles contain capital letters, such as Elementor’s e-animation-fadeInUp or a theme’s google-fonts-Inter: their ids were stored in lower case and rejected when combining. They stayed render-blocking. Results saved by earlier versions are matched too.
- Fixed: a stylesheet printed under several handles (a theme’s heading fonts, h1 to h6) only had optimized CSS for the first one, because the renderer keeps one result per address; the others stayed render-blocking. Each copy now uses that result in its own place.
- Fixed: minified copies and combined bundles were named after a script’s full address, so a theme that versions scripts with the time made a new copy on every page view, filling the 250-file folders within hours. Full folders then stopped minifying and combining changed files for good. Cache busters no longer name copies; files record when pages last used them; a full folder now schedules a background clean-up of files no page used for a day, followed by a refresh of saved pages.
- Fixed: a page type waiting for optimized CSS whose scheduled sync was lost waited forever; its next visit schedules it again. Results of page types no longer tracked are deleted (daily and when the list is trimmed) instead of filling uploads.
- Improved: Defer scripts moves WordPress’s jQuery (jquery-core, jquery-migrate and their inline parts) from the head to just before the first script, inline event handler or asynchronous script of the page, so it no longer blocks the first paint. Nothing moves when something in the head may use it; developers can veto with the arvaseo_connector_move_head_scripts filter.
2.10.1
- Fixed: successful image compression now notifies page and connected CDN caches, including when a larger WebP sidecar is removed. Images that do not change do not trigger a purge.
2.10.0
- New: inline CSS/JavaScript minification and explicitly approved static inline/external sources in compatible ordered bundles; external files are cached in bounded pinned background requests, never fetched while rendering pages.
- New: inline or cached-file UCSS, per-URL CSS generation, inline/external asynchronous CSS loader and supported font-display swap.
- New: deferred/delayed JavaScript loading choice under the existing script control; changing the public mode returns it to preview.
- Improved: existing-image compression is visible directly on the Speed card and available as a native Media Library bulk action, with queue/compression/savings status. Added lossless local WebP compression while retaining originals and cloud consent/allowances.
- Kept: default-off new switches, existing settings, exclusions, optimized-CSS delivery, source files and unsupported-resource fallback.
2.9.0
- New: separate opt-in Combine CSS and Combine JavaScript controls with administrator-only Try mode and existing file/page exclusions.
- Compatible neighboring local files share a cached bundle in their existing order. CSS image and font URLs are preserved; unsupported, inline, asynchronous, module and optimized-CSS delivery stays separate.
- Combining is separate from minification. Original files are untouched, failed or unsupported groups retain their original delivery, and both controls start off.
2.8.1
- Fixed: large completed CSS results no longer exceed the connector’s normal response limit when fetched together. CSS results download individually with a bounded CSS-only response allowance; other API calls retain their existing limit.
- Result checks prioritize recently requested page types and process a bounded number per run, so large old backlogs continue in the background without delaying current pages indefinitely.
- Fixed: uninstall finishes speed cleanup before removing its logs and options, avoiding writes to already-removed tables.
2.8.0
- New: Minify CSS and Minify JavaScript serve smaller cached copies of supported local files, preserve original files and loading order, and fall back to originals for unsupported or unsafe files. Both start off and respect existing exclusions and other optimizers.
- New: DNS prefetch and Preconnect for explicitly chosen external HTTPS origins, with limits, duplicate prevention and optional anonymous preconnect for fonts or CORS resources. These start off and do not change DNS records.
- Fixed: themes adding a changing v/ver timestamp to Google Fonts no longer make unchanged styles a new CSS optimization on every request. Font family, subset, display and text choices still distinguish different CSS.
- Updating refreshes cached pages once when speed fixes are on, so HTML from the previous version …
