Hafen

Removing Elementor without losing content: 58 pages move to Hafen

The German guide schwule-beziehung.de ran on OceanWP and Elementor for years. A single page loaded up to 39 stylesheets, and the home page scored 60 in mobile Lighthouse. On 18 November 2026 we removed Elementor, converted all 58 Elementor pages and posts into regular blocks and switched the theme to Hafen. Here are the steps, the traps and all the numbers.

schwule-beziehung.de is a German-language guide for gay men: relationships, dating, coming out, health and the scene, plus pages about cities, saunas and Pride events. Several hundred posts, some of them built with Elementor over the years, the rest in the block editor. We look after the site's technology and search engine optimisation.

The site was slow, and the server was not the only reason. Before we changed anything, we measured.

The starting point

Active were OceanWP as the theme, Elementor, Elementor Pro, an extra widget pack, a timeline add-on, Ocean Extra and Ocean Social Sharing. Each of these packages brings its own stylesheets and scripts, and many of them load on every page, whether they are needed there or not.

Metric (home page, mobile)before
Lighthouse performance60
Largest contentful paint (LCP)6.1 s
Requests96
Transferred1,531 KB
CSS files per page27 to 39
Server response without cache1.4 to 2.5 s

Two findings had nothing to do with the theme. Google Analytics ran twice: once properly through Site Kit, once as a code snippet stored in Elementor. And a second snippet preloaded an image that is not even the first thing on the page. Both disappeared together with Elementor.

Why deactivating alone is not enough

Elementor stores a page's structure as JSON in the _elementor_data field. It also writes a plain HTML version into the regular post content, so that something still appears after deactivation. On schwule-beziehung.de this version was outdated in many places. It also contained block markers like <!-- wp:paragraph --> that had slipped into Elementor texts at some point when content was copied over from the block editor.

Simply switching Elementor off here gives you old text and broken pages. So we converted from the Elementor data.

The conversion: widget by widget

First the inventory via the REST API: 58 published items used Elementor, 23 posts, 34 pages and one private page. A trap right at the start: a plugin that hides individual posts from lists also hid them from the REST API's lists. Three Elementor posts were therefore missing from the first count and had to be fetched one by one.

The conversion ran directly in the block editor, with the tools WordPress ships with. Every Elementor widget got an equivalent:

ElementorBlock
Text editorParagraphs and lists via wp.blocks.rawHandler
HeadingHeading at the same level
ImageImage in the “large” size, alt text from the media library
HTMLCustom HTML
Image carouselGallery
VideoEmbed
Button, icon list, quoteButtons, list, quote
Multi-column sectionColumns
Google MapsLink “View on Google Maps” with the address

We deliberately did not rebuild the maps as maps. An embedded Google Map loads data from Google on every visit, before anyone needs the map. A link opens the same address, costs nothing and only transfers data when someone clicks. Elements that were hidden on desktop in Elementor were left out. That affected 14 elements, all on the home page.

Trap 1: the empty HTML block

The obvious way to create an HTML block is wp.blocks.createBlock('core/html', { content: html }). In WordPress 7.1 this block then saves empty, as <!-- wp:html /-->. We only noticed in the check, because some pages suddenly had only 43 to 63 percent of their words. The route that works is parsing a finished block:

const block = wp.blocks.parse(
	'<!-- wp:html -->
' + html + '
<!-- /wp:html -->'
)[0];

Trap 2: stray block markers and nested headings

The stray block markers in Elementor texts produced 75 invalid blocks in the first run. So we removed them before converting. After that, 30 invalid headings remained: Elementor titles that contained another heading or paragraph, including a hard-coded font. We cleaned those up beforehand as well. In the end exactly one invalid paragraph was left, which we checked and kept.

The check: word by word

For every item we collected all words from the Elementor data and counted how many of them appear in the converted result. All 58 were between 99.5 and 100 percent. We also looked at four test drafts in the new theme before anything went live.

Writing without knocking the site over

The site runs on low-cost hosting, where saving a single post takes 20 to 30 seconds because SEO, cache and security plugins all do their work on every save. 58 saves in a row can bring such a database to its knees. So the write run was throttled: a three-second pause after every save, a measurement of the uncached home page after every 15 saves, and an abort if the response took longer than 3.5 seconds.

One measurement came in at 5.0 seconds. The run waited a minute, measured again (1.6 seconds) and carried on. In the end: 58 writes in 14 minutes, zero errors, and in five samples the saved content matched the converted content character for character.

We did not touch the Elementor data itself. Elementor and OceanWP are deactivated but still on the server. Reactivating both brings the old site back.

Switching the theme to Hafen

Hafen is our own block theme, free in the WordPress directory. Since WordPress 6.3 you can set up a block theme in the preview before activating it. That is how we built the menu and footer while the site was still running on OceanWP.

