Question

Pointing domain from hinet

Posted August 1, 2021 61 views
WordPressDNSCMSDevelopmentCDN

Hi,

I have a website (home.bltc.com.tw) that is hosted on the Namecheap hosting, and the domain is on the Hinet (https://hinet.net/). It is a WordPress website and currently, it is extremely slow (that’s the main reason for migrating the website). For now, I just need to point the subdomain (home.bltc.com.tw) to the digitalocean, not the main bltc.com.tw domain.

So, I have two questions:

  1. Is there a way to point just the subdomain to the digital ocean hosting?
  2. Which droplet or plan do you recommend for the website? The loading speed is the most important thing for me. Currently, the speed score is 11 on mobile and about 50 on desktop. I try different WordPress plugins for speeding the website loading, but nothing helps.

Thank you!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
2 answers

Hi @lidia90,

In order to point your subdomain to DigitalOcean you need to go where your DNS is being managed. From a quick search I can see your NameServers are:

   Domain servers in listed order:
      admns1.hinet.net
      admns2.hinet.net

This means your Domain’s DNS is being managed by hinet.net. Go to your control panel there and for the A record for your subdomain change the IP address to your Droplet’s IP address you have with DigitalOcean.

For the second point. I’ll recommend starting with the smallest droplet and if needed you can always update to a bigger one.

As for the speed you’ll need to optimize your WordPress and Droplet if you want to make the most out of it.

Hi @lidia90 ,

I’m just posting the typical points you follow to optimize your Droplet and Website, especially if it’s WordPress.

Let’s start with Server Optimization.

When looking at Server/Droplet Optimization, there are a few necessary services/packages that are universal.

  • The first one would be Server-side caching. Server cache is an umbrella term covering a number of different types of caching. This includes Content Delivery Network (CDN) caching, object caching, and opcode caching. Depending on what you want to achieve you might need one or the other. Usually, though, you can have all 3 types of caching as it shouldn’t interfere with your Website/App. I won’t go into more details about what each caching does as this post will become 3 pages long. There are multiple documents providing services/packages for each of the server-type caching.

  • Next would be using PHP-FPM (if your Website is using PHP of course). PHP-FPM is an efficient method on how to minimize the memory consumption and rise the performance for the Websites with heavy traffic. It is significantly faster than traditional CGI-based methods in multi-user PHP environments.

  • Another solution would be Database Caching. A database cache supplements your primary database by removing unnecessary pressure on it, typically in the form of frequently accessed read data. The cache itself can live in a number of areas including your database, application or as a standalone layer. Usually, for this kind of caching is being used Redis.

  • Apache NPM modules. If you are using Apache, you are using one of three NPM modules. Most certainly if you haven’t configured anything on it and have used the default configuration, you are using NPMPrefrok which is the most outdated one and thus the slower. I’ll recommend using one of the other two - NPMWorker and NPM_Event depending on your situation. Again, I would urge you to read more about these 3 and what is applied in which case.

  • Apache Workers. Basically, the Apache workers are equivalent to a room full of seats. These seats are the projection to your website. When someone opens your website, it’s like one person going to this room and sitting on one of the chairs. When the limit is reached, in order for a person to load your website, another one needs to close it. So basically, I’ll suggest increasing that value as well.

Those were the basic optimizations on a server level, let’s start with your Website/App

If you are using a CMS like WordPress, Magento, Joomla, Opencart or anything of the same matter, there will be plugins/addons. These addons can be very powerful if used correctly. The most helpful plugins are:

  • Caching Plugins
  • Image Optimization Plugins
  • Plugins that reduce redirections/requests
  • Plugins that reduce the size of JS and CSS files.
  • More often than not, there are a lot of JS and CSS files that are not being used, removing those should work as well

If you are not using a CMS, you’ll need to try and do what these plugins are doing manually.

Usually, Websites/Apps are slow because of a couple of reasons which range from too many requests or big images to a bunch of unnecessarily big JS or CSS files. Optimizing these whether you are using a Plugin or doing it manually is enough.

I hope this was helpful.