Rule limiting requests over a period and scope, such as an account, key or other criterion. HTTP 429 can signal the limit, sometimes with Retry-After. Clients need appropriate retry handling; immediately repeating the same request can prolong failure rather than resolve it.
Real User Monitoring (RUM): measurement of performance and errors encountered during real visits. Results depend on the devices, networks, pages and visits actually represented in collection.
HTTP response indicating a permanent move to the address supplied by Location. Check destination and method; deleted pages should not all lead to an unrelated homepage. Check the final destination and possible loops. Redirecting an old record to the homepage does not guarantee that the visitor’s need remains satisfied.
HTTP response indicating a temporary move to another address. Some clients may convert POST to GET; if the method must be preserved, examine the appropriate status. Document the temporary reason and check the intended return path. A redirect chain adds steps without making content equivalent.
Sequence of redirects before the final destination. Each step adds an exchange and can create a loop; use a relevant destination and update internal links too.
Traffic attributed by an analytics tool to links from other websites under its collection and classification rules. The referral category depends on available source information and configured exclusions. It therefore does not necessarily capture every link followed or every person involved.
In practice: examine referring domains and a known test journey. Check returns from a payment provider and relevant exclusions before treating them as new acquisition; a missing domain in a report does not prove that no visitors came from it.
Organisation through which a domain is registered and managed. Registrar, DNS provider and hosting provider can differ; keep their responsibilities and access arrangements distinct.
Resource whose processing delays a step required to display the page. Its effect depends on type, placement and loading mode. Reducing blocking must preserve essential styles and behaviours; a large resource does not necessarily block rendering in the same way.
Operations turning a document and styles into displayed pixels, including style calculation, layout, painting and compositing. A size change can trigger new layout work. Downloading files quickly therefore does not alone guarantee a responsive interface.
Stated period between receipt of an enquiry and a useful first reply. It needs a defined starting point, treatment of non-working periods and scope of requests.
In practice: state a response period the team can meet and review requests that exceed it.
Design that adapts layout, media and text to available space. Flexible grids alone are insufficient: also check navigation, long content and essential tasks at intermediate widths.
Image whose file or crop adapts to display context. Distinguish resolution selection from art direction: changing the crop is more than compressing the same file.
API designed around REST architectural constraints, including identifiable resources and stateless exchanges. Using JSON or HTTP alone does not establish that an API follows REST. HTTP methods and statuses should match the action. Do not assume that a read operation has no side effects from its URL shape alone.
Intermediary placed in front of servers to receive and forward requests. It can handle balancing, TLS or caching according to configuration. Addresses and forwarded headers must be interpreted within that chain; the application server may not see the original client directly.
File at a host’s root communicating crawl rules to supporting robots. It is neither access control nor a guarantee of removal from an index: links can still make a blocked URL known.
Return on Investment: relationship between value obtained and resources committed to an action or project.
Apply this term to a comparison
The comparator adds entered costs; it predicts neither future revenue nor return on investment. Lower cost does not prove better results. Keep documented expenses separate from measured outcomes.
Organisation of accessible actions and resources by profile and context. Permissions require server-side checks for each request and target object. A useful test compares two accounts and a resource owned by each; hiding the access button does not protect request handling.
In common web and SEO usage, the registrable domain to which subdomains belong, such as example.co.uk for shop.example.co.uk. It cannot always be inferred from the final two labels. This usage differs from the technical DNS root at the top of the naming hierarchy.
In practice: identify the registered domain, its holder and active subdomains before migration. A public suffix list helps locate the domain boundary; it does not establish purchase availability or ownership.
Definitions written for people, structured for machines.
The entries are editorially reformulated in plain language, connected to stable URLs and represented with DefinedTerm structured data. They provide orientation, not a substitute for official standards, legal advice or vendor documentation.