NeoDigify website home page shown on desktop, laptop, tablet and phone screens

Explore more from:

Migration

WordPress + Elementor Pro to WordPress + Gutenberg block theme

NeoDigify

NeoDigify is our own agency, and we moved our website from Elementor to Gutenberg without changing how it looks to visitors. We work as a white label development partner on WordPress and Shopify. We build custom WordPress themes, Shopify themes and apps, cross-platform mobile apps in React Native, and UI/UX design for web and mobile. The site is where people browse our portfolio, read our case studies and ask for a quote.

  • CMS: WordPress
  • Theme: custom block theme, replacing Hello Elementor with Elementor Pro and JetEngine
  • Integrations: our own companion plugin (portfolio, quote form, SMTP email log), Yoast SEO, Google reCAPTCHA v3, intl-tel-input phone field, Google Tag Manager, self-hosted fonts
  • Live site: neodigify.com

Before:

Pages on our own site were built and edited in Elementor, on WordPress with Hello Elementor and Elementor Pro. The portfolio lived in a JetEngine post type with its own fields and categories. The home page pulled in dozens of stylesheets and scripts, jQuery included. A speed plugin could have trimmed some of that, but the builder’s own files would still have to load.

The one rule on this job was that visitors had to see exactly the same site on any screen, phones included. So any gain had to come from what sits under the design, not from a new look.

NeoDigify website before and after comparison

What we did:

Our own white label web development agency site left Elementor for a custom Gutenberg block theme and a small companion plugin, and the design stayed exactly as it was.

Rebuilding the same design as a block theme

Every section of the old site is now a block pattern. We edit each one in the Site Editor or stack them into new pages. Colours and fonts are set once as design tokens. No page builder or paid block library runs on the site. The fonts are self-hosted and the front end loads no jQuery. The new build matches the old design at every screen width we checked, from wide desktops down to phones.

Keeping the SEO through the move from Elementor to Gutenberg

We moved the portfolio post type and its fields into the plugin without renaming anything, so each project still lives at the same address. Pages, posts and projects all kept their slugs, Yoast titles and meta descriptions, and the domain stayed the same. That is how the SEO carried over at launch. The sitemap lists the same URLs as before. Only one old address changed. The second page of the portfolio listing now sends a 301 redirect to the first. We tested the new build on desktop and on phones before we switched the live site over. We kept the old Elementor build running on a subdomain to compare the two side by side.

What we added after launch

After the move from Elementor to Gutenberg went live, we kept building:

  • our own quote form, built into the plugin, with reCAPTCHA v3, rate limits, a phone field with country flags, a spam view and an email log
  • gallery images on project pages that load at the size the screen needs
  • text that holds still while the fonts load
  • a numbered timeline on the home page that fills as you scroll
  • button labels that roll letter by letter on hover
  • a footer call to action on every page

Google PageSpeed now scores mobile performance at 96, up from 79, and accessibility rose from 87 to 96.

Our custom WordPress theme for the Checkout Bouncer product site is another lean build with self-hosted fonts.

Results:

  • Homepage requests cut from 80 to 49
  • Gallery images across our project pages trimmed from 59.2 MB to 9.5 MB on desktop
  • Mobile PageSpeed performance score raised from 79 to 96
  • Accessibility score raised from 87 to 96 on mobile and desktop
  • Slugs and Yoast titles unchanged at launch, with one old listing page redirected