GWebsites
A Google service measuring events and analysing website and app use. Report quality depends on setup, consent and data coverage. Reports are neither complete visit records nor automatic evidence of campaign effectiveness.
Definition and sources→GWebsites
A Google tool assessing a page through lab testing and, when available, real-user data. Scores can vary between runs. A high score does not replace usability testing or cover every browsing condition.
Definition and sources→GSEO / Websites
A Google service reporting on search presence, indexing and selected technical problems. It does not purchase rankings. Reports change over time, and the tool does not guarantee every submitted page will be indexed.
Definition and sources→GWebsites
A file-based CMS not requiring a conventional relational content database. It supports themes and plugins; backups must include files and configuration.
Definition and sources→GWebsites
A website performance-testing service with defined test conditions. Results depend on location and device profile and do not replace real-user data.
Definition and sources→GWebsites
A lossless compression format used in HTTP among other contexts. It reduces text-resource transfer but requires compatible client and server support.
Definition and sources→HWebsites
A three-line-icon button opening navigation. It needs an accessible name, expanded-state information and correct keyboard operation.
Definition and sources→HWebsites
An architecture separating the storefront from commerce services through APIs. It offers presentation flexibility but adds integration, SEO and frontend-maintenance responsibilities.
Definition and sources→HProgramming / Servers
An Apache configuration file affecting a directory when the server permits overrides. It can control redirects and access. It is not universal to every hosting server; Nginx does not read it like Apache.
Definition and sources→HSEO / Websites
The h1–h6 elements express content hierarchy, not font size. One principal h1 is a clear editorial convention. The number of h1 elements is not a simple Google ranking rule.
Definition and sources→HServers / Websites
An application protocol using requests and responses, including for websites and APIs. It defines methods, headers and statuses. Protocol statelessness does not prevent applications from implementing sessions.
Definition and sources→HServers / Websites
An HTTP status indicating a resource has moved permanently. The server normally provides the new address in Location. It is a redirect, not an error, and does not guarantee preserved search rankings.
Definition and sources→HServers / Websites
An HTTP status indicating a temporary redirect while the original address remains the reference. It is not an error. Indexing effects depend on context rather than a blanket rule that 302 never affects search.
Definition and sources→HServers / Websites
An HTTP status indicating that the server refuses the request, possibly because of permissions or access rules. A TLS certificate failure is not a 403 response. Resolve permissions with the administrator instead of bypassing protections.
Definition and sources→HServers / Websites
An HTTP status indicating that a resource was not found or its existence is not disclosed. Check addresses and links. DNS failure happens at a different stage and is not itself an HTTP 404 response.
Definition and sources→HServers / Websites
A general HTTP status signalling an unexpected server-side problem. It does not identify a specific cause. Diagnosis requires safe inspection of logs and configuration; updating PHP at random is not a universal fix.
Definition and sources→HServers / Websites
An HTTP status indicating that the server does not support, or refuses to support, the major protocol version used in the request. It concerns HTTP, not the browser version or a general network outage.
Definition and sources→HWebsites
Headers controlling selected browser protections, such as CSP and HSTS. They need application-specific configuration; their presence does not prove absence of vulnerabilities.
Definition and sources→HWebsites
A browser policy enforcing HTTPS for a host. Long lifetimes and subdomain coverage should be enabled only after the full scope is ready.
Definition and sources→HServers / Websites
HTTP carried over a TLS-protected connection. It protects transmission confidentiality and integrity and supports server authentication. A padlock does not establish the owner's honesty or protect against every application defect.
Definition and sources→IWebsites
A responsiveness metric describing interaction latency until the next visual update. It covers more stages than historical FID and is part of Core Web Vitals.
Definition and sources→IProgramming / Projects
Tools and activities for processing, storing and communicating information. Business IT includes applications, devices, networks and their maintenance. It extends beyond programming.
Definition and sources→JWebsites
An approach separating presentation from services through generated assets and APIs. It does not mean every site is static or needs no server.
Definition and sources→JProgramming / Websites
A programming language used in browsers and server environments for events, data and application logic. JavaScript and Java are different languages. Modern engines can use just-in-time compilation.
Definition and sources→