Along the way we found two bugs in our own theme. After activation, the default footer shows a sample company with a placeholder address, and a navigation without an assigned menu lists every page of the website. On a site with many city and sauna pages, that is a very long menu. We replaced both with custom versions beforehand and noted them for the next theme update.

The order when switching: deactivate Elementor and its extensions first, then activate Hafen, then switch off the OceanWP add-ons. After that, clear the page cache once.

The new design

Hafen provides the frame. We built the look of schwule-beziehung.de through the global styles and custom templates, without changing a single theme file:

  • Contrast: the old brand blue had a contrast of 2.5:1 on white, too pale for links and buttons. The new, darker blue reaches 6.8:1.
  • Fonts: system fonts only, no font files, no Google Fonts.
  • Header: logo, search, a topic bar with a city menu and a slim rainbow stripe as a signature.
  • Home page: search first, then new posts, topics, cities and the coaching offer. The old home page moved in full to its own coaching page.
  • Posts: a calm reading column, the first paragraph as an answer box, a visible table of contents.

Do not forget the internal links

OceanWP had a sidebar with categories, latest posts and notices. That was around 30 internal links on every page. A block theme with a slim reading column no longer shows them, and search engines suddenly see far fewer connections between posts. We replaced them: at the end of every post there are now six posts from the same category, the category itself and the neighbouring posts with their titles. That is 27 to 29 more links per post than right after the switch. One guide went from 20 to 48, for example.

The numbers

Measured with Lighthouse 13.6 locally, mobile, using the same procedure before and after the rebuild:

PagePerformanceLCPRequestsTransferred
Home page before606.1 s961,531 KB
Home page after981.2 s18284 KB
Frankfurt city page before972.1 s1281,468 KB
Frankfurt city page after991.2 s18354 KB

On desktop, every measured page scores 100. Accessibility, best practices and SEO are at 100 in all runs, layout shift at 0. Without cache, the server now responds in 0.8 to 1.0 seconds instead of 1.4 to 2.5, because far fewer plugins run on each request. One post with a large featured image narrowly misses the 2.5-second target for the largest contentful paint, at 2.7 seconds. A smaller image helps there, not the theme.

The city page shows that a good Lighthouse score does not tell the whole story. It already scored 97 before, but it loaded 128 files and almost 1.5 MB to get there. Anyone opening it on a weak mobile connection clearly notices the difference to 18 files.

What you can take away for your own website

  • Convert from the Elementor data, not from the post content. The HTML copy in the post content is a fallback and often out of date.
  • Check every page with a word comparison. Looking at ten pages will not find an empty HTML block on the eleventh.
  • Leave the Elementor data in place. As long as _elementor_data stays untouched, the way back is one click on “Activate”.
  • Write with throttling. On shared hosting, saving in bulk is a real load. Pauses and a measurement in between cost minutes and save you an outage.
  • Set up the new theme in the preview. Menu, footer and home page are then ready before the first visitor sees them.
  • Replace the links from the old sidebar. Count a post's internal links before and after the switch. If 30 are missing afterwards, search engines notice first.

Reasons for moving away from Elementor and what the alternatives can do are covered in Elementor alternative. How Hafen compares with other block themes is shown in The fastest WordPress block theme, measured. A second theme switch with all the numbers is described in the case study on the theme switch of flirtuniversity.de.

What this case study does not show

The rebuild dates from 18 November 2026. How speed and the new design affect rankings and visitors we have not measured yet, so we do not claim anything about it. The Lighthouse scores are lab measurements. How fast the site loads for real visitors will only show in Google's field data after a few weeks.

Is your website stuck on Elementor?

We convert your Elementor pages into regular blocks, check every page word by word and measure before and after. The Hafen theme is free in the WordPress directory.

Send an enquiry

Frequently asked questions

What happens to my pages if I simply deactivate Elementor?

WordPress then shows the regular post content. Elementor does store a plain HTML copy there, but it is often outdated or incomplete, and layout, columns and widgets are missing. The real content lives in the _elementor_data field. If you deactivate without converting, you often see old text or broken pages.

Can Elementor pages be converted to blocks automatically?

Yes, from the Elementor data. Text, headings, images, lists, buttons, galleries and columns all have a direct equivalent in the block editor. What matters is a check afterwards: is every word of the old page also in the new one? In our case coverage was at least 99.5 percent for all 58 items.

Can I go back if something does not fit after the switch?

If you do not delete the Elementor data, yes. We only rewrote the post content and left _elementor_data untouched. Elementor and the old theme are deactivated but still installed. Reactivating both brings back the old state, and the previous content is also kept in the revisions.

Back to blog A post by hafenstudios