Testers Needed: Jetpack Plugin Browser

While our Jetpack development team has been hard at work keeping your Jetpacks fueled up and ready for action – our developers over on WordPress.com have been busy too!

You may already be familiar with the great Jetpack features that utilize the WordPress.com interface: the ability to update your plugins across multiple sites with a single click, being able to view enhanced stats about your site, write new and update existing posts and pages with a beautiful editor, and more.

banner-1544x500

Now, there’s even more new things to try!

Over on the WordPress.com Horizon, where the makers of WordPress.com test upcoming changes and new features with the WordPress.com community, there’s a call for testers for a new addition to the Jetpack management features on WordPress.com.

They’re currently looking for testers with Jetpack sites to test the new Plugin Browser feature.

The Plugin Browser lets you find and install plugins from the WordPress.org plugin directory. You can search for keywords or browse within Featured, New and Popular categories. If you’ve got plugins on your site that you no longer need, then this update also lets you remove (delete) those plugins from your sites. You can still activate/deactivate plugins, and turn on (or off) auto-updates as well.

As part of the plugin browser project they have added more details to the single plugin view, which now serves reviews and ratings from the WordPress community, as well as the full description, changelog and other information specified by the plugin author.

“That’s great – how can I help?” you might ask.

Simple! There’s a post on the Horizon Feedback blog with all the details you may need including what to test, how to test, and how to submit feedback to the WordPress.com development team.

The Plugin Browser will be open for feedback through September 28th – so head on over to the Horizon post and get a sneak peek at this great new feature.

Thank you so much if you take the time to test. We appreciate it!

Posted in Contribute, Jetpack News | Tagged , , | 6 Comments
data examining Jetpacks plugin: image of cables

Is Jetpack Bloated? More Data that Debunks the Myth

This article was originally published on the BruteProtect blog. BruteProtect was a plugin designed to stop malicious IPs from accessing WordPress websites. The technology behind BruteProtect is now part of Jetpack’s security features, protecting millions of website from brute force attacks every day.


Thanks for all the feedback and shares on Part 1, see that post for more info on which modules in Jetpack are activated by default and which “Other” plugins we used to test against.

There have been a number of requests for us to show what WordPress core (with no plugins) and Jetpack activated but all modules deactivated looks like, so here we go.

Note that all of the numbers have changed a bit because we re-ran all tests from scratch with an updated version of WebPageTest.

 Other PluginsJetpack (with default modules)Jetpack (with no modules)WordPress Core, no plugins
First load, TTFB1103ms569ms470ms408ms
First load, Fully loaded2742ms1970ms1756ms1620ms
Jetpack vs. WordPress Core without Plugins
Jetpack timing tests
Jetpack Benchmark Assets
Jetmark Benchmark Visual Load
Jetpack Benchmark Bytes

About our testing methodology:
Tests were run from a private instance of WebPageTest, run from an EC2 instance within 1ms of our test subject server. Each test was run 27 times, and we used the median score for each factor. The test server had no other traffic on it while these tests were being performed.


Still have questions about the Jetpack plugin? Contact support or search documentation for quick answers.

Posted in Performance | Tagged , , , , | Comments Off on Is Jetpack Bloated? More Data that Debunks the Myth
jetpack load time impact: image of clock

The Jetpack Bloat Myth: Does the Plugin Slow Down Your Site?

This article was originally published on the BruteProtect blog. BruteProtect was a plugin designed to stop malicious IPs from accessing WordPress websites. The technology behind BruteProtect is now part of Jetpack’s security features, protecting millions of website from brute force attacks every day.


Want the TL;DR? Jump to the test results

To date, the majority of the feedback we’ve received about our acquisition by Automattic has been positive, but we’ve continued to hear from some of our users that they’re concerned about being forced to use Jetpack if they want to continue to receive the protection offered by BruteProtect. Most of these objections are due to the perceived “Bloat” of Jetpack, a plugin that has the capability to add over 30 discrete features to your WordPress site.

We’ve just passed the four-month mark as a part of the Jetpack team at Automattic, and I’d like to address the “Bloat.”

The power of Jetpack is its ability to provide functionality which can’t (or shouldn’t) be included in core for one reason or another. The primary reason for many of the features is their need to be connected to outside servers in order to function well – tools like Photon (which provides a free content delivery network to your site using WordPress.com’s extensive global infrastructure), Related Posts (which uses Automattic’s large Elasticsearch cluster to calculate similarity between your posts), Monitor (which provides uptime monitoring from a number of servers around the world), Stats, Publicize, Subscriptions, Single Sign On, etc. Most, if not all, of these are features are tools that make your site faster, more secure, keep visitors on your site longer, create a better user experience, help you build more traffic, and help you know more about the traffic that is currently coming to your site.

