OceanWP Speed: A Light Theme, and Everything You Stacked on It

Very fast, says the listing. Measured by whom?

OceanWP's only speed claim is two words on its WordPress.org listing: 'very fast.' No benchmark, no demo score, no comparison chart. That is refreshingly modest for a theme with 400,000+ active installs, and it leaves the measuring to you. Good. A theme's own number would tell you little anyway, because on a working OceanWP site the theme is rarely where the milliseconds go.

The typical stack looks like this: the free theme, the free Ocean Extra companion plugin, Elementor for page layouts, perhaps a Pro Bundle with its extensions, WooCommerce for a shop, and a caching or host optimization plugin. Each layer adds files to every page unless someone tells it not to. This guide works through OceanWP's own switches first, then the companion plugin and extensions, then the trap that catches owners who let an optimizer combine everything. Start by measuring your current pages with our WordPress theme speed test method, so every change has something to beat.

Ten switches in Customizer, Performance

OceanWP's documentation lists the panel's settings in this order. Nearly every one is a way to stop the theme loading something by default. None adds a feature.

The icon settings deserve a second look. OceanWP's docs warn that switching off the theme's Font Awesome does not stop other plugins from loading their own, so an Elementor site can end up with two copies of the same icon library. Check the network panel after each change, not just the setting. If your styling stops updating after you move it to a file, the cause is usually a cache serving the old file, covered in OceanWP CSS not updating.

Google Fonts: the setting that sits outside the panel

Font loading lives in the Customizer's typography settings, under Google Font Settings, and the docs say local hosting needs the free Ocean Extra plugin active. Enable Local Google Fonts hosts any Google font you pick from your own server, which the docs say is faster and friendlier to privacy rules. Preload Local Google Fonts tells the browser to fetch those files early. Font Format offers TTF, WOFF or WOFF2; choose WOFF2, the smallest of the three. Then cut the families and weights the design does not use. When text appears in the wrong typeface after this, see OceanWP fonts not loading.

Ocean Extra and the extensions: weight you opted into

Ocean Extra, the free companion plugin with 500,000+ active installs, is where many OceanWP features really live. Its WordPress.org page lists the per-page settings metabox, custom templates for headers and footers, extra widgets, a mega menu with menu icons, shortcodes, the OceanWP Panel dashboard, template import, and an integrations panel for SVG uploads, Mailchimp, Google reCAPTCHA and Google Maps. Useful pieces, each with its own code.

The plugin's description says its Extra Settings panel lets you disable components such as the metabox, custom templates support and widgets. Turn off what the site does not use. The integrations deserve the same scrutiny: a reCAPTCHA or Maps script on pages without a form or a map is pure cost.

• Customizer Controls are an admin fix, not a visitor fix. Under OceanWP, OceanWP Panel, Customizer, you can stop unused sections loading in the Customizer. The docs pitch it as a way to make the Customizer itself load faster. Your visitors will not notice.
• Each extension is another plugin. The Pro Bundle adds 14 premium extensions to 7 free ones. Install the ones a page actually uses, not the whole bundle because it was paid for.
• Templates bring their builder. Imported full-site templates come with the sections, images and widgets that made the demo look good, and the higher plans add an Elementor sections library on top. Delete what you did not adopt.
• Elementor is usually the heavier layer. Our OceanWP and Elementor guide covers how the two share the work and where they overlap.

The Combine JS menu bug, and what it teaches

Here is the cautionary tale. An owner turns on Combine JS in SiteGround Speed Optimizer, as any sensible owner might, since merging scripts sounds like free speed. The mobile menu stops opening. Users reported exactly this on the WordPress.org support forum, and an OceanWP staff reply on August 12, 2026 said the team was aware of the issue and that a fix would come in an upcoming update. We could not confirm from the thread that the fix has shipped, so treat the combination as risky until you have tested it on your own site.

Why it happens is the useful part. Combining scripts changes the order and timing in which they run. A menu toggle that expects its dependencies to be ready finds them missing, or bound twice, and quietly does nothing. The host's optimizer and the theme are each behaving as designed. The visitor still cannot reach your contact page. The same logic applies to any delay-JavaScript or combine feature in any caching plugin.

An order of work for a faster OceanWP site

1. 1

   Copy the site and measure

   Work on staging. Test the homepage, a service or landing page, a blog post and, if you sell, a product page in PageSpeed Insights on mobile. Record LCP, CLS and INP. Our PageSpeed Insights guide explains lab versus field numbers.

