Frequently asked questions

No formal compliance guarantee is included in the standard scope. We use sensible accessibility best practice, while formal WCAG work, audits or certification can be quoted separately.

No. We use an efficient underlying framework, but the visual direction is created around your business, brand and content.

A page template is a reusable structure. For example, one service template can support several individual service pages using the same underlying layout.

Yes. The standard website is designed and tested across desktop, tablet and mobile.

Yes. Agreed content migration within the standard scope is included. Large archives or more complex historic content may require additional migration work.

Yes. DNS, domain and SSL changes can form part of the migration work where required.

Yes. We can migrate the website and database and handle backups, DNS, SSL and post-migration testing.

Yes. We check important pages, forms and functionality after migration to make sure the site is behaving as expected.

Yes. Appropriate backups are part of a sensible migration process.

Yes. Inherited websites are a normal part of what Upkeep is designed to support.

Yes. We can retain agreed content and structures where they still make sense while improving the areas that need to change.

Potentially. We can review the plugin stack and identify unnecessary, outdated or problematic plugins where they are contributing to performance problems.

No. Performance depends on the theme, plugins, hosting, third-party scripts, ecommerce and custom code. We’ll tell you what is realistically achievable.

Yes. We can review images, caching, plugins, front-end files, hosting, CDN setup and general WordPress housekeeping.

Potentially, yes. We’ll review how the site has been built, including the theme, child theme, plugins and any custom code, before recommending the safest route.

Send us the website address. We’ll take a look at the setup before confirming whether we can confidently support it.

Our core platform support includes Elementor, WPBakery, Jupiter / Jupiter X and WooCommerce, alongside inherited and custom WordPress setups.

Yes. We can help maintain, fix and improve existing WPBakery websites rather than automatically assuming they need replacing.

Common signs include unsupported themes, recurring plugin problems, expensive routine changes, poor usability and a platform that is holding the business back.

When basic changes are becoming disproportionately expensive, the software is unsupported or recurring issues are consuming more time and money than a cleaner replacement would.

Yes. If the foundations are still sound, we can improve layouts, performance, responsive behaviour, plugins and content without starting again.

Often, yes. We can improve layouts, navigation, hierarchy, responsive behaviour and content without automatically replacing the entire site.

Not automatically. If it remains supportable and useful, repairing it can make sense. If routine changes have become expensive or the underlying software is no longer supported, rebuilding may offer better long-term value.

We can review how users move through key pages, how calls to action are presented and where obvious friction may be getting in the way.