Drupal audit

Know where your Drupal site stands. And what comes first.

Taking over, improving or renewing your Drupal site? A focused audit reveals risks, bottlenecks and strengths. You get evidence-based priorities to decide your next step.

When an audit helps

An independent view of your Drupal project

You are taking over a site

Understand the code, dependencies and operational agreements before you take responsibility for the site.

Problems keep recurring

Investigate the causes of slow pages, errors and risks, instead of fixing the same symptoms again.

You want to build further

Find out whether your architecture can support your plans, before you invest in new features.

01 / Code & security

A dependable foundation starts under the hood

Code audit: quality that supports further development

We analyse Drupal core, patches, contributed modules and custom code. Are modules necessary and current? Does the code follow established development practices? Can another developer understand and maintain the project? We also look at whether functionality is organised into modules that can be changed, reused or disabled. You receive concrete findings about maintainability and technical dependencies.

Security audit: make risks visible

Within the agreed scope, we examine versions, configuration, roles and access permissions, and connect findings to their impact on visitors, editors and administrators. For older Drupal installations, we also identify maintenance and upgrade questions. You get focused remediation points; penetration testing requires a separate agreement.

developer
02 / Performance & SEO

Faster journeys. Better discoverability.

Performance audit: from symptom to cause

A slow page may come from an image, an external integration, backend processing or several factors together. We measure representative pages and user journeys, not only a score, and separate rendering, network, caching, queries and external calls. In a test environment, we examine caching settings, database size, queries and indexes, as well as the web server and deployment. Every recommendation gets an expected impact, an owner and a repeatable check.

Drupal SEO audit: content and technology together

Discoverability starts with a site that search engines understand and that helps visitors complete their tasks. We review indexability, content and technical structure and, where relevant, conversion tracking and Analytics settings. Content editors and developers each get their own action points, so improvements can be planned together.

03 / Architecture & integrations

A Drupal site rarely works in isolation

Information architecture that fits your work

We examine whether the data model and the relationships between content types, taxonomy, users and other entities support your needs. Where do coupling, custom code or unclear ownership make change difficult? We follow concrete tasks, such as publishing content or processing a request. The outcome is a proportionate route: keep what works, reduce risk first and replace only where the value justifies it.

Web services, infrastructure and operations

In a test environment and with agreed access, we examine calls to web services and other integrations: request duration, caching opportunities and how data is exchanged. We also review infrastructure, the file system and deployment, and advise how monitoring can detect problems earlier.

AI, where it is part of the application

Does your site include an answer service or agent? Then we also check source selection, access boundaries and configuration, using agreed test questions. Read more about source-grounded AI answers.

gimv

04 / Approach & outcomes: turn technical findings into a practical next step

  1. A clear starting point

    We begin with the decision you need to make and the risks you need to understand. Together we agree environments, components, user journeys and access. You can also focus on one area: code, security, performance, SEO or architecture.
  2. Investigate, report and prioritise

    For each finding, we describe the observation, evidence, potential consequence and proposed response. We separate necessary fixes, further investigation and desirable improvements, and state clearly where time or access limited the assessment.
  3. Improve and reassess

    Your team sets the business priorities; we connect them to technical dependencies. Each action gets an owner and acceptance criteria. Your own team or Dropsolid implements the changes, and we check that the original issue is resolved.
  4. What you take away

    A report with evidence and impact, priorities that take dependencies into account, and a verifiable next step: keep, repair or modernise with purpose.

Keep, improve or replace your current site?