WordPress 2019 Survey Results Show Professionals Slow to Adopt Block Editor, 2020 Survey Now Open

WordPress has opened its 2020 Annual Survey, a short set of questions designed to collect more information on how different groups of people are using the software. It takes approximately 5 minutes to complete and all data is anonymized.

WordPress Executive Director Josepha Haden Chomphosy said she uses the results from the survey to inform her plans and recommendations all year long. In addition to providing valuable information for WordPress’ leadership, the results will also be shared with the wider community.

The Community Team has prepared a report with results from the 2015 and 2019 surveys, which had not been previously published. The 2019 results are summarized in a set of Google slides and are also available as a PDF or PPT.

Despite 2019 being the first year that the survey was translated into five different languages, it only received 6,203 respondents, as compared to nearly 46,000 in 2015. The highest number of responses came from Europe (62%) and Asia (12%), while North American engagement has declined drastically to just 10%. Unchanged from previous years, most WordPress users identify as male (79%).

2019 NPS Results: Detractors are Steadily Shrinking

The 164-page report has a lot of information to digest but one of the highlights is the Net Promoter Score (NPS). It is a loyalty metric derived from users’ responses to the question of how likely they are to recommend WordPress to friends, colleagues, or clients. It provides an informal measurement of user satisfaction or perception.

WordPress’ 2019 NPS was 54, an increase from previous scores of 50 and 52. Promoters remain static while Detractors are steadily shrinking. This score, however, is skewed towards representing those who have a favorable enough opinion of WordPress to take the time to respond to the survey. The software’s truest detractors have likely already moved on to following other tech communities and may be underrepresented in the NPS score.

More than 75% of respondents have been using WordPress for three years or more. Results indicated the project’s open source community is an important driver for why people use the software:

“Nearly six-in-ten (59%) of survey respondents choose WordPress because it’s what they know best. Half (50%) say they enjoy its open source community. Nearly half (48%) say WordPress has the features they need.”

This indicates that the WordPress community provides a factor of “stickiness” equal to that of the features the software offers. Improving and maintaining a healthy community is an important consideration for user retention, since a user sticking with WordPress is just as important as attracting new users.

CMS Usage on the Rise Among Professionals, Blogging Is Declining

The 2019 survey found that 76% of professionals are using WordPress as a CMS, with slightly higher numbers (79%) for the WordPress Company Pros segment (those who work for a company that designs/develops websites). Blogging usage among professionals is consistently declining.

In the segment of respondents reporting as Users, blogging is also on the decline, with 49% using WordPress as a personal blog in 2019 vs. 63% in previous years (2015-2017).

WordPress Professionals Slow to Adopt the Block Editor

One noteworthy section in the 2019 results includes data on block editor adoption. When asked “Which editor do you currently use?”, 53% of respondents who identified as professionals said they are using the Classic Editor. This indicates the block editor is still finding its footing among professionals. An increasing percentage of these professionals are also self-employed (44% in 2019 vs 36% in 2016).

Another question asked, “Have you or your team built blocks for the new editor?” Less than half of those using the new editor confirmed they have new blocks added for using it, and 17% were not sure. If more than half of professionals have yet to adopt the new editor, it seems the market for block-based products has a great deal of room to grow.

Block editor adoption among Users could be as low as 36% or as high as 56%, but a large portion of users (20%) are unsure which editor they are using. This is not a bad thing, as most new users will have no prior knowledge of the Classic editor. Results from the 2020 survey should be useful for tracking adoption of the block editor over a longer period of time since its debut in WordPress 5.0 (2018.)

Attendance at WordPress community events, such as meetups and WordCamps, seemed to be on the rise, as well as submitting bug reports and contributing to documentation. However, 2019 saw a sharp decline in the percentage of those who report having created their own theme (61% to 42%) or plugin (50% to 38%), when compared with previous years. The percentage of core contributors (5%) has remained steady. This might mean that creating themes and plugins is becoming more difficult or less rewarding, or perhaps the survey attracted more of a different type of user than it did in previous years. There are any number of explanations but this may be a trend to continue watching.

WordPress Users Remain Uneasy about Auto-Updates, Positive Sentiment is Declining

In light of the incident last week where WordPress’ auto-update system misfired, updating live sites to an alpha version, the survey includes valuable data about how users are feeling about this feature. The data from 2019 indicates that positive sentiments regarding auto-updates were already on the decline since 2015.

Those reporting that they loved auto-updates declined from 41% to 35%. The percentage of those who would like to see auto-updates for major releases of WordPress declined from 24% to 15%. Positive sentiment regarding theme and plugin auto-updates also decreased. Meanwhile, awareness of auto-updates increased in 2019, and slightly more users reported the feature makes them nervous or that they hate it.

These are just a few major highlights from the 2019 survey results, but the report includes much more detailed data regarding contributor satisfaction, time spent contributing, contributors’ experiences, and other topics. Check out all the summaries in the Google docs presentation, and make sure to take the 2020 survey to improve the representation of WordPress users this year.

