A blind person hears it instead of seeing the photo, so it should say what is in the picture rather than stuff in keywords. Purely decorative images get an empty alt so they don't get in the way. It is one of the WCAG requirements and a simple piece of image SEO.
Glossary
Terms worth knowing
Short definitions of the things clients ask about most. Just the facts, no advertising.
-
Alt text
A description of an image for screen readers and search engines, also shown when the image fails to load.
-
API
The way two systems exchange data, for example a website fetching stock levels from a warehouse program.
-
Authentication and authorization
The first checks who you are, the second what you are allowed to do.
Logging in is authentication. Authorization is a separate question: whether this logged-in user may open a particular page or record. Confusing the two is the source of many serious vulnerabilities, including IDOR, so the permission check has to run on every request.
-
Backup
A copy of the files and database kept outside the website’s server, which lets you restore the site after a failure or an attack.
A copy stored only on the same server as the website is not a backup. In a serious failure it disappears together with the original. Every so often, check that restoring really works.
In practice: Dyżur: a daily database backup and a copy you can download with one click
-
Block editor (Gutenberg)
The WordPress editor in which you build a page from blocks: paragraphs, photos, buttons, layouts.
It lets you change content and layout without a developer, with a live preview. In modern block themes, the header, footer and templates are edited the same way. A well-prepared theme limits the choices to what fits the design, so it can't be broken by accident.
-
Brute-force attack
Guessing a password by automatically trying thousands of combinations.
On WordPress sites it goes on constantly: bots try the username admin and popular passwords. The effective defences are long, unique passwords, a limit on failed login attempts and two-factor authentication. Changing the login address only helps as an extra.
-
Cache
A ready-made copy of a page or file that displays faster than building it from scratch.
Cache works on several levels: in the visitor's browser, on the server and in the CDN. It speeds the site up, but it is sometimes the reason you still see the old version after changing content. A hard refresh (Ctrl+F5) or clearing the cache helps then.
-
Canonical URL
A hint to the search engine about which address is the original when the same content exists at several.
The same page can be reachable with parameters, with and without www, with and without a trailing slash. The canonical tag tells the search engine which variant to count, so signals aren't split between duplicates. It is set in the page's head.
-
CDN
A network of servers around the world that keep copies of files close to the visitor.
Instead of downloading images and scripts from a single server, the visitor gets them from the nearest node, so the site loads faster and the main server has less work to do. A CDN helps most with heavy traffic from many countries; for a local business, good hosting is usually enough.
-
CI/CD
Automation of building and deploying: an approved change in the code reaches the server on its own.
It reduces the most common source of failures when publishing, which is copying files by hand.
In practice: Dyżur: every change builds itself in GitHub Actions
-
CLS
Cumulative Layout Shift: a measure of how much content jumps around while the page loads. A good result is under 0.1.
The most common causes are images without specified dimensions and fonts that get swapped after the text has been rendered.
-
CMS
A content management system: an admin panel where you change texts and photos yourself, without knowing how to code.
The most popular one is WordPress. The alternative is lighter “headless” systems, where the admin panel is separate from the website itself.
In practice: Vantage Hunting: an advice section you can edit without a developer
-
Core Web Vitals
A set of measurable Google metrics describing how quickly and stably a page displays for the user.
The most important are LCP (when the largest element appears), INP (how quickly the page responds to a click) and CLS (whether content jumps around while loading).
-
CSP (Content Security Policy)
A header that tells the browser where the website may load scripts, styles and images from.
If someone injects a malicious script (XSS), a well-configured CSP can block it, because the script doesn't come from an allowed source. It is rolled out carefully: first in report-only mode to see what it would block, and only then is blocking switched on.
In practice: Guide: how to secure WordPress, including security headers
-
CSRF
An attack in which a foreign website forces a logged-in user to perform an action they didn’t intend.
A logged-in administrator opens a planted page, and it sends a request on their behalf, for example to change the password. One-time tokens in forms (nonces in WordPress) and the SameSite cookie attribute protect against this. Many plugins have vulnerabilities because they lack these safeguards.
-
CVE
The number of a publicly known vulnerability in a specific piece of software, for example CVE-2021-41773.
If a vulnerability has a CVE number, there is usually a fix too, most often in a newer version of the software. The number makes it easy to check whether the vulnerability affects your version.
In practice: Rysa: a scan result matched against CVE numbers
-
CVSS
A score from 0 to 10 of how dangerous a vulnerability is in itself. From 7.0 it is high, from 9.0 critical.
The number knows nothing about your business. Urgency also depends on whether the vulnerability is reachable from the internet and whether anyone is already exploiting it.
In practice: Guide: how to read a security audit report
-
CWE
A catalogue of types of software weaknesses, with numbers, for example CWE-79 for XSS.
A CVE describes a specific vulnerability in a specific product, while a CWE describes the class of flaw that such vulnerabilities come from. Audit reports often give both numbers, so the developer knows which error pattern to fix, not just one spot in the code.
-
DNS
The internet’s address book: it turns a domain name into the address of a server.
When you type lysyweb.pl, the browser asks DNS what IP address that website is at. This is also where you set where the domain's email goes. DNS changes take from a few minutes to a day to spread, which is why moving a website is planned with some margin.
-
Docker
A tool that packages an application together with its environment so it runs the same way everywhere.
This makes deployment to a new server repeatable and removes the need to configure the machine by hand.
In practice: Dyżur: the panel runs in a container on my server
-
Framework
A ready-made skeleton to build an application on, so you don’t have to write everything from scratch.
Astro and Next.js are popular for websites, Flutter for mobile apps. The choice of framework affects how fast the site is and who will be able to develop it later.
-
Frontend and backend
The frontend is the part you see in the browser; the backend is the server, logic and database working in the background.
A simple business card site may have no backend at all. A shop, a customer panel or a login already needs one.
In practice: Zdzichu: the device on the desk is the frontend, my server is the backend
-
GDPR
The EU regulation on personal data protection, called RODO in Poland and enforced there by UODO (the Polish data protection authority); on a website it covers contact forms and cookies, among other things.
The minimum is a privacy policy describing who processes the data and for what purpose, and collecting only the data that is needed for that purpose.
-
Git
A system that records every change to the code and lets you go back to it.
With Git you know who changed a given line, when and why, and a failed change can be undone in seconds. The code is also kept in a remote repository (for example GitHub), so a computer failure does not mean losing the project.
-
Headless CMS
A content editing system that doesn’t render the website: it hands only the data to another application.
You keep the content in the panel, and a separate application (the frontend) fetches it through an API and takes care of the look. It gives technical freedom, but it means two systems to maintain instead of one. For a typical business website, plain WordPress is simpler and cheaper to run.
-
Hosting
The server where your website’s files are stored and from which they are sent to visitors.
On cheap shared hosting you share resources with hundreds of other sites, which can show up in loading times. A VPS is a dedicated machine: more expensive, but predictable.
In practice: Guide: what a website really costs to run
-
HSTS
A header that tells the browser to connect to the website only over HTTPS.
After the first visit, the browser switches http to https by itself, so an attacker on a public network can't serve an unencrypted version. Before turning it on you have to be sure the whole website and all subdomains work over HTTPS, because undoing it is slow.
In practice: Guide: how to secure WordPress, including security headers
-
HTML, CSS, JavaScript
The three core languages of websites: HTML is the content and structure, CSS is the look, JavaScript is the behaviour and interaction.
-
IDOR
A flaw that lets you see someone else’s data by changing a number in the address, for example invoice/101 to invoice/102.
The application checks that you are logged in, but not whether the resource is yours. It is one of the most common flaws in web applications and a frequent finding in audits. It is fixed with a server-side permission check on every read.
-
INP
Interaction to Next Paint: a measure of how quickly the page responds to clicks, taps and typing.
INP replaced the earlier FID metric in Core Web Vitals. A good result is under 200 ms. Heavy scripts that block the browser make it worse, so plugins and widgets added without measuring are what most often ruin this metric.
-
JSON
A simple data format that programs use to exchange information.
It looks like a list of fields with values and is readable by humans. Most APIs return data in JSON. In SEO it is also used for structured data (JSON-LD), which describes the page to search engines.
-
Landing page
A single page focused on one goal, for example collecting enquiries about a service.
The menu is usually trimmed down, because every extra link is a chance for the visitor to leave before sending an enquiry.
-
Lazy loading
Loading images only when they get close to the visible part of the screen.
It shortens the time to the first display and saves bandwidth, because the browser doesn't download photos from the bottom of the page that nobody may ever see. It isn't used for the main image at the top of the page: delaying it makes the LCP metric worse.
-
LCP
Largest Contentful Paint: the time until the largest visible element of the page appears. A good result is under 2.5 seconds.
-
llms.txt
A file in the website’s root directory that describes its contents in a simple form for AI models.
It is a proposed standard, not an official norm, and no major engine has promised to use it. The cost is small: one page describing the offer and the most important addresses. It doesn't replace good content or structured data.
-
Meta description
A short description of the page that a search engine may show under the title in the results.
It doesn't directly affect ranking, but it decides whether someone clicks. It is around 150 characters long and should honestly summarise what is on the page. Google sometimes replaces it with its own snippet if it decides that fits the query better.
-
OWASP Top 10
A list of the ten most common categories of web application vulnerabilities, maintained by the OWASP organisation.
It is the reference point for audits: instead of looking for “anything at all”, you check the best-documented classes of flaws one by one.
In practice: Guide: OWASP Top 10 without jargon
-
Password hashing
Storing passwords as an irreversible hash instead of the password itself.
If the database leaks, the attacker gets hashes, not passwords. This is done with slow algorithms designed for passwords (for example Argon2, bcrypt), not plain MD5 or SHA-1, which can be cracked at billions of attempts per second. A password should never be visible in code or in logs.
-
Penetration testing (pentest)
A controlled attempt to break into an application, carried out with the owner’s consent, to find weaknesses before an attacker does.
It ends with a report: what was found, how serious it is and in what order to fix it. After the fixes, a retest is done.
In practice: Rysa: a phone as a station for checking networks
-
Plugin
An add-on for WordPress that adds a single feature, for example a form, a shop or backups.
Plugins are convenient, but each one is someone else's code on your website: it slows the site down and may have a vulnerability. Most WordPress break-ins start with an outdated plugin. That is why you install only the ones you need, with active support, and keep them updated.
In practice: Guide: how to secure WordPress, 12 steps in order of importance
-
Progressive web app (PWA)
A website you can add to your phone’s home screen and use like an app, without an app store.
It works on any phone and computer from a single codebase and can partly work offline. It has less access to phone features than an app installed from a store.
In practice: Guide: app or website
-
Rate limiting
A limit on how many times in a given period one user can trigger a given action.
It protects login and contact forms from password guessing and spam flooding, and APIs from overload. The limit is applied on the server, not in the browser, because the attacker controls the browser.
-
Responsive design
A website’s ability to display correctly on any screen, from a phone to a large monitor.
More than half of traffic in Poland comes from phones, so the design starts with the phone version (“mobile-first”) and only then is the desktop layout built.
-
REST API
The most popular way for applications to exchange data over the internet using ordinary web addresses.
An application sends a request to an address (for example, get the list of posts) and receives a response, usually in JSON. WordPress has its own REST API. Every endpoint of such an API has to be secured just like the website: check who is asking and what they are allowed to do.
-
robots.txt
A file in which you tell search engine robots what they may and may not access.
It is a request, not a protection: honest robots respect it, malicious ones don't. Don't hide addresses that are meant to be secret in it, because the file is public. It is good to point to the sitemap in it and not to block files needed to display the page.
-
security.txt
A file on the website that tells researchers how to report a vulnerability they have found.
It lives at /.well-known/security.txt and contains a contact, the language for reports and an expiry date. Thanks to it, a person who found a flaw knows whom to write to, instead of publishing it or giving up. It is described by the RFC 9116 standard.
-
SEO
Search engine optimisation: work that increases a website’s visibility in free (organic) search results.
SEO consists of a technical layer (speed, structure, structured data), content that answers the questions people type into a search engine, and links from other websites.
-
Sitemap
A file with a list of the website’s addresses that helps search engines find all its pages.
It usually lives at /sitemap.xml and is submitted in Google Search Console and Bing Webmaster Tools. A sitemap doesn't guarantee rankings or indexing, but it speeds up the discovery of new pages and shows which addresses you consider important.
-
Source code
The files your website is built from. They decide whether it can be developed further.
When you order a website, agree in writing that the code and access credentials pass to you once you have paid. Without that, changing developers can mean rewriting the site from scratch.
-
SQL injection
An attack that injects your own query into the database through an ordinary form field.
A successful attack can read or delete data. The defence is simple and has been known for years: parameterised queries instead of gluing text together.
-
SSL / HTTPS
Encryption of the connection between the browser and the server. It is where the padlock next to the site’s address comes from.
Without HTTPS, browsers mark the site as unsafe and data from forms travels as plain text. The certificate is free today and renews automatically.
-
SSL/TLS certificate
A certificate that lets the browser encrypt the connection and confirm that this really is that website.
Thanks to it, the address starts with https and the browser shows a padlock. Free certificates (for example Let's Encrypt) are fully sufficient for a typical business website and renew automatically. An expired certificate shows visitors a warning instead of the site.
-
SSRF
An attack in which a server is forced to send a request to a place the attacker can’t reach themselves.
If an application fetches an address supplied by the user (for example a link preview), the attacker can point it at an internal address, not reachable from the internet. The defence is an allowlist of permitted addresses and blocking internal networks, not just checking whether the address looks valid.
-
Staging environment
A copy of the website where changes are tried out before they go to the live site.
A plugin update or a new feature runs on the copy first. If something breaks, customers don't see it. It is standard for websites that earn money, because testing on the live site risks downtime at the worst possible moment.
-
Structured data (schema.org)
A description of the content, hidden in the code in a machine-readable format, for example that this is an FAQ, a service or a price.
Thanks to it, search engines can show an expanded result, and AI assistants have somewhere to quote facts about the business from.
-
Supply chain attack
A break-in through someone else’s code that you trust: a plugin, a library or a developer tool.
Instead of attacking your website, the attacker poisons a popular plugin or package, and the update delivers them access. It is limited by a minimum of dependencies, checking who maintains an add-on, updating after a short wait and backups you can quickly roll back to.
-
TTFB
Time to first byte: the time from the click to the first byte of the server’s response.
It shows how quickly the server starts responding, before the browser draws anything. A high TTFB usually means slow hosting, a heavy database or no cache. As long as it is bad, optimising images won't save the result.
-
Two-factor authentication (2FA)
Logging in with a password plus a second proof, for example a code from an app or a hardware key.
Even if the password leaks, nobody can log in without the second factor. Hardware keys and code-generating apps are best; SMS codes are convenient but weaker. For a website administrator's account, it is one of the cheapest and most effective safeguards.
In practice: Guide: how to secure WordPress, including two-factor login
-
VPS (virtual private server)
A separate slice of a physical server, with its own system and resources just for you.
It gives full control over the configuration, but also full responsibility: system updates, security and backups are on you or on the developer. Shared hosting is simpler; a VPS is more flexible and usually faster as traffic grows.
-
WAF (Web Application Firewall)
A filter in front of the website that rejects requests that look like an attack.
It checks traffic for known patterns, for example SQL injection attempts, before it reaches the application. It is an extra layer: it doesn't fix a vulnerability in the code, it only makes it harder to exploit. Rules that are too aggressive can block real users, so they need tuning.
-
WCAG and accessibility
A standard describing how to build websites that are usable by people with disabilities too. The level generally required is AA.
In practice this means, among other things, sufficient text contrast, full keyboard operation and alternative text for images. Everyone benefits, including people using the site in bright sunlight or with one hand.
-
WordPress theme
A set of templates and styles that decides how a WordPress website looks.
A ready-made theme from the directory is cheap, but often heavy and full of features you don't use. A custom theme is written for one website: lighter, faster and without unnecessary code. Content (texts, photos) is stored separately, so changing the theme does not delete it.
-
Zero-day
A vulnerability that attackers already know about and for which there is not yet a fix.
The vendor has zero days to fix it, hence the name. Updating alone doesn't protect against a zero-day, which is why layered defence matters: backups, a minimum of plugins, limited permissions and monitoring that notices unusual traffic.
Ready to start?
Let’s start with a conversation
Describe what you want to build. The reply contains the scope, the price and the timeline. The inquiry costs nothing and commits you to nothing.