Click here for our UK shared web hosting FAQ

Why choose UK hosting?

When most of your visitors are in the United Kingdom, keeping the website on a UK-based server is a sensible way to keep the connection between them and your site as direct as possible. Physical distance is one factor in network latency, so a nearby data center can help reduce the time involved in delivering pages and other website content. It is not the only thing that affects speed, but it is an important part of the overall picture.

The type of website you run does not really change that basic requirement. A local company, online store, personal blog, or larger business site all depend on hosting that stays dependable behind the scenes. Our UK platform uses cloud infrastructure and provides a straightforward control panel, so you can spend your time running the website rather than dealing with the underlying server.

For organizations serving customers across England, Scotland, Wales, and Northern Ireland, keeping the site within the UK can make particular sense. It keeps the primary server close to the people you are trying to reach while also giving you good connectivity beyond the country's borders.

Ideal for businesses, bloggers and online stores

There is room for a wide range of websites on our UK plans. A small company can use one to build its online presence, a freelancer can display services and previous work, a blogger can concentrate on publishing, and an ecommerce site can provide a platform for handling customers and orders.

You also do not have to choose a large package on day one simply because you expect the site to grow. Starting smaller can make sense when the current workload is modest. Later, when you need more storage, bandwidth, or space for additional websites, you can move to a larger plan.

That makes the setup suitable for both a first website and a collection of projects. The amount of capacity can change as the work around the website changes.

Easy website management

You shouldn't need to understand server administration just to perform routine website tasks. The custom control panel included with each UK hosting account brings the main controls together, including domains, email, databases, files, and security settings.

Need to install WordPress? The process takes only a few clicks. If the website is already online somewhere else, the migration service can also handle much of the work involved in bringing it into the new account, rather than leaving you to figure out the entire transfer yourself.

Reliable cloud infrastructure

The platform is built around cloud technology intended to provide steady performance and dependable service. SSD storage, daily backups, and several security measures form part of the environment supporting the website.

There is another part to the service that matters just as much when something unexpected happens: support. The aim is to give you a hosting environment that is capable enough for modern websites without making everyday management unnecessarily complicated.

Why host your website in the United Kingdom?

The UK is a major digital market and a natural location for websites whose main audience is based there. Keeping the server in the country can reduce network latency for local visitors, which may help pages, stores, and web applications respond more promptly.

That doesn't mean the UK is automatically the right choice for every website. Where your visitors are located matters. For audiences concentrated in other regions, one of our international data centers may be a better fit. In general, placing the server closer to the majority of your visitors is a practical starting point when considering performance.

Perfect for WordPress websites

WordPress can adapt to just about anything from a simple blog to a business site or online store, which is a big part of its appeal. Our UK hosting environment is designed to support those different types of WordPress projects, as long as the site's actual workload fits within the selected plan.

You also don't have to change providers when the website becomes more demanding. Moving to a larger plan allows you to continue using the same platform while giving the site access to additional capacity.

Website security and backups

Keeping a website available is only part of the job; protecting its data and reducing the consequences of something going wrong matter too. Our platform includes built-in security measures, along with daily backups for eligible accounts. These provide additional protection if an unexpected incident affects the website.

No hosting environment can promise that every possible attack or failure will be prevented. The purpose of these features is to give your website a stronger starting point and a way to recover from certain problems rather than leaving you without any safeguards.

Moving your website is easy

There is no need to rebuild an existing website simply because you want to change hosts. Our migration service can usually move the site's files, databases, and other important data into your new UK hosting account, taking much of the technical work out of the transfer.

After the new copy has been moved and checked, the final step is to change the domain settings so visitors are directed to the new account. The domain itself can remain the same, so from a visitor's perspective the change can happen without much being visible.

How to choose the right UK hosting plan

Begin with what the website needs today. A personal site, blog, or small business website may have relatively modest requirements and can often start comfortably with an entry-level package. A larger site, several domains, or a business expecting heavier usage may justify a plan with greater capacity.

All of the plans use the same cloud infrastructure and provide the same control panel. What changes from one package to another is mainly the amount of resources available. That lets you choose a starting point that suits the current site and move upward later when the workload increases.

Shared web hosting in the UK FAQ.

