{"id":20402,"date":"2026-11-02T12:26:07","date_gmt":"2026-11-02T11:26:07","guid":{"rendered":"https:\/\/stage.surver.nl\/kennisbank\/wordpress-website-traag-oorzaken\/"},"modified":"2026-11-03T14:54:15","modified_gmt":"2026-11-03T13:54:15","slug":"causes-of-a-slow-wordpress-website","status":"publish","type":"kennisbank","link":"https:\/\/stage.surver.nl\/en\/kennisbank\/wordpress-website-traag-oorzaken\/","title":{"rendered":"Why Is My WordPress Website Slow? 8 Causes"},"content":{"rendered":"
\"Why<\/figure>\n\n\n\n

Your site feels sluggish or PageSpeed Insights is showing red, and you have no idea what\u2019s causing it. A slow WordPress website is usually caused by cheap shared hosting, missing caching, uncompressed images, too many or resource-intensive plugins, an outdated PHP version, a cluttered database, external scripts, and a resource-intensive theme or page builder. Below, you\u2019ll find information on how to identify each cause and how to check for it. The order in which you should address these issues is listed in How to Speed Up WordPress: The Complete Guide<\/a>.<\/p>\n\n\n\n

Measure first, then search<\/h2>\n\n\n\n

First, figure out where the bottleneck is, because without measuring it, you\u2019re just guessing. A doctor wouldn\u2019t prescribe medication without a diagnosis, and installing a caching plugin on an overloaded server is like taking acetaminophen for a broken leg. I always test using PageSpeed Insights or GTmetrix, on both mobile and desktop, and several times in a row, because a single measurement doesn\u2019t tell you much. Do this while logged out in an incognito window, because your own browser and your logged-in session skew the results. Also, test more than just the homepage. A product page or the checkout page often behaves very differently.<\/p>\n\n\n\n

Three metrics tell you the most. TTFB (time to first byte) is the time it takes for the server to send back the first byte, and for a healthy site, this is less than 0.8 seconds. LCP measures when the largest visible element appears on the screen, and Total Blocking Time (TBT) measures how long scripts block the page. A PageSpeed score of 90 to 100 is good, and 50 to 89 could be better, but it\u2019s still just a lab test. What Google counts are the Core Web Vitals<\/a> for real visitors, with an LCP within 2.5 seconds. With those three values in hand, use this table to find the track.<\/p>\n\n\n\n

What You See<\/th>Probable cause<\/th><\/tr><\/thead>
High TTFB on all pages<\/td>Hosting or No Caching<\/td><\/tr>
Slow LCP, large image at the top<\/td>Images<\/td><\/tr>
High Total Blocking Time<\/td>External scripts, plugins, or themes<\/td><\/tr>
Slow dashboard, fast front end<\/td>Database, plugins, or server resources<\/td><\/tr>
Slow only when it's busy<\/td>Insufficient server resources<\/td><\/tr>
Only the shopping cart and checkout are slow<\/td>Pages without a cache, see Slow WooCommerce online store<\/a><\/td><\/tr>
It's been running slowly since yesterday<\/td>Update, bots, malware, or system failure<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Server-side causes<\/h2>\n\n\n\n

Slow performance can be caused by issues on the server side or the front end, and you can identify server-side issues by a high TTFB. The first suspect is cheap shared hosting. If there are too many sites on a single server, yours will have to wait its turn, especially during peak traffic. If the TTFB is high even on a cached page, it\u2019s almost certainly due to the hosting. In that case, choose hosting optimized for WordPress, such as Managed WordPress Hosting<\/a>, or for an online store Managed WooCommerce Hosting<\/a>. See also What Makes Up Fast WordPress Hosting<\/a>. A CDN is especially helpful for visitors from far away, since for traffic from the Netherlands, a server in Europe is already close by.<\/p>\n\n\n\n

Without caching, the server rebuilds each page from scratch for every visitor. You can tell from the response headers whether there was a cache hit. A common mistake I see is when two caching plugins interfere with each other. See Caching in WordPress<\/a>. An outdated PHP version is the third one, because each new version processes the same code faster. You can see your version under Gereedschap > Sitediagnose > Info > Server<\/strong>. Test an upgrade first and follow Update PHP Version<\/a>. Then the database. Revisions, transients, and autoload options from old plugins in wp_options<\/code> slow down every database query. Site Diagnosis issues a warning if there is a large amount of autoload data. Make a backup, and then clean up the database<\/a>.<\/p>\n\n\n\n

Most of what we handle as standard at Surver is on this side. All shared hosting plans run on LiteSpeed servers with NVMe storage and LiteSpeed Cache; OPcache is always enabled; and each account is isolated from neighboring accounts using CloudLinux and CageFS. You can change your PHP version yourself via cPanel > Select PHP Version<\/strong>, from 7.4 through 8.5. To find out whether your site is reaching the CPU or memory limits of your plan, please contact support.<\/p>\n\n\n\n

Root causes<\/h2>\n\n\n\n

On the front end, you\u2019ll see the delay reflected in a slow LCP or a high TBT, even though the server itself responds quickly. It usually starts with images. A single photo of a few megabytes at the top of the page can single-handedly determine your LCP, and PageSpeed Insights simply identifies it as the LCP element. Resize, compress, and convert to WebP; see Optimize images<\/a>. By the way, you don't upload a video yourself; you embed it via YouTube or Vimeo.<\/p>\n\n\n\n

When it comes to plugins, the type matters more than the number. A single heavy plugin that loads scripts on every page slows things down more than ten lightweight ones. Query Monitor shows which plugin takes the most time. If you want to disable plugins without visitors noticing, use Health Check & Troubleshooting or a staging environment<\/a>, which you can do on Surver by cloning your installation in Installatron. Outdated plugins and themes are often slower as well, so Clean up outdated plugins<\/a> It's part of the deal. If you don't want to keep track of that yourself, it falls under WordPress maintenance<\/a>.<\/p>\n\n\n\n

External scripts are the silent speed killers. Take a Meta Pixel or a Hotjar script, for example\u2014it loads from a different server and blocks the page while it\u2019s loading, which shows up as render-blocking JavaScript and a high TBT. In PageSpeed Insights, under \u201cThird-Party Resources,\u201d you can see exactly what\u2019s being loaded. My advice is to remove anything that doesn\u2019t add value and load the rest via Google Tag Manager only after cookie consent is granted. A heavy theme or page builder creates a lot of extra HTML elements, which PageSpeed flags as an excessive DOM size. Temporarily switch to a default theme on your staging environment to compare, and read Page Builder or Block Editor<\/a>.<\/p>\n\n\n\n

Is the dashboard slow, or did it suddenly start running slowly?<\/h2>\n\n\n\n

If only your dashboard is slow, it\u2019s almost never because of your images, since the front end is served from the cache and the dashboard never is. That\u2019s where you\u2019ll immediately notice the impact of heavy plugins, extensive autoload options, and insufficient PHP memory or PHP workers. The Heartbeat API and background tasks via WP-Cron\u2014such as a backup or import that\u2019s currently running\u2014can also slow down the dashboard. Query Monitor shows you where the time is being spent here as well. You can adjust PHP settings in Surver via cPanel > Select PHP Version > Options<\/strong>. If a value cannot be set higher, please contact support.<\/p>\n\n\n\n

If your site has suddenly become slow, check to see what has changed recently. These are the things I check first.<\/p>\n\n\n\n