Dirigible Optimize changelog

0.0.67 2026-10-24

Removed

• reCAPTCHA on demand is gone. It was off on every site (only Dirigible support could turn it on, and no site had it on), so forms using reCAPTCHA work exactly as before, and Google's reCAPTCHA v3 script loads as the Gravity Forms reCAPTCHA add-on sets it up. One spam check per form (reCAPTCHA stepping aside on forms Turnstile protects) is unchanged, and the old help page now leads there.

0.0.66 2026-10-24

Fixed

• When the server stopped partway through compressing or resizing an upload (an error, or a request that ran too long), a working copy could be left beside it, named like "photo-ds-compressing.jpg". Optimize now deletes those leftovers once they're an hour old, a few folders at a time while its compression jobs run in the background (Compress older images, imports, PDFs), never while someone is viewing a page. Uploads, their sizes, and any file the Media Library actually uses are never touched.
• PDF compression: Ghostscript now stops on its own after about three minutes of work, even when the server ends the background job that started it, so a PDF Ghostscript can't finish no longer keeps the server busy.

0.0.65 2026-10-24

Fixed

• Compress older images now leaves alone images that Smush, Imagify or ShortPixel already compressed, even after that plugin is gone, instead of compressing them again and lowering their quality. Imported images those plugins compressed on another site are left alone too, and the Media Library's Savings column shows what the plugin saved on them.

0.0.64 2026-10-22

Changed

• Fewer files to wait for on pages with large blocks. WordPress puts each block's styles inside the page only up to 40 KB in total, and sends the rest as separate files that the page waits for before it appears; those are the largest ones, usually Cover, Gallery, Navigation or Social Icons. Now they come inside the page too, up to 100 KB, for WordPress's own blocks and Dirigible's; other plugins' styles load as before. Where Cover's styles were a separate file, the page now makes one request fewer before it appears and is about 1.5 KB larger compressed. Pages look exactly the same, and pages whose styles already fit don't change at all. Developers can turn it off by returning 0 from the dirigible_optimize_inline_block_css filter.

0.0.63 2026-10-22

Added

