304 North Cardinal St.
Dorchester Center, MA 02124
304 North Cardinal St.
Dorchester Center, MA 02124
OceanWP is now faster, slicker and more stable! With modernized and object-oriented codes, it executes functions swiftly, using far less resources and far less dependencies.
Before we explain the upcoming changes and improvements, we’d like to go over some basics with you. This will help users – primarily those who aren’t code savvy – understand the benefits of the upcoming changes.
Why are we boring you with these details?
Countless times we have received requests for assistance where a user would ask us to help them remove jQuery from their website because “some speed/optimization tool suggested that it’s slowing the website down”.
These situations made us realize it will take some time for users to understand such assessment tools are anything but accurate and perfect. It also gave us an insight that there are a lot of WordPress users who are unfamiliar with the “under the hood” functionality of WordPress, therefore WP themes and plugins as well.
In order to get a better grasp of (online) assessment tools, essential knowledge of the overall WordPress functionality is necessary. Even if you don’t plan to learn any programming languages or become a WordPress developer, this information will assist you in determining whether a “report” from a specific tool is accurate or false. Eventually, you’ll instantly know whether you are able to do something about the report or not.
And to summarize, you cannot remove jQuery from WordPress websites.
Would it surprise you to learn that out of 1 million top websites on the internet (not only WordPress sites), 80% of them use jQuery?
jQuery helps creating and handling complex tasks, such as AJAX requests, events, animations, CSS manipulations and the overall website’s front-end functionality. Compared to other JS libraries, a complicated task is easier to achieve with jQuery because it requires minimal coding.
After all, the jQuery motto is “write less, do more”.
Of course, by now you’ve probably guessed.
For those of you just starting out with OceanWP or at least considering it – OceanWP is one the best themes to use for WooCommerce and/or Elementor. Check out all OceanWP features or preview our full-website demo templates.
Since 2016, with the help of jQuery, we were able to help our users do and achieve more with one single WordPress theme and without the use of additional unnecessary plugins. Needless to say, we’re talking about OceanWP
Compared to the jQuery motto, our own isn’t that much different at all. OceanWP aim is to enable everyone – from beginners to pros – to build amazing websites of all types (eCommerce, blog, portfolio) fast and in a smooth and user-friendly way. Judging by the feedback and reviews we get from our users, we were successful.
Most importantly, we plan to continue with this tradition, but in an improved way.
Unlike jQuery or Underscore JS, Vanilla JS means coding from the scratch, without the use of frameworks or libraries as dependencies.
Where did the term Vanilla JS come from then?
It’s actually a fun fact, and, believe it or not, it’s related to the real vanilla ice cream. Vanilla ice cream represents the first form or ice cream flavor. So, if you’re in a pastry shop and order ice cream without specifying the flavor, you’ll get vanilla.
Sadly, there is no such thing as a rulebook or a guidebook to specify when it’s best to use one or the other.
Like mentioned earlier, jQuery is one of the fastest and most-widely used JS script.
Scripts alone do not make any website slower – it’s the quality of codes that influences a website’s performance (among other internal and external factors).
And it’s the exact same code quality that made feature-rich OceanWP websites perform just as fast or even better compared to other themes with the least amount of features.
The short answer to this question is – no.
The long answer, and without involving complicated developer terminology, there are still tasks that only jQuery can perform. Or, better yet, there are no Vanilla JS code substitutes for these jQuery codes.
That being said, OceanWP will still use jQuery in its codes within the theme and all our plugins, but at the minimum level.
OceanWP switching to Vanilla JS won’t have any negative impacts and will not cause conflicts with plugins that use jQuery.
In fact, your overall website experience and especially the experience of your website visitors will be significantly improved. With improved coding, OceanWP now relies on a lot less dependencies, which ensures stability and minimizes chances for a possible JS conflict. Most importantly, it executes functions faster using far less resources.
The era of using Vanilla JS in OceanWP starts with the version 3.0.
You can expect the official release on July 20th – the exact day the new WordPress 5.8 version is expected.
And that brings us to the most important part – preparing for the update.
Besides the OceanWP theme, the following Ocean extensions have also been upgraded to Vanilla:
The Ocean Extra 1.7.8 update is released as well, however this plugin does not contain any Vanilla changes.
Along with OceanWP, all plugins with the Vanilla JS version will be released the same day.
The correct update order is:
Before you update, make sure you have taken necessary precaution measures.
Remember, this is a major update.
The best practice is to test new changes on localhost, test or staging environments.
If you don’t have the option to test the updates anywhere, do not update immediately. Wait for a couple of days or even a week, until we’ve gathered feedback and made sure it’s safe for you to update.
Remember, even if everything is fine, something can always go wrong during updates. After all, the bad thing about software is – it’s software.
Make sure to backup your websites properly. Do not rely on hosting backups alone, take manual backups as well and store data in a safe place. If you’re using the WordPress Reset plugin (not to be confused with WordPress Database Reset), you can also create website snapshots.
Important: remember to purge cache thoroughly after the update, multiple times if necessary. The same goes for the CDN (cloud) cache.
In order to take full advantage of the Vanilla JS, all scripts via Theme Panel > Scripts & Styles must be ENABLED at all times.
Short explanation: disabling any script creates an entirely new file which is then placed in your website’s installation folder, then applied on the front-end of your website instead of using default OceanWP theme scripts.
Long explanation: at the time when the Scripts & Styles (part of Ocean Extra plugin) option was introduced, good (and free) caching plugins weren’t accessible to everyone. Over time, the situation has changed. If you’re running good optimization and caching plugins, disabling any script is completely unnecessary.
Important: remember to purge cache thoroughly, multiple times if necessary. The same goes for the CDN (cloud) cache.
No, it will not.
That’s also one of the main reasons we have introduced Vanilla JS. However, we don’t plan to stop there.
Although we use conditional script loading in our codes (load scripts on the front-end only when necessary), after the Vanilla release we plan to enhance this functionality even more. Basically, we plan to automate the functionality previously provided by the Scripts & Styles feature.
The next step is to enjoy your website’s enhanced performance
We are committed to constant improvement. Our goal is to make yours and your website’s visitors experience with OceanWP the best as possible. When it comes to future updates, our main focus will be on performance, further improved accessibility, new features and styles, as well as existing codes revision.
OceanWP was built for the WordPress community. If you would like to contribute with your ideas, let us know how you believe we could get and do better. Share your ideas about features and improvements using our feature requests form.
We are releasing major updates.
Take website backups, including manual backup, before updating OceanWP and Ocean plugins.
The best practice is to test all updates on test, localhost or staging environments. If you don’t have the opportunity to test the updates, do not update immediately. Wait with the updates a couple of days until we’ve gathered feedback.
In case of any problems or issues, inform us about possible bugs or submit tickets.