This FAQ covers shared web hosting for websites aimed at visitors in Britain or hosted within a UK based environment. It focuses on the practical issues that matter when several websites share the same underlying resources, including setup, domains, software, email, security, performance, backups, migrations, troubleshooting and long term maintenance. Features differ between providers, control panels and server configurations, so the answers below identify where a particular arrangement needs to be checked.

FAQ menu

• Choosing the right shared plan
• UK location, connectivity and visitors
• Getting started and managing the account
• Domains, DNS and website addresses
• Applications, software and compatibility
• Files, databases and permissions
• Email and mail delivery
• SSL, security and account protection
• Performance, resources and caching
• Backups, recovery and data protection
• Moving an existing website
• Development, scheduled tasks and staging
• Troubleshooting and long term maintenance

Choosing the right shared plan

1. What is shared web hosting?

It is a setup where multiple customer accounts operate on the same physical infrastructure. Each account is kept separate logically, while parts of the underlying computing, memory, storage and network capacity are shared. That arrangement keeps prices lower than a dedicated machine, but it also means your resources are not unlimited.

2. Why is shared hosting still suitable for many UK websites?

A large number of small business sites, blogs, brochure sites and modest online stores do not need an entire machine to themselves. A properly configured shared environment can provide enough capacity for those workloads without paying for resources that remain unused most of the time.

3. Which types of websites are a good fit?

Typical examples include company websites, portfolios, local business sites, personal projects, information sites and smaller content management systems. The important issue is the workload rather than the label of the site. A busy application may outgrow the platform even when the website itself is quite simple.

4. When does shared hosting become a poor choice?

It becomes less attractive when a site needs sustained high CPU usage, large amounts of memory, unusual server software, advanced networking control, or consistently heavy traffic that regularly pushes account limits. Those requirements may call for a VPS, cloud platform or dedicated environment.

5. Does a cheaper package always mean a weaker website?

No. Cost and suitability are not the same thing. A smaller site may perform perfectly well on a modest package, while a badly matched plan can cause problems even when it costs considerably more. Pay attention to resource limits, software support, backups and the actual needs of your site.

6. How much storage does a small website really need?

The answer depends heavily on photographs, videos, backups, mailboxes and downloadable files. A basic site may occupy surprisingly little space. Large media libraries can change the calculation quickly, so storage should be assessed from your real content rather than from the number of pages alone.

7. Is unlimited storage really unlimited?

Not necessarily in the way the phrase sounds. Plans described as unlimited often remain subject to fair use rules, file type restrictions, inode limits, account policies or other technical constraints. Read the provider's current terms rather than assuming that every kind of storage use is permitted.

8. What does unlimited bandwidth mean on a shared plan?

It generally means there is no simple fixed monthly transfer allowance, but it does not guarantee unlimited use of every resource. CPU, memory, connection limits, fair use policies and traffic spikes can still affect an account.

9. Should a new UK business choose a local server?

A nearby data centre can reduce network distance for visitors in Britain, but it is only one part of the performance picture. The quality of the network, web server, caching, application and database setup also matters. A poorly configured nearby environment can be slower than a well run one farther away.

10. What should I compare before ordering a plan?

Look beyond the headline price. Check the supported PHP versions, database options, control panel, email facilities, SSL arrangements, backup policy, resource limits, migration help, technical support and any restrictions that matter to your application. Renewal pricing and cancellation terms also deserve attention.

Back to FAQ menu

UK location, connectivity and visitors

11. Does having a UK data centre make a website load faster for British visitors?

It can reduce network distance and therefore lower latency for some visitors, particularly when compared with a server on another continent. The gain is often measurable, but page generation, images, scripts, caching and the visitor's own connection can have a much larger effect on total load time.

12. Does server location matter for visitors outside Britain?

Yes, because network distance can affect latency. Visitors in Europe may still have a good experience from a British facility, while people in Asia, North America or Australia are physically farther away. A content delivery network can help distribute static content closer to those users.

13. Is a London data centre always the best choice for a UK audience?

Not automatically. London is a major connectivity hub, but the quality of the particular facility, transit providers, hardware and setup matters more than the city name alone. Other UK locations can also provide very good connectivity.

14. Can hosting in Britain improve SEO for a UK audience?

