diff --git a/docs/best-practices/performance/how-to-enable-pagespeed-booster.md b/docs/best-practices/performance/how-to-enable-pagespeed-booster.md
deleted file mode 100644
index f0f3de21..00000000
--- a/docs/best-practices/performance/how-to-enable-pagespeed-booster.md
+++ /dev/null
@@ -1,126 +0,0 @@
----
-myst:
- html_meta:
- description: Learn how to enable PageSpeed Booster, a reverse proxy that increases
- page speed and performance on Hypernode. Requirements included.
- title: How to enable the PageSpeed Booster? | Hypernode
-redirect_from:
- - /en/best-practices/performance/how-to-enable-pagespeed-booster/
----
-
-
-
-# How to Enable PageSpeed Booster
-
-PageSpeed Booster is a reverse proxy that acts like a filter in front of your website, similar to Varnish. On pages that can be cached,
-it uses many static optimisation techniques to greatly increase the page speed score and performance of your website.
-
-This article will explain how to enable PageSpeed Booster on your Hypernode account.
-
-Requirements
-
-To get started with the PageSpeed Booster (formerly known as Percolate), you must meet the following requirements:
-
-- ***A production environment that is hosted on Hypernode.***
-- ***A development environment hosted on Hypernode containing a copy/mirror of the production site.***
-- ***Varnish enabled on both the production and development environment.***
-- ***Time to thoroughly test the environment with the PageSpeed Booster enabled.***
-- ***The PageSpeed Booster implemented on your development environment according to [these steps](../../troubleshooting/performance/how-to-implement-pagespeed-booster.md#configuring-pagespeed-booster-on-your-development-environment) listed in our documentation.***
-
-## Step 1: Getting started
-
-### Step 1.1: Activation of the PageSpeed Booster
-
-From the main page on your [Control Panel account](https://my.hypernode.com/) go to the "PageSpeed Booster" page under "Performance" by clicking on "Hypernodes" top left corner of your screen.
-
-
-
-On the next page you are able to select which Hypernode Development plan you want to enable the PageSpeed Booster on. When PSB is working correctly on the Development Plan you apply these same steps to your Production plan.
-On this page you can add one or multiple domains for which PSB will be enabled on. Note that both the **[www.example.com](http://www.example.com)** and the non [www](http://www). domain **example.com** must be added. We highly recommend doing extensive testing on a subdomain first before running PSB on your live webshop and domains. For example the subdomain **psb.example.com**
-
-
-
-After adding your domain(s) and accepting the terms and conditions, your PageSpeed Booster will be booted in about a minute or two.
-
-### Step 1.2: The PageSpeed Booster on the Control Panel
-
-When PSB is activated your PageSpeed Booster view on the Control Panel will be changed. This will now show you on which domains PSB is applied, the renewal date, costs, as well as the Security Token. This token can be used for login on your own PSB panel.
-In the top of your screen you can see the PSB CNAME record. This is where you PSB applied domains should point to. This records will look something like this:
-
-**"appname-appname.fsn1.percolate-3.hipex.cloud**"
-
-### Step 1.3: The PageSpeed Booster panel
-
-The next step is to go to your own PSB panel. You can use the orange button to go there or visit your test domain, for example with our test subdomain: Here you will be asked to use your Security Token to get access to the PSB environment.
-
-
-
-## Step 2: The PSB panel
-
-The PSB panel provides all sorts of information and settings about your PageSpeed Booster. We advise the following recommend settings for new users. Go to "Settings" in the top of your screen and change these accordingly:
-
-### Step 2.1: Recommended PSB settings
-
-For the live webshop URL the setting **Site map only** under "General" can be turned to **True**:
-
-
-
-For \*\*[staging.example.com](https://staging.example.com)\*\*this settings can be turned to **False**.
-
-The setting **Purge mode** under "General" can be turned to **DELAYED_BOT**:
-
-
-
-The setting **OPTIMIZED_DIFER_ENABLED** under "Javascript " can be turned to **FALSE**:
-
-
-
-The setting **OPTIMIZE_CSS_COMBINE_ENABLED** under "CSS " can be turned to **FALSE**:
-
-
-
-If you are curious what a specific setting does or means, you can click on the **i**button for additional information.
-
-### Step 2.2: Additional recommend settings
-
-When your webshop has a good sitemap it can be loaded into PageSpeed Booster. This can be done under the settings "General" Sitemaps:
-
-
-
-Take note that [Cloudflare RocketLoader](https://support.cloudflare.com/hc/en-us/articles/200168056-Understanding-Rocket-Loader) is not supported by PageSpeed Booster and therefore should be disabled.
-
-## Step 3: Implementation of the PageSpeed Booster
-
-After following the above steps, it is now time to set up the necessary Hypernode server configuration for the PageSpeed Booster. These steps are written in our article [How to Implement PageSpeed Booster](../../troubleshooting/performance/how-to-implement-pagespeed-booster.md). It is recommended to implement and use PSB first on your Development Hypernode and subdomain setup for PSB testing.
-
-The steps include:
-
-- Configuring PageSpeed Booster on your Development Environment
-- Configure SSL and DNS
-- Configuring Varnish
-- Modifying your Varnish VCL configuration
-- Add the user agent **PSB**to the [allowlist for the ratelimiter](../../hypernode-platform/nginx/how-to-resolve-rate-limited-requests-429-too-many-requests.md#allowlisting-additional-user-agents) in `~/nginx/http.ratelimit` file
-- Turn off ESI Block Parsing
-- Add PageSpeed Booster as Flush Target
-
-## Step 4: Testing of PageSpeed Booster
-
-### Step 4.1: Run PSB and monitor the queue
-
-Go to the PSB panel and open your queue, for our example it is this URL . For the Development Hypernode there is 1 available worker for the web page optimization.
-For the Production Hypernode there are 4 workers.
-The optimization queue will run when pages are visited or when you scan the available **sitemap**(**s**). The button is in the top left of your PSB panel:
-
-
-
-### Step 4.2: Reading out the PSB queue
-
-When the PageSpeed booster tries to optimize your webshop, there are three different situations:
-
-- **Optimized** The page is optimized by the PageSpeed Booster.
-- **Failed-retry** The page could not be optimized by the PageSpeed Booster, but you can run a retry.
-- **Failed** Because of an error within the page, the PageSpeed booster could not optimize the page. The most common cause for this failed optimization is a **parse**error.
-
-## Step 5: Troubleshooting PSB
-
-Keep in mind that PageSpeed Booster is a complex tool that require a lot of testing before it can be pushed to the live site. For example, it is possible that your site has errors in the HTML/CSS code. The PageSpeed Booster will find these errors, and they have to be fixed for the PageSpeed Booster to work correctly. We have created a separate documentation article were we will list some of the more common errors we have seen and how to fix them.
diff --git a/docs/troubleshooting/performance/how-to-implement-pagespeed-booster.md b/docs/troubleshooting/performance/how-to-implement-pagespeed-booster.md
deleted file mode 100644
index d8619471..00000000
--- a/docs/troubleshooting/performance/how-to-implement-pagespeed-booster.md
+++ /dev/null
@@ -1,157 +0,0 @@
----
-myst:
- html_meta:
- description: "Improve your website speed with Hypernode's PageSpeed Booster. Learn
- how to implement it in just a few clicks and get the most out of your website. "
- title: How to implement the PageSpeed Booster? | Hypernode
-redirect_from:
- - /en/troubleshooting/performance/how-to-implement-pagespeed-booster/
----
-
-
-
-# How to Implement PageSpeed Booster
-
-## Requirements
-
-To get started with the PageSpeed Booster (formerly known as Percolate), you must meet the following requirements:
-
-- ***Production environment that is hosted on Hypernode.***
-- ***Development/staging environment that is a copy of live and hosted on Hypernode.***
-- ***Varnish has to be enabled***
-- ***Time to thoroughly test the environment with PageSpeed Booster enabled.***
-
-If you don't have a dev environment, then you can easily acquire one in your Control Panel
-
-After you meet the requirements, you can send us a support ticket that includes the domain name where we can activate PageSpeed Booster on. For example psb..com
-
-After this, we will create a shared Slack channel with you, so we have a central place for the communication.
-
-In this channel, we can quickly communicate during the test period.
-
-Keep in mind that PageSpeed Booster is a complex tool that require a lot of testing before it can be pushed to the live site.
-
-For example, it is possible that your site has errors in the HTML/CSS code. The PageSpeed Booster will find these errors, and they have to be fixed for the PageSpeed Booster to work correctly.
-
-## What is PageSpeed Booster
-
-PageSpeed Booster is a reverse proxy that sits in front of your website, just like Varnish. On pages that can be cached, it uses many static optimisation techniques to greatly increase the pagespeed score and performance of your website.
-
-PageSpeed Booster is build on top of Kubernetes. For each application, a separate PageSpeed Booster instance is started on the cluster. None of the components, settings or version used are shared between applications. This ensures maximum stability and complete control over the update process.
-
-**Internals**
-
-PageSpeed Booster consists of a few components, you should not be bothered by most of them but for the purpose of understanding how PageSpeed Booster works, it is useful to keep these in mind.
-
-- Proxy - Proxy requests to the application backend, creates new optimize jobs and handles API requests.
-- Worker - Runs optimize jobs.
-- RabbitMQ - Jobqueue for optimize jobs.
-- Redis - Caches stored optimized responses.
-- MongoDB - Stores optimize state for optimize requests and handled optimize requests.
-- Chromium - Render engine.
-- Cypress - Test environment.
-- Test server - Test server to mock behavior of a real webserver during tests.
-- Imgproxy - Service for resizing and optimizing images.
-
-## Configuring PageSpeed Booster on your Development Environment
-
-### Configure SSL and DNS
-
-To setup PageSpeed Booster on your development environment you'll need a unique domain. For example you can use, **psb.example.com**. So make sure to follow these steps:
-
-1. Point the DNS of the test domain, **psb.example.com**, to your development Hypernode.
-1. Create the vhost with SSL and Varnish:
- `hypernode-manage-vhosts psb.example.com --https --force-https --varnish`
-1. Now point the DNS to the PageSpeed Booster instance with the records you got at the PageSpeed Booster page in your Control Panel.
-1. Make sure Varnish is enabled on the server: hypernode-systemctl settings varnish_enabled.
-1. Add the user agent **PSB**to the [allowlist for the ratelimiter](../../hypernode-platform/nginx/how-to-resolve-rate-limited-requests-429-too-many-requests.md#allowlisting-additional-user-agents) in\*\*~/nginx/http.ratelimit\*\* file.
-1. Disable the [basic-authentication](../../hypernode-platform/nginx/basic-authentication-on-hypernode-development-plans.md#disable-the-basic-authentication) on the development Hypernode.
-
-### Configuring Varnish
-
-By now you've a valid SSL for your test domain, and pointed it to the PageSpeed Booster instance which now works as a proxy. What's left is that you make the required changes to your **.vcl** so that the PageSpeed Booster is able to optimize your pages.
-
-If you're using the default generated .vcl configuration file from the Magento 2 backend you could replace that **.vcl** with **[this template](https://gist.github.com/hn-support/2478eb5ed8328553de813f524ae12f91)** which we already adjusted for the PageSpeed Booster.
-
-## Configure Varnish on your application
-
-The last step will be configuring Varnish on your application. Below you can find our available documentation for configuring Varnish on the application you’re using:
-
-- [How to configure Varnish for Magento 1](../../ecommerce-applications/magento-1/how-to-configure-varnish-for-magento-1-x.md)
-- [How to configure Varnish for Magento 2](../../ecommerce-applications/magento-2/how-to-configure-varnish-for-magento-2-x.md)
-- [How to configure Varnish for Shopware 5](../../ecommerce-applications/shopware-5/how-to-configure-varnish-for-shopware-5.md)
-- [How to configure Varnish for Shopware 6](../../ecommerce-applications/shopware-6/how-to-configure-varnish-for-shopware-6.md)
-
-## Modifying your Current Varnish VCL configuration
-
-If you already have an existing .vcl active with some customisations specific for your shop you'd have to make some changes to your existing .vcl. Make sure to make the following changes:
-
-### Turn off ESI Block Parsing
-
-Configure Varnish to turn off parsing Edge Side Includes. You can do this by editing the following configuration.
-
-```vcl
-if (beresp.http.content-type ~ "text") {
- set beresp.do_esi = true;
-}
-```
-
-Change it to:
-
-```vcl
-if (!beresp.http.X-Percolate && beresp.http.content-type ~ "text") {
- set beresp.do_esi = true;
-}
-```
-
-Edit the lines that are responsible for setting the Cache-Control header to `"no-store, no-cache, must-revalidate, max-age=0";`. How this looks exactly, depends on your Varnish configuration and could differ per project. >The most common configuration looks like:
-
-```vcl
-# Not letting browser to cache non-static files.
-if (resp.http.Cache-Control !~ "private" && req.url !~ "^/(pub/)?(media|static)/") {
- set resp.http.Pragma = "no-cache";
- set resp.http.Expires = "-1";
- set resp.http.Cache-Control = "no-store, no-cache, must-revalidate, max-age=0";
-}
-```
-
-We'll change the configuration fragment to check if the `X-Percolate` header is present, by using a condition.
-
-```vcl
-# Not letting browser to cache non-static files.
-if (!req.http.X-Percolate && resp.http.Cache-Control !~ "private" && req.url !~ "^/(pub/)?(media|static)/") {
- set resp.http.Pragma = "no-cache";
- set resp.http.Expires = "-1";
- set resp.http.Cache-Control = "no-store, no-cache, must-revalidate, max-age=0";
-}
-```
-
-Remove the following line:
-
-```vcl
-unset resp.http.X-Magento-Tags
-```
-
-Now, save the new .vcl as for example **psb_varnish.vcl**, and all you need to do is reload the varnish configuration into Varnish. This can be done by loading it with a slightly different identifier followed by activating the new config:
-
-```bash
-varnishadm vcl.load psb /data/web/psb_varnish.vcl
-varnishadm vcl.use psb
-```
-
-## Add PageSpeed Booster as Flush Target
-
-With the addition of Pagespeed booster, you'll have to deal with an extra layer of cache that needs to be flushed when demanded.
-
-Add your Pagespeed booster URL to your Magento `http_cache_hosts` configuration:
-
-```bash
-bin/magento setup:config:set \
- --http-cache-hosts=varnish:6081,appname-appname.fsn1.percolate-3.hipex.cloud:80
-```
-
-After the change in your **env.php** perform a cache clean:
-
-```bash
-bin/magento cache:flush
-```