Disable Emojis (GDPR friendly)
This plugin disables the WordPress emoji functionality, removing unnecessary code bloat that adds support for emojis in older browsers. What it does Removes the emoji detection script from wp_head and the admin Removes emoji styles from wp_print_styles and admin Removes emoji DNS prefetching, preventing connections to s.w.org Removes the wpemoji TinyMCE plugin Strips emoji CDN hostname from DNS prefetch hints Performance & Privacy Emojis will still display in modern browsers that have built-in support. This plugin simply removes the extra HTTP requests and JavaScript overhead for browsers that don’t need it. Additionally, it prevents DNS prefetching to WordPress.org’s emoji CDN, improving privacy. Note: Emoticons like :) will continue to work as expected. Requirements PHP 7.4+ WordPress 5.0+ GDPR compliancy This plugin does not send any data to external servers. It disables DNS prefetching of emojis within WordPress, which should ensure improved privacy. To determine if your site is GDPR compliant, please seek legal advice. I have done my best to ensure the plugin is 100% GDPR compliant, but I am not a lawyer so cannot guarantee anything. Architecture The plugin uses: Quality All code uses declare(strict_types=1) and follows PSR-12. The plugin runs the following tooling: PHP_CodeSniffer (run via composer phpcs) — sniffs for PSR-12 violations PHP-CS-Fixer (run via composer cs) — dry-run style check PHPStan at level 6 (run via composer phpstan) — static analysis
Staatic – Static Site Generator for WordPress
Staatic turns WordPress into a practical static site generator. Keep editing posts, pages, menus, media, and settings in WordPress, then publish a static copy made of HTML, images, CSS, JavaScript, and other assets. The public site can be served without WordPress, PHP, or a database in the visitor request path. That can improve performance, reduce origin load, and shrink the public attack surface while preserving the familiar WordPress editing workflow. This is especially useful for a private-origin, public-static setup: WordPress remains available for editors and publication work, while visitors receive prebuilt files from your chosen hosting target. Staatic includes the publication workflow and deployment methods needed to run a self-hosted static WordPress site. Features of Staatic include: Crawls your WordPress site and builds a static publication from the pages and assets it discovers. Publishes from WordPress Admin, with publication status, logs, resource details, and downloadable output. Deploys to Local Directory, Amazon S3 or S3-compatible storage, GitHub, Netlify, SFTP, or a zip archive. Supports redirects, custom 404 pages, additional URLs and paths, exclude rules, and HTTP headers. Includes a WP-CLI command for command-line publication workflows. Works with WordPress Multisite, WPML, and HTTP Basic Auth protected WordPress origins. Helps separate the public site from WordPress admin, plugin runtime, and database-backed page generation. Provides integration hooks and compatibility improvements for common WordPress setups. Staatic Premium and Staatic Cloud add features such as forms integration, search integration, scheduled publications, change-based publications, and managed static WordPress hosting. The Community edition remains suitable when you want to generate and deploy a static version of a WordPress site yourself. Staatic Premium Staatic Premium supports ongoing development and adds functionality for teams that need more than the Community edition. Premium features include forms integration, search integration, scheduled publications, change-based publications, additional automation, and Staatic Cloud deployment options. For more information, visit Staatic.