Server location can be one signal among many, but it is not a shortcut to better search rankings. Search engines consider the overall site, content, relevance, technical quality, performance and other signals. A UK address and sensible geographic signals may be more relevant to local targeting than location alone.

15. Will a UK based account automatically give me a UK IP address?

Not in every situation. The physical location and the IP address allocation are related but are not identical concepts. Check the provider's documentation if a British IP address is specifically required.

16. Is a dedicated UK IP address necessary for a normal shared website?

Most ordinary sites do not need one. Modern SSL certificates can work on shared addresses, and many websites can safely operate behind shared IP infrastructure. A separate address is only useful where a particular technical requirement calls for it.

17. Can network congestion affect a UK hosted website?

Yes. Congestion can occur within the data centre, upstream network, local access network or elsewhere between the visitor and the site. A data centre being physically close does not eliminate every possible source of delay.

18. What is latency, and why does it matter here?

Latency is the time required for data to travel between two points. Higher latency can make interactive requests feel slower, especially when a page or application requires many separate round trips. Good caching and efficient page design can reduce the practical effect.

19. Is IPv6 important for a shared account in Britain?

IPv6 support can be useful as internet connectivity continues to use both IPv4 and IPv6. Whether it matters to your particular site depends on the provider's network and your technical requirements. There is no need to enable it simply because it exists.

20. Can a UK hosted website be accessed normally from other countries?

Yes. Hosting location does not normally restrict ordinary worldwide access. Problems are more likely to come from network filtering, local connectivity issues, firewall rules or deliberate geographic restrictions configured for the site.

Back to FAQ menu

Getting started and managing the account

21. What do I need before setting up an account?

You normally need a registered domain or a temporary address supplied by the provider, access to your website files, and any database or email details required for an existing site. For a new installation, knowing which application you intend to use is also helpful.

22. What is a control panel used for?

It provides a web interface for common administrative tasks such as managing files, databases, email accounts, domains, DNS records, SSL certificates, backups and scheduled jobs. The exact tools vary between providers and panels.

23. Is cPanel required for a UK shared account?

No. cPanel is one possible control panel, not a requirement. Other environments can provide similar functions through different interfaces, and some hosts use their own management systems.

24. Can one account host more than one website?

Many multi-site packages allow several websites, but the permitted number differs by plan. Each additional site still consumes the same overall pool of storage, processing capacity, memory and other account resources.

25. What is an addon domain?

In control panels that use this term, it generally means another website address managed under the same hosting account. The terminology differs between platforms, so another provider may describe the same arrangement as an additional domain or separate site.

26. What is a subdomain used for?

A subdomain creates an additional web address beneath an existing one, such as shop.example.co.uk. It can be useful for sections that need separate routing or configuration, although a folder is often simpler when there is no technical reason to separate them.

27. Can I manage the account without using the command line?

Often yes. File managers, database tools, mail controls and application installers are commonly available through the web interface. Some advanced maintenance tasks still benefit from command line access, but that depends on what the provider permits.

28. Is SSH available on shared accounts?

Some providers offer SSH access, while others restrict or disable it. Even where SSH exists, available commands, PHP versions, process limits and permissions may be constrained by the shared environment.

29. Can I change PHP settings myself?

Many control panels expose selected PHP settings through an interface or configuration file. However, shared systems typically prevent changes that could affect the whole machine or conflict with security policies.

30. How do I know which limits apply to my account?

Look for the provider's resource documentation, control panel statistics and account terms. Useful figures include storage, memory, CPU allowance, entry processes, inode counts, database limits and scheduled task restrictions. When documentation is vague, ask support for the specific limits before relying on the plan.

Back to FAQ menu

Domains, DNS and website addresses

31. Can I use a .co.uk domain with this type of service?

Yes. A .co.uk address can point to a shared account just like many other domain extensions. The domain registrar and the web host do not have to be the same company.

32. Can I host a .uk domain if the company is elsewhere?

Yes. The important issue is how the domain's DNS records are configured. The physical location of the registrar does not determine where the website itself must be hosted.

33. Do I have to transfer my domain to the same company?

No. You can normally keep the registration with one provider and the website with another. This can be useful when you prefer separate specialists for registration and web services.

34. What DNS records are normally involved in moving a website?

The most common records are A or AAAA records for the web address and MX records for email. CNAME, TXT and other entries may also be needed for verification services, mail security or specific applications.

