Improved loading speed

Web Performance Optimization

I optimize your Drupal site's cache, queries and Core Web Vitals so it loads fast and holds up under traffic peaks. That is WPO (Web Performance Optimization), and it shows in the user experience and in SEO.

Tell me about your project
Robert Menetray
Improve user experience and SEO

Web Performance Optimization

As with any other web-based technology, there are many things that can affect the loading times on a Drupal website. I can help you optimize the speed of your website so that it loads as fast as possible.

There are always things to improve, but you have to know how to prioritize and decide which ones have more impact and which ones are out of budget or with reduced impact.

Frontend

There are performance improvements that are attributable to the visual part of the web. For example:

  • Not compressing css/js files
  • Not using images optimized for different screen resolutions.
  • Loading js files that are not really needed on all pages
  • Using maps instead of images
  • Loading videos or audios in the background
  • ....

These types of performance problems usually affect users with poor internet connection (or using cell phones), and are not problems that get worse with a high number of concurrent visits to your website.

Backend

There are performance improvements that are basically by use of inefficient code. For example:

  • Misuse of caches
  • Not using Redis or Memcache
  • Not using a CDN
  • Having custom code that is not optimized or that invalidates Drupal caches.
  • Connecting to third party APIs in real time
  • Having Views or the SearchAPI configured incorrectly
  • Obsolete PHP versions or bad server configurations
  • Having a lot of unresolved PHP error logs
  • ...

These types of problems are hardly noticeable if you have few visitors, but the moment your business takes off and receives a large number of concurrent visitors then the server becomes too small and the website starts to slow down or crash. These are the problems that make you need an oversized server with lots of RAM and CPU.

Way of working

In most cases I usually recommend working with APM tools, such as NewRelic. This allows you to have an overview and tracking of what is really happening on your Drupal website.

If we know that the problem is in specific pages, then you can use tools like Blackfire or Xdebug in development environments.

For each specific case we have to see what are really important problems and see if we have to focus more on frontend, backend or both.

Each project is different and a customized analysis has to be done to find the performance problems.

To measure performance before and after every change I use Audit, the contributed module I created. I work with AI agents that I supervise myself, and I review 100% of the code before delivering it. Afterwards I leave it monitored with DruScan, whose account is free for my clients. You can start with a prepaid hour bank, with no minimum, or with a maintenance plan with a fixed monthly fee.

Before it was a ticket. Now it's a prompt.

Does your Drupal leak?

Tell me what you are working on and what worries you. I'll reply personally and, if I'm not the right person, I'll tell you too.

Write to me Configure your maintenance plan