{"id":636,"date":"2021-06-28T09:09:00","date_gmt":"2021-06-28T08:09:00","guid":{"rendered":"https:\/\/targetict.co.uk\/blog\/?p=636"},"modified":"2021-06-27T09:09:35","modified_gmt":"2021-06-27T08:09:35","slug":"wordpress-site-to-static-html-conversion","status":"publish","type":"post","link":"https:\/\/targetict.co.uk\/blog\/wordpress-site-to-static-html-conversion.html","title":{"rendered":"WordPress site to static html conversion"},"content":{"rendered":"

WordPress site to static HTML conversion is a project we are carrying out at the moment and we decided to write on this to create more insight for any website owner who is having thoughts of doing something similar since the more popular conversion is HTML to WordPress.<\/p>\n

According to the hosting tribunal<\/a>, WordPress, which is available in 57 languages, powers 39.5% of the internet and 64% of content management system (CMS) websites globally are built with it.<\/p>\n

The widespread use and adoption of WordPress as the platform of choice for most new website builds has been as a result of the ease of use and deployment as well as the large community with a vast range of themes, plugins and other customisation option that makes it possible to build almost anything with it as a base. It is also easy to learn, so it’s easy for anyone to be a “web developer” after 3 days of playing with a page builder.<\/p>\n

The easiest part of the CMS is deploying it though, if you have used WordPress long enough, you most likely have had issues with website speed, having to return over and over to make updates, security issues as well as complex gremlins (especially with page builders).<\/p>\n

A lot of WordPress website owners after deployment get hit with higher hosting bills (as a result of the larger size and resource intensive nature) and more spending on monthly or annual maintenance.<\/p>\n

While WordPress is an awesome platform (we build on WordPress a lot<\/a> too,) for a small website with no blog<\/a>, no e-commerce functionality<\/a> and no need to update information regularly, it tends to be overkill as a plain WordPress installation with zero customisations has over 5,000 files & the plugins and themes that get added while customising also add a lot to the overhead.<\/p>\n

This issue was what we discussed with a prospect (now client) at the start of last week. The client, a Hong Kong based steel firm had a basic, one pager website which just displayed company details and a contact form but was built with WordPress.<\/p>\n

The website kept getting compromised<\/a> and kept breaking with every major PHP update (the latest was with the update to PHP 8.0 a few weeks ago) and the client was frustrated with the constant disruption.<\/p>\n

We decided to find a solution and after looking at the website, which was a basic one-pager – no blog, no e-commerce functionality realised the issues. There were 23 active plugins in the backend, the theme license seemed dodgy and the site was really slow to load,.<\/p>\n

We agreed then that the best option would be to convert the WordPress (WP) site to static HTML while maintaining the layout and functionality as the client was on a budget.<\/p>\n

We do a lot of HTML to WordPress conversions,<\/a> so this was a lot different from the usual as we would usually just build static websites from scratch and then create a custom WP theme based on the site layout to serve as the blog<\/a> (this website is an example. The entire website is static with only the blog pages using WordPress.)<\/p>\n

The Process<\/h3>\n