Skip to content
Peter KagundaWeb Developer

Web Design Terms and Terminology: A Plain-English Glossary for Business Owners

March 21, 2024

Illustration of web design interface elements for a web design terms glossary
Peter KagundaBy Web Development Published Updated 12 min read

In short

The web design terms most business owners need are domain, hosting, SSL, CMS, responsive design, UX and maintenance. Knowing what they mean helps you brief a designer clearly, compare quotes fairly and make sure you own and can look after your website.

Web design terms can make a simple conversation about your website sound like a foreign language. When a designer says your site "isn't responsive", your "DNS hasn't propagated" or your "LCP is too slow", it helps to know exactly what they mean and whether it matters to your business.

I'm a freelance web developer, and most of the business owners and agency clients I work with don't need to learn to code. They do need enough vocabulary to brief a project, compare quotes and ask good questions. This glossary covers the web design terminology I use most often with clients, grouped by topic and explained in plain English, with a note on why each one matters to you. At the end you'll find a quick-reference table of web design acronyms and a few buzzwords decoded.

Website wireframe sketches on paper, an early step in web design

Why knowing basic web design terms saves you time and money

Most website problems I'm asked to fix started as a misunderstanding. A client thought "hosting" was included in the build price, or assumed "SEO" meant guaranteed first-page rankings, or didn't realise the template they bought wasn't responsive. Knowing the language helps you:

  • Write a clearer brief, so quotes from different designers are actually comparable. My guide on how to write a website brief pairs well with this glossary.
  • Spot gaps in a proposal, such as no mention of backups, SSL or who owns the domain.
  • Make decisions faster, because you understand the trade-offs your developer is describing.

The basics: domains, hosting and how a website loads

Domain name

Your website's address, such as yourbusiness.com. You rent it yearly from a registrar. Always make sure the domain is registered in your name or your company's name, not your designer's. If they leave, you keep control.

DNS (Domain Name System)

The internet's phone book. DNS records point your domain to the server where your website lives and tell the world where to deliver your email. "Propagation" is the delay, usually minutes to a few hours, while those changes spread across the internet.

Web hosting

The server space where your website's files and database are stored so visitors can reach them around the clock. Shared hosting is cheap but you share resources with other sites; a VPS or cloud server gives you dedicated resources. If you want this handled for you, I offer managed website hosting.

SSL certificate (HTTPS)

The technology behind the padlock in the browser bar. It encrypts data between visitors and your site. Browsers warn people away from sites without it, so it is no longer optional for any business website.

CDN (Content Delivery Network)

A network of servers around the world that keeps copies of your site's images and files close to visitors. If your customers are spread across countries, a CDN makes your pages load faster for all of them.

Staging site

A private copy of your website where changes are built and tested before they go live. If your developer works directly on the live site, every mistake is public.

URL and slug

The URL is the full address of a page. The slug is the last part that identifies it, such as /contact/. Short, readable slugs are easier to share and remember.

Design and user experience terms

UX (user experience)

How easy and pleasant your site is to use: can visitors find what they need, understand your offer and get in touch without frustration? Good UX is mostly about removing friction.

UI (user interface)

The visual layer people interact with: buttons, menus, forms, colours and typography. UX is how it works; UI is how it looks and feels.

Wireframe

A simple black-and-white sketch of a page layout, showing where content goes before any colours or images are added. Reviewing wireframes early is the cheapest moment to change your mind.

Mockup and prototype

A mockup is a full-colour static design of a page. A prototype is a clickable version that lets you test how moving between pages feels before any real code is written.

Sitemap (planning) and information architecture

Before design starts, a planning sitemap lists every page and how they relate. Information architecture is the wider job of organising content so people can find it. Both shape your menu.

Responsive design

A layout that automatically adapts to phones, tablets and desktops. Since most visitors now browse on mobile, a site that isn't responsive loses enquiries every day.

Mobile-first

Designing for the small screen first, then expanding for larger screens. It forces clear priorities and usually produces faster pages.

Above the fold

The part of a page visible before anyone scrolls. It should say clearly what you do, who it's for and what to do next.

Hero section

The large banner area at the top of a page, usually with a headline, short supporting line, image and main button.

CTA (call to action)

A button or link that asks the visitor to take a specific step, such as "Request a quote" or "Book a call". Every important page should have one obvious CTA.

Navigation is your menus and links. Breadcrumbs are the small trail (Home › Services › Web Design) that shows where a visitor is. Both help people and search engines understand your site; see my guide to website navigation.

White space

The empty space around text and images. It isn't wasted space; it makes pages easier to scan and makes important elements stand out.

Typography and web fonts

The choice and arrangement of typefaces. Web fonts are loaded by the browser, so using too many slows the site down.

Colour palette and style guide

The set of brand colours, fonts and rules used across the site. A style guide keeps new pages consistent long after launch.

Accessibility (WCAG)

Designing so people with disabilities can use your site, for example with screen readers, keyboard navigation and enough colour contrast. The Web Content Accessibility Guidelines are the recognised standard, and in some markets accessibility is a legal requirement.

Favicon

The small icon shown in browser tabs and bookmarks. It's a minor detail, but its absence makes a site look unfinished.

Building blocks: platforms and code

Front end and back end

The front end is everything visitors see in their browser. The back end is the server, database and logic behind it, such as order processing or user accounts.

HTML, CSS and JavaScript

The three core languages of the web. HTML gives a page its structure, CSS controls its styling and layout, and JavaScript adds interactivity like sliders, filters and form validation.

CMS (content management system)

Software that lets you edit your own content without touching code. WordPress is the best-known example; Shopify plays a similar role for online stores. If you're weighing options, see my comparison of WordPress vs a custom website.

Theme and template

A pre-designed layout applied to a CMS. Themes are quick and affordable but can be bloated or hard to customise. A custom theme is built around your content instead of the other way round.

Page builder

A drag-and-drop editor, such as Elementor or Divi, that lets you lay out pages visually. Convenient, but often heavier and slower than a lean custom theme.

Plugin or extension

An add-on that gives a CMS extra features, such as forms, booking or SEO tools. Each plugin is also code you must keep updated, so fewer, well-maintained plugins is the safer approach.

API (application programming interface)

A way for two systems to talk to each other, for example your website sending orders to your accounting software or pulling availability from a booking system.

Database

Where dynamic content such as posts, products, orders and users is stored. Backups need to include the database, not just the files.

Static vs dynamic website

A static site serves the same pre-built pages to everyone. A dynamic site builds pages on request from a database, which allows logins, shops and personalised content.

Headless CMS

A CMS that only stores and serves content, while a separate front end (often built with a JavaScript framework) displays it. Flexible, but usually more expensive to build and maintain.

Performance and SEO terms

SEO (search engine optimisation)

The work of helping search engines understand and rank your pages: technical setup, useful content, sensible structure and links from other sites. No honest developer can guarantee rankings.

Keywords

The words and phrases people search for. Each important page should target one main keyword. My guide to keywords in digital marketing explains how to choose them.

Meta title and meta description

The title and short summary that often appear in search results. They don't show on the page itself, but they strongly influence whether someone clicks.

Sitemap (XML)

A file listing your important pages so search engines can find them. Most modern platforms generate one automatically; it still needs submitting to Google Search Console.

Indexing

Google storing a page so it can appear in results. A page can be crawled and still not indexed. See how to index your website on Google.

301 redirect

A permanent forward from an old URL to a new one. Redirects are essential during a redesign, otherwise old links break and rankings can drop.

Canonical tag

A line of code telling search engines which version of a page is the main one when similar versions exist.

Schema markup (structured data)

Extra code that describes your content to search engines, such as your business details, reviews or FAQs. It can make your listing richer in search results.

Page speed and Core Web Vitals

How quickly your pages load and become usable. Core Web Vitals are Google's measurements of loading speed (LCP), responsiveness to clicks and taps (INP) and visual stability (CLS). Slow sites lose visitors before they read a word.

Image optimisation

Resizing and compressing images, often to modern formats like WebP, so they look sharp without slowing the page. Oversized photos are the most common speed problem I find in audits.

Lazy loading

Loading images only when a visitor scrolls near them, so the top of the page appears faster.

Caching

Storing ready-made copies of pages so the server doesn't rebuild them for every visitor. Good caching is one of the cheapest speed improvements available.

Bounce rate and conversion rate

Bounce rate is the share of visitors who leave without interacting. Conversion rate is the share who complete a goal, such as sending an enquiry or buying. Conversion rate is the number that matters most.

Looking after a website after launch

Maintenance

