CASE STUDIES

HydrantSystem Website Rebuild From Scratch After the Old Site Was Lost

Willya Randika |
HydrantSystem website case study

This case study did not start with a normal redesign. It began with an emergency: the old website could no longer be restored because the hosting and domain had not been renewed for too long, and there was no backup available.

The rebuilt website was hydrantsystem.co.id, which continued the earlier site from firesystem.co.id.

Short Summary & Key Takeaways

Starting Point

Old site lost, no backup available

Solution

Full rebuild from scratch

Core Stack

GeneratePress + GenerateBlocks

Desktop PageSpeed

100 / 98 / 100 / 92

If your old website is already gone from the server and there is no backup, let’s discuss it first via a free consultation so we can choose the right recovery and rebuild path.

Project Timeline: From Quick Fix to Full Rebuild

June 10, 2024: 404 Errors After Hosting Migration

On June 10, 2024, the PT Rasa Nday Suksindo team contacted me because their website, firesystem.co.id, was showing a problem after migration to Hostinger: every page except the homepage returned a 404 Not Found error.

This is a classic WordPress issue and is often related to permalink configuration or rewrite rules. After the client explained the symptoms, I was able to fix it within minutes.

October 29, 2025: The Old Website Could No Longer Be Restored

The client contacted me again on October 29, 2025 to reactivate the website that had been inactive because the domain and hosting were no longer renewed.

The challenge was straightforward:

  • It had been more than a year since renewal.
  • The old website data had already been removed by the provider.
  • There was no backup from the client.

That meant restore was no longer an option. The only realistic path was to rebuild the website from scratch.

After a call discussion, we agreed on a full rebuild, I prepared the proposal, and then the rebuild work began.

Technical Approach and Architecture

Theme and Builder Foundation

The main stack I used was:

  • GeneratePress as the base theme.
  • GenerateBlocks as the page builder.

The reason was the same as in most of my projects: lightweight, flexible, and much easier to maintain long term compared with a heavy stack.

A More Lively Homepage Hero with AI Video

To improve the first impression on the homepage, I used Gemini AI to generate a short video for the hero area. That made the opening section feel more alive without adding unnecessary heavy elements.

Hero HydrantSystem

Product Pages Without WooCommerce, by Design

One of the most important decisions in this project was not to use WooCommerce for the product catalog.

Why?

  • The business did not need cart, checkout, or order automation.
  • Transactions were handled manually through WhatsApp.
  • Using WooCommerce only to get shop and single-product pages would add features the business would not actually use.

Instead, I built the shop and single-product pages using:

  • custom post types through Secure Custom Fields (SCF)
  • layout and template handling through GeneratePress Elements

This kept the experience looking professional while making the architecture lighter and better aligned with the actual business need.

Plugins Used

The project used these plugins:

  1. Carousel Slider Block
    For rotating testimonials, video documentation, and photo galleries.

  2. Fluent Snippets
    For custom snippets.

  3. GenerateBlocks
    As the main page builder.

  4. GP Premium
    For extra GeneratePress Pro features.

  5. LiteSpeed Cache
    Chosen because Hostinger uses LiteSpeed Web Server, so it was the most sensible cache option.

  6. NinjaFirewall (WP Edition)
    For an additional security layer.

  7. Safe SVG
    For SVG logo assets.

  8. Secure Custom Fields (SCF)
    For custom post types and custom fields.

  9. Slim SEO
    Lightweight SEO plugin that fit the project’s needs.

  10. WA Floating Chat
    Our internal plugin for a floating WhatsApp chat widget.

  11. WC Product Gallery
    For the single-product gallery so it still felt similar to a WooCommerce experience, while the data was managed through custom fields.

Before vs After

Homepage

Old homepage before:

Homepage before HydrantSystem

New homepage after:

Homepage after HydrantSystem

About Page

About page after HydrantSystem

Shop / Product Page

HydrantSystem shop page

Performance Results

Desktop PageSpeed results:

  • Performance: 100
  • Accessibility: 98
  • Best Practices: 100
  • SEO: 92

HydrantSystem desktop PageSpeed

Business and Operational Impact

After the rebuild:

  • The website was active again with a more modern structure.
  • The presentation looked more professional and aligned with the business positioning.
  • Content management became easier for day-to-day work.
  • The technical architecture stayed lightweight because features were only built where they were actually needed.

Lessons from This Project

  1. A website without backup can still be rescued as a business asset through the right rebuild strategy.
  2. Not every product website needs WooCommerce, especially when the transaction flow is manual via WhatsApp.
  3. Choosing a lightweight stack that matches the real business need usually gives better long-term stability.

Want to Rebuild Your Website with a Similar Approach?

If your website can no longer be restored, or if you want to rebuild it with a lighter and more maintainable stack, we can start with a needs audit first.

You can also explore our website development service and custom WordPress plugin service depending on the project scope.

Willya Randika

Willya Randika

Founder of Harun Studio, web developer, blogger, and hosting reviewer. He helps business owners build healthier websites through design, development, and long-term maintenance.

Related Articles

Explore more insights that connect closely with this topic.