35. How long does a DNS change take?

There is no single guaranteed time. DNS information is cached according to the relevant TTL settings, so some networks may see the change sooner than others. Changes can appear gradual rather than instantaneous.

36. Should I change nameservers or edit individual DNS records?

That depends on how you want the domain managed. Changing nameservers moves DNS management to another service. Editing individual records lets you keep the existing DNS provider while pointing specific services elsewhere.

37. Can I keep email with one company and the website with another?

Yes. The website and mail system can be directed independently using DNS. This is often useful when a business uses a separate mail provider while retaining a web account for its site.

38. Why can a domain work on one network but not another after a change?

Different networks may hold cached DNS information for different lengths of time. Local DNS resolvers, browser caching and other intermediate caches can also produce temporary differences.

39. What happens if I change DNS before the new website is ready?

Visitors may reach the new account before the site has been fully prepared. A safer migration normally involves building and testing the replacement first, then making the final DNS change when the content, database and configuration are ready.

40. Can multiple domain names show the same website?

They can, provided the account and application are configured for those addresses. It is important to decide which address should be the canonical one and redirect alternatives where appropriate rather than creating several identical public versions.

Back to FAQ menu

Applications, software and compatibility

41. Can I install WordPress on a shared UK account?

WordPress is commonly supported by shared environments, but the account still needs a compatible PHP version, database system and sufficient resources. Installation methods differ, so use the provider's current requirements rather than relying on an old tutorial.

42. What PHP version should a website use?

The safest choice is normally a currently supported version that the application itself supports. Using an obsolete release merely because an old plugin still works can create security and compatibility problems. Check both the application's requirements and the versions offered by the provider.

43. Can I choose the PHP version myself?

Some shared control panels let each account select from several installed releases. Others assign a fixed version or provide only a limited selection. The available choices are controlled by the host.

44. What happens when a provider removes an old PHP version?

Older applications may stop working or show warnings if they depend on features removed from newer releases. The best response is to update the application and its extensions before the older runtime reaches end of support.

45. Can I install any PHP extension I want?

No. Shared customers generally cannot install arbitrary system components. Only extensions enabled by the provider are available, although many commonly required modules are already present.

46. Are Python and Ruby applications supported?

Support varies considerably. Some shared packages provide limited application hosting for these languages, while others are designed primarily for PHP based websites. Check the exact runtime and process requirements before choosing a plan.

47. Can I run Node.js on shared hosting?

That depends on the environment. Some hosts support selected Node.js applications, while others do not permit long running processes on shared accounts. A conventional static or PHP website is a different requirement from a persistent Node.js service.

48. Can I install custom server software?

Not in the same way as you could on a fully controlled virtual or dedicated machine. Shared customers generally cannot change operating system packages or install services that require system level privileges.

49. How do I check whether a plugin or application is compatible?

Compare its documented requirements with the PHP version, database version, extensions and operating environment supplied by the host. Pay particular attention to older software that has not been maintained recently.

50. What is a one click installer?

It is a control panel tool that automates part of an application's setup. It may create files, a database and initial configuration for you. You still remain responsible for updates, passwords, configuration and ongoing maintenance.

Back to FAQ menu

Files, databases and permissions

51. Where should my website files be uploaded?

The public web directory depends on the control panel. Common names include public_html, www or a site specific document root. The provider's documentation should identify the correct location for your account.

52. Can I upload files through a browser?

Many shared accounts include a web based file manager. It is convenient for small changes, but FTP or SFTP is often more practical when transferring a large number of files.

53. Is SFTP safer than ordinary FTP?

SFTP encrypts the connection used to transfer files. Traditional FTP can expose credentials and data on an unencrypted connection, so SFTP is generally preferable when the provider supports it.

54. Why do file permissions matter?

Permissions determine which users and processes may read, write or execute a file. Incorrect settings can cause an application to fail, while overly broad write access can increase security risk.

55. Should every file be writable by the website?

No. Applications should have only the write access they actually need. Giving broad write permission to everything can make a compromised account easier to abuse.

56. What is an inode limit?

An inode represents a filesystem object such as a file, directory, shortcut or similar item. A package can therefore reach its inode limit even when there is plenty of unused storage, especially when it contains many small files, cached copies or email messages.

