Slow load times cost you customers and rankings. This checklist walks JTL-Shop operators through every relevant lever – from image optimisation and caching to hosting infrastructure.
Google treats page speed as a direct ranking factor. Shops that take longer than 3 seconds to load lose an average of 40% of their visitors – before they've seen a single product. For JTL-Shop operators that's not an abstract SEO problem, it's lost revenue.
This checklist walks you through every relevant lever – from quick wins to infrastructure-level improvements.
Without a baseline you can't track improvement. Use these free tools:
Note your current scores for LCP (Largest Contentful Paint), INP (Interaction to Next Paint) and CLS (Cumulative Layout Shift). These three metrics are your target – and Google's benchmark since 2021.
Target values:
Product images are the biggest performance drain in most JTL shops. Concrete actions:
srcset so mobile devices load smaller versionsA quick test: open your shop on a mobile phone on a 4G connection. If you can visibly watch product images loading in, they're too large.
Every plugin you activate potentially loads additional CSS and JavaScript – even when you're not actively using it. Common problem sources:
Recommendation: load your shop URL in GTmetrix and sort resources by size. You'll often find plugin assets that nobody consciously activated anymore.
JTL-Shop has built-in caching mechanisms that are frequently not optimally configured:
Without caching, your shop rebuilds all content from scratch on every page request – that costs time and server resources.
All application-level optimisations only go as far as the infrastructure beneath them allows. Common hosting bottlenecks that often get overlooked:
With iDeployed, JTL shops run on infrastructure optimised for e-commerce – with automatic caching, HTTP/3 support and isolated database resources. TTFB averages under 150ms.
Before you open GTmetrix next time – work through these points:
If you can tick all eight boxes and your LCP is still above 2.5 seconds, hosting is the most likely cause.
Ready to get your JTL-Shop infrastructure up to speed? Start for free →