A guide on DEV Community describes four typical mistakes that slow down shops built on JTL-Shop 5. It starts from Google's Core Web Vitals, which are its measures of user experience. According to web.dev, good values are a Largest Contentful Paint (LCP, the time until the biggest visible element appears) of 2.5 seconds or less, an Interaction to Next Paint (INP, how fast the page reacts to input) of 200 milliseconds or less, and a Cumulative Layout Shift (CLS, how much content jumps around) of 0.1 or less.
The first mistake is an outdated PHP version and a switched-off object cache. According to the JTL-Guide, JTL-Shop 5 needs at least PHP 8.1 from version 5.2, and JTL recommends PHP 8.2 from version 5.2.3. The object cache is off by default. The article says to test a PHP change on a copy of the shop first, because plugins and the template must be compatible. It also notes, citing PHP.net, that security support for PHP 8.2 ends on 31 December 2026.
The second mistake is lazy loading the main image. The article says the LCP image should never carry loading="lazy", according to web.dev, because that always delays it. Images should also have width and height set, so the browser reserves space. The third mistake is too many third-party scripts, such as tracking, chat widgets and external fonts, often loaded before consent is given. The fourth is unused plugins and a template that is not built as a child of the standard NOVA template.
The guide also recommends measuring first. It separates lab data from Lighthouse, which changes straight after a fix, from field data from the Chrome User Experience Report, which covers real visits over the previous 28 days. Its suggested order is hosting, PHP and cache first, then template, images and third-party scripts, and finally plugins, the sync with JTL-Wawi and the database.
Why it matters
The article's main point is that speed work fails when many things change at once. If you change one area at a time and measure before and after, you can see which step actually helped. Looking at real visitors, often on phones, matters more than a fast result on an office connection.
Several of the fixes are cheap and sit in the shop settings or templates: the object cache, the main image attribute, reserved space for cookie banners and removing plugins you no longer use. Others, such as a PHP upgrade, need testing on a copy so sales are not put at risk.
Source: DEV Community. This brief summarises their reporting; read the original for the full detail.