• Dirigible Analytics: Outbound links and Events now open up for detail. Click a site or event to see where those visitors came from (for example "Social: instagram.com", "Campaigns: QR code", "Direct"), which pages they clicked on, and, for links to other sites, the exact addresses they went to (without anything after a ? or #). On a Dirigible Music link page, that's "Spotify, 38 clicks: 22 from Instagram, 9 from the QR code". Export CSV has all three. It covers clicks from the update on (pages the host already has cached start once their cache refreshes); older clicks still count but have no details.
• Dirigible Analytics: so that a click on the second or third page of a visit still knows where the visit came from, the browser keeps the visit's source (ds_avs, no personal data) once cookies are allowed: straight away on sites without the cookie banner, after Accept on sites with it. Before Accept, clicks on later pages show as "Not known", and nothing is stored. Decline removes it with the other Analytics data. The script grows by about 150 bytes compressed.

0.0.62 2026-10-22

Added

• Dirigible Analytics: other Dirigible plugins can now count clicks on their own buttons and links (Dirigible Music's listening links, for example). They show in a new Events table under Leads when the period has any, and a click on a link to another site still counts under Outbound links too. Same cookie-banner, Do Not Track and once-per-page-view rules as every other click.

0.0.61 2026-10-21

Security

• Dirigible Analytics: visitors without the cookie now add at most four anonymous codes per page-view batch (the visitor and up to three pages) and at most 200,000 a day, so a script faking visitors can no longer fill the site's database. Past the daily limit, the rest of that day's visitors without the cookie still count as page views and visits, but not as visitors. Yesterday's codes are now deleted in small batches (the rest by the daily clean-up), so no visitor's request waits on a large delete. Normal traffic counts exactly as before.
• On WooCommerce sites still running Dirigible People older than 4.0.20 or Dirigible Events older than 4.1.43, logged-out visitors now get "access restricted" from those plugins' REST routes (/wp-json/wp/v2/people, /wp-json/wp/v2/events), which in those versions showed contact phone numbers, emails and addresses. Before, the forced REST lock for those versions skipped WooCommerce sites entirely. The rest of REST, including the cart and checkout, stays open.

0.0.60 2026-10-21

Fixed

• Google Maps embeds anywhere on the site (Map blocks, Custom HTML, location pages, footers) now have a name for screen readers ("Map") when the pasted code has none, so they're no longer announced as just "frame". Embeds with their own title keep it, and Dirigible Locations names its maps after the location.

0.0.59 2026-10-21

Changed

• Matterport 3D tours now show a preview picture of the tour with a View 3D tour button, and the tour loads when a visitor presses it. Pages with a tour load faster (a tour pulls 1–2 MB before anyone looks at it) and score higher on PageSpeed. The box keeps the tour's size, so nothing moves. Developers can turn it off with the dirigible_optimize_matterport_facade filter.

0.0.58 2026-10-21

Changed

• The site report's server tools check also says whether the server can draw SVG images (with CSS styles), so we know which sites can get a generated share image from an SVG logo. Nothing changes on the site.

0.0.57 2026-10-20

Changed

• Hovering over the Analytics chart now shows that day's page views and visits right away, plus the earlier period's visits when there's a comparison. The whole day's column counts, so quiet days with short or no bars are easy to hover, and a tap shows them on a phone. Before, only the bar itself had a tooltip, it took a moment to appear, and it didn't work on phones.
• Bounce rate on the Analytics page now explains why Google Analytics shows a lower one: Google doesn't count a one-page visit that lasts 10 seconds or more as a bounce, while Dirigible counts every one-page visit.

0.0.56 2026-10-15

Changed

• The Dashboard's Analytics tile now counts full days only: Visitors, Page views and the top page cover the last 7 full days, and the Page views, 30 days graph ends yesterday. Today is still counting, so including it made traffic always look down, with the graph dipping at the end. A Today so far chip shows today's page views on their own.

0.0.55 2026-10-14

Changed

• The Analytics menu icon is now WordPress's own pie chart icon, so it matches the other admin menu icons.

0.0.54 2026-10-14

Changed

• The Analytics menu icon in wp-admin is now a solid pie chart, which can't be mistaken for a trend in the site's own numbers.

0.0.53 2026-10-14

Changed

• The Analytics menu icon in wp-admin shows a steadily rising line. The old chart icon dipped in the middle, and some clients took it for their own visit numbers.

0.0.52 2026-10-13

Added

• After WordPress, the theme or a plugin updates, Optimize loads the home page once, about a minute and a half later, so the first visitor usually gets the fast cached page instead of waiting for the site to build it. Updates clear the host's cache, and with near-daily releases the first visit after one was often noticeably slower. Several updates in a row get one visit, and Optimize's own updates count too.
• The daily PageSpeed test loads the page once just before Google tests it, so Google usually tests the cached page visitors get rather than one an update has just cleared (dirigiblestudio.com scores 70–72 uncached, 98–100 cached). A test that found the page uncached says so on the chart.

Changed

• Dirigible Analytics sends nothing more from a page once the visitor withdraws consent (Decline after accepting, from the theme's Cookie settings link, Dirigible theme 5.31.137+). Before, that page's view still went out, counted with consent, while the page reloaded.

0.0.51 2026-10-12

Added

• Before someone activates an image plugin that Dirigible already covers (Smush, Imagify, ShortPixel, Optimole, WebP Express or Converter for Media), the Plugins screen asks first and says what changes while it's active, with a link to the Images docs. Activated another way, it gets a one-time notice instead. Needs the Dirigible theme release that adds this warning; with an older theme nothing changes.

Changed

• While Smush, Imagify, ShortPixel Image Optimizer, Optimole or ShortPixel Adaptive Images is active, Optimize leaves image compression to it so nothing is compressed twice: new uploads are compressed by that plugin only, the Savings column and Compress older images are hidden until it's deactivated, and the Images card says why. Optimize still shrinks very large uploads and saves PNGs as JPGs. PDF compression keeps working too, except beside Imagify and ShortPixel Image Optimizer, which compress PDFs themselves. Optimize never deactivates these plugins.

0.0.50 2026-10-10

Changed

• On shop sites with the header cart, the cart panel's styles (about 140 KB, 13 KB compressed) are no longer downloaded with the page: they load a few seconds after the page has finished loading, or as soon as a visitor points at, taps or tabs to the cart. Until 0.0.49 they still downloaded alongside the page's own styles and images, which PageSpeed's lab test counts. The cart button looks the same, and a panel opened before its styles arrive stays blank until they do, with keyboard focus moving into it once its contents show.
• The site report and the Shop Cart card say whether the cart change is actually in effect, or exactly why not (header cart off, WordPress, WooCommerce or theme too old, WooCommerce changed, not checked yet).

Fixed

• If WooCommerce's files can't be read for the cart check (for example mid-update), Optimize tries again within the hour instead of keeping WooCommerce's loading until the next WooCommerce update.

0.0.49 2026-10-10

Added

• Shop Cart card on Optimize Settings (WooCommerce sites). Load the cart panel's styles with the page puts WooCommerce's own loading of the header cart panel's styles back, for example to rule it out when the cart looks wrong. The card also says when the header cart is off, or when a WooCommerce update means the change isn't in effect.

Fixed

• On shop sites with the header cart, the cart panel's styles (about 140 KB, 13 KB compressed) load after the page appears again. Since WooCommerce 11.2 they had been holding up every page, because Optimize only ran this on WooCommerce 11.1. It now checks WooCommerce's files after each WooCommerce update instead, so later updates keep it working unless they change what it relies on.

Changed

• A cart panel opened before its styles have loaded (in the first moment, on a very slow connection) now slides in blank and shows its contents once the styles arrive, instead of showing them unstyled.

0.0.48 2026-10-09

Changed

• Attachment pages are off on every site. Sites set up before WordPress 6.4 still gave each upload an indexable page of its own; now its address goes straight to the file, as on newer sites. Image blocks and galleries made since WordPress 5.9 that are set to Link to: Attachment page open in the lightbox instead; older galleries, Media & Text blocks and SVG images link to the file.
• Uploads no longer take page names: a new page gets the address it asks for even when an upload already has that name (before, uploading "about.jpg" first made a new About page /about-2/). Existing pages keep their addresses.
• Images that arrive without an upload (an import, sample data, an image URL added in the editor, a feed, WP-CLI) are compressed a few minutes later in the background, the same way as uploads, so imports no longer stay full size. They keep their format and size; only uploads are resized and converted to JPG. The Images card says how many are waiting.
• After Compress older images, the card's count of images still to do no longer calls them newly added: it says they haven't been checked yet.

0.0.47 2026-10-09

Changed

• The previous image optimization plugin is deactivated as soon as Optimize takes over, instead of after its leftover WebP copies are removed: on sites where pages pointed at those copies, that wait was a month. Its WebP and lazy load were already off, and the copies (and later the plugin) are still only removed once cached pages have expired, so nothing on the site changes. It's also deactivated on sites that used its image CDN or had its WebP turned back on (their pages get another 30 days before it's removed), and where the WebP cleanup was skipped. The setting to turn its WebP back on is gone.

0.0.46 2026-10-09

Added

• jQuery card on Optimize Settings. On the public site, pages skip jQuery Migrate and jQuery loads after the page whenever every script that uses it can wait, as the Dirigible theme did until now. Load jQuery Migrate and Don't defer jQuery put WordPress's behaviour back, and Defer other plugins' jQuery scripts too is the theme's old Aggressive Defer.

Changed

• jQuery loading moves here from the Dirigible theme's Customizer → Scripts & Embeds → Performance, so it can be switched off with Optimize's other speed changes. Each site keeps the choice it made in the Customizer, and pages load exactly as before. It takes over once the theme is updated to hand it over; until then the theme keeps handling it and the card doesn't show. With the updated theme, deactivating Optimize turns the jQuery tweaks off (WordPress's own jQuery loading).

0.0.45 2026-10-09

Changed

• Compress older images: the progress on the Images card updates by itself while Optimize Settings is open, and the job moves faster while the page is open. It pauses while the browser tab is hidden and checks less often when the server is busy or low on disk space.
• Compress older images looks at each image only once: images the previous image optimization plugin already compressed are recorded the first time, so a later run skips them straight away. An image that can't be compressed is tried again by later runs, set aside after three tries, and tried again a week later.

0.0.44 2026-10-09

Added

• Media Library list view has a Savings column: how much smaller each upload is than the file that was uploaded, and what was done to it (resized, saved as JPG). Older images the previous image optimization plugin compressed show what it saved (all sizes); compressed PDFs show theirs.
• The Images card on Optimize Settings totals what compression has saved so far (images and PDFs, size before and after).
• A quiet Manage media optimization link beside Add Media File in the Media Library goes to the Images card (administrators only).
• Compress older images on the Images card: compresses the JPG and PNG images already in the Media Library, and all their sizes, the same way as new uploads, in the background with a progress bar. File names, dimensions and addresses don't change, an image that wouldn't get smaller is left as it is, and images the previous image optimization plugin already compressed are skipped. It only runs when an administrator starts it, and it can be stopped and continued.

Changed

• Optimize Settings: the Images, Dirigible Analytics, Public REST API, Language and RSS Feeds, Pingbacks and Trackbacks, Editor, YouTube Videos, Revisions and Daily PageSpeed Score cards list what Optimize does as a checklist, each next to the checkbox that puts WordPress's behaviour back, and each checkbox and radio choice is a card that's highlighted when it's on, drawn the same in every browser.
• Optimize Settings has its own Optimize item in the admin menu, just above Dirigible, instead of sitting under Dirigible → Tools. Old links and bookmarks still open it.
• The Images card is now first on Optimize Settings, and no longer shows the WebP cleanup and previous-plugin status, or the checkbox to turn that plugin's WebP back on. Those still run as before; a site that turned WebP back on keeps it.

Fixed

• PNGs reduced to 256 colours keep their colour profile, so Display P3 screenshots and exports no longer look slightly washed out.
• A file whose name doesn't match its format (a PNG named .jpg, say) is no longer converted when it's compressed.
• Compressing a PDF, or adding new image sizes to older images, no longer strips backslashes from the file's details in the Media Library (such as a caption or credit containing one).

0.0.43 2026-10-08

Changed

• The previous image optimization plugin is removed a week after Optimize deactivates it, and never sooner than 30 days after its WebP and lazy load were switched off, so pages still cached with its scripts keep working. This includes sites where it was already deactivated. Reactivating it keeps it. Its settings stay stored, and media files are never touched. The Images card shows the date. Needs Dirigible theme 5.31.110 or newer; on older themes it stays deactivated until the theme updates.

0.0.42 2026-10-08

Changed

• Optimize now handles image compression on every site: a previous image optimization plugin is deactivated once its leftover WebP copies are cleaned up, including on sites that used a paid API key for it. Uploads are compressed by Optimize from then on. Its settings are kept, so reactivating it brings it back.
• The Images card and the Images docs describe the image cleanup as Optimize's own feature. WebP cleanup lines only appear on sites that had an image optimization plugin.

0.0.41 2026-10-08

Added

• New image sizes reach older images: when a theme or plugin update adds an image size, Optimize adds it to images already in the Media Library in the background. This moved here from the Dirigible theme, and a job already in progress carries on. Deactivating Optimize pauses it. Its status line stays under Tools & Maintenance → Media.

0.0.40 2026-10-08

Fixed

• Upgrade notice: purge the site cache on the Colony blogs to start counting straight away; otherwise counting starts as their pages refresh.
• Dirigible Analytics now counts visits on blogs that live in a folder of a bigger site behind a proxy (the Colony blogs at /blog/). Before, nothing was counted there, and each visit sent a stray request to the main site. Visits from the main site count as visits with the main site as their source, and links to it count as outbound clicks.

0.0.39 2026-10-08

Added

• Revisions card on Optimize Settings: each post keeps its newest 10 revisions (a number set in wp-config is left alone), and Trim existing revisions now removes older ones in the background, keeping every autosave. Lowering the limit and trimming are Administrator-only. This moves here from the Dirigible theme, which drops its own copy in its next release.

Changed

• Trimming waits until the Dirigible theme has updated and finished repairing posts' last-modified dates, which reads older revisions, and says so on the card.

0.0.38 2026-10-08

Added

• Optimize Settings → YouTube Videos: "Load the YouTube player with the page" turns off the Dirigible theme's YouTube click-to-load across the site (events too), to rule it out when a video misbehaves. Off by default; purge the site cache after changing it.

0.0.37 2026-10-08

Added

• A Leads group on the Analytics page shows leads, leads per 100 visits, forms, contact clicks, buttons, goals, outbound links and downloads; all of them are in the CSV export too.
• Analytics counts leads: Gravity Forms submissions, with the source and campaign each came from (spam and administrators' test submissions are skipped), and clicks on phone, email and text-message links (the number or address is never kept).
• Goals without code: give any block the class ds-goal-name (for example ds-goal-quote) under Advanced → Additional CSS class(es). Button blocks are counted automatically by their text.

Changed

• Campaign values that look like an email address, a phone number or a long code (including Google Ads' numeric {campaignid}) aren't stored, so use words in campaign links. The Analytics script is 2.3 KB compressed (was 2.0 KB); cached pages start counting clicks as their cache refreshes.

0.0.36 2026-10-08

Added

• Analytics keeps two years of daily detail and five years of monthly totals. Older date ranges show whole months, and comparisons count both periods the same way.
• On sites with the cookie banner, visitors who haven't accepted cookies (or who declined) are counted once a day by an anonymous code made from their connection and browser, which changes daily and will be deleted. Nothing is stored on their device.

Changed

• Dirigible Analytics is on by default: visitor numbers show under Analytics in the admin menu and on the Dashboard. Sites where "Count visits with Dirigible Analytics" was unchecked stay off. Pages the host has cached start counting as their cache refreshes.
• Analytics lists pages by their title, with the address in grey; the home page reads Home. The CSV export adds an Address column.

Fixed

• Analytics counts more accurately after accepting cookies early, on devices with a fast clock, for long non-Latin page addresses, when coming back from PayPal, Stripe or a sign-in, and for visits whose next page has no script. Page links work again on sites installed in a subfolder.

0.0.35 2026-10-08

Added

• Dirigible Analytics, off by default: visitor numbers counted on the site itself, with no third-party service. Turn it on under Dirigible → Optimize Settings to get an Analytics page in the admin menu and a summary on the Dashboard: visitors, page views, visits, top pages, where visits come from, countries and devices. A small script runs after each page has loaded, respects Do Not Track, and on sites with the cookie banner stores nothing in a visitor's browser until they accept. Logged-in administrators aren't counted unless Track Admin Sessions is on. Deleting Optimize keeps the numbers unless Also delete the Analytics numbers is checked on Optimize Settings.

Fixed

• The PDF compression status keeps backslashes in its stored messages.

0.0.34 2026-10-06

Added

• The site report shows whether REST is locked, whether Gravity Forms' REST API is on, and whether the theme hides users.

Changed

• On a site still running Dirigible People before 4.0.20 or Events before 4.1.43, REST stays locked for logged-out visitors until those update, so contact details are never exposed. The site report says why.
• robots.txt no longer adds crawl delays for SEO tools such as AhrefsBot and SemrushBot, so site audits run at full speed and every crawler follows the same rules. robots.txt is now exactly what WordPress or your SEO plugin writes. The "Do not add crawl-delay rules" setting is removed.
• Upgrade notice: the REST API is now open to logged-out visitors on sites that never checked the old "Allow REST API access" box. To restore the old behaviour, check "Lock down REST for logged-out users" on Optimize Settings.
• The REST API works for logged-out visitors, as WordPress ships it, so plugin features that load data on the page work for everyone. The Dirigible theme still hides user accounts, and Dirigible People (4.0.20+) and Events (4.1.43+) keep contact details out of it.
• The Public REST API card's checkbox is now "Lock down REST for logged-out users" (off). The old "Allow REST API access" setting is removed.

0.0.33 2026-10-05

Changed

• With Gravity Wiz's Spellbook installed, its weekly report to Gravity Wiz (site details, active plugins and Gravity Wiz license keys in plain text) is no longer sent. Gravity Perks still check their licenses and update as usual.

0.0.32 2026-10-05

Added

• On Gravity Forms forms that Simple Cloudflare Turnstile protects, reCAPTCHA now steps aside automatically: the CAPTCHA field and Google's script stop showing there, and the reCAPTCHA add-on's v3 check is switched off for those forms. Visitors get one check, not two, and a form with missing or broken reCAPTCHA keys can be sent again. Forms Turnstile doesn't protect are unchanged, and nothing in your forms or settings is edited.

Changed

• Upgrade notice: after turning off Turnstile's "Enable on all Gravity Forms", adding a form to its Disabled Form IDs, or deactivating Turnstile or Optimize, purge the site's cache, or cached pages without reCAPTCHA may not send until it clears. The update itself needs no purge.
• When every form that uses reCAPTCHA v3 is protected by Turnstile, Google's v3 script (about 1 MB) no longer loads on the site's pages. On those forms, new entries show the reCAPTCHA score as "Disabled" and aren't sent to Spam over a low score; Turnstile turns bots away instead.

0.0.31 2026-10-05

Added

• reCAPTCHA on demand (off unless Dirigible support turns it on): with the Gravity Forms reCAPTCHA add-on (v3), Google's script loads when a visitor starts using the page or nears a form, not with every page view.

Changed

• On shop sites that show the cart in the header, the cart panel's styles load after the page appears instead of holding it up. The cart button looks the same and the panel works as before.
• With Smash Balloon's Instagram Feed (free or Pro), its styles and scripts load only on pages that show a feed, so other pages load faster. Where nothing else needs jQuery up front, this also lets the theme defer jQuery.

0.0.30 2026-10-05

Changed

• Google Maps embeds load when a visitor scrolls near them (within one screen), not with the page. Chrome's own lazy loading fetched a map 1,250–2,500 px early, so a map lower on a page added about half a megabyte to every page view and to the PageSpeed score. A map near the top still loads straight away, and maps look and work the same. Only Google Maps embeds change. Developers can opt out with dirigible_optimize_lazy_map_embeds.
• On WooCommerce sites with Simple Cloudflare Turnstile, pages with a form (My Account login and lost password, Gravity Forms) no longer load WordPress's React and data scripts (16–19 files, about 110 KB). Only the checkout uses them, and the checkout, including any page with a Checkout block, loads them as before. Developers can opt out with dirigible_optimize_turnstile_woo_drop_data.
• Optimize Settings has no Save buttons: each checkbox saves when you click it, and a message confirms it (for example "RSS feeds turned on."). If a save fails, the box goes back to how it was and an error explains why. Messages need Dirigible theme 5.31.87 or newer; older themes show a short note under the checkbox.
• The Images and Daily PageSpeed cards on Optimize Settings update straight after a change, without reloading the page.

0.0.29 2026-10-05

Changed

• On shop sites, new uploads no longer get WooCommerce's own copies (including a 768-pixel square crop); WooCommerce uses the theme's image sizes instead. Images already uploaded keep their WooCommerce copies, so existing products don't change. Product images in cart and checkout stay square with Dirigible theme 5.31.85 or newer.

0.0.28 2026-10-05

Changed

• New uploads keep up to 3,000 pixels (was 2,400), so full-width images stay sharp on large retina screens, while most screens still get the 2,400-pixel size. An upload only a little larger than 2,400 pixels no longer gets a near-identical 2,400-pixel copy beside it.

Fixed

• Large desktop screens get the 2,400-pixel image size instead of the full-size upload. WordPress left sizes wider than 2,048 pixels out of each image's srcset, so full-width Hero and Background images on 1920 px screens downloaded the 2,560–4,000 px original. Existing content picks it up as pages leave the cache.

0.0.27 2026-10-05

Added

• Uploads are compressed by Optimize, replacing EWWW Image Optimizer's paid compression. Every JPEG WordPress saves, the original and each size, is quality 78 and progressive, with camera details and location removed and the colour profile kept: about a third smaller with no visible difference. Photos are turned upright first, and nothing is ever saved bigger than the upload. While EWWW is active this stays off and EWWW keeps compressing. Developers can opt out with the dirigible_optimize_compress filter.
• PNGs are reduced to 256 colours when that makes them at least 20% smaller and they look the same (photos and soft edges keep their full colours); otherwise only hidden text data is removed.
• Large PDFs (10 MB and up) without accessibility tags, form fields, signatures or encryption are compressed in the background on servers with Ghostscript 10.03.1 or newer, bringing images over 250 dpi down to 200 dpi; the original is kept for 30 days with a Restore original link in the Media Library, and other PDFs over 1 MB get a Compress PDF button. On servers with older Ghostscript, which is most of them today, PDFs are left alone. Developers can opt out with dirigible_optimize_compress_pdfs.
• The site report shows what compression has saved so far and, when PDF compression is off, why.
• PageSpeed checks in the site report also record when PageSpeed painted the page and how much it had loaded by then, which explains most swings in the lab score.

0.0.26 2026-10-04

Changed

• Pages with the Simple Cloudflare Turnstile plugin load the "verify you're human" check on demand through Optimize instead of the theme, so deactivating Optimize switches it off. Comment forms and WooCommerce My Account login and lost-password forms now wait too, and Gravity Forms and login forms on WooCommerce sites, which used to load the check straight away, now wait as well. The checkout and the WordPress login screen still load it at once. Spam protection is unchanged: a form sent before its check finishes is turned away. Opt out with DS_TURNSTILE_LAZY, ds_turnstile_lazy or dirigible_optimize_turnstile_lazy. Upgrade notice: this takes over once the Dirigible theme is 5.31.84 or newer; until then the theme keeps loading Turnstile on demand as before.

Added

• The site report says whether Optimize or the theme loads Turnstile, and lists each reason it left a page as the plugin prints it once per kind of form, instead of once per page.

0.0.25 2026-10-04

Added

• The site report lists the image and PDF tools the server offers (Imagick, GD, and whether tools such as jpegoptim, pngquant and Ghostscript are installed and allowed to run), and EWWW Image Optimizer's PDF setting. It's checked once a day, never on a visitor's page view, and helps decide what can replace EWWW's paid compression. Nothing changes on the site.

0.0.24 2026-10-02

Changed

• Visitors' next page loads sooner: in Chrome and Edge, a page starts loading when the visitor hovers a link, not only when they click it, so it's usually ready by the time they do. Logged-in users and links to wp-admin, uploads or addresses with a query string aren't affected, and analytics only count pages that are actually opened.
• Pages with a Gravity Forms form no longer load Placeholders.js, a fallback for Internet Explorer 9 that no current browser needs. Placeholder text in fields looks and works the same.

0.0.23 2026-10-02

Changed

• robots.txt no longer asks every crawler to wait 5 seconds between pages. Google ignored that delay, but Bing honoured it, and Bing's index also powers DuckDuckGo, Yahoo, Copilot and ChatGPT search, so new pages reached those more slowly. SEO tools such as AhrefsBot and SemrushBot, and a few foreign search engines, are still slowed down, and they now also keep out of wp-admin like other bots. Sites set to "Discourage search engines" get no crawl-delay rules.

0.0.22 2026-10-02

Added

• Translations and RSS feeds can be turned back on: a new "Language and RSS Feeds" card on Optimize Settings, with "Use the Site Language" and "Turn RSS feeds back on". Both stay off unless checked, so no site changes on update. After changing either, purge the site's cache on Rocket.net so visitors see it.

Changed

• Very large uploads are shrunk again, as EWWW Image Optimizer did: an image longer than 2,400 pixels (the largest size the Dirigible theme uses) is resized to 2,400 before it reaches the Media Library. It's kept as one file, with no full-size original and no "-scaled" copy; this corrects 0.0.21's note. Phone photos stay upright, and their GPS and camera details are removed. A 4,000-pixel photo of about 1.8 MB ends up around 600 KB. Animated images and images at or under 2,400 pixels are left alone. Off while EWWW Image Optimizer is active.
• Optimize Settings wording: the "Enable REST for Public" card is now "Public REST API", and the Images card describes only what's on.

0.0.21 2026-10-02

Added

• PNG uploads with no transparency, and GIFs that aren't animated, are saved as JPGs when that makes them smaller (photos and screenshots usually shrink several times over). The Media Library, the image and its sizes are all the JPG from the start. This is off while EWWW Image Optimizer is active, since EWWW converts on its own. "Keep PNG and GIF uploads as they are" under Optimize Settings → Images turns it off.
• Gravity Forms pages no longer load WordPress's Dashicons stylesheet for visitors (35 KB of render-blocking CSS) with Dirigible 5.31.78 or newer, which draws the form's password, upload and date icons itself. Logged-in pages with the admin bar keep it.

Changed

• Upgrade notice: after this update, deactivate EWWW Image Optimizer but don't delete it for 30 days. Pages cached at the edge before the update can still load its lazy-load and WebP scripts from the plugin folder. Deactivating keeps those files; deleting removes them.
• EWWW Image Optimizer no longer makes WebP copies, rewrites pages to WebP or lazy loads images. Cloudflare already serves WebP to browsers that take it, and the theme lazy loads images without a script. EWWW's other settings are untouched. A checkbox under Optimize Settings → Images turns these back on.
• The WebP copies EWWW already made are removed once, in the background, along with its WebP rules in .htaccess. Images you uploaded as WebP, and any WebP file a page or field links to, are kept. Sites where EWWW rewrote pages to WebP wait 31 days first, so cached pages never point at a missing file. Optimize Settings → Images shows how many files and how much space were freed.
• Once its WebP copies are gone, EWWW Image Optimizer is deactivated, and Dirigible Optimize handles uploads. EWWW stays active on sites that use an EWWW API key or Easy IO. Its settings are kept, so reactivating it brings everything back.
• With EWWW deactivated, new uploads keep their full-size original, and WordPress adds its usual "-scaled" copy (longest side 2560 px, quality 82) for pages to use. Before, EWWW shrank the original itself, so very large uploads now take more disk space, but pages look the same.

0.0.19 2026-10-01

Changed

• Update checks use the Dirigible theme's license handling, so a plugin with no license key no longer sends an empty one.

0.0.18 2026-09-30

Changed

• Each daily PageSpeed run now also records how fast the home page answered, so a test that hit an uncached page (for example right after a cache purge) shows up in the site report.

0.0.17 2026-09-30

Changed

• Publishing a post no longer sends pingbacks or trackbacks, checks links for feed enclosures or notifies Ping-o-Matic, and pingbacks and trackbacks from other sites are turned away. "Send and accept pingbacks and trackbacks" on Optimize Settings restores them.
• The block editor no longer fetches WordPress.org's patterns or loads the Block Directory (130 KB of JavaScript that offers plugins to install from the inserter); theme patterns still show. Both have a restore checkbox under Optimize Settings → Editor.
• Post lists and classic edit screens check for editing conflicts once a minute instead of every 10 seconds, as the block editor already did; "someone else is editing" notices can lag by up to a minute. A checkbox restores the 10-second check.

0.0.16 2026-09-30

Fixed

• One fewer database query on every uncached page load: the PageSpeed on/off setting added in 0.0.12 is now stored up front instead of being looked up and not found on each request.

Changed

• WordPress's emoji script no longer loads on post embed pages, and the classic editor no longer loads its emoji plugin file. Normal pages already had no emoji code.

0.0.15 2026-09-30

Security

• Updates come only from Dirigible: WordPress no longer matches this plugin to a WordPress.org listing with the same name.

Changed

• The installable zip is smaller: build sources, source maps, right-to-left stylesheets and Markdown are no longer shipped. Nothing sites load changed.

0.0.14 2026-09-30

Changed

• Once a site has two weeks of PageSpeed results, the PageSpeed panel moves up the Dashboard Welcome screen, just below Palette. It's hidden if the Dirigible Optimize license lapses, rather than showing a chart that has stopped updating.
• The PageSpeed panel's small print (the median note and the "What these numbers mean" link) is quieter, so the figures and chart stand out.

0.0.13 2026-09-30

Changed

• The PageSpeed panel shows four figures (score, largest paint, layout shift, blocking time) as 7-day medians, each marked Good / Needs work / Slow, with a chart that fills the panel at any width and a tooltip for each test on hover, tap or arrow keys.
• Until a site has five tests, the panel says it's still collecting data, so one unusual first result isn't read as the site's score; a "What these numbers mean" section explains each figure in plain words.
• Test now shows "Testing…" and refreshes the card when the result arrives, without a manual reload.

0.0.12 2026-09-30

Added

• A daily PageSpeed Insights test of the home page (mobile), with a 90-day score chart on the Dashboard Welcome screen and on Optimize Settings. Runs only where Dirigible Optimize is licensed.
• A "Turn off daily PageSpeed tests" setting.

Fixed

• A visitor who lands while Dirigible Optimize is being updated sees "This site is updating, refresh in a minute" instead of a critical error, and error replies never include server file paths.

0.0.11 2026-09-21

Changed

• Optimize Settings uses the Dirigible Tools shell: jump nav, card layout for REST and crawl-delay options, and quiet Save actions instead of the classic settings-API table.