The ongoing work of updating the CMS, themes and plugins, checking backups, fixing small issues and monitoring security. A website is never truly "finished", which is why I offer website maintenance plans.

Backup

A full copy of your site's files and database stored somewhere other than your server. Ask how often backups run, where they're kept and whether a restore has ever been tested.

Uptime

The share of time your website is online and reachable. Uptime monitoring alerts you when the site goes down, so you aren't the last to know.

Malware

Malicious code injected into a site, usually through outdated software or weak passwords. It can redirect visitors, send spam or get your site flagged by Google.

Analytics

Tools such as Google Analytics that show how many people visit, where they come from and what they do. Without analytics you're guessing whether your website works.

Web design acronyms at a glance

AcronymStands forIn one line
APIApplication programming interfaceHow two systems exchange data
CDNContent delivery networkServers worldwide that speed up delivery
CLSCumulative layout shiftHow much the page jumps while loading
CMSContent management systemSoftware for editing your own site
CROConversion rate optimisationImproving the share of visitors who act
CSSCascading Style SheetsThe language for styling pages
CTACall to actionThe button that asks for the next step
DNSDomain Name SystemPoints your domain to your server
FTP / SFTP(Secure) File Transfer ProtocolA way to upload files to a server
GA4Google Analytics 4Google's current analytics tool
HTMLHyperText Markup LanguageThe structure of a web page
HTTPS / SSLSecure HTTP / Secure Sockets LayerEncrypted connection and the padlock
INPInteraction to Next PaintHow quickly a page responds to taps and clicks
LCPLargest Contentful PaintHow fast the main content appears
MVPMinimum viable productThe smallest useful first version
PWAProgressive web appA website that behaves like an app
SEOSearch engine optimisationHelping pages rank in search
SERPSearch engine results pageThe page of Google results
SaaSSoftware as a serviceSoftware you rent online, like Shopify
UIUser interfaceWhat the site looks like
UXUser experienceHow the site feels to use
WCAGWeb Content Accessibility GuidelinesThe accessibility standard
WYSIWYGWhat you see is what you getAn editor that shows the final look as you type

Web design buzzwords, decoded

  • "Pixel-perfect": the build matches the approved design closely. Ask how it will look on screen sizes the design didn't show.
  • "SEO-optimised web design": should mean clean code, fast loading, proper headings, titles, redirects and a sitemap. It doesn't mean guaranteed rankings.
  • "Conversion-focused": the layout is planned around enquiries or sales, with clear CTAs. Ask how success will be measured.
  • "Bespoke" or "custom": designed for you rather than from a template. Ask whether the code is also custom or a customised theme. See bespoke website development.
  • "Future-proof": nothing is. Ask about updates, maintenance and who owns the code.

How to use this glossary with your web designer

You don't need to memorise every term. When you're comparing proposals, run through this short checklist and ask about anything that's missing:

  • Who will own the domain, the hosting account and the website files?
  • Is SSL included, and is the design responsive on all devices?
  • Which CMS will be used, and can I edit the content myself?
  • How will page speed and basic SEO be handled at launch?
  • Are redirects planned if this replaces an existing site?
  • Who handles updates, backups and security after launch?

If a designer can answer those clearly, you're likely in good hands. If you'd like a second opinion on a proposal, or want me to build or look after your site, get in touch and tell me what you're working on.

Frequently asked questions

What is the difference between web design and web development?

Web design covers how a site looks and how people move through it, including layout, colours, typography and user experience. Web development is building it in code so it works, including the CMS, databases and integrations. Many freelancers, including me, do both.

What is the difference between a domain and hosting?

The domain is your address; hosting is the space where your website actually lives. You need both, and they can be with the same provider or different ones as long as DNS points the domain to the hosting.

Is UX the same as UI?

No. UI is the visual interface: buttons, menus and styling. UX is the whole experience of using the site, including how easy it is to find information and complete a task. Good UI supports good UX, but a beautiful site can still be frustrating to use.

Which web design terms should a business owner know first?

Start with domain, hosting, SSL, CMS, responsive design and maintenance. Those six cover ownership, security, editing and long-term costs, which are the areas where misunderstandings cause the most trouble.

Is "web design" the same as "website design"?

Yes. People use web design, website design and site design interchangeably to mean planning and designing how a website looks and works.

Leave a comment

Replying to ·

Keep reading