57. What causes a database connection error?

Common causes include incorrect database credentials, a wrong database hostname, a missing database user, insufficient permissions, an unavailable database service or application configuration that points to outdated information.

58. Can I create more than one database?

Many plans permit multiple databases, subject to the package limits. Separate databases can be useful for distinct sites or applications, but the total workload still draws from the same account resources.

59. Should every website have its own database?

When an application supports separate databases, keeping sites separate is often easier to manage and recover. Some software installations may share a database by design, so the application's documented architecture should guide the decision.

60. Can I repair a database from the control panel?

Some panels provide basic database management tools, while others allow access through utilities such as phpMyAdmin. More serious corruption may require a backup restore or assistance from the provider.

Back to FAQ menu

Email and mail delivery

61. Can I create email addresses using my website's domain?

Many shared packages include mailbox facilities, allowing addresses such as info@example.co.uk. Some providers instead focus on web hosting and leave mail to an external service, so this needs checking before purchase.

62. Is email included with every shared package?

No. Mail may be included, limited, or omitted altogether. The distinction is important if the website and business email are currently operated together.

63. What is an MX record?

An MX record tells other mail systems where messages for your domain should be delivered. It is separate from the DNS record used to direct normal web traffic.

64. Can I use Microsoft 365 or Google Workspace with the website?

Yes. The website can remain on the shared account while email is handled elsewhere. DNS records are then configured so mail goes to the chosen provider rather than the local mail system.

65. Why are messages from a shared account sometimes rejected?

Mail reputation can be influenced by the behaviour of other customers sharing the same outbound infrastructure. Authentication records, message content, recipient policies and the sending IP reputation can all matter as well.

66. What are SPF, DKIM and DMARC?

They are email authentication and policy mechanisms. SPF identifies permitted sending systems, DKIM adds a cryptographic signature and DMARC tells receiving systems how to handle messages that fail authentication checks. They should be configured according to the actual mail service being used.

67. Does using a UK based website account guarantee good email delivery?

No. Deliverability depends on far more than geography. Sender reputation, authentication, recipient filtering, mailing behaviour and the reputation of the sending infrastructure all play a role.

68. Can I send bulk newsletters from a shared mailbox?

A standard shared mail system is generally not the right tool for large campaigns. Providers often impose sending limits, and specialist mailing services are better equipped for subscription management, bounce handling and compliance requirements.

69. Why does a new mailbox sometimes fail to receive mail immediately?

New mailbox settings can take time to become available, while DNS changes are subject to caching. If MX records were changed during the setup, temporary delivery differences can occur.

70. What should I do if website mail suddenly stops working?

First determine whether the problem affects sending, receiving or both. Then check mailbox capacity, DNS and MX records, authentication settings, connection details and any service status information supplied by the provider.

Back to FAQ menu

SSL, security and account protection

71. Does a shared website still need HTTPS?

Yes. HTTPS protects traffic between visitors and the website and is especially important when passwords, forms or other private information are transmitted. It is now a basic expectation for modern websites.

72. Can several websites use SSL on the same shared machine?

Yes. Modern web servers can serve many secure sites from the same infrastructure using separate certificates and hostnames. Shared infrastructure does not prevent encrypted connections.

73. Are free SSL certificates suitable for business websites?

For ordinary domain validation and encrypted web traffic, a free certificate can be perfectly suitable when it is supported and renewed correctly. A paid certificate is not automatically more secure simply because it costs money.

74. What happens when an SSL certificate expires?

Visitors may receive browser warnings, and secure connections can fail validation. Automated renewal is convenient, but it should still be monitored rather than assumed to work forever.

75. Is one website able to compromise another customer on the same machine?

Shared platforms are designed to isolate accounts from one another. Good account separation, permissions and security controls are intended to prevent one customer from directly accessing another. No internet system is completely risk free, however.

76. Why are outdated plugins dangerous?

Old extensions can contain known security weaknesses that attackers already understand. Keeping the application, themes, plugins and runtime maintained reduces one common route into a website.

77. Does the provider protect my application from every attack?

No. The host is responsible for the underlying environment it controls, but the website owner remains responsible for application security, passwords, updates and configuration. The exact division of responsibility varies by provider.

