Website and marketing terms beginning with H

H.264

H.264 is the ITU standard associated with Advanced Video Coding, often abbreviated AVC. It identifies a picture encoding, separate from a container such as MP4. Ask for the actual exported configuration and review intended playback; the codec label alone does not guarantee a particular file size, quality or complete audio arrangement.

Also called: AVC, Advanced Video Coding

H1 heading

An H1 heading is the top-level heading in HTML, commonly used for a page’s main title.

Also called: H1

Hard link

A hard link allows more than one path to reference a single file in the same volume in the documented NTFS arrangement. Changes to that file are visible through its referring links. Keep this relationship distinct from independent copies when reviewing website sources or recovery material; several visible paths can still refer to the same underlying file.

Also called: Filesystem hard link

Hashing

Hashing maps input to a digest under an algorithm and is different from reversible encryption. Password storage needs an appropriate password-hashing design, not simply any fast hash. Ask the application maintainer to use current supported security practices rather than designing a custom password mechanism.

Also called: hash function

Headless CMS

A headless CMS manages content separately from the system that displays it, usually providing an API for websites or other channels. It can support shared structured information, but adds decisions about previews, publishing and integration maintenance. A Jersey business should choose the arrangement for a clear editing need rather than the label.

Also called: decoupled CMS

Health check

A health check probes a configured system or endpoint to assess a defined condition, often supporting monitoring or routing decisions. It confirms only what that check measures. Review the target, criteria and coverage, because a simple successful response does not establish that the full customer task or every dependency is working.

Heatmap

A website heatmap presents aggregated interaction information visually, such as areas receiving clicks or scroll activity. It can suggest where to investigate usability. It does not explain every visitor’s intention, and collecting interaction data requires appropriate privacy controls. Confirm an apparent problem by testing the actual task.

Heuristic evaluation

A heuristic evaluation reviews an interface against relevant usability principles. It relies on reviewers’ judgement and can identify issues for investigation. It differs from observing actual users complete tasks, so record the criteria and scope and avoid presenting the reviewer’s prediction as measured customer behaviour.

High cardinality dimension

A high cardinality dimension has many distinct values, which can contribute to large reporting tables and grouped results in Analytics. Review whether the chosen breakdown answers the business question. A long list of unique values needs an explained purpose before the owner can turn it into a useful content or campaign decision.

History API

The History API lets page code work with the browser’s session history, including navigation and relevant entry changes. It can support interfaces that update content without loading a whole new page. For a Jersey business, review Back, Forward, reload and direct links against the visible information; changing a history entry alone does not establish that the correct customer view appears.

History back

The History back method moves one entry back through the browser’s session history, with no effect when there is no previous entry. It is asynchronous navigation rather than a guarantee of reaching a particular service page. Review the actual supported route and distinguish returning to a view from reversing a business action.

Also called: history.back()

History forward

The History forward method moves one entry forward through the browser’s session history and is asynchronous. It uses the existing navigation route rather than create a new business result. Review the resulting information and address after a representative Back-and-Forward sequence, especially when the feature updates content within one page.

Also called: history.forward()

History go

The History go method navigates by an entry offset relative to the current session-history position. Negative offsets move back, positive offsets move forward, and zero or an omitted offset reloads. Have the maintainer explain the actual route and inspect its content rather than equate a history offset with a particular business stage.

Also called: history.go()

History push state

The History pushState method adds a browser session-history entry with associated serializable state and an optional same-origin URL. Adding the entry is separate from fetching and rendering the intended information. Review the actual customer view and Back-button route rather than assume a changed address establishes complete navigation behaviour.

Also called: pushState()

History replace state

The History replaceState method modifies the current session-history entry using the supplied state and optional same-origin URL. It differs from adding another entry. Agree why the feature should replace the current step, then inspect the actual content, address and supported Back or Forward route with the maintainer.

Also called: replaceState()

History state

The History state property exposes the state value associated with the relevant history entry without waiting for a popstate event. It helps code work with navigation state. Agree what the feature stores and how it restores the customer view; a state value is separate from confirmation that business information was saved at a receiver.

Also called: history.state

HMAC

HMAC is a hash-based message authentication code that combines a cryptographic hash function with a secret key to support message integrity and authentication. It does not make the message confidential. For a Jersey business, review the provider’s verification rules, key handling and exact message format before allowing an integration to act on a message claimed to be authentic.

Also called: hash based message authentication code

Homepage

A homepage is the main starting page of a website, usually reached at its root address. It should help visitors understand the business and choose their next step. For a Jersey company, clear services, location and contact routes matter more than fitting every detail onto this one page.

Also called: home page

Horizontal scaling

Horizontal scaling adds more relevant instances or components to handle work, rather than increasing one component’s capacity. The application must support the arrangement, including shared data and request handling. Review the actual bottleneck and workload before assuming that adding servers will improve every part of a website.

Also called: scaling out

Hot module replacement

Hot module replacement updates supported modules in a development session without necessarily reloading the whole page. It helps developers inspect changes while working. A development preview and a production build still have different roles, so verify the released output separately from a convenient local update.

Also called: HMR

Hour cycle

An hour cycle describes the clock-numbering arrangement used in supported locale and time-formatting operations. JavaScript Intl supports identified cycles associated with twelve- and twenty-four-hour presentation. Keep clock presentation separate from the appointment’s date and time-zone meaning, then review the actual displayed time and surrounding context for the intended reader.

Also called: Locale hour cycle

Hreflang

Hreflang annotations help describe language or regional alternatives for a webpage. They are relevant when genuine alternate versions exist, not a shortcut for targeting a place with unchanged content. Keep the versions, links and canonical choices consistent with the actual language experience.