11

11 responses to “WordPress 2019 Survey Results Show Professionals Slow to Adopt Block Editor, 2020 Survey Now Open”

  1. Gutenberg Lover says:

    For a professional blogger, editor, writer, news editor, journalist or someone else that needs an editor for content new content to be added to a blog, news site, magazine and others, there must be a write mode in Gutenberg, something that is similar to a familiar text editors like from the 50 years – Microsoft Word, OpenOffice, Google Docs, Notepad, email clients etc. Even this comment form – it uses a regular and well known text editing flow, not blocks.

    Gutenberg needs two modes – one that is for “building” and the other for “writing”, the first happens once and it happens for sites that are small biz sites, static sites that do not need constant updating, while the “editing” mode is for those who constantly need to write new content.

    Block building is not how a professional editor, writer, journalist, magazine editor or newspaper editor writes his content. They need a write mode.

    That will move people from the Classic to Gutenberg editor.

    DO IT!

    Report

    • Hubert Gaz says:

      Doesn’t Gutenberg include a “classic” block that works exactly like the older WordPress editor? Add the one block to a post and write to your heart’s content. Perhaps the Gutenberg devs can add an option to add the classic block to all posts/pages by default (unless of course the block is only available as a stopgap and will be removed in future).

      Report

      • Li-An says:

        Sorry, it does not work “exactly” like old editor. Write some text, add an an image and you’ll see it’s no “the old editor”. Each time I try to work with Gutenberg, I got an headache. And it’s not metaphoric, it’s a real headache. And for HTML/Markdown user like me, Gutenberg has no interest at all.

        Report

      • Yes, you can use the classic block in the block editor and keep your whole post/page as one block. If so you prefer. Quite under-communicated option.

        Report

    • Lukasz says:

      I disagree, gutenberg is the evolution of writing creatively.

      I work with technical writers, over the years they have requested all sort of formatting and function options such as columns, accordion, indenting, etc. I started with shortcodes for the above, than elementor, custom fields…Always re-inventing and trying to look for a way to make the CLASSIC type of editors(word, google doc, wp classic editor) simpler to use. WordPress felt very incomplete without these basic functions, along came gutenberg block editor and solved all of those issues and gets better with each release.

      Also going back to the survey I can see why there is slower adoption in gutenberg, as in my case, I have elementor setup on one of my sites that meets all the needs currently. It’s a bit of a process to convert to gutenberg from elementor, maybe they can be used well enough in tandem?

      Report

      • Yes, the block editor solves mos of the shortcomings of the classic editor, especially for creative writers and content producers.

        After starting to use it, there is never a going back.

        Of course, you don’t need it for a simple post, and you always have the classic block, until comfortable. Block editor gives you all!

        Th Classic Editor plugin is disabling all the goodies. That’s bad.

        Report

    • Otto says:

      I don’t understand what the difference between your two “modes” actually is?

      You know that you can just type and not worry about the blocks, right? Can you clarify what this “editing” mode would be, exactly? Or how it would be different?

      Because honestly, it sounds like sticking a big empty box shape around the block editor would satisfy your needs, so I must be missing something here.

      Report

      • To Otto says:

        As each paragraph is block, splitting and merging text from these blocks requires much more effort than any traditional effort. Same goes for formatting of headings, bullet points etc. Imagine writing this comment in blocks. Otto, you are a dev, not a writer, get some feedback from professional journalists and news editors. Hence why they’ll choose custom CMS or Jamstack. Journalists are not dev/geek/coders, they don’t use blocks for text editing and writing. WordPress cannot invent a new culture for them and if you believe you can, then that is I guess unrealistically ambitions to the point it is impossible.

        Report

      • Gutenberg Positive Reinforcement says:

        Try Slab and see how they implemented block content editing and management in symbiosis with text editing. Perfect example of what Gutenberg had to be. Brilliant content editing in blocks, perfect for block building and writing.

        Report

  2. Rod Oldman says:

    This does not look good for Matt’s investors.

    With 2157 1-star reviews and only 632 5-star reviews (a lot of them mistakes, since the system defaults to 5-star when the users wanted to give 1-star), delayed features and no roadmap, the future does not look bright for WordPress users.

    Not that anyone has been listening to them so far anyways.

    Report

    • Gutenberg Lover says:

      Blocks are the future, I do agree, I like the idea, they try to compete with Wix/Squarespace and make something faster and simpler for site building, but there is a problem – that alienates bloggers, journalists, editors and those who need to write and publish content on the site regularly. That’s because they didn’t build their focus group too well and imagine a world where everyone is a tech-nerd with coding/geeking/nerding tendencies and not professionals. I work with professional journalists, none of them wants to edit or publish their content in Gutenberg. The sunsetting is the reason why one of the project sticks to a custom CMS despite my push to went with WP.

      Report

Newsletter

Subscribe Via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

%d bloggers like this: