Drupal audit, testing and second opinion

When you need to decide on an upgrade, partner change or website acquisition, a technical audit shows the state of code, modules, security risks and critical workflows.

When this helps

  • before a Drupal upgrade, migration or larger development;
  • before buying a web project or choosing a new development partner;
  • when the site has recurring errors;
  • when you need a review of another team's work;
  • when critical workflows have no tests.

What WebPro does

  • reviews code, configuration and risks;
  • checks the state of custom modules and integrations;
  • assesses Drupal and PHP versions, module upgradeability and security update state;
  • checks backup and recovery readiness;
  • reviews performance, technical SEO and basic accessibility signals;
  • creates a practical order for fixes;
  • writes Playwright UI tests;
  • adds PHP and Drupal tests where useful.

The free Drupal site check gives an initial public signal. This service is the next step when code, configuration, permissions, workflows and the release process need to be reviewed properly.

What you receive after the audit

  • a written report with the main findings;
  • findings grouped as critical, important or suitable for later planning;
  • recommendations on what to fix immediately and what to combine with the next upgrade or maintenance cycle;
  • an approximate action plan;
  • where useful, a rough work estimate for the next step.

What to send first

Describe what needs checking, which workflows are most important, whether a test environment exists and whether you need a written summary.

An audit is a good starting point before larger changes. The report shows whether the next step should be Drupal maintenance, a Drupal upgrade or a smaller set of fixes. For setting up automated tests, see the automated testing service.

Next step: describe the platform's current state and main concerns. We will suggest a small and clear starting scope.

Fill in the contact form