awddesign.co.uk No paid content found

Web hosting solutions are the services that store your website's files and serve them to visitors, and the right type depends on three things: how much traffic you get, how much control you need, and how much you're willing to manage yourself. Shared hosting suits simple brochure sites on a budget; VPS and cloud hosting suit growing or variable-traffic sites; dedicated hosting suits high-traffic or resource-heavy applications; managed WordPress hosting suits WordPress sites where you'd rather not handle server maintenance. The sections below explain how each type differs and what to check before you commit.

The main types of web hosting

Shared hosting

Your site sits on a server with many other sites, and you share its CPU, memory, and bandwidth.

• Best for: brochure sites, blogs, small business sites with modest traffic.
• Control: limited — you usually get a control panel (such as cPanel or a custom dashboard) but no root access.
• Watch for: "unlimited" storage or bandwidth claims that are actually capped by fair-use policies, and resource limits that only show up when your traffic spikes.

VPS hosting

A virtual private server partitions a physical machine so you get dedicated resources, even though the hardware is shared.

• Best for: sites outgrowing shared hosting, or those needing custom software, specific PHP versions, or root access.
• Control: high — often full root access, so you can install what you need.
• Trade-off: you're typically responsible for server updates and security unless you buy a managed plan.

Dedicated hosting

You rent an entire physical server.

• Best for: high-traffic sites, large ecommerce stores, or applications with heavy, consistent resource demands.
• Control: complete.
• Trade-off: highest cost and the most administration, unless managed.

Cloud hosting

Your site runs across a network of virtual servers, so resources can scale up or down with demand.

• Best for: sites with unpredictable or fast-growing traffic, and teams that want to pay for what they use.
• Control: varies — from managed platforms to raw infrastructure you configure yourself.
• Trade-off: pricing can be harder to predict than a flat monthly fee.

Managed WordPress hosting

A specialised service where the provider handles WordPress-specific tasks: core and plugin updates, caching, security hardening, and often staging environments.

• Best for: WordPress sites where performance and low maintenance matter more than full server control.
• Control: lower — you generally can't install arbitrary server software.
• Trade-off: usually costs more than equivalent unmanaged hosting, and some hosts restrict which plugins you can use.

Matching hosting type to your site

Work backwards from what your site actually does:

• Simple brochure or portfolio site: shared hosting is usually enough. Don't pay for resources you won't use.
• Ecommerce store: prioritise reliability, SSL, backups, and the ability to handle checkout traffic spikes. VPS, cloud, or a well-specced managed plan are common choices.
• Custom software or web app: you likely need root access and specific runtimes, which points to VPS, cloud, or dedicated.
• WordPress site: managed WordPress hosting removes most maintenance work; unmanaged VPS is cheaper but you handle updates and security yourself.
• Traffic that varies a lot: cloud hosting's scaling avoids both overpaying for idle capacity and crashing during peaks.

A useful rule: choose the least powerful option that comfortably handles your peak traffic, not your average. Upgrading later is usually easy; recovering from downtime during a spike is not.

The real cost drivers

The headline monthly price rarely reflects what you'll pay. Check these:

• Renewal pricing: introductory rates often jump sharply after the first term. Compare the renewal price, not the promo price.
• Storage and bandwidth: confirm actual limits and what happens when you exceed them (overage fees vs. throttling).
• Backups: are they included, how often do they run, and how far back can you restore?
• SSL certificates: many hosts include a free certificate; others charge. You need one either way.
• Email hosting: some plans include mailboxes, others don't — factor in a separate email provider if not.
• Migration help: free migration saves time and risk; paid or absent migration is a hidden cost.

Performance and reliability signals to check

• Uptime guarantee: look at the actual wording — a 99.9% guarantee still allows several hours of downtime a year, and check what compensation, if any, is offered.
• Server location: a server closer to your main audience generally means faster load times.
• Support response times: check whether support is 24/7, and whether it's chat, ticket, or phone. Read reviews for real response experiences.
• Scalability: can you upgrade your plan without migrating to a new host?

Common pitfalls to avoid

• Chasing the cheapest introductory rate without checking the renewal price.
• Assuming migration is included — confirm before signing up, especially if you have email accounts or databases to move.
• Trusting "unlimited" claims without reading the acceptable-use policy.
• Ignoring resource limits (CPU, memory, concurrent connections) that only surface under load.
• Skipping the backup question until you actually need a restore.

How to decide

1. List your site's requirements: expected traffic, software stack, ecommerce or not, and how much server management you're willing to do.
2. Match those requirements to a hosting type using the table above.
3. Compare at least two or three providers on renewal price, backups, SSL, email, and support — not just the first-month cost.
4. Confirm migration support and the upgrade path before you commit.

If you're unsure, start with shared or managed hosting and move up only when you hit real limits. The goal isn't the most powerful plan — it's the one that keeps your site fast and online without paying for capacity you'll never use.

Responsive web design is not simply a site that shrinks to fit a phone screen. It is a set of layout and styling techniques that let one set of HTML and CSS adapt to any viewport: fluid grids that resize in proportion, flexible images and media that never overflow their containers, and media queries that change layout rules at defined breakpoints. A genuinely responsive site also rethinks navigation, tap targets, forms, typography and image loading for small screens, rather than squeezing a desktop page into a narrower frame.

The three core techniques

Fluid grids

Instead of fixed pixel widths, a fluid grid uses relative units such as percentages, fr units in CSS Grid, or rem-based maximum widths. A three-column desktop layout might become a single stacked column on a phone, not because the columns are squashed, but because the layout rules change at a breakpoint.

A simple example:

.container {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(260px, 1fr));
  gap: 1.5rem;
}

This produces as many columns as fit, then wraps the rest — no breakpoint needed for the basic behaviour.

Flexible images and media

Images should never force horizontal scrolling. The classic safeguard is:

img, video {
  max-width: 100%;
  height: auto;
}

Modern practice goes further with srcset and sizes, so a phone downloads a smaller image file rather than a 2000px desktop hero scaled down in the browser. That distinction matters: a visually correct but heavy page is still a poor mobile experience.

Media queries

Media queries apply CSS only when conditions are met — typically viewport width, but also orientation, resolution or user preferences such as prefers-reduced-motion. They are where most of the visible layout change happens: switching a horizontal menu to a hamburger, moving a sidebar below the main content, or increasing font size on small screens.

Responsive vs. scaled-down vs. separate mobile site

A separate mobile version can work, but it doubles maintenance and often drifts out of sync with the desktop site. For most businesses, one responsive codebase is simpler to maintain and easier for search engines to index.

What responsive design changes beyond layout

Navigation

A desktop menu with eight top-level items rarely fits a phone. Responsive navigation usually collapses into a toggle, an off-canvas drawer, or a bottom bar. The important part is that the menu remains reachable with one thumb and that the toggle is clearly labelled — an icon alone is often ambiguous.

Tap targets and spacing

Interactive elements should be large enough to tap reliably. A common guideline is a minimum target of around 44×44 CSS pixels, with adequate spacing between adjacent links. Cramped footer links and tightly packed pagination are frequent offenders.

Forms

On mobile, form fields should be full width, use appropriate input types (type="email", type="tel") so the right keyboard appears, and avoid placeholder-only labels that vanish once typing starts. Labels above fields generally work better than labels beside them on narrow screens.

Typography

Body text needs a comfortable line length and size on small screens. A common approach is a base size around 16–18px with a line height of roughly 1.5, and headings that scale down without becoming unreadable. Long paragraphs benefit from slightly increased line height on narrow viewports.

How responsive behaviour interacts with speed and hosting

Responsive design and performance are linked. A layout that adapts but still loads desktop-sized images, unused CSS or heavy scripts will feel slow on mobile networks. Practical measures include:

• Serving appropriately sized images with srcset and modern formats such as WebP or AVIF.
• Lazy-loading images below the fold.
• Keeping critical CSS small and deferring the rest.
• Avoiding layout shift by reserving space for images and embeds.

Hosting also plays a part. A fast, well-configured host with caching and a content delivery network reduces the time it takes for any layout to appear. Responsive design cannot compensate for a server that responds slowly, and good hosting cannot fix a layout that breaks on a phone — the two need to work together.

Practical checks you can run yourself

1. Resize the browser window slowly from wide to narrow. Watch for horizontal scrollbars, overlapping text, or elements that jump awkwardly.
2. Use browser device emulation (developer tools) to test common widths such as 360px, 390px, 768px and 1280px.
3. Test on a real phone, not just an emulator. Touch behaviour, keyboard appearance and font rendering differ.
4. Rotate the device to check landscape orientation.
5. Zoom to 200% on desktop to confirm content remains usable.
6. Tab through the page with a keyboard to check focus order and visibility.
7. Check the viewport meta tag is present: <meta name="viewport" content="width=device-width, initial-scale=1">.
8. Run a performance check to see whether mobile users are downloading oversized assets.

Common signs a responsive implementation is incomplete

• Horizontal scrolling on any common phone width.
• Text that requires pinch-zooming to read.
• Menus that open but cannot be closed, or that cover the whole screen with no exit.
• Buttons or links too close together to tap accurately.
• Images that overflow their containers or stretch out of proportion.
• Forms where the keyboard covers the submit button.
• Content that is hidden entirely on mobile with no alternative.
• Desktop-only hover effects that leave mobile users without the same information.

If you are briefing a designer or agency, it helps to ask specifically how they handle breakpoints, image delivery, navigation on small screens and testing across devices. Those questions reveal whether responsive design is treated as a genuine part of the build or as an afterthought.

