This episode discusses how content and commerce team can avoid common site performance issues and take sensible steps to improve site speed and keep their websites secure.
Listen on your favourite player
Watch the video
WordPress has an extensive community and massive install base. Over 409 million people view more than 20 billion pages each month! It’s used on content sites like TechCrunch and commerce sites like the Bjork Official Store (for 90s Indie lovers like James!!).
At the same time, being Open Source presents challenges to ensure your implementation delivers a high performance site & poor governance around plugins can ruin your CWV scores. For this episode, we talked to a leading voice in the WordPress community, a marketing technologist whose favourite things are web development, futurology, WordPress, science-fiction, and gin. Jono Alderson is currently heading up Special Ops for Yoast and has extensive experience fixing, optimising and improving WordPress sites of all sizes.
Tl;dr: what you’ll learn:
- How to improve WordPress site performance
- Common issues and how to fix them
- Where WordPress is heading as a platform
Key Discussion Points
- WordPress sometimes gets a bad press for being insecure and targeted for hacking/malicious injections: is this criticism fair & how do ecommerce teams minimise the risk?
- What role does the overall site architecture play in page speed vs. simply the front-end code?
- What has changed in the last 12-24 months that has helped dev teams make WordPress sites perform better & how?
- You’re a big fan of AMP; where does AMP fit for an ecommerce brand and what impact have you seen it have on performance?
- What are most common WordPress issues that make sites slower than necessary and how do you fix them?
- Can you talk us through any case studies of when you’ve seen big improvements on WordPress sites and what drove them?
- How is WordPress evolving as a platform – what are key changes in last 12 months and what can merchants expect in 2022?
Want to suggest a topic or guest for a future episode? Contact us via the website or on Twitter.