On top of those core heavy-duty features, Jetpack adds a number of smaller but still useful features – items like Custom CSS, Omnisearch, Beautiful Math, Markdown, Spelling and Grammar tools, Widget Visibility, integrated notifications, contact forms, and more. These are features that add no weight to your WordPress install if you choose not to utilize them.

This doesn’t even begin to touch on the new site management features. You can now manage plugins, posts, and pages on all of your WordPress sites from one interface, keeping your sites automatically up to date and secure.

It’s worthwhile to consider the fact that nearly all of Jetpack’s functionality shares a codebase with the same functionality on WordPress.com, so this code is under constant load and testing by tens of millions of users around the world and is being written by some of the best WordPress developers in the world including public contributors (everything we do is public on Github). Every line of code has eyes on it from multiple developers who are looking at it to be both well-performing and secure.

Since joining Jetpack, Derek and I have written a series of 35 tests which are run against Jetpack EVERY TIME there is a commit to the master branch. This tool will immediately raise red flags if there are any code changes which negatively impact the performance of the a WordPress site running Jetpack. We’ll be releasing all the results of these tests to the public in the near future. Every member of the Jetpack team is committed to making sure that performance is a high priority for the project.

Time for Testing

In an effort to look at exactly what effect Jetpack has on a site, we decided to create a test site and run tests against it in two situations. In situation 1, a user is running only Jetpack, with the 19 Jetpack modules that are activated out of the box (After The Deadline, Contact Form, Custom Content Types, Custom CSS, Gravatar Hovercards, Latex, Notes, Omnisearch, Post By Email, Publicize, Sharedaddy, Shortcodes, Shortlinks, Stats, Subscriptions, Vaultpress, Verification Tools, Widget Visibility, Widgets). In situation 2, a user is running five plugins that replicate some of our most used functionality: Contact Form 7, Google Analytics Dashboard for WP, Simple Custom CSS, Share Buttons by AddToAny, NextScripts: Social Networks Auto-Poster. Each of these plugins has the most downloads in the WordPress.org plugin directory for its functionality.

The results:

  • Jetpack, First load, TTFB: 773ms
  • Jetpack, First load, Complete page load: 1876ms
  • Jetpack, Repeat view, TTFB: 143ms
  • Jetpack, Repeat view, Complete page load: 322ms

  • Other Plugins, First load, TTFB: 797ms
  • Other Plugins, First load, Complete page load: 2609ms
  • Other Plugins, Repeat view, TTFB: 460ms
  • Other Plugins, Repeat view, Complete page load: 529ms

The only place running the standalone plugins even gets close is time to first byte on a first page load. Complete first page load is 28% faster, complete repeat page load is 39% faster, and time to first byte on a repeat page load is 69% faster! So you can see that Jetpack (with 19 active modules) offers SIGNIFICANT load time improvements over these five other tools combined. If you start replicating additional functionality, these improvements get even more pronounced.

Jetpack bloat myth: timing tests
Jetpack bloat myth: requests

At the end of the day, it’s very easy to have a negative reaction to Jetpack because of its size and scope, but, thankfully, those fears don’t tend to be realized in the real world.

As to the questions about if we’ll keep supporting BruteProtect as a standalone tool, the answer is “not forever.” If you are currently running BruteProtect Shield’s botnet protection on your site, it will continue to function until at least the end of 2015. At some point during the year, we’ll remove the ability to generate new API keys from BruteProtect, and at some point in 2016 we will completely discontinue BruteProtect as a standalone service.

If you’ve had issues with Jetpack in the past, please don’t write it off – come back and give it another shot, I’m pretty sure that you’ll be glad you did.


Still have questions about the Jetpack plugin? Contact support or search documentation for quick answers. Read the follow-up to this test for more data on Jetpack site speed.

Posted in Jetpack News | Tagged , , , , | Comments Off on The Jetpack Bloat Myth: Does the Plugin Slow Down Your Site?

Want to contribute to Jetpack? Here’s how!

What? Me? Contribute to Jetpack?

That’s right. While we’re hard at work bringing you more Jetpack features, we need your help! What can you do? Why, thank you for asking!

Continue reading → Want to contribute to Jetpack? Here’s how!

Posted in Contribute | Tagged , , , , | 4 Comments
  • Enter your email address to follow this blog and receive news and updates from Jetpack!

    Join 175,219 other followers

  • Browse by topic