<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Performance — Articles | WebPro Company OÜ</title>
    <link>https://webpro.company/blog/tag/performance/</link>
    <atom:link href="https://webpro.company/blog/tag/performance/rss.xml" rel="self" type="application/rss+xml" />
    <description>Drupal performance and Core Web Vitals — caching, images, JavaScript and measurable user experience.</description>
    <language>en-US</language>
    <lastBuildDate>Thu, 02 Jul 2026 06:00:00 GMT</lastBuildDate>
    <item>
      <title>Why does Drupal get slower over time?</title>
      <link>https://webpro.company/blog/why-drupal-gets-slower-over-time</link>
      <guid isPermaLink="true">https://webpro.company/blog/why-drupal-gets-slower-over-time</guid>
      <pubDate>Thu, 02 Jul 2026 06:00:00 GMT</pubDate>
      <category>Performance</category>
      <category>Drupal</category>
      <category>Maintenance</category>
      <description>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. Slowness rarely comes from one change A Drupal site does not usually become slow overnight. It is usually a gradual process: more content is added; more images and files are uploaded; new modules are installed; small custom features are built; analytics, marketing and chat scripts are added; cache or server configuration falls behind; old solutions remain in place next to new ones. Each individual change may seem small. Together, they can make the site slower, harder to manage and more expensive to develop further. Content growth has a bigger impact than expected A large organisation&apos;s Drupal…</description>
    </item>
    <item>
      <title>Core Web Vitals in Drupal — common problems and how to fix them</title>
      <link>https://webpro.company/blog/core-web-vitals-in-drupal</link>
      <guid isPermaLink="true">https://webpro.company/blog/core-web-vitals-in-drupal</guid>
      <pubDate>Wed, 06 May 2026 06:00:00 GMT</pubDate>
      <category>Drupal</category>
      <category>Performance</category>
      <description>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. Core Web Vitals are three performance metrics established by Google, measured using real user data. They are not only a technical benchmark — they affect search ranking. The three metrics LCP — Largest Contentful Paint measures the time until the largest visible element appears on screen (typically an image or heading). The target is under 2.5 seconds. CLS — Cumulative Layout Shift measures layout instability — how much elements on the page shift during loading. An example: the user is about to click a button, but an advertisement loads first and pushes the button down. The target is…</description>
    </item>
    <item>
      <title>Drupal cache, images and Core Web Vitals</title>
      <link>https://webpro.company/blog/drupal-cache-images-and-core-web-vitals</link>
      <guid isPermaLink="true">https://webpro.company/blog/drupal-cache-images-and-core-web-vitals</guid>
      <pubDate>Tue, 10 Mar 2026 06:00:00 GMT</pubDate>
      <category>Performance</category>
      <category>Drupal</category>
      <description>A Drupal site can be slow for several reasons. Core Web Vitals helps separate loading, responsiveness and visual stability problems. Where problems appear Core Web Vitals measures user-visible experience. Drupal sites often repeat the same causes: images are too large, caching is incomplete, JavaScript blocks rendering or components shift while loading. Check: whether image styles produce correctly sized files; whether lazy loading is used correctly; whether cache headers and Drupal cache are configured; whether third-party scripts slow down the front page; whether font and image dimensions are known in advance. Why a plugin is not enough A performance module can help, but the wrong configuration can create new defects. Measure first, then change. WebPro connects performance fixes with…</description>
    </item>
    <item>
      <title>Drupal performance optimization — practical steps</title>
      <link>https://webpro.company/blog/drupal-performance-optimization</link>
      <guid isPermaLink="true">https://webpro.company/blog/drupal-performance-optimization</guid>
      <pubDate>Sat, 15 Nov 2025 06:00:00 GMT</pubDate>
      <category>Performance</category>
      <category>Drupal</category>
      <description>Drupal is fast when configured correctly. Most performance problems are solvable without changing servers. A slow website costs money. Every second of loading time reduces conversions, damages SEO and frustrates users. Drupal itself is not slow — but a misconfigured Drupal installation can be very slow. Layer 1: Drupal&apos;s built-in cache Drupal includes a multi-layered caching mechanism. The first step when diagnosing a slow site is to check whether caching is actually working. Internal Page Cache — stores page HTML for anonymous users. If disabled, every visit regenerates the page from scratch. Dynamic Page Cache — stores page fragments that do not depend on the user. Works for logged-in users too. BigPipe — delivers the page skeleton immediately and fills in personalised sections…</description>
    </item>
    <item>
      <title>Website speed and conversion — the measurable connection</title>
      <link>https://webpro.company/blog/website-speed-conversion</link>
      <guid isPermaLink="true">https://webpro.company/blog/website-speed-conversion</guid>
      <pubDate>Thu, 05 Jun 2025 06:00:00 GMT</pubDate>
      <category>Performance</category>
      <category>UX</category>
      <description>Speed is not just a technical question — it is a business question. A slow website costs you conversions and customers. Amazon found that 100 milliseconds of added load time reduced sales by 1%. Google data shows 53% of mobile users abandon a page that takes more than 3 seconds to load. Walmart found that every 1-second speed improvement increased conversions by 2%. These are not hypotheses — these are measured results from analysis of the world&apos;s largest websites. Why speed affects conversion First impression forms quickly. A user decides within 50 milliseconds whether a page feels trustworthy. A slow-loading page gives the wrong signal before content even appears on screen. Mobile is the dominant channel. Over 60% of web traffic comes from mobile devices, where connection speed is…</description>
    </item>
  </channel>
</rss>
