Last reviewed 26 July 2026

AI, automation and web glossary.

Clear explanations of the terms that come up when planning websites, automation, AI and custom software, written for independent businesses and grounded in practical use.

Showing 70 of 70 terms.

AI

#

AI agent

Software that uses an AI model to choose and carry out steps towards a defined goal, often through tools or connected systems.

Why it matters

An agent can coordinate multi-step work, but every permission, failure path and consequential decision still needs a clear boundary.

A scripted workflow that follows fixed rules is automation, but it is not necessarily an AI agent.

Websites

#

CMS

Content management system

Software that lets authorised people create or update website content without editing the underlying code directly.

Why it matters

A CMS is useful when the business genuinely needs regular structured updates. It also adds permissions, maintenance and training responsibilities.

A website does not need a CMS merely because content might change occasionally.

Websites

#

Conversion

A defined useful action completed by a visitor, such as sending an enquiry, booking through an existing platform or making a purchase.

Why it matters

A conversion should describe a real action and be measured without inventing business results or sending personal form values into analytics.

Websites

#

DNS

Domain Name System

The system of records that connects a domain name to website, email and verification services.

Why it matters

A website launch must change only the records needed for the new service and preserve unrelated email and security records.

Websites

#

Domain name

The human-readable address used to reach a website or another internet service, such as feralonline.com.

Why it matters

The business should control its important domain account and preserve email and verification records when website hosting changes.

Search

#

Largest Contentful Paint

LCP

A Core Web Vital that measures when the largest visible content element in the initial viewport finishes rendering.

Why it matters

LCP is a practical signal for perceived loading speed and is affected by hosting, images, fonts, CSS and rendering decisions.

Apps

#

Local-first software

Software designed so important data and core use remain available on the user's device, with network services added where useful.

Why it matters

A local-first design can support offline use and user control, but backup, synchronisation and multi-device conflict decisions still matter.

Websites

#

Mobile-first design

Planning the core layout and journeys for constrained mobile screens before adding space and enhancement for wider viewports.

Why it matters

Mobile-first work forces priorities to be clear, especially for local-business journeys such as menus, calling, booking and directions.

Websites

#

Page speed

The practical loading and interaction performance experienced when a visitor uses a page.

Why it matters

Fast, stable pages reduce friction, but one laboratory score cannot guarantee every device, connection, ranking or business outcome.

Privacy and security

#

Rate limiting

Restricting how many requests a client can make during a period of time.

Why it matters

Rate limiting helps protect forms and APIs from abuse, but the threshold and identifier should avoid blocking ordinary use or collecting unnecessary data.

Websites

#

Responsive design

A layout approach that adapts content and controls to different viewport sizes, zoom levels and device capabilities.

Why it matters

Responsive work keeps reading, navigation and actions usable across phones, tablets, laptops and wide screens rather than shrinking one desktop layout.

Apps

#

Version control

A system that records changes to source files so work can be reviewed, compared and restored.

Why it matters

Version control supports safe collaboration and rollback, but it must not contain secret values and does not replace a production data backup.