Also called: language alternate annotations

HSTS

HSTS means HTTP Strict Transport Security. It tells a supporting browser to use HTTPS for a host during the policy’s effective period. Hostname scope, subdomain handling and stored browser policy matter. A Jersey business should confirm its HTTPS arrangement and affected services before a planned policy change, because removing a header does not immediately erase previously learned rules.

Also called: HTTP Strict Transport Security

HTML

HTML is the markup language that describes the structure and meaning of a webpage.

Also called: HyperText Markup Language

HTML input

An HTML input is a form control for entering or selecting information, with behaviour determined partly by its type and the browser or device. Different tasks need appropriate controls, clear labels and helpful instructions. For a Jersey business, review customer entries and the receiving workflow; choosing an input type alone does not verify the information or complete an enquiry.

Also called: input element

HTML sanitisation

HTML sanitisation processes supplied HTML to remove or restrict unsafe content while retaining permitted markup. It differs from displaying all input as plain text. Use a maintained, appropriate sanitisation arrangement and review how the result is subsequently handled, because later modifications can undermine the intended protection.

Also called: HTML sanitization

HTML slot

The HTML slot element is a placeholder within a web component for supplied markup. It lets the component present its structure together with content provided when it is used. Review the content contract and actual rendered result; a placeholder alone does not establish that the intended business information is present.

Also called: Slot element

HTML template

An HTML template stores markup that is not rendered by default and can be reused to create website content. Its content is available through a document fragment; supported declarative Shadow DOM is a distinct use. For a Jersey business, identify how the stored structure becomes a visible feature, receives approved information and behaves when required content or code is unavailable.

Also called: HTML template element

HTML template content

The HTMLTemplateElement content property exposes the template’s content as a document fragment. It gives code access to stored structure rather than establish that customers already see it on the page. Identify the instantiation and information-supply process with the maintainer, then compare the actual visible result with the business’s approved content.

Also called: template.content

HTMLCollection

HTMLCollection is an array-like collection of elements. In the HTML DOM it is live, updating as the underlying document changes. Review how the feature works with that collection, especially while adding or removing items, so the maintainer can explain the intended sequence and verify the actual customer result.

HTTP

HTTP is a protocol used for communication between a web client and a server. It describes requests and responses for resources. HTTPS adds transport encryption to that communication. A business site should use its intended HTTPS address consistently rather than asking customers to submit details over an unencrypted connection.

Also called: Hypertext Transfer Protocol

HTTP header

An HTTP header carries additional information in a request or response, such as content type or caching instructions. It is separate from the visible page body. A Jersey website review may need to inspect headers because important behaviour can come from hosting configuration rather than page text.

HTTP method

An HTTP method indicates the purpose of a request under the protocol’s semantics, such as retrieving a resource representation or submitting data. The method is separate from permission to perform the operation. Review the actual endpoint and implementation, including documented retry behaviour, instead of inferring the complete application outcome from the method name.

Also called: HTTP verb

HTTP representation

An HTTP representation is transferable information reflecting a resource’s state, with relevant metadata and data. A resource can have more than one representation, such as alternative formats. Distinguishing the resource from its representation helps explain content negotiation, version checks and what a website response actually contains.

HTTP request

An HTTP request is a message a client, such as a browser or application, sends to ask a server to perform an action on a resource. It includes a method and target, with relevant headers and sometimes content. Sending a request is separate from receiving a response and completing a business task.

HTTP response

An HTTP response is a message a server sends in reply to an HTTP request. It includes a status and relevant headers, and may contain a body such as page content or error details. A Jersey business should interpret the response alongside the requested operation and verify the application’s expected customer outcome.

HTTP status code

An HTTP status code is a server response value describing the handling of a request.

Also called: response code

HTTP/2

HTTP/2 is a version of HTTP that changes how messages are transported, including carrying multiple exchanges over one connection. It retains HTTP’s meaning for requests and responses. Ask the provider what is supported, then measure the actual page and connected services rather than assuming a fixed performance gain.

Also called: HTTP2

HTTP/3

HTTP/3 carries HTTP exchanges over QUIC rather than TCP. It keeps the same underlying request and response meanings while changing the transport arrangement. Hosting, browser and network conditions affect use. Verify the actual service and performance instead of promising that a protocol version guarantees faster enquiries.

Also called: HTTP3

HttpOnly cookie

An HttpOnly cookie has an attribute preventing relevant JavaScript access to its value through browser cookie interfaces. The browser can still send it with applicable requests. It can limit a particular exposure, but it does not stop all cross-site scripting or replace secure session and request handling.

HTTPS

HTTPS is HTTP carried over a connection protected by TLS.

Also called: secure connection

Hybrid business

For Google Business Profile, a hybrid business serves customers at its own business address and also visits or delivers directly to them. Its representation needs to meet the actual storefront and service-area requirements. Review the genuine customer arrangement before showing an address, and keep the website’s visit and coverage information consistent.

Also called: Google hybrid business

Hybrid search

Hybrid search combines methods such as keyword matching and vector search, then brings their results together. This can help when a collection includes both exact identifiers and questions expressed in different words. The combination still needs evaluation on actual tasks; it does not guarantee that the selected passage answers the customer’s question.

Hydration

Hydration connects interactive browser code to previously rendered page content. It lets a page begin with HTML and then gain scripted behaviour. Check that essential content remains understandable during loading and that the interactive component does not create confusing changes or duplicate controls.

Also called: component hydration

Hypervisor

A hypervisor provides the layer that runs and manages virtual machines over the underlying host resources. It handles relevant resource allocation and isolation. Review who maintains the host, the virtual machines and their applications, because responsibility for one layer does not automatically include the others.