# WebPro Company OÜ > Drupal development partner in Estonia — maintenance, migration, custom modules, automated testing, WCAG and AI/GEO readiness audits. WebPro Company OÜ helps organisations maintain, upgrade and develop complex Drupal platforms. Main topics: Drupal maintenance, security updates, Drupal 7/8/9/10 → 11 migration, custom modules, API integrations, automated testing (Playwright + PHPUnit), WCAG accessibility, AI/GEO/LLMO readiness, structured data and llms.txt. Contact: WebPro Company OÜ — technical lead Kaido Toomingas, kaido@webpro.ee, +372 53 533 822 Location: Estonia Service area: Estonia and international ## Services - [Home](https://webpro.company/): Drupal development partner in Estonia — maintenance, migration, custom modules, automated testing, WCAG and AI/GEO readiness audits. - [Drupal AI and GEO readiness audit](https://webpro.company/ai-drupal): If an organisation's Drupal site needs to be understandable to AI systems, adding a single AI-friendly text block is not enough. We review content structure, metadata, permissions, APIs, security risks and whether machines can interpret the public information correctly. - [When you need an audit, tests or a second opinion](https://webpro.company/audit-and-testing): Use this path when you want to know the technical state before a larger change, or need confidence that key workflows will not break. - [Automated testing for Drupal projects](https://webpro.company/automated-testing): Tests make change safer: before updates reach the public platform, we check critical user flows, business rules and code quality. - [Custom Drupal development and module development](https://webpro.company/custom-drupal-development): Off-the-shelf Drupal modules do not cover every need. We write custom modules, integrations and workflows to Drupal API standards — exactly what the business logic requires. - [Drupal 10, 11 and 12 readiness check](https://webpro.company/drupal-10-11-12-readiness): Late 2026 is a practical checkpoint for Drupal sites. Drupal 10 reaches end of life, Drupal 12 arrives and it is better to know the real upgrade blockers before they become urgent. - [Moving from Drupal 6 or 7 to Drupal 11](https://webpro.company/drupal-6-7-migration): Use this path when the platform is on a very old Drupal version and patching is no longer a responsible plan. For the client, this means building a new system without losing important content, business logic or visibility. - [Upgrading Drupal 8, 9 or 10 to Drupal 11](https://webpro.company/drupal-8-9-upgrade): Use this path when the site is already on the modern Drupal generation, but updates have stalled. For the client, this means extending the life of the existing site while keeping content and core workflows in place. - [Drupal development](https://webpro.company/drupal-development): WebPro is a Drupal development partner since Drupal 6. We build new platforms, extend existing ones, develop custom solutions and ensure long-term technical reliability. - [Drupal maintenance — controlled updates and technical ownership](https://webpro.company/drupal-maintenance): Ongoing maintenance is not just about applying security patches. It means that changes are tested before deployment, risks are mapped and someone understands the system's history. - [Drupal 7 to Drupal 11](https://webpro.company/drupal-migration): Drupal 7 support ended in 2023. We move the platform to supported Drupal 11 — starting with a risk review, a realistic scope and a quote. - [Drupal takeover audit](https://webpro.company/drupal-takeover): When the previous developer is gone, the first task is not building a new feature. The first task is understanding where the code, data, access, backups and largest risks are. - [When an old Drupal platform needs an upgrade](https://webpro.company/drupal-upgrade): Use this path when your Drupal platform runs on an older version, updates have stalled or you need a controlled move to Drupal 11. The first goal is to understand whether the work is a content migration, a regular upgrade or a larger rebuild. - [Pricing and terms](https://webpro.company/pricing): We publish approximate prices — a precise quote always comes after reviewing your system. - [Why Drupal?](https://webpro.company/why-drupal): Drupal is not the right choice for every website. It makes sense when the website or information system needs complex content, workflows, integrations, permissions and long-term development. ## Case studies - [Palmako associated websites development and support](https://webpro.company/work/palmako): Five associated websites migrated from Drupal 7 onto a shared Drupal codebase — a cooperation running since 2016, now on Drupal 11 — with per-brand customisation and a shared maintenance workflow. - [Estonian Chamber of Commerce and Industry Drupal solution](https://webpro.company/work/koda): A complex Drupal solution where purchase and member workflows, security, accessibility, GDPR compliance and analytics were improved — plus an online store, API integrations and ongoing development support for over five years. - [State Real Estate Ltd Drupal maintenance and custom development](https://webpro.company/work/rkas): Drupal platform maintenance, custom development including a procurements module, security improvements and WCAG 2.1 AA accessibility work. - [Tallinn Health Care College — Drupal 7 to Drupal 11](https://webpro.company/work/ttk): WebPro migrated Tallinn Health Care College's website from Drupal 7 to Drupal 11. An institutional platform with over 5,000 pages, about 40 content editors, a component-based frontend and ongoing support. - [International Melges24 Class Association](https://webpro.company/work/melges24): Drupal development and ongoing support for a US-based international sailing class — covering member management, event systems, results and ranking functionality across 26 countries. - [Tartu Oskar Luts City Library — Drupal migration and security work](https://webpro.company/work/luts): Two Drupal platforms managed by Tartu Oskar Luts City Library upgraded from legacy versions to Drupal 11 with security updates, WCAG accessibility work and GDPR compliance. - [WebPro website](https://webpro.company/work/webpro): A fully custom solution — Node.js static generator, written with Claude and Codex assistance, two language versions, live Drupal scanner. Not Drupal, not a ready-made framework. - [Pegasus.ee — CMS migration and Drupal updates](https://webpro.company/work/pegasus): E-commerce migration from a legacy CMS to Drupal 7, subsequent Drupal 8–10 upgrades and ongoing maintenance. - [Suveniiritehas.ee Drupal e-commerce](https://webpro.company/work/suveniiritehas): Drupal-based online store for Estonian souvenirs with a product catalogue and ongoing maintenance support. - [Eestitoit.ee Drupal 7 → Drupal 10 migration](https://webpro.company/work/eestitoit): Drupal 7 platform migrated to Drupal 10 with content, structure and functionality updated throughout. - [All case studies](https://webpro.company/work/) ## Blog — selected articles - [Blog index](https://webpro.company/blog/) ### Security - [Drupal roles, permissions and editorial workflow](https://webpro.company/blog/drupal-roles-permissions-and-editorial-workflow): Drupal allows very detailed role and permission management. That is exactly why permissions should be reviewed regularly instead of leaving years of exceptions in place. - [How to check if a Drupal module is risky](https://webpro.company/blog/how-to-check-if-a-drupal-module-is-abandoned-or-risky): A Drupal module can solve a problem quickly, but the wrong module can later make updates, security patching and migration difficult. - [Drupal security in practice — what actually happens when you skip updates](https://webpro.company/blog/drupal-security-in-practice): Drupal security updates feel like tedious routine — until the day your site is compromised. Here is the real picture of what happens and how to protect yourself. - [Drupal security incident plan — what to do when your site is compromised](https://webpro.company/blog/drupal-security-incident-plan): During a security incident there is no time to start planning. Here is a step-by-step guide that every Drupal site owner should prepare in advance. - [Drupal backup restore test — why "backup exists" is not enough](https://webpro.company/blog/drupal-backup-restore-test): A backup that has never been restored is an untested hypothesis. Here is how to make sure your Drupal backup actually works. ### Migration - [Drupal 7 Migration Statistics in 2026: What the Numbers Really Mean](https://webpro.company/blog/drupal-7-migration-statistics-2026): A Drupal 7 migration in 2026 should not be treated as a simple technical upgrade. The statistics point to a wider operational risk that requires audit work, budgeting, content migration planning, and editorial interface decisions. - [Drupal CMS 1 to Drupal CMS 2 upgrade](https://webpro.company/blog/drupal-cms-1-to-2-upgrade): Drupal CMS 2.0 brings a new starting point, Canvas and site templates, but an existing site created from Drupal CMS 1 does not automatically become the same thing. Before changing it, you need to understand what the site actually uses. - [How much does a Drupal upgrade cost](https://webpro.company/blog/drupal-upgrade-cost): The same Drupal version upgrade can be a small maintenance task on one site and a full migration on another. The difference comes from content, modules and business logic. - [Drupal 10 end of life and Drupal 11 readiness](https://webpro.company/blog/drupal-10-end-of-life-and-drupal-11-readiness): A Drupal 10 site does not break overnight. The risk appears when the upgrade plan is left too late and dependencies are not ready. - [Drupal 7 in 2026: what to do with an old site](https://webpro.company/blog/drupal-7-in-2026-what-to-do): A Drupal 7 website can still look fine in 2026, but official security support has ended and every new change is becoming harder to control. - [Drupal Migrate API — how to bring content from another system](https://webpro.company/blog/drupal-migrate-api): Content migration is part of every significant Drupal project. Migrate API is the right tool for the job — here is how it works and what to plan for. ### Development - [Drupal admin interface as an editorial workbench](https://webpro.company/blog/drupal-admin-interface-editorial-workbench): Drupal is a strong platform for complex digital services, but its long-term value depends on how well people can use it every day. The admin interface should support the editorial team, not slow it down. - [Component-based Drupal — how it is built in practice](https://webpro.company/blog/component-based-drupal): Drupal has several ways to build a page from components. Which one fits depends on whether the layout decision belongs to the editor or the developer. - [Contact form without reCAPTCHA — catching bots without Google](https://webpro.company/blog/contact-form-without-recaptcha): Most spam on contact forms does not come from humans — it comes from bots. Bots behave differently from humans, and that difference is enough to build protection on without Google's help. - [Headless Drupal — when it actually makes sense](https://webpro.company/blog/headless-drupal-when-it-makes-sense): Headless has been a popular term for a few years. Like all architectural choices, it suits some projects well and others not at all. - [How much does a Drupal website cost?](https://webpro.company/blog/drupal-website-cost): "How much does a Drupal website cost?" — there is no single answer, because Drupal is a platform, not a product. Here is what the price actually covers. - [Drupal multisite — one platform, multiple websites](https://webpro.company/blog/drupal-multisite): When an organisation runs multiple websites — different brands, regions or products — that does not necessarily mean multiple separate platforms. - [Modern website checklist — security, performance, GDPR and AI readiness](https://webpro.company/blog/modern-web-requirements): The question is no longer only whether a website works. It must meet a range of parallel requirements — some regulatory, some technical, some tied to how search engines and AI agents read the web. - [Who builds a modern website — the skills and roles involved](https://webpro.company/blog/modern-website-team): When a website must meet security, performance, accessibility, privacy and SEO requirements at the same time, it is no longer a one-person job. Each layer needs its own expertise — and those areas of expertise must fit together. - [How WebPro built its website — custom build, AI-assisted, honest review](https://webpro.company/blog/how-webpro-website-was-built): The WebPro website is not Drupal and not a ready-made framework. It is a Node.js static generator written from scratch, with most of the code written by AI. This is an honest account of how that happened and what it actually meant. - [Drupal go-live checklist](https://webpro.company/blog/drupal-go-live-checklist): A new or updated Drupal site goes live more smoothly when the final day is not driven by memory. - [Website budget: work that is often missing](https://webpro.company/blog/hidden-work-in-a-website-budget): Website cost is not only design and development. Budget is also affected by content, migration, testing, accessibility and maintenance after launch. - [What to ask a web developer before signing](https://webpro.company/blog/what-to-ask-a-web-developer-before-signing): Web project problems do not come only from code. They often come from failing to agree how the result will be tested, handed over and maintained. - [What a good web project brief contains](https://webpro.company/blog/web-project-brief): A brief is not a formality — it is an agreement. The more precisely it describes what needs to be done, the less room there is for interpretation, surprises and extra costs later. - [Technical debt in web projects — how it builds and what it costs](https://webpro.company/blog/technical-debt-in-web-projects): Every web project accumulates technical debt over time. That is not a failure — it is inevitable. The question is whether it is managed consciously or left to grow until it becomes an obstacle. - [When Drupal needs refactoring, not only an update](https://webpro.company/blog/when-drupal-needs-refactoring): A Drupal upgrade improves the platform's technical state, but it does not automatically fix a poorly designed workflow, data model or custom code. - [Drupal Search API — search that actually works](https://webpro.company/blog/drupal-search-api): Search is often the most-used feature of a site — and the most often done poorly. Here is how to set it up properly in Drupal. - [Drupal Paragraphs module — flexible content builder](https://webpro.company/blog/paragraphs-module-drupal): Paragraphs makes content structured and editor-friendly — but requires thoughtful component design upfront. - [Drupal Layout Builder vs Paragraphs — when to use which](https://webpro.company/blog/drupal-layout-builder-vs-paragraphs): Two common approaches to flexible page building in Drupal. Here is what sets them apart and when to use which. - [Drupal Views — what it is and when it falls short](https://webpro.company/blog/drupal-views-when-it-falls-short): Views is at the heart of Drupal — almost every listing, search result and archive is powered by Views. Here is what it is and where it falls short. - [Drupal configuration management — why config sync matters](https://webpro.company/blog/drupal-configuration-management): Drupal configuration — content types, views, fields, roles — lives in the database. Config sync moves it to git. Here is why that changes everything. - [Drupal custom module development — when it makes sense and what it costs](https://webpro.company/blog/drupal-custom-module-development-cost): Drupal has thousands of contributed modules — but sometimes none of them cover the exact need. Here is when a custom module is the right choice and what it means. ### Testing - [Visual regression testing for websites](https://webpro.company/blog/visual-regression-testing-for-websites): A normal automated test checks whether a button works. Visual regression testing helps check whether the button, form or component is still in the right place and readable. - [Playwright tests for forms, menus and carts](https://webpro.company/blog/playwright-tests-for-forms-menus-and-cart): Automated testing does not need to start with a large suite. Forms, menus, search and carts are often enough for the first useful step. - [Automated tests do not need to start big](https://webpro.company/blog/automated-tests-for-drupal): Testing does not have to cover the whole system from day one. A small set that checks the most important workflows often gives the highest value. ### AI - [Managing Drupal content with ChatGPT and MCP](https://webpro.company/blog/managing-drupal-content-with-chatgpt-and-mcp): Drupal content can be managed by machines without giving up human control. The key is not to hand ChatGPT the full admin interface, but to expose narrow MCP tools: find an article, open a draft, propose a change, validate it, show the diff and let a human approve publishing. - [AI agents do not only read web pages: how to make a Drupal site understandable and safe for machines](https://webpro.company/blog/drupal-ai-agents-llm-geo-readiness): AI agents do not browse the web in the same way people do. They look for structure, APIs, permissions, verifiable answers and trustworthy sources. Drupal has strong foundations for this, but only when the platform is deliberately maintained and structured. - [AI builds your site and deploys it. But who's responsible?](https://webpro.company/blog/ai-builds-and-deploys-sites): OpenAI Codex Sites builds a website and hosts it automatically — no server to manage, no web developer needed. Sounds great. But who's responsible when something goes wrong? - [AI content generation for websites — where it helps and where it harms](https://webpro.company/blog/ai-content-generation-for-websites): AI tools have made content writing more accessible and faster. But accessibility does not mean the result is good — and poor content can harm SEO and credibility more than no content at all. - [AI as a developer-guided assistant](https://webpro.company/blog/ai-as-developer-assistant): AI is not a tool that should act alone inside a client system. It is most useful when a person guides, checks and decides. - [AI in code review: benefits, limits and responsibility](https://webpro.company/blog/ai-in-code-review): AI works well as a code review assistant when it helps raise questions. It should not be the final authority on whether a change is safe and business-correct. - [How AI helps plan a Drupal migration](https://webpro.company/blog/ai-in-drupal-migration-planning): Drupal migration includes a lot of repeated analysis: modules, fields, custom code, logs and test scenarios. AI can help when it is used with guidance. - [Drupal AI modules — what they actually do](https://webpro.company/blog/drupal-ai-modules): Drupal has a growing ecosystem of AI modules — from content generation to translation, search and moderation. Here is an overview of the most relevant ones. ### Drupal - [Drupal core July security updates: what site owners should check now](https://webpro.company/blog/drupal-core-july-security-updates): On July 15, 2026, Drupal published several core security advisories. If an organisation's website, portal or service platform runs on Drupal, now is the time to check not only the version number, but the whole update process. - [Drupal vs Headless CMS: which approach fits a large organization's digital platform?](https://webpro.company/blog/drupal-vs-headless-cms): When an organization plans a new digital platform or modernizes an existing Drupal website, the discussion often turns to one question: should Drupal be used as a full content management and web platform, or should the organization move toward a headless CMS model? The right answer depends less on the trend and more on how content, services, users and administration work in practice. - [Drupal CMS 2.0 and Canvas in a client project](https://webpro.company/blog/drupal-cms-20-canvas-client-project): Drupal CMS 2.0 promises a faster start, visual page building and AI-assisted workflows. In a client project, the important question is not only how good the demo looks, but how the solution behaves two years later. - [Drupal CMS vs Drupal — what is the difference?](https://webpro.company/blog/drupal-cms-vs-drupal-core): The Drupal CMS announced by the Drupal Association has caused confusion — is it a separate product? Is old Drupal going away? No and no. - [Drupal scanner: a public pre-check before maintenance or upgrades](https://webpro.company/blog/drupal-scanner-public-precheck): The real state of a Drupal website is best checked with access to code, logs, configuration and the database. A public scanner still helps reveal visible warning signs quickly. - [Schema.org structured data — a practical guide for Drupal](https://webpro.company/blog/structured-data-schema-org): Structured data is a machine-readable layer added to a page — it changes nothing visible to the user, but tells search engines and AI systems precisely what they are looking at. - [Why we automate Drupal work as much as possible](https://webpro.company/blog/git-composer-and-automated-drupal-workflow): Good Drupal work is not only about writing code. It is also about how a change moves from a developer machine to a test environment and then to the public website. - [Core Web Vitals in Drupal — common problems and how to fix them](https://webpro.company/blog/core-web-vitals-in-drupal): Google measures three performance metrics — time to load the largest element, layout stability and response time — and uses them in search ranking. Drupal sites have specific causes and solutions for each. - [Drupal 11 migration: plan before code](https://webpro.company/blog/drupal-11-migration): The first task in a Drupal migration is usually not writing code. The first task is understanding what exists and what the business depends on. - [Multilingual Drupal website — how it works](https://webpro.company/blog/multilingual-drupal-website): A multilingual website is not simply translated content. It is a separate content strategy, a separate URL structure, separate SEO logic and a separate editorial workflow. Drupal supports all of these at once. - [Drupal vs WordPress — when to use which](https://webpro.company/blog/drupal-vs-wordpress): Drupal and WordPress are both widely used, but they have different strengths. The choice depends on site complexity, security requirements, content structure and available development resources. - [Drupal migration, upgrade or maintenance — how to choose](https://webpro.company/blog/drupal-migration-upgrade-or-maintenance): Many Drupal site owners know something needs to be done — but not exactly what. Maintenance, upgrade and migration solve different problems and cost differently. - [Composer in a Drupal project: why it matters](https://webpro.company/blog/composer-in-a-drupal-project): If modules are copied manually to the server, the Drupal update process is no longer easy to track. Composer solves that problem. - [Why Drupal suits the public sector](https://webpro.company/blog/drupal-for-public-sector): Government and education websites have specific requirements: WCAG accessibility, data protection, long-term support and open source. Drupal meets all of them. - [How long does a Drupal project take — realistic timelines](https://webpro.company/blog/drupal-project-timeline): The Drupal project timeline is one of the most asked and most underestimated topics. Here are realistic estimates and what actually drives the schedule. - [Fixed price vs hourly rate — which suits a Drupal project](https://webpro.company/blog/fixed-price-vs-hourly-drupal): "How much will it cost?" — the answer depends on how the contract is structured. Fixed price and hourly rate are both reasonable, but in different situations. - [How Drupal projects stall — and how to avoid it](https://webpro.company/blog/why-drupal-projects-stall): A Drupal project is not just stalled when the code does not work. It is stalled when invoices keep growing, deadlines keep slipping, and nobody knows what happens next. - [Which CMS platforms Estonian businesses use — and why Drupal stands out](https://webpro.company/blog/cms-landscape-estonia): Choosing a CMS is a long-term decision. Here is an overview of the Estonian web market and when Drupal is the right choice compared to cheaper alternatives. ## Optional ### Maintenance - [Hiring a Drupal agency outside your country — what actually matters](https://webpro.company/blog/drupal-agency-outside-your-country): When you search for a Drupal partner, geography is often the first filter. It should probably be the last. - [Drupal hosting requirements — what to expect from a server](https://webpro.company/blog/drupal-hosting-requirements): Wrong hosting does not take a Drupal site down — but it makes updates harder, performance worse and maintenance more expensive. Here is what to check. - [Maintenance contract or one-off fix for a Drupal site](https://webpro.company/blog/maintenance-contract-or-one-off-fix): Not every website issue needs a maintenance contract. At the same time, some Drupal sites carry business-critical risk if support is only occasional. - [Why an old website can be a business risk](https://webpro.company/blog/why-an-old-website-can-be-a-business-risk): An old website is not only a problem when it breaks. Often the real risk is that nobody can change it safely anymore. - [Drupal security updates — why they cannot be postponed](https://webpro.company/blog/how-drupal-security-updates-work): Drupal has one of the more mature security processes among open-source CMS platforms. But applying a security update is not simple — it is technical work that requires planning. - [What happens when a Drupal site is not updated](https://webpro.company/blog/what-happens-when-drupal-is-not-updated): Nothing happens to an unmaintained Drupal site — until something does. Accumulating known vulnerabilities, ageing dependencies and rising remediation costs are real consequences, not theoretical risks. - [PHP version and Drupal hosting](https://webpro.company/blog/php-version-and-drupal-hosting): A website may appear to work while the server already runs an outdated PHP version. That quiet risk should be visible before major upgrades. - [How to choose a Drupal maintenance partner](https://webpro.company/blog/how-to-choose-a-drupal-maintenance-partner): Drupal maintenance is not just having a developer available in an emergency. It is recurring work that keeps the platform secure, tested and maintainable. - [What to do when the previous developer is gone — taking over a Drupal project](https://webpro.company/blog/taking-over-drupal-from-previous-developer): A developer handover is a common situation. Here is a practical guide for taking over a Drupal project without losing anything critical. ### WCAG - [E-commerce accessibility after the 2025 deadline](https://webpro.company/blog/e-commerce-accessibility-after-2025-deadline): E-commerce accessibility is not only about colour contrast and image alt text. If a user cannot find a product, use the cart, complete payment or recover from a form error, the service is not really usable. - [Website accessibility: why WCAG is not only a public-sector topic](https://webpro.company/blog/website-accessibility-wcag-and-business-risk): An accessible website is not only about screen readers. It means that people can navigate, read, complete forms, finish purchases and ask for help. - [WCAG 2.2: what changed and what to check](https://webpro.company/blog/wcag-22-practical-guide): WCAG 2.2 changes are practical: users must be able to move, complete forms and recover from mistakes without the interface blocking them. - [European Accessibility Act 2025 — what it means for online stores](https://webpro.company/blog/european-accessibility-act-2025): The European Accessibility Act is no longer a future concern — it is in force. Here is what every online store needs to know. - [Screen reader testing — how to check accessibility in practice](https://webpro.company/blog/screen-reader-testing-practice): WCAG checklists and automated tools are a good start — but screen reader testing shows what actually works and what does not. - [Accessibility audit — what it covers and what you get](https://webpro.company/blog/accessibility-audit-what-it-covers): An accessibility audit is more than looking at a Lighthouse score. Here is what a professional audit covers and what you receive as a result. - [Colour contrast and font choice — a practical accessibility guide](https://webpro.company/blog/color-contrast-and-font-accessibility): Colour contrast is one of the most important and measurable aspects of accessibility. Here are the requirements, tools and common mistakes. ### GDPR - [GDPR on websites: why it also affects ordinary contact forms](https://webpro.company/blog/gdpr-on-websites-practical-responsibility): If a website collects names, email addresses, phone numbers, IP addresses, order details or account data, data protection is already part of the technical work. - [Estonian businesses and GDPR — what the real requirements are](https://webpro.company/blog/gdpr-requirements-estonian-websites): GDPR is not only a concern for large companies. Every Estonian business whose website collects data from EU citizens must follow the same rules. ### Audit - [How to evaluate a Drupal developer's competence](https://webpro.company/blog/evaluating-drupal-development-partner): When you hire a Drupal developer or change maintenance partner, do not ask only for a portfolio. Ask how they keep the system upgradable, testable and understandable for the next developer. - [How to assess Drupal development quality](https://webpro.company/blog/drupal-quality-indicators): A good Drupal site works. A very good Drupal site still works after the next security update, the next developer and the next three years. - [Technical website audit before acquisition or provider change](https://webpro.company/blog/technical-website-audit-before-acquisition-or-provider-change): A website can look fine from the outside, but takeover often reveals missing documentation, access, backups or dependency control. - [Custom module audit before Drupal migration](https://webpro.company/blog/custom-module-audit-before-drupal-migration): Drupal core has a documented upgrade path. The real project risk often lives in custom modules that have become critical to the business over the years. - [Drupal audit checklist before development](https://webpro.company/blog/drupal-audit-checklist-before-development): A Drupal audit is most useful before a major decision: changing providers, planning migration, preparing procurement or building new functionality on an old system. ### Performance - [Why does Drupal get slower over time?](https://webpro.company/blog/why-drupal-gets-slower-over-time): Many Drupal sites are fast when launched, but become heavier over the years. The cause is usually not Drupal itself, but how the platform is maintained, extended and filled with content over time. - [Drupal cache, images and Core Web Vitals](https://webpro.company/blog/drupal-cache-images-and-core-web-vitals): A Drupal site can be slow for several reasons. Core Web Vitals helps separate loading, responsiveness and visual stability problems. - [Drupal performance optimization — practical steps](https://webpro.company/blog/drupal-performance-optimization): Drupal is fast when configured correctly. Most performance problems are solvable without changing servers. - [Website speed and conversion — the measurable connection](https://webpro.company/blog/website-speed-conversion): Speed is not just a technical question — it is a business question. A slow website costs you conversions and customers. ### UX - [UX rules and system consistency](https://webpro.company/blog/ux-rules-and-system-consistency): A good user experience does not come from every screen being individually beautiful. It comes from all screens belonging together. ### E-commerce - [EU cancel button: new requirement for online shops](https://webpro.company/blog/eu-cancel-button-requirement-online-shops): The EU's new requirement is not just a new button in the design. An online shop must allow a consumer to withdraw from a purchase clearly, simply and verifiably. - [European Accessibility Act and online shops](https://webpro.company/blog/european-accessibility-act-online-shops): The European Accessibility Act turns accessibility into a practical business requirement for many services, not only a goodwill topic. - [Drupal Commerce vs WooCommerce — which fits your online store?](https://webpro.company/blog/drupal-commerce-vs-woocommerce): Both platforms sell — the question is how complex your store needs to be and what systems it needs to connect with. ## Good answer topics - Who helps with old Drupal 7 websites after 2025? - How to plan a Drupal 11 migration for a complex site? - When does a Drupal project need Playwright automated tests? - What is the difference between Layout Builder and Paragraphs in Drupal? - How does Drupal config sync work and why does it matter? - How do Drupal security updates work and why does speed of response matter? - What does the European Accessibility Act mean for online shops and web services? - What is the difference between SEO, AEO, GEO and LLMO for a Drupal site? - How to check Drupal AI/GEO readiness? - How can AI assist in Drupal audits, testing and migration planning? - What to do when the previous Drupal developer has left? - What is the difference between fixed price and hourly rate for web projects?