[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f0y5dSklsEH5SuG12dmypqKJ37meRGaKBn0Pj5O0XZxs":3},{"slug":4,"display_name":5,"profile_url":6,"plugin_count":7,"total_installs":8,"avg_security_score":9,"avg_patch_time_days":10,"trust_score":11,"computed_at":12,"plugins":13},"peterwilsoncc","Peter Wilson","https:\u002F\u002Fprofiles.wordpress.org\u002Fpeterwilsoncc\u002F",5,180,97,30,92,"2026-04-04T15:12:09.106Z",[14,35,51,67,81],{"slug":15,"name":16,"version":17,"author":5,"author_profile":6,"description":18,"short_description":19,"active_installs":20,"downloaded":21,"rating":22,"num_ratings":22,"last_updated":23,"tested_up_to":24,"requires_at_least":25,"requires_php":26,"tags":27,"homepage":31,"download_link":32,"security_score":20,"vuln_count":22,"unpatched_count":22,"last_vuln_date":33,"fetched_at":34},"rapid-canonical-urls","Rapid Canonical URLs","1.0.3","\u003Cp>WordPress uses 301 redirects to redirect URLs to their canonical version.\u003C\u002Fp>\n\u003Cp>In cases where the non-canonical version will show the correct content,\u003Cbr \u002F>\nit is possible to use the HTML5 history API to show visitors the correct\u003Cbr \u002F>\nURL without the additional HTTP request.\u003C\u002Fp>\n\u003Cp>This reduces HTTP requests, speeding up access for visitors and reducing\u003Cbr \u002F>\nthe load on your server.\u003C\u002Fp>\n\u003Cp>It is \u003Cem>strongly recommended\u003C\u002Fem> you use this plugin in association with an\u003Cbr \u002F>\nSEO plugin that adds canonical URL meta tags.\u003C\u002Fp>\n","Reduce 301 redirects and HTTP requests by using HTML5’s history API to show visitors the correct, canonical URL.",100,7031,0,"2025-11-15T22:38:00.000Z","6.9.4","4.4.0","5.6.20",[28,29,30],"canonical-urls","history-api","html5","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Frapid-canonical-urls.1.0.3.zip",null,"2026-03-15T15:16:48.613Z",{"slug":36,"name":37,"version":38,"author":5,"author_profile":6,"description":39,"short_description":40,"active_installs":41,"downloaded":42,"rating":22,"num_ratings":22,"last_updated":43,"tested_up_to":24,"requires_at_least":44,"requires_php":45,"tags":46,"homepage":31,"download_link":50,"security_score":20,"vuln_count":22,"unpatched_count":22,"last_vuln_date":33,"fetched_at":34},"simple-search-submission","Simple Search Submission for IndexNow","1.2.0","\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.indexnow.org\u002F\" rel=\"nofollow ugc\">IndexNow\u003C\u002Fa> is a simple way of notifying search engines of updates to URLs on a site.\u003C\u002Fp>\n\u003Cp>IndexNow allows website owners to submit a request to search engines to prioritize the crawling of a particular page or blog post on your site.\u003C\u002Fp>\n\u003Cp>This plugin provides a no-fuss, simple alternative to just submit updates to the search engines.\u003C\u002Fp>\n\u003Cp>Crawl requests will be sent to search engines when:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>new content is published\u003C\u002Fli>\n\u003Cli>existing content is updated\u003C\u002Fli>\n\u003Cli>existing content is unpublished (this encourages de-indexing)\u003C\u002Fli>\n\u003Cli>the post slug changes (both the old and new are sent index the redirect URL)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>De-indexed and redirect URLs are only sent to IndexNow once.\u003C\u002Fp>\n\u003Cp>The biggest features of this plugin are the features that it’s missing:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>there are no settings, it just works\u003C\u002Fli>\n\u003Cli>there are no onboarding steps, it just works\u003C\u002Fli>\n\u003Cli>there are no custom database tables, it just works\u003C\u002Fli>\n\u003Cli>simply put, there is no fuss!\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Simple Search Submission for IndexNow submits the update requests as you save your content. If you wish to submit the URLs asynchronously via a cron job, you can include the code \u003Ccode>add_filter( 'simple_search_submission_notify_async', '__return_true' );\u003C\u002Fcode> in your theme or or plugin.\u003C\u002Fp>\n","A simplified plugin for submitting crawl requests to search engines supporting IndexNow.",40,1016,"2025-12-30T23:58:00.000Z","6.3","7.4",[47,48,49],"crawling","indexnow","seo","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsimple-search-submission.1.2.0.zip",{"slug":52,"name":53,"version":54,"author":5,"author_profile":6,"description":55,"short_description":56,"active_installs":57,"downloaded":58,"rating":22,"num_ratings":22,"last_updated":59,"tested_up_to":60,"requires_at_least":61,"requires_php":45,"tags":62,"homepage":31,"download_link":65,"security_score":66,"vuln_count":22,"unpatched_count":22,"last_vuln_date":33,"fetched_at":34},"fonts-to-uploads","Fonts to Uploads","1.0.1","\u003Cp>WordPress 6.5 introduces a new Font Library feature. By default these new files are stored in the directory \u003Ccode>wp-content\u002Ffonts\u003C\u002Fcode>. This plugin relocates the font files to the \u003Ccode>wp-content\u002Fuploads\u002Ffonts\u003C\u002Fcode> instead.\u003C\u002Fp>\n\u003Cp>This is to ensure that sites using S3 buckets, file partitions and immutable file systems can make use of the new Font Library feature without the need to refactor their server or duplicate their offloading capacity.\u003C\u002Fp>\n\u003Cp>If you find any bugs or wish to contribute a pull request, please do so via the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fpeterwilsoncc\u002Ffonts-to-uploads\" rel=\"nofollow ugc\">plugin’s GitHub repository\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Most sites will not require this plugin as their file system will allow for the new folder to be created and written to. As with most WordPress features, the Font Library will just work! This is for websites with complex and heavily customized hosting environments.\u003C\u002Fp>\n","Relocate the WordPress fonts folder to the uploads directory.",20,1962,"2024-03-21T00:37:00.000Z","6.5.8","6.4",[63,64],"font-library","uploads","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffonts-to-uploads.1.0.1.zip",85,{"slug":68,"name":69,"version":70,"author":5,"author_profile":6,"description":71,"short_description":72,"active_installs":57,"downloaded":73,"rating":22,"num_ratings":22,"last_updated":74,"tested_up_to":24,"requires_at_least":75,"requires_php":45,"tags":76,"homepage":31,"download_link":80,"security_score":20,"vuln_count":22,"unpatched_count":22,"last_vuln_date":33,"fetched_at":34},"local-twemoji","Local Twemoji","1.3.1","\u003Cp>Local Twemoji is a WordPress plugin to serve fallback emoji images from your own site URL rather than the WordPress.org CDN.\u003C\u002Fp>\n\u003Cp>The purpose of this plugin is to aid sites served over a CDN as browsers now cache requests on a per site basis rather than globally.\u003C\u002Fp>\n\u003Cp>The effect of this is that the WordPress.org CDN’s splat image is treated as two different images if downloaded from site-one.example and site-two.example. You can read more about this in the Chrome post on \u003Ca href=\"https:\u002F\u002Fdeveloper.chrome.com\u002Fblog\u002Fhttp-cache-partitioning\" rel=\"nofollow ugc\">cache partitioning\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>For sites served over a CDN, downloading the image from your own URL will be quicker as it reduces the number of servers the visitor’s browser needs to connect to.\u003C\u002Fp>\n\u003Ch4>WordPress version support\u003C\u002Fh4>\n\u003Cp>A new version of Twemoji is released each time the emoji are added to the Unicode specification, each major version bump of Twemoji will contain new images.\u003C\u002Fp>\n\u003Cp>To avoid the risk of serving broken images to your visitors, this plugin should be kept up to date.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>WordPress 6.9 requires Local Twemoji 1.3.1 or later\u003C\u002Fli>\n\u003Cli>Earlier versions of WordPress require Local Twemoji 1.1.0 or later\u003C\u002Fli>\n\u003C\u002Ful>\n","Self hosted Twemoji images",649,"2025-12-27T02:58:00.000Z","6.0",[77,78,79],"emoji","performance","twemoji","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flocal-twemoji.1.3.1.zip",{"slug":82,"name":83,"version":84,"author":5,"author_profile":6,"description":85,"short_description":86,"active_installs":22,"downloaded":87,"rating":22,"num_ratings":22,"last_updated":88,"tested_up_to":89,"requires_at_least":61,"requires_php":90,"tags":91,"homepage":31,"download_link":93,"security_score":20,"vuln_count":22,"unpatched_count":22,"last_vuln_date":33,"fetched_at":34},"performant-transients","Performant Transients","1.0.0","\u003Cp>This is a utility plugin for backporting a minor performance improvement scheduled for inclusion in WordPress 6.6 to earlier versions.\u003C\u002Fp>\n\u003Cp>In WordPress 6.4 the function \u003Ccode>wp_prime_option_caches()\u003C\u002Fcode> was introduced to allow for multiple options to be queried in a single database call.\u003C\u002Fp>\n\u003Cp>On sites without a persistent cache, temporary transients are stored in two options. One containing the transient itself, the other containing the timeout. These are stored as \u003Ccode>_transient_[transient name]\u003C\u002Fcode> and \u003Ccode>_transient_timeout_[transient name]\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>In WordPress 6.6 and later, these options are primed by a single database call using the priming function. This plugin can be used on WordPress 6.4 and 6.5 to backport the functionality.\u003C\u002Fp>\n\u003Cp>While a mild improvement on sites making limited use of transients, this can significantly reduce the number of database queries on sites running plugins making heavy use of transients.\u003C\u002Fp>\n","Reduce the number of database calls querying transients.",343,"2025-06-24T02:50:00.000Z","6.6.5","7.2",[78,92],"transients","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fperformant-transients.1.0.0.zip"]