GuyGas Inc. - Industrial, Medical & LPG Gas Supply
From a one-page placeholder to a product, safety and recruitment website
GuyGas Inc. supplies LPG and specialty gases across Guyana, and its website was a single page that described almost none of that. Firelinkx rebuilt it as a static Next.js site covering every product and market, LPG safety guidance and a recruitment notice with a fixed closing date.
Updated · By Timothy Indarsingh
Case Study
Replacing a placeholder with a product, safety and recruitment website
GuyGas Inc. supplies LPG and specialty gases to domestic, commercial, industrial and medical customers across Guyana. Its public website was a single WordPress and Elementor page whose browser title still read "Elementor #555".
Firelinkx rebuilt the site as a statically rendered Next.js application: eight gases with their cylinder sizes and applications, the four markets GuyGas serves, LPG safety guidance, company background, an enquiry and quote path, and a recruitment notice that had to be live before a published closing date.
Every line of copy traces to a wording document the client approved, and the mapping is recorded in the repository. The site went live on the client's existing hosting, the recruitment notice went from a dead link to a working page the same day, and the WordPress install was retired.
The Challenge
The old site said very little, and a circulated recruitment link was landing on a dead page.
The public surface of the WordPress install was enumerated from its own sitemap before anything was replaced. It came to three pages: a home page, a "coming soon" page and a default first post. Eight gas products, four customer markets and the company's safety guidance had no presence at all, so the site could not be found for any of them.
Recruitment added a deadline. GuyGas was circulating a specific URL for an Expression of Interest with a fixed closing date, and that URL returned a 404 on the live site. Anyone already holding the link was arriving at an error page.
Hosting set the third constraint. The site had to run on the client's existing shared cPanel account, behind Passenger, on a plan whose process limits turned out to matter.
Project Goals
The rebuild had to serve customers, the sales team and prospective staff at the same time.
Give every product and market a page
Cover eight gases, four customer markets, applications and safety guidance so the site can be found for the products it sells as well as for the company name.
Publish only approved wording
Build every page from the client's wording document, so each statement on the site traces to text GuyGas signed off.
Get the recruitment notice live against a deadline
Stand up the circulated Expression of Interest URL with the full role list, submission requirements and closing date, indexable and readable on a phone.
Make the site fast on modest connections
Prerender every page that has no per-request state, and keep the client off a platform that needs a build server it does not have.
Run reliably on the client's existing hosting
Deploy into the shared cPanel account already paid for, and document the operating rules that keep it stable.
The Solution
A statically rendered Next.js site, deployed as a self-contained server bundle into the client's existing cPanel Node.js application.
Every page without per-request state is prerendered at build time, so most of the site is served as static HTML with no server work. The enquiry and quote routes render on demand, because they read query parameters and accept submissions.
Content lives in typed modules. The source is the client's wording document, which changes rarely and has to stay traceable, so every line on the site maps to that document and the mapping is recorded in the repository. When the client revises a page, the revision is an edit to one module and the page follows.
The site ships its own design system: a brand-tinted elevation scale, a radius scale, and one easing curve used for every entrance and hover. Entrance animation is CSS only, with no JavaScript deciding whether content is visible.
The home page opens on a strip of four facts: the number of gases supplied, the number of markets served, the supply formats, and the plant location. Each one is counted from content already on the site or taken from the client's wording document.
Copy a regulated supplier can stand behind
A gas supplier's website is read by customers, insurers and regulators, so Firelinkx applies one discipline to every line of copy.
One approved source
Every statement traces to the client's wording document and the mapping is recorded, so a question about any line on the site has a documented answer.
Facts are counted
The hero and the product pages carry figures counted from the site's own content, such as the number of gases and markets, alongside the client's approved wording. Superlatives are not used.
Certifications are tied to their evidence
Any statement that depends on a certificate, a test result or a supplier specification is tied in the codebase to the document that supports it, so a claim can be traced to its evidence and updated when the evidence changes.
Revisions are edits
Because content lives in typed modules, a change to a notice, a product or a contact detail is one edit in one place, and the page follows.
A recruitment notice with a closing date
The Expression of Interest was already being circulated when the rebuild began, and the page had to outlive the first version of its link.
Live the day the site launched
The circulated URL went from a 404 to a full notice: twenty positions, submission requirements, the closing date and the client's own limitation notice, with the authoritative PDF alongside.
The notice is data
Roles, deadline and submission requirements live in one typed module. When GuyGas issued an updated notice, the page was rebuilt from the new document by editing that module, and the superseded PDF path now redirects to the current document.
Circulated links keep working
GuyGas later chose a new URL for the notice. The earlier address redirects to it, so every link in an inbox and every printed QR code still resolves.
Planned for the day after the deadline
The redirect is deliberately temporary, so after the closing date the page can become a "submissions closed" notice without fighting a permanently cached redirect in candidates' browsers.
Key Features
Full product range
Eight gases with cylinder sizes, bulk capacities and the applications each one serves, so customers can confirm GuyGas supplies what they need before contacting anyone.
Applications by market
Domestic, commercial, industrial and medical sections, each linking through to an enquiry form that arrives pre-filled with that customer type.
LPG safety guidance
Cylinder handling, storage, maintenance and a numbered leak procedure, marked up so the leak steps are machine-readable as well as legible.
Enquiry intake that keeps the lead
Every submission is recorded on the server before any email is attempted. If delivery fails, the visitor is told plainly and given the phone and WhatsApp numbers.
Works without JavaScript
The enquiry and quote forms, their pre-filled selects and their confirmation are all in the server-rendered HTML, so a submission succeeds on a slow connection or a locked-down browser.
Accessible by construction
Visible focus outlines, a reduced-motion path that disables every animation, semantic heading order maintained even where the design shows no visible heading, and no information carried by colour alone.
Technical SEO Approach
The site was audited before it was optimised, and the audit found no structured data and page titles spent on slogans and navigation labels.
Titles and headings were rewritten so each page names the products and the country. The home page's brand line is still the largest text on screen, but it is no longer the H1, because the strongest on-page ranking signal should name what the page is about. Every client line displaced this way was preserved elsewhere on the site, and the mapping was documented.
Structured data was added for the business, the site and the safety FAQ. The FAQ markup is generated from the page's own visible content, so the two cannot drift apart.
Several properties were left out on purpose. Opening hours, coordinates, price range and ratings are all supported by the schema, and none of them were in the approved content. Publishing a guess would have produced either an inaccurate listing or, for ratings, a penalty risk.
Hosting and Operations
An early redeploy tipped the hosting account over its process ceiling for about an hour. Diagnosing it produced an operating rule every later deploy has followed.
The ceiling counts threads
The account showed almost no memory or CPU use during the outage. The limit being hit was the process ceiling, which on this platform counts threads, and a single Node.js instance was eleven of them.
Restart does not reap the old instance
Measured directly: after a restart the previous process was still running a hundred seconds later and stayed until stopped by hand. Every redeploy had been adding another instance.
A redeploy has a definition of done
It is finished when exactly one application instance is confirmed running and older processes have been stopped. The rule is in the runbook, and each later deploy has been verified against it, with the account settling at around a fifth of its ceiling.
Each instance was made cheaper
Constraining the runtime's thread pools took a fresh instance from eleven threads to seven, which leaves the account with headroom on every deploy.
Cutover in place
The Node application replaced WordPress in the same document root. The old front controller was removed, the retired install was moved out of the web root, www now redirects to the apex, and certificate renewals were kept working under Passenger.
Rollback is three commands
The previous build is retained beside the live one, and the runbook records the rollback and the reaping rule, written so someone other than its author can run them.
Outcome
GuyGas has a site that describes its full business, loads fast on a phone and runs on hosting the company already pays for.
The WordPress install has been retired. The site now covers the products, markets and safety guidance that previously had no page at all, with structured data describing the business, the site and the safety FAQ.
The recruitment notice is live at the address GuyGas circulates. When the client updated the notice and later chose a new URL for it, the page was rebuilt from the new document and both earlier addresses redirect, so no link or QR code already in circulation has broken.
Warm responses measure under a third of a second on the client's shared hosting, the deployment procedure is documented to the level that lets someone other than its author run it, and the account has stayed well inside the limit that caused the outage.
Project Links
The live site and the recruitment notice built against a fixed deadline.
GuyGas Inc. Website
The rebuilt product, applications, safety and company site for GuyGas Inc., serving domestic, commercial, industrial and medical customers across Guyana.
Visit GuyGasExpression of Interest
The time-limited recruitment notice, carrying the full role list, submission requirements and the client's own limitation notice alongside the authoritative document.
View the noticeServices Delivered
Need a System Like This?
Let's discuss the workflow, controls, and outcomes your business needs.