2. 2

   Update the theme and Ocean Extra together

   Bring both to current versions before tuning. If an update has already broken something, fix that first with OceanWP update broke site.

3. 3

   Work through the Performance panel

   Move Styling Options Location to Custom File, then switch off emoji, unused icon sets, lightbox, custom select, the widgets stylesheet and scroll effect where the site does not need them. Clear caches and check pages after each group.

4. 4

   Host fonts locally

   Enable Local Google Fonts, choose WOFF2, preload, and remove unused weights. OceanWP's docs also describe an option, from version 3.3.4 with Ocean Extra active, to serve Elementor's Google Fonts from your own site; use it so Elementor stops fetching its own copies.

5. 5

   Trim Ocean Extra and extensions

   Disable unused Ocean Extra components and integrations, deactivate extensions no page uses, and delete leftover template content.

6. 6

   Fix images on the first screen

   Size the hero image to its display width, serve a modern format, and make sure it is not lazy-loaded. With a Transparent header over a hero, confirm the image is real content rather than a CSS background.

7. 7

   Add script optimization last

   Only now try your cache plugin's combine or delay options, one at a time, testing the mobile menu on a real device after each.

8. 8

   Retest and keep a log

   Run the same tests, write down each change and its effect, and repeat after the next theme or plugin update.

Core Web Vitals on an OceanWP and Elementor page

LCP on these sites is nearly always a hero built in the page builder. If it is a section background, the browser finds it only after reading the CSS, which delays the paint; an image element is discovered sooner. Header choice matters too: with the Transparent header, the hero sits underneath it and is usually the largest thing on the first screen. Read WordPress vs Next.js on LCP for the mechanism and slow LCP on WordPress themes for fixes.

CLS comes mostly from fonts and the header. Fonts loaded from Google late, or in several weights, swap in and shift lines; local hosting with preload reduces that. Headers that change size when they become sticky, and announcement bars injected by plugins, push the page down. A shop page whose layout looks wrong may be a different problem, covered in OceanWP WooCommerce layout broken. The general picture is in WordPress vs Next.js on CLS.

INP tracks how fast a tap gets a response. On OceanWP stores, product quick view, the off-canvas filter, mini cart and Floating Bar all add interactive scripts, and Elementor widgets add more. Each is reasonable alone. Together on a mid-range phone they slow every tap. Use the features that sell, switch off the rest, and see the INP comparison for why script volume decides this score.

What OceanWP cannot fix from the Customizer

• The page builder's output. Elementor's markup and assets are Elementor's. OceanWP's switches stop at the theme's own files.
• Other plugins' scripts. Forms, sliders, reviews and chat often load on every page. Stopping them takes code or a replacement plugin.
• Server response time. If the HTML arrives slowly, the cause is hosting, PHP or uncached database work, upstream of any theme setting.
• Optimizer conflicts. The theme cannot stop a host plugin from combining scripts in an order that breaks it, as the Combine JS reports show.
• Third-party tags. Analytics, ads and chat widgets cost what they cost, whatever theme sits underneath.

There is no separate OceanWP slow-site repair guide yet, so our general WordPress speed optimization guide covers the stack-wide causes, and the OceanWP repair hub lists the faults that often travel with a slow site. When the evidence points at the theme layer specifically, our theme speed optimization service does this work on staging and reports what it could not move.

When a faster OceanWP is still not fast enough

For a modest brochure site or a small shop, a tuned OceanWP stack is a sound, cheap answer, and we would tell you to keep it. Speed becomes a reason to leave when it is tied to revenue: most leads come from phones, the site needs hundreds of pages built from data, or the store keeps adding extensions to do what customers expect. At that point you are tuning five vendors' code to hold a speed that a coded site starts with.

A Next.js build prerenders pages and serves them from a CDN, sends less JavaScript through React Server Components, sizes images with next/image and self-hosts fonts with next/font. Nothing combines scripts after the fact, so there is no Combine JS lesson to learn. It costs more up front and needs a developer for layout changes, and our OceanWP vs Next.js comparison weighs that fairly. Leaving a classic Customizer theme is lighter work than leaving most builders; moving from OceanWP to Next.js explains how content and URLs come across. Owners then edit in Athena CMS. More themes are reviewed in the WordPress themes hub.