A practical checklist to help business owners decide whether a slow or outdated website needs fixing or a full rebuild, with honest timelines for each path.

Most slow business websites do not need a rebuild. They need a focused set of fixes to speed, structure, schema and business details. A rebuild is worth considering only when the site’s foundations are broken, for example when it cannot be updated, is not mobile-friendly, or keeps breaking after every fix. Start by checking the existing site against a clear checklist. Then decide.

This guide gives you that checklist in plain language. It also covers the common mistakes, a realistic example and what to expect for timelines on either path.

Why does the rebuild vs optimise decision matter so much?

Choosing between a rebuild and optimisation affects your budget, your timeline and the search visibility you already have.

A rebuild often feels like the clean answer. The site looks old, it loads slowly, and a new one promises a fresh start. But a rebuild has real costs beyond the build itself:

• Time. Planning, design, content and testing take weeks or months. During that time, the old problems are still there.
• Risk to existing rankings. If page addresses (URLs) change without proper redirects, pages that already show up on Google can drop out.
• Lost content. Useful older pages, such as service pages or FAQs, sometimes get left behind in a move.
• The same problems, repeated. If the new site is built without search in mind, you can end up with a newer-looking site that has the same issues.

Optimising the existing site is usually faster and lower risk. It also tells you something useful. If the fixes work, you saved the cost of a rebuild. If they do not, you now know exactly why a rebuild is needed and what the new site must get right.

What is the difference between optimising and rebuilding a website?

Optimising means improving the site you already have. Rebuilding means replacing it with a new one.

What optimisation usually includes

• Compressing large images and removing unused plugins or scripts
• Setting up caching, which stores ready-made copies of pages so they load faster
• Fixing broken links, missing page titles and unclear headings
• Adding schema markup, which is code that tells search engines and AI assistants what your business is and what each page is about
• Making your business name, address, phone number and services consistent across your site and other listings
• Improving or rewriting key pages so they answer customer questions clearly

What a rebuild usually includes

• A new design and page layout
• A new theme, page builder or platform
• Moving content across, often with rewrites
• Setting up redirects from old page addresses to new ones
• Rebuilding forms, booking tools and integrations

Both can improve search visibility. The question is which one your site actually needs.

The five-part checklist: does your site need fixing or rebuilding?

The fastest way to decide is to check five areas: speed, structure, schema, brand details and the quality of the original build.

Go through each one. For most areas, the problems you find will be fixable. Pay attention to the “rebuild signals” in each section. One signal alone rarely means you need a new site. Several of them together often do.

1. Speed: why is my site slow?

Most website slowness comes from a few fixable causes, not from the site being “too old”.

Start with Google’s free PageSpeed Insights tool. Test your home page and one or two key service pages on mobile, because that is how many Filipino customers browse. The tool reports on Core Web Vitals, which are Google’s measures of how a page feels to use. In simple terms, they check three things:

• Loading: how quickly the main content appears
• Responsiveness: how quickly the page reacts when someone taps or clicks
• Visual stability: whether things jump around while the page loads

Usually fixable: oversized images, too many plugins, no caching, slow web fonts, heavy sliders or video backgrounds, and cheap or overloaded hosting.

Rebuild signals: the theme or page builder adds heavy code to every page and cannot be trimmed, speed drops again soon after each round of fixes, or the site relies on outdated tools that no longer receive updates.

2. Structure: can search engines and AI assistants understand your site?

A well-structured site makes it clear what you offer, where you are and which page answers which question.

Check the following:

• Does each main service have its own page, or is everything crammed onto one page?
• Does each page have one clear main heading and logical subheadings?
• Can a visitor reach any important page within a few clicks of the home page?
• Are your opening hours, location and contact details easy to find?
• Do key pages answer the questions customers actually ask, such as “How much is a consultation?” or “Do you deliver to Makati?”

Usually fixable: missing service pages, weak headings, thin content, poor internal linking and unclear menus. These can almost always be improved on the existing site.