78. Should I use a separate administrator account instead of the main account login?

Yes, where the software supports it. Limiting administrative privileges and using unique credentials reduces the risk associated with unnecessary access.

79. Is two factor authentication useful for a shared hosting account?

It can provide an important extra layer of protection for the control panel or management account. Whether it is available depends on the provider and the control panel.

80. Can malware scanning guarantee that a website is clean?

No scanning system can guarantee perfect detection. Scanners can identify many known patterns, but prevention, updates, strong credentials, restricted permissions and good backups remain important.

Back to FAQ menu

Performance, resources and caching

81. Why can performance vary on a shared environment?

Multiple accounts draw from the same underlying infrastructure. Providers normally enforce limits and isolation, but workload changes, storage activity, database demand and network conditions can still affect performance.

82. What does CPU usage mean for a website?

CPU time reflects the amount of processor work needed to handle requests and background tasks. Dynamic pages, image processing, large database queries and certain plugins can consume considerable processing time.

83. What does memory usage mean?

Memory is used by the application, database connections, scripts and other processes. An application that regularly exceeds its available memory may become slow, return errors or terminate processes.

84. Why can a website become slow after installing a plugin?

A plugin may add database queries, background jobs, scripts or external requests. The effect can be minor or substantial depending on what it does and how often it runs. Performance tools and logs can help identify the cause.

85. What is page caching?

Page caching stores prepared output so repeated visits do not require the application to rebuild the same page every time. For suitable sites, that can reduce processing work and improve response times.

86. Is browser caching the same as server caching?

No. Browser caching stores resources on the visitor's device, while server side caching stores data or generated content within the hosting environment or another service. They can work together.

87. Can a content delivery network help a UK website?

It can, especially when visitors are spread across several countries. Static resources such as images, scripts and stylesheets can sometimes be delivered from locations closer to the visitor, reducing the amount of content that must travel back to the origin account.

88. Why does a website sometimes return a resource limit error?

The account may have reached a CPU, memory, process, entry process, database or other defined threshold. The useful next step is to inspect the account statistics and logs rather than assuming that storage space is the problem.

89. Can large images slow down a site even when the hosting account is fast?

Absolutely. Large files increase download time and can also consume more storage and processing resources. Correct dimensions, compression and modern image formats often make a noticeable difference.

90. Does installing a caching plugin always make a website faster?

No. Results depend on the application, the existing configuration and the type of caching already provided by the platform. Two caching systems can also conflict or create stale content if configured poorly.

Back to FAQ menu

Backups, recovery and data protection

91. Are backups included automatically?

Some providers include automated backups, while others sell them separately or apply limits on retention and restoration. The safest approach is to read exactly what is backed up, how often it runs and how long copies are retained.

92. Is a backup stored on the same machine as the website?

It may be, but a proper backup strategy should not rely on the same storage being available after a hardware failure or account problem. Ask where backup copies are kept if the provider's documentation does not make this clear.

93. How often should a website be backed up?

The right interval depends on how often data changes and how much work you could afford to lose. A frequently updated shop or membership site needs more recent recovery points than a brochure site that changes once a month.

94. What should a backup contain?

A useful website backup generally includes both the files and the database. Email may be a separate service and therefore require its own backup arrangement.

95. Can I restore only one website from a multi-site account?

Sometimes. The answer depends on the backup system and how sites are separated. Some tools allow individual files or databases to be restored, while others work at account level.

96. Is a backup the same as a snapshot?

Not necessarily. A snapshot is typically a point in time representation of storage or a system state, while a backup may be stored separately and designed specifically for recovery. The exact behaviour depends on the technology used by the provider.

97. Should I keep a copy of my website somewhere else?

Yes, especially when the site is important to a business. An independent copy gives you another recovery option if the account, provider or backup system becomes unavailable.

98. What should I do before updating a major application?

Confirm that a recent usable backup exists, check compatibility, review the application's release notes and test the change where practical. A backup is valuable only if it can actually be restored.

99. Can deleted files be recovered after an accidental mistake?

Recovery may be possible from a backup, but not every provider retains deleted material indefinitely. Do not assume that a deleted file remains available unless the provider explicitly says so.

100. How often should I test a restore?