Web site maintenance is the ongoing work that keeps a live site secure, available, and functioning after launch. It typically covers software and plugin updates, backups, security monitoring, uptime checks, and fixes to broken content or forms. It matters most for sites running a CMS such as WordPress, where outdated components are a common entry point for attacks, and less intensively for static sites that have no database or login system to patch. If your site takes payments, stores user data, or generates leads, treat maintenance as a recurring commitment rather than a one-off task.

The core maintenance tasks

Most maintenance programmes bundle a predictable set of jobs. The exact mix depends on your platform, but these are the usual components:

• Software and plugin updates. Applying updates to your CMS core, themes, plugins, and server-side runtimes. Updates patch known vulnerabilities and fix bugs, but they can also break layouts or functionality, so they are normally tested before going live.
• Backups. Scheduled copies of your files and database, stored somewhere separate from your hosting account. A backup is only useful if you have tested restoring from it.
• Security monitoring. Watching for malware, suspicious logins, and unauthorised file changes, plus hardening measures such as firewalls and login limits.
• Uptime checks. Automated monitoring that alerts someone when the site goes down, so problems are caught before visitors or customers notice.
• Performance checks. Reviewing load times, image sizes, and caching so the site does not gradually slow down as content is added.
• Content and form fixes. Repairing broken links, contact forms that stop sending, outdated pricing or opening hours, and layout issues introduced by updates.
• Reporting. A summary of what was updated, what was fixed, and what needs attention.

Routine maintenance vs emergency fixes vs redesigns

These are often confused, and the distinction affects both cost and expectations.

Routine maintenance aims to prevent emergencies. A provider who only responds after a site is defaced is offering a repair service, not maintenance. A redesign is a separate project with its own scope, timeline, and budget, and should not be folded into a maintenance retainer.

How the platform changes what you need

Maintenance effort is not the same across all site types.

• WordPress and other CMS platforms. The heaviest maintenance load. Core, theme, and plugin updates arrive frequently, and each plugin is a potential vulnerability. You also need database backups and, usually, staging to test updates safely.
• Static sites. Built from fixed HTML, CSS, and JavaScript files with no database or admin login. There is far less to patch, so maintenance is mostly about content edits, link checks, and hosting. Security risk is lower because there is no login page to attack.
• E-commerce sites. Add payment gateway updates, PCI-related considerations, order and inventory data integrity, and stricter uptime expectations, since downtime directly stops sales.

If you are unsure which category you fall into, the practical question is: does your site have a login area or a database? If yes, plan for regular updates and backups.

What happens when maintenance is skipped

Neglect rarely causes an immediate visible failure. The damage accumulates:

• Compromised security. Outdated plugins and CMS versions are a common route for malware injection, spam redirects, and defacement.
• Downtime. Unpatched software and exhausted server resources lead to outages that can last hours or days.
• Broken forms and checkout. A silent failure in a contact form or payment step can lose enquiries or sales without anyone noticing for weeks.
• Declining performance. Growing image libraries and uncached pages slow the site, which affects both user experience and search visibility.
• Costly recovery. Cleaning a hacked site or rebuilding from a corrupted database usually costs more than a year of routine maintenance.

DIY maintenance or hire someone?

There is no universally correct answer, but the decision usually comes down to time, technical comfort, and risk tolerance.

Handle it yourself if:

• Your site is static or very simple.
• You are comfortable with your CMS admin area and can follow update and backup instructions.
• You can commit to a regular schedule rather than doing it only when something breaks.
• Downtime or a security incident would be inconvenient but not business-critical.

Hire a provider if:

• You run an e-commerce site or handle customer data.
• You use WordPress with many plugins and cannot test updates safely.
• You do not have the time to monitor uptime and respond to alerts.
• You want a documented record of what was done and when.

A middle option is a managed hosting plan, which often includes updates, backups, and security scanning as part of the hosting fee. This can cover the basics without a separate maintenance contract, though it usually excludes content edits and design fixes.

What to ask a maintenance provider

Before agreeing to a retainer, get clear answers on these points:

• Scope. Which tasks are included, and which are billed separately? Content edits and design changes are frequently excluded.
• Response times. How quickly are emergencies acknowledged, and is there a difference between business hours and out of hours?
• Backups. How often are they taken, where are they stored, and how long are they retained?
• Reporting. Will you receive a regular summary of updates and fixes?
• Access and ownership. Do you retain ownership of your domain, hosting, and site files if you leave?
• Testing process. Are updates applied directly to the live site, or tested on a staging copy first?

If a provider cannot answer these plainly, that is useful information in itself.

A practical starting point

Whatever route you choose, the minimum viable maintenance routine is: keep your CMS and plugins updated, take automated backups stored off your hosting account, monitor uptime, and check your contact forms and checkout regularly. Everything beyond that — performance tuning, security hardening, content updates — can be layered on as your site's role in your business grows.