Rebuild signals: the site cannot add new pages without a developer, the menu structure is locked in by the theme, or the whole site is built as images or a single long page that cannot be split up.

3. Schema: does your site describe your business in a way machines can read?

Schema markup is a layer of code that labels your business details, services, reviews and FAQs so search engines and AI assistants can read them reliably.

Visitors never see it. But it can help search engines show richer results and helps AI assistants understand who you are. You can test any page with Google’s free Rich Results Test.

Usually fixable: no schema at all, incomplete local business details, or missing FAQ and service markup. On WordPress, schema can usually be added through a plugin or added directly to page templates.

Rebuild signals: very few on their own. Schema can be added to almost any site. It only becomes a rebuild factor when it sits alongside other deep problems.

4. Brand details: is your business information the same everywhere?

Your business name, address, phone number and services should match across your website, your Google Business Profile, social pages and directories.

Inconsistent details are common in the Philippines. A clinic moves from one floor to another. A restaurant changes its mobile number. A firm writes “Brgy.” in one place and “Barangay” in another, or lists an old branch that has closed. Each small difference makes it harder for Google and AI assistants to be confident about who you are and where you are.

Check:

• Your website footer and contact page
• Your Google Business Profile
• Your Facebook page and other social profiles
• Online directories and booking or delivery platforms you use

Usually fixable: almost always. This is clean-up work, not a website problem. A rebuild will not fix inconsistent listings elsewhere on the web.

Rebuild signals: none. This is a good example of a problem a new website cannot solve by itself.

5. Past build quality: was the site built to be maintained?

The original build matters because it decides how easy, safe and affordable every future fix will be.

Ask yourself:

• Can you or your team log in and edit text and images without help?
• Are WordPress, the theme and plugins up to date, and can they be updated without breaking the site?
• Do you have full ownership of the domain, hosting and admin access?
• Does the site display properly on phones?
• Is it secure, with an SSL certificate (the padlock in the browser)?

Usually fixable: out-of-date plugins, missing SSL, small mobile layout issues and access problems that can be resolved with your old developer or host.

Rebuild signals: the site is built on an abandoned theme or custom code nobody can maintain, it is not mobile-friendly at its core, updates repeatedly break it, or you cannot get full access to your own site.

Quick comparison: fix it or rebuild it?

Area	Usually fixable on the existing site	Signals a rebuild may be worth considering
Speed	Large images, too many plugins, no caching, weak hosting	Heavy theme code that cannot be trimmed; speed falls again after every fix
Structure	Missing service pages, weak headings, thin content, poor menus	Cannot add pages; layout locked by the theme; site built as images
Schema	Missing or incomplete markup	Rarely a rebuild reason by itself
Brand details	Inconsistent name, address, phone or services	Not a rebuild reason; fix through clean-up
Build quality	Outdated plugins, missing SSL, minor mobile issues	Abandoned theme, broken updates, not mobile-friendly at its core, no admin access

A simple rule of thumb: if most of your problems sit in the middle column, optimise. If several sit in the right-hand column, especially under speed and build quality, a rebuild deserves a serious look.

A realistic example: one site fixed, one site rebuilt

The following two scenarios are illustrative, not real clients. They show how the same complaint, “our website is slow”, can lead to different answers.

Scenario A: a family restaurant in Quezon City

The owner feels the site is outdated and asks about a new one. The checklist shows:

• Menu photos uploaded straight from a phone, each one very large
• Over a dozen plugins, several unused
• No caching
• An old phone number on the website and a different one on the Google Business Profile
• No schema for the restaurant’s location and opening hours
• A WordPress theme that is still supported and easy to edit

Every issue sits in the “fixable” column. Compressing images, removing plugins, adding caching, correcting the phone number everywhere and adding local business schema can all be done on the current site. The design can be refreshed with new photos and clearer menus later if needed. A rebuild would cost more and take longer, without solving anything the fixes cannot.

Scenario B: an accounting firm in Cebu City

The firm’s site was built years ago by a freelancer who is no longer reachable. The checklist shows:

• The theme is no longer updated and breaks when WordPress is updated
• Pages are slow even after images are compressed
• The layout does not adjust properly on phones
• Staff cannot edit services without the page layout breaking

Here, the problems sit mostly in the rebuild column. Patching would mean ongoing cost with limited benefit. A rebuild is reasonable. Even so, the useful parts of the old site, such as service descriptions and existing page addresses, should be kept or redirected so that any visibility the firm already has is protected.

What are the most common mistakes when deciding?

The most common mistake is rebuilding to fix problems that a rebuild does not actually solve.

• Rebuilding for looks alone. A fresh design can help visitors, but it does not by itself make a site faster or easier for search engines to understand.
• Skipping redirects. When old page addresses disappear without redirects, visitors and search engines hit dead ends.
• Ignoring off-site details. A new site will not fix an incomplete Google Business Profile or old directory listings.
• Testing on desktop only. Many customers find local businesses on their phones. Always test mobile first.
• Adding plugins to fix plugins. Each extra plugin can add weight. Removing is often better than adding.
• Launching a rebuild in a busy season. If enrolment, holiday bookings or tax season drives your leads, avoid a major launch right in the middle of it.

How long will it take to see results?

Technical fixes can show effects within weeks, while ranking and AI citation gains usually build over three to six months.

Speed improvements are often visible soon after the work is done. You can re-test pages and see the change. Search engines then need time to recrawl your pages, and visibility in rankings and AI assistant answers tends to build gradually. Results vary by industry, location and competition. Anyone who promises fixed rankings or AI mentions by a set date is promising something no one can control.

A rebuild adds its own timeline before any of this starts, because the new site has to be planned, built, tested and launched first.

A step-by-step way to make the decision

1. Audit first. Run through the five-part checklist above, or have it done for you.
2. List the problems in two columns. Fixable now, and signs of deeper issues.
3. Make the quick fixes. Images, plugins, caching, brand details and schema are usually the best starting points.
4. Measure again. Re-test speed and check whether pages are easier to edit and understand.
5. Decide with evidence. If the site improves and stays stable, keep optimising. If problems return or the build blocks progress, plan a rebuild that keeps what already works.

How does Archlabs approach this?

At Archlabs, we work on your existing site before we suggest a rebuild. Our process is simple: audit, plan, implement and report. We look at speed, structure, schema and brand consistency together, because they affect how you show up on Google, in answer boxes and in AI assistants like ChatGPT.

When a rebuild genuinely makes sense, we build on WordPress with Breakdance, and our sites are built to pass Core Web Vitals. Either way, you get fixed-scope packages and plain-language monthly reports covering rankings, answers won and AI citations. You can see how Archlabs helps businesses get found on Google and recommended by AI assistants.

Not sure which path your site needs?

You do not have to guess. A short, honest review of your current site will usually show whether fixes are enough or whether the foundations need replacing.

Our free visibility audit looks at how your business appears on Google and in AI assistants, and it includes three quick wins you can act on. It will not fix your site by itself, but it will give you a clear starting point. Book a free visibility audit and we’ll show you three quick wins.

Frequently asked questions

Will a new website automatically rank better on Google?

No. A new website does not automatically rank better. Visibility depends on speed, clear structure, useful content, schema and consistent business details. A rebuild can help if the old site blocked those things, but a poorly planned rebuild can also lose existing visibility if page addresses change without redirects.

How do I know if my WordPress site is too slow?

Test your key pages on mobile using Google’s free PageSpeed Insights tool. It reports on Core Web Vitals, which measure loading, responsiveness and visual stability. If pages feel slow on your own phone over mobile data, your customers likely feel it too. Common causes such as large images, too many plugins and no caching are usually fixable without a rebuild.

Is Breakdance good for SEO?

Breakdance is a WordPress page builder that can support fast, well-structured sites when it is set up carefully. Like any tool, the results depend on how the site is built: clean layouts, optimised images, clear headings and proper schema matter more than the builder alone. Archlabs uses WordPress with Breakdance for web builds, and our sites are built to pass Core Web Vitals.