Periodically. A successful backup job does not prove that the resulting data can be restored correctly. Testing exposes missing files, broken archives, unsuitable retention and other problems before an emergency.

Back to FAQ menu

Moving an existing website

101. Can I move a website from another provider to a UK shared account?

Yes. A normal migration involves copying files, moving the database, recreating the necessary settings and then changing the domain or DNS configuration. The exact process depends on the application.

102. What should I collect before starting a migration?

Keep copies of the website files, database, DNS records, email settings, SSL details where relevant, scheduled tasks and any special configuration. Record the existing PHP version and other runtime details as well.

103. Should I move the database before the files?

There is no universal rule. For many applications, it is easiest to prepare the new files and database together, import the data, update configuration and test the site before changing public DNS.

104. Can I test the new site before changing the domain?

Often yes. The method depends on the host and application. Some providers offer temporary URLs, preview features, staging addresses or local host based testing. Make sure the final configuration will use the real domain correctly.

105. What commonly breaks during a migration?

Typical problems include incorrect database credentials, missing files, incompatible PHP versions, incorrect file paths, changed permissions, missing extensions, rewritten URLs and incomplete DNS changes.

106. Do email accounts move automatically with the website?

No. Website files and mailboxes are separate services even when one company provides both. Moving a website does not automatically copy old messages or recreate the mail configuration.

107. Should I lower DNS TTL before changing providers?

Reducing the TTL ahead of a planned move can allow new DNS information to be recognised sooner after the change, although existing caches may still retain the previous value for some time. Make the change early enough for it to take effect before the migration.

108. How can I reduce downtime during a move?

Prepare the new account first, copy the data, test thoroughly and make the final DNS change only when the replacement is ready. For sites where content changes continuously, a final database synchronisation may also be needed.

109. What should I check after DNS has changed?

Test the main pages, forms, logins, images, downloads, database features, SSL certificate, email and important redirects. Check from more than one network where practical because DNS caches can differ.

110. Should the old account be cancelled immediately?

It is safer to keep the old service active until you have confirmed that the new site works and that no important data remains behind. This is particularly important for mailboxes, databases and files that changed during the migration.

Back to FAQ menu

Development, scheduled tasks and staging

111. Can I create a staging copy of a website?

Some shared platforms provide a staging feature, while others do not. A staging copy can be useful for testing updates without changing the public site, but its resource use still counts against the account where applicable.

112. Is staging always identical to the live website?

Not necessarily. It may be a copy of files and database content taken at a particular time. Changes made afterward on the live site may not appear in staging unless the environments are synchronised.

113. Can I run scheduled PHP scripts?

Many shared accounts support scheduled tasks through cron or a similar system. Providers commonly restrict how often tasks may run and how long they may execute.

114. What is cron used for?

It schedules commands or scripts to run automatically. Common uses include maintenance tasks, application jobs, report generation, database cleanup and other recurring processes.

115. Can a scheduled task run every minute?

Not necessarily. Some providers impose a minimum interval to protect shared resources. A one minute schedule should never be assumed unless the account documentation specifically permits it.

116. Why can a scheduled task work manually but fail automatically?

The cron process may use a different working directory, PHP binary, environment or permissions. The command may also depend on a path or variable that exists in an interactive session but not in the scheduled environment.

117. Can I use Git on a shared account?

Some providers allow Git repositories or deployment through Git, while others restrict command line tools. The availability of Git itself does not guarantee that every automated deployment workflow will work.

118. Is Git deployment suitable for all websites?

It can be useful for code based projects, but simple sites may not need it. Applications that store uploads or database content outside version control require a deployment process that handles those pieces separately.

119. Can I create a development subdomain?

Yes, when the account permits additional subdomains. It can be useful for testing, although access should be restricted when the site contains unfinished work, customer information or other private material.

120. Should a staging site be indexed by search engines?

No. A development copy should generally be kept out of public search results. The exact protection method depends on how the staging environment is configured, but access control is stronger than relying on a simple robots directive alone.

Back to FAQ menu

Troubleshooting and long term maintenance

121. Why might a website suddenly show a 500 error?

A 500 error indicates that the server could not complete the request. Common causes include application errors, incompatible PHP code, exhausted resources, incorrect permissions or server configuration problems. Error logs are often the fastest route to the underlying cause.

122. What should I check when a page shows a 403 error?

Look at file and directory permissions, access rules, security settings and whether the requested path is being blocked deliberately. A web application firewall can also produce a 403 response when it considers a request suspicious.

123. Why might a website suddenly show 404 errors after moving it?

The page may not exist at the expected path, rewrite rules may not have been transferred, or the application's base URL may be wrong. Check both the physical files and the application's routing configuration.

124. What should I do when the database suddenly becomes slow?

Check whether the slowdown affects one query, one application or the entire account. Review recent changes, database size, inefficient queries and resource usage. If the problem appears outside the website itself, provider support may need to investigate the underlying service.

125. Why can a website become slower after years of operation?

Content, plugins, database tables, logs, cached files and background tasks can accumulate. Software can also become more demanding over time. Regular maintenance helps prevent gradual resource growth from becoming a sudden performance problem.

126. How can I tell whether a problem is caused by the application or the hosting environment?

Start with the evidence in error logs, access logs and resource statistics. A reproducible application error points one way, while multiple unrelated sites or services failing together suggests an infrastructure issue. Comparing behaviour after disabling a recently changed component can also help isolate the cause.

127. What should I do after changing the PHP version?

Test the public pages, administration area, forms, database features, scheduled jobs and important extensions. An older plugin or theme may use code that the newer runtime no longer accepts.

128. Why can a website work in a browser but fail for an automated task?

Automated requests may use different user agents, authentication, IP addresses, timeouts or execution environments. Firewalls, rate limits and application rules can treat those requests differently from normal visitors.

129. What logs are useful when diagnosing a shared hosting problem?

Error logs are especially valuable for PHP and web server failures. Access logs can reveal request patterns and status codes, while application specific logs may show database, plugin or authentication errors. The level of log access varies by provider.

130. When should I contact the provider instead of changing the website myself?

Contact support when the issue involves the underlying machine, network, control panel, mail service, SSL provisioning, resource enforcement or another component outside your account's control. Making repeated configuration changes without understanding the fault can make recovery harder.

131. How often should I update the software running a website?

There is no useful universal schedule such as once a month. Security updates should be applied promptly when appropriate, while larger application upgrades should be checked for compatibility first. A maintained site should not be left for years between updates.

132. Should I update every plugin immediately?

Security fixes deserve prompt attention, but every update still needs to be considered in context. Important websites should have a recent backup and, where practical, a staging test before major changes are pushed live.

133. What should I remove from an old website?

Unused plugins, themes, scripts, test files, obsolete backups stored inside the public area and abandoned development copies are all worth reviewing. Anything unnecessary can add security risk, storage usage or clutter.

134. Does deleting inactive plugins improve performance?

Removing software that is genuinely inactive does not normally produce a large speed increase by itself. The bigger benefits are reduced maintenance, fewer potential vulnerabilities and a simpler codebase.

135. How can I avoid exhausting space on a long running account?

Monitor storage growth, large uploads, old backups, logs, mailboxes, cache files and duplicated copies. A website that has operated for several years can accumulate considerable data without anyone noticing until a limit is reached.

136. What happens when an account reaches its storage limit?

New files may fail to upload, applications may be unable to create temporary data, databases can encounter problems and email may stop accepting new messages where mail shares the same quota. Freeing space or increasing the allowance may be necessary.

137. Why can a full disk cause problems beyond file uploads?

Applications often need temporary space for updates, sessions, logs, caches, image processing and database operations. Once storage becomes critically low, functions that do not appear related to file management can also fail.

138. Can I host a large number of small websites on one shared account?

A plan may allow multiple sites, but the practical limit is determined by more than the advertised site count. Every site adds files, databases, processes, logs, SSL certificates and maintenance work. A technically permitted arrangement can still become difficult to manage.

139. When should I consider moving from shared hosting to a VPS?

A move becomes sensible when the site consistently approaches resource limits, needs greater control over the environment, requires software unavailable on the shared platform, or has traffic patterns that no longer fit comfortably within the shared model.

140. Is shared hosting a long term solution for a UK business website?

It can be. A business does not need to move to a larger platform simply because the site has been online for several years. If the application remains compatible, performance is stable, resources are adequate and the provider meets your operational needs, the arrangement can remain practical for a long time.

Back to FAQ menu