WP Café #135 Efficient asset loading - CourtneyR.dev's 2nd Brain

WP Café #135 | Efficient asset loading 🔗 **Source:** [WP Café #135 | Efficient asset loading](https://www.youtube.com/watch?v=NkfDAyoW5B8) > [!note]+ Document Notes > tags: [wordpress-performance, asset-loading, block-development] > author: WP Café > source: YouTube > reference: https://www.youtube.com/watch?v=NkfDAyoW5B8 > date created: 2024-12-27 10:30 > > # 🏷️ Title: WP Café #135 | Efficient asset loading >  ## 🧰 Action Inbox - [H1] Split theme CSS into block-specific files — performance optimization #asset-loading - [H2] Test conditional JavaScript loading for block styles — 25:30 timestamp #javascript - [H3] Fix sanitize_title function for special characters — 34:45 timestamp #debugging ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [WP Café Show](https://wpcafe.show) - [High-Rise Digital](https://high-risedigital.com) ## 📝 Summary - WordPress developers Keith Devon and Mark Wilkinson discuss efficient asset loading techniques for WordPress sites - Core focus on loading block-specific CSS and JavaScript only when blocks are present on pages - Technical solutions include using wp_enqueue_block_style() and render_block filters for conditional loading - Also covers debugging URL encoding issues with special characters and pricing strategy discussions - Bottom line: Performance optimization through conditional asset loading can significantly reduce payload ## 📖 Main Content This episode covers advanced WordPress performance optimization techniques, specifically focusing on conditional asset loading. The hosts demonstrate how to load block-specific CSS and JavaScript files only when those blocks are actually used on a page, rather than loading all assets globally. The technical approach involves using WordPress's built-in `wp_enqueue_block_style()` function combined with file system scanning using PHP's `glob()` function. For JavaScript, they explore using the `render_block` filter to detect specific block styles and conditionally enqueue scripts. They also troubleshoot a real-world issue where special characters (umlauts) in job titles were causing 403 errors, revealing the importance of proper URL sanitization using `sanitize_title()` instead of `sanitize_title_with_dashes()`. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/NkfDAyoW5B8?t=0) — [H1] Introduction and health updates - Key idea: Both hosts dealing with seasonal illnesses affecting UK population - Evidence: "Everyone seems to be a bit down under the weather, don't they?" #### ⏱️ [03:30](https://youtu.be/NkfDAyoW5B8?t=210) — [H2] Performance audit triggers optimization work - Key idea: Large theme CSS file identified as performance bottleneck - Evidence: "One of the main insights was that the theme CSS file was quite large" #### ⏱️ [06:15](https://youtu.be/NkfDAyoW5B8?t=375) — [H1] Block-specific CSS loading approach - Key idea: Using PHP glob() to scan for block CSS files automatically - Evidence: "We get all of the registered blocks and then you kind of loop through each of those" #### ⏱️ [09:45](https://youtu.be/NkfDAyoW5B8?t=585) — [H2] wp_enqueue_block_style() function benefits - Key idea: WordPress handles registration and conditional loading automatically - Evidence: "It registers your CSS file with WordPress and it encues it when that block is detected" #### ⏱️ [12:20](https://youtu.be/NkfDAyoW5B8?t=740) — [H3] CSS inlining for small files - Key idea: WordPress automatically inlines small CSS files for efficiency - Evidence: "It will try and inline those styles if it judges that they are suitable" #### ⏱️ [15:30](https://youtu.be/NkfDAyoW5B8?t=930) — [H2] JavaScript loading for blocks - Key idea: Using block_type_metadata filter for front-end script loading - Evidence: "You can add your script into that. It's called view script" #### ⏱️ [19:15](https://youtu.be/NkfDAyoW5B8?t=1155) — [H1] Conditional JavaScript for block styles - Key idea: Only load JavaScript when specific block styles are applied - Evidence: "I only want to encue that logo slider JavaScript file when that block style is selected" #### ⏱️ [22:45](https://youtu.be/NkfDAyoW5B8?t=1365) — [H3] render_block filter solution - Key idea: Using render_block filter to detect block styles and conditionally enqueue assets - Evidence: "Looking for a class name called is style whatever your style is" #### ⏱️ [25:30](https://youtu.be/NkfDAyoW5B8?t=1530) — [H2] HTTP/2 and multiple requests - Key idea: HTTP/2 handles multiple simultaneous requests efficiently - Evidence: "Browser can only handle one request at a time vs HTTP2 can open a connection" #### ⏱️ [30:15](https://youtu.be/NkfDAyoW5B8?t=1815) — [H2] Editor vs front-end loading considerations - Key idea: JavaScript often shouldn't load in editor due to usability issues - Evidence: "How do you click on an image to then start replacing it if it's a slider?" #### ⏱️ [34:45](https://youtu.be/NkfDAyoW5B8?t=2085) — [H1] Special character URL encoding bug - Key idea: Umlaut characters in job titles causing 403 errors - Evidence: "Job that had the issue had an uml in the title making the URL look very strange" #### ⏱️ [38:20](https://youtu.be/NkfDAyoW5B8?t=2300) — [H3] sanitize_title vs sanitize_title_with_dashes - Key idea: Wrong sanitization function doesn't handle special characters - Evidence: "sanitize_title calls remove_accents which does the replacement" #### ⏱️ [42:15](https://youtu.be/NkfDAyoW5B8?t=2535) — [H2] Pricing strategy and discount philosophy - Key idea: Questioning the logic behind Black Friday sales and discount codes - Evidence: "If you're not selling unless you offer a discount, isn't your pricing just wrong?" #### ⏱️ [48:30](https://youtu.be/NkfDAyoW5B8?t=2910) — [H3] Customer expectations around discounts - Key idea: Discount code boxes create expectation that discounts are available - Evidence: "Is there a Christmas discount that I can use? All feeling of goodwill" ## 📚 References - [WordPress Developer Documentation](https://developer.wordpress.org/) - [WP-CLI](https://wp-cli.org/) - [ACF Blocks Documentation](https://www.advancedcustomfields.com/resources/) ## 🗣️ Paraphrase - WordPress sites can be optimized by loading CSS and JavaScript only when specific blocks are present on pages, rather than loading everything globally - Technical implementation involves scanning theme directories for block-specific asset files and using WordPress's built-in conditional loading functions - Special character handling in URLs requires proper sanitization functions to prevent server errors and ensure cross-browser compatibility ## 📰 Newsletter ## Optimize Your WordPress Performance with Smart Asset Loading This week's WP Café episode dives deep into performance optimization techniques that every WordPress developer should know. The hosts demonstrate practical approaches to conditional asset loading that can significantly improve your site's performance. **Key Technique**: Use `wp_enqueue_block_style()` to automatically load CSS only when specific blocks are present. Combined with PHP's `glob()` function, you can create a system that scans your theme's block assets and loads them conditionally without manual configuration. **Pro Tip**: For JavaScript loading based on block styles, leverage the `render_block` filter to detect specific CSS classes and conditionally enqueue scripts. This prevents unnecessary JavaScript from loading when block variations aren't being used. **Debug Alert**: Watch out for special characters in URLs - use `sanitize_title()` instead of `sanitize_title_with_dashes()` to properly handle international characters and prevent 403 errors. Resources: [Learn WordPress](https://learn.wordpress.org/), [Developer Docs](https://developer.wordpress.org/), [WP-CLI](https://wp-cli.org/) ## ✅ Action Items #### WordPress - Core Performance: Implement conditional asset loading patterns in themes - Themes: Review asset loading strategies for better performance scores - Documentation: Document wp_enqueue_block_style() usage patterns and benefits - Community: Share performance optimization techniques at meetups #### The WPCC - Programs: Developer workshops on performance optimization techniques - Projects: Performance audit tools and guidelines for theme developers ## 🧪 Hypotheses - Conditional asset loading reduces initial page load times compared to bundled assets - HTTP/2 makes multiple small requests more efficient than single large bundles - Block-specific CSS files improve caching strategies for WordPress sites - Special character handling affects international WordPress site reliability ### 📊 Methodology - Performance testing comparing bundled vs conditional asset loading - HTTP/2 request analysis using browser network tools - International character URL testing across different server configurations ### ❓ Questions - How does the number of conditional requests impact HTTP/2 performance? - What's the optimal file size threshold for CSS inlining vs separate files? - How do CDNs handle numerous small asset files compared to bundles? ### 🔮 Future Research - Performance impact studies of conditional loading at scale - Browser caching behavior with block-specific assets - Server configuration optimization for numerous small requests ### 💡 Implications - Practice: Theme developers need to reconsider asset bundling strategies - Performance: Conditional loading can significantly improve Core Web Vitals scores - Education: Developer training should include modern asset loading techniques - Tooling: Build processes need updating to support block-specific compilation ### 🧠 Learning Styles Assessment Reading level estimate: 12th Grade (technical content with code examples) #### 👀 Visual learners - Present: Code examples and file structure explanations - Improve: Network waterfall diagrams, file organization visuals #### 🔊 Aural learners - Present: Podcast format with detailed verbal explanations - Improve: Audio descriptions of code functionality #### 🗣️ Verbal learners - Present: Technical terms explained with analogies and examples - Improve: Glossary of WordPress performance terms #### 🧩 Kinesthetic learners - Present: Step-by-step implementation guidance - Improve: Hands-on code examples and testing procedures #### 🧠 Logical learners - Present: Performance metrics and before/after comparisons - Improve: Decision trees for choosing asset loading strategies #### 🧑‍🤝‍🧑 Social learners - Present: Discussion between hosts, community interaction - Improve: Code review examples, collaborative optimization #### 🧘‍♀️ Solitary learners - Present: Detailed technical explanations for independent study - Improve: Self-assessment checklists for implementation #### 🌿 Naturalistic learners - Present: Performance optimization as ecosystem health - Improve: Environmental impact of efficient loading ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure, code explanations - Improve: More descriptive alt text for code examples #### Keyboard navigation - Present: Standard video controls accessible - Improve: Timestamped navigation for topics #### Contrast and readability - Present: Good contrast in video presentation - Improve: Code syntax highlighting for better readability #### Media and captions - Present: Full transcript provided - Improve: Synchronized captions with technical terms ### 🌍 DEIB Assessment #### Cultural breadth - Present: UK-based perspective with international considerations - Improve: Examples from diverse WordPress communities globally #### Inclusive language - Present: Technical terms explained clearly - Improve: Avoid assumptions about prior knowledge levels #### Representation - Present: Technical discussion focused on practical implementation - Improve: Diverse use cases and examples ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Performance optimization principles well-established - Inductive strength: Real-world examples support general principles - Causal reasoning: Clear connection between asset loading and performance #### Fallacies - None identified: Technical discussion stays factual and evidence-based #### Tone of voice - Overall tone: Conversational and educational, appropriate for developer audience ### 🛡️ DARVO Analysis - No concerning patterns identified - technical discussion focused on problem-solving ## 🎯 Conclusion This episode provides valuable insights into modern WordPress performance optimization through conditional asset loading. The practical techniques demonstrated - using `wp_enqueue_block_style()` for CSS and `render_block` filters for JavaScript - offer immediate improvements for WordPress developers. Key takeaway: Moving beyond traditional asset bundling to conditional loading aligns with modern web performance best practices, especially when combined with HTTP/2's capabilities for handling multiple simultaneous requests efficiently. The debugging insights around URL sanitization also highlight the importance of proper internationalization practices in WordPress development. ## 🧱 Refactor Appendix ### 📚 Literature Split Pad ### [H1] Conditional asset loading improves WordPress performance > [!quote] [WP Café #135](https://youtu.be/NkfDAyoW5B8) by WP Café via YouTube. Published 2024. Accessed 2024-12-27. > "Load block styles only when those blocks are on the page if possible." Performance optimization through selective resource loading. [view highlight](https://youtu.be/NkfDAyoW5B8?t=375#H1) #performance #optimization ID:rw_001 ### [H2] wp_enqueue_block_style handles registration and conditional loading > [!quote] [WP Café #135](https://youtu.be/NkfDAyoW5B8) > "It registers your CSS file with WordPress and it encues it when that block is detected." WordPress provides built-in conditional asset loading functionality. [view highlight](https://youtu.be/NkfDAyoW5B8?t=585#H2) #wordpress-functions ID:rw_002 --- ### 🔖 Atomic Split Pad (Zettel Candidates) #### [Z1] HTTP/2 enables efficient multiple request handling - Modern protocol supports simultaneous asset loading - Pointer to 25:30 timestamp discussion - Links: [[Web-Performance]] [[Asset-Loading]] #### [Z2] Special character sanitization prevents URL errors - Use sanitize_title() over sanitize_title_with_dashes() - Pointer to 34:45 debugging discussion - Links: [[WordPress-Internationalization]] [[URL-Handling]] --- ### ✏️ Fleeting Queue - [F1] Test block-specific asset loading implementation — performance audit context #fleeting #performance - [F2] Review special character handling in current projects — 403 error prevention #fleeting #debugging - [F3] Research optimal file size thresholds for CSS inlining — efficiency optimization #fleeting #research --- ## Full Transcript [00:02] Hello and welcome to episode number 135 [00:06] of WP Cafe, the show where we share the [00:08] real unfiltered experience of running a [00:11] WordPress business. I'm Keith Devon and [00:14] as always I'm joined by my co-host Mark [00:16] Wilkinson. We're both from High-Rise [00:18] Digital, which is a tiny agency building [00:20] WordPress websites and products. Today [00:23] we're going to be talking about a number [00:24] of things. I guess mostly about [00:27] efficient asset loading in our WordPress [00:29] websites that we build. Uh so grab a [00:32] brew, settle in as we explore what it's [00:34] really like behind the scenes. You can [00:36] follow us over on X, formerly Twitter at [00:39] WP Cafe Show, and find us on Blue Sky [00:42] and the web at wpcafe.show. [00:46] If you enjoy the episode, hit subscribe [00:48] and like, leave us a comment, and share [00:50] it with someone who might find it [00:51] useful. And we'd love to hear your [00:53] thoughts. So, if you're watching along [00:55] live on YouTube, please do join the [00:56] conversation and let us know what you [00:59] think. So, on to the show. But before we [01:01] get stuck into the topics, let's catch [01:03] up with Mark. Mark, how have you been [01:05] this week? What's been going on? [01:07] >> Uh, not so bad. I'm not uh feeling 100% [01:11] I must admit like the rest of the UK. I [01:14] think everyone seems to be a bit uh down [01:16] under the weather, don't they? So, um if [01:18] I disappear, it's probably because I'm [01:20] about to sneeze my head off. Um but I [01:22] will be back. But when I finish doing [01:24] that, so put your head back on. [01:26] >> Yeah. [01:28] >> So, uh, but yeah, other than that, um, [01:30] doing all right. Just plotting along. [01:32] Uh, yeah. Got a few things to chat [01:33] through today, so it's good. What about [01:34] you? [01:35] >> Yeah. Uh, similar. Took a couple of days [01:38] off at the start of this week. Um, with [01:40] a bit of a a nasty cold. They hit me [01:43] really hard and then disappeared really [01:44] quickly, which is unusual for me because [01:46] usually usually once I get a cold, I'm [01:48] like I'm in it for quite a while. I'm [01:50] still a little bit kind of blocked up, [01:52] but I feel so much better. Um, ginger [01:55] and cinnamon is what I was taking. And I [01:57] don't know. I don't know. It's uh it's a [02:00] sample of one, but uh I I heard I I saw [02:04] some stupid thing on the internet about [02:05] like traditional remedies for colds and [02:08] the guy was all about about it. So, I [02:10] was like, well, I've got I've got ginger [02:11] and cinnamon in the house, so I'll give [02:12] it a go. Few cups of that was right. Um [02:16] but [02:17] >> put it in boiling water, you know. [02:19] >> Yeah. Yeah. Yeah. Yeah. Yeah. I just [02:20] chopped up a bunch of ginger, sprinkled [02:23] in some ground cinnamon with [02:25] >> honey. [02:26] >> Yeah. [02:27] >> Yeah. [02:27] >> Yeah. [02:28] >> And uh Yeah. It was reasonably tasty. [02:31] It's quite fiery and apparently [02:33] apparently that's what works, but you [02:35] know, it gets the blood flowing and blah [02:37] blah blah. Anyway, it's probably [02:39] absolute nonsense, but [02:40] >> um but now my daughter's really sick and [02:42] I've I've got a horrible feeling that a [02:45] hospital visit is imminent cuz she's got [02:47] a very high temperature and I know what [02:50] the GP is going to say. They're just [02:52] going to send us all off to hospital [02:54] with the rest of the country. Like you [02:55] said, like everyone's everyone's sick at [02:57] the minute. So, it could be in for a [02:58] pretty grim 24 hours, but [03:00] >> uh let's enjoy the last of it before [03:02] that happens. [03:06] All right. So, yeah, let's get on with [03:08] uh let's get on with the show. Um, so [03:11] yeah, a few things to chat about there. [03:14] Um, [03:17] the first one is all about basically [03:19] efficiently loading CSS and JavaScript [03:23] in our WordPress sites. And it came [03:26] about I'll do the intro mark because I [03:27] reckon you're going to be talking [03:28] through the technicalities because it's [03:30] mostly been your work so far. Um but it [03:33] came about because of a performance kind [03:35] of audit uh that we're doing for a [03:37] client of ours and one of the you know [03:42] we're just running it through Google [03:43] page speed. One of the main insights was [03:46] that the theme CSS file was quite large [03:49] and it was it's kind of grown over time. [03:52] Um, and it's reasonably big. And we have [03:57] previously and since this project uh [04:02] been much clever about how we kind of [04:04] load our CSS. I don't know how why this [04:06] project kind of we haven't we weren't [04:08] doing those things. Um, but what we what [04:11] we thought is that we should probably be [04:12] loading block styles uh like block CSS [04:16] specifically uh only when those blocks [04:19] are on the page if possible. and we we [04:22] know it is possible. Um so you set about [04:26] to figure out um how to look for [04:31] those assets in a particular place in [04:33] the theme if the block was on the page [04:37] over to you. What challenges did you [04:39] face? What solutions did you come up [04:41] with? [04:41] >> I'm just checking out the right branch [04:43] so I can see my code at the same time as [04:46] >> Yeah, good idea. [04:48] And it magically appears in my file. [04:50] There we go. Um, so I've done this [04:52] before actually, so it's just a matter [04:53] of like revisiting it. And I've actually [04:55] approached it in a few different ways. [04:58] The very first way I approached it was [04:59] to get all of the blocks on the website. [05:02] So you can do that. I think there's like [05:04] a block registry [05:06] class thing and you can get all of the [05:08] registered blocks and then you kind of [05:10] loop through each of those. You check [05:12] whether you've got a file present and if [05:15] you have, you kind of incue it. But that [05:18] that's kind of inefficient. So I thought [05:20] we may as well do it the other way [05:21] around in that if we have a block file [05:23] block file present then loop through [05:27] those and then work out what the block [05:29] is that you need to sort of add the [05:30] block style. So that's the approach I've [05:31] gone for. So essentially we get um we're [05:35] just using the PHP glob function which [05:37] basically looks at a directory of the [05:39] files. So, I'm looking at in this [05:41] directory. I think it's assets. This is [05:43] in the theme. It's assets blocks [05:46] essentially. Um, and it looks for any [05:49] files in there that are ending in CSS. [05:52] And then we loop through each of those [05:54] files. We build a path because you need [05:56] the path. Come to that in a minute. We [05:58] build a file name. And then we from the [06:00] file name, we build the block name [06:01] because obviously the file name is going [06:02] to be like core- paragraph whereas the [06:04] blocks called core slash paragraph. [06:08] bit annoying, but that's what you have [06:09] to do. Um, and then for each of those, [06:12] we then use the core WordPress function [06:15] WP NQB block style, [06:18] >> which kind of does what it says on the [06:20] tin. It it registers your CSS file with [06:23] WordPress and it encues it when that [06:26] block is detected in a page load. So, [06:29] you'll only ever get that loaded if you [06:32] have that block on the page, which seems [06:34] much more efficient. you know, if we've [06:36] got some specific styles for a media and [06:38] text block, but that's not on the [06:39] current page, it seems silly to load the [06:41] CSS for that when we don't need it. So, [06:43] this is trying to attack this so that [06:46] only the CSS you want is loaded. [06:50] And that should help because our CSS [06:52] files quite large. So, we can split that [06:53] into smaller files and only load those [06:55] when they're needed. It makes sense. The [06:58] other thing that the WPMPQ block style [07:02] does and this is why you need the path [07:04] of your stylesheet. Uh it's like the [07:07] path on the server is because it will [07:10] try and inline those styles if it judges [07:13] that they are suitable for being [07:15] inlined. [07:16] >> Um I haven't actually looked into what [07:18] the criteria is that. I think part of it [07:19] is how how much CSS there is in your [07:22] file. So if you've only got a few rules, [07:23] it's probably just going to inline them [07:24] straight away, which is again a little [07:26] bit more efficient. So uh that works. So [07:29] basically once that has that function [07:31] has been running and I've just added [07:32] that into the theme, um it's hooked into [07:36] the ad, uh the in it hook and it will it [07:38] will try and cue styles for each block [07:41] uh if they're present. So now all Keith [07:43] has to do is put the files in the folder [07:46] and they'll just automatically get [07:47] incued because they because of their [07:49] presence essentially when those blocks [07:51] from the page. [07:52] >> So the next task after that is to go and [07:56] look at the theme stylesheet which is [07:57] all one and then try and split that into [08:00] the different block stylesheets and try [08:02] and then [08:04] >> split those out. We'll still have a [08:05] theme stylesheet because not [08:07] everything's rel, you know, relative to [08:08] a block. But, um, that's that's the [08:11] plan. So, I don't know how you're going [08:12] to do that obviously because you're [08:14] using SAS. SAS, is that right? [08:16] >> Yeah. Yeah. CSS. Yeah. Yeah. [08:18] >> So, to try and compile those into the [08:21] right place. I'm not sure. But that's [08:23] the next task. Um, that is the next [08:25] task. We So, Mark, we did something [08:28] similar uh on the Kimolton school. I [08:31] don't want to put you on the spot having [08:32] to remember exactly what code you wrote [08:34] for that. [08:35] >> Yep. [08:35] >> Uh I wasn't compiling my CSS. I was just [08:38] writing CSS files on that particular [08:40] project. I just thought I'd try that as [08:41] an approach. So So my side of things was [08:43] in a way much simpler. [08:45] >> Is is your new approach different to [08:48] what we did for Kim Bolton? [08:50] >> And if so, how and kind of is it better? [08:55] >> Uh no, it's extremely similar. The only [08:57] thing that I have changed, and this is [09:00] because you don't need it with the [09:02] original site where we did this, uh, I'm [09:06] doing the same approach, looping through [09:07] each of the files that we've got. [09:10] >> Yeah. And what I was doing is [09:12] registering a style and then encuing the [09:15] block style which actually you don't [09:17] need to do because the WPNQ block style [09:20] function handles the registration and [09:23] the NQing very much like the WPNQ style [09:26] function does. [09:28] >> If it hasn't been registered, it will [09:29] register it. If it is registered and it [09:31] it won't register it. [09:33] >> So that's the only change here just to [09:34] make it a little bit more efficient. Um, [09:36] but it's essentially very similar. [09:38] >> And are we doing the same thing with our [09:42] JavaScript? [09:45] >> Good. I'm glad you asked. So, [09:48] um, we're not, but we probably could be. [09:53] I've been experimenting with that, uh, [09:56] this week. [09:57] >> Yeah. What what was a key thing for me [10:00] was [10:02] I you can load JavaScript for any block [10:06] on the front end quite straightforward. [10:08] So we've we've done this for this [10:10] particular project. So we have [10:12] >> um I'll take an example. We have a a [10:16] gallery block and we turn that into a [10:19] slider when they want like a logo [10:20] slider. So what we essentially do is we [10:22] create a block style that's called logo [10:26] slider I think it's called and when they [10:28] apply that block style the JavaScript [10:31] that we've got will obviously then hook [10:33] into the CSS class that's added and turn [10:35] it into a slider. So you want to incue [10:38] your JavaScript when the gallery block [10:41] is loaded. [10:42] >> Yes. So you can do that uh using the [10:45] filter called block type metadata which [10:48] essentially filters the block JSON file [10:50] for the blocks in question [10:53] >> and you can add your script uh into [10:56] that. It's called view script. View [10:58] means like viewing is on the front end. [11:00] It's basically load this script when [11:02] we're viewing this on the front end. So [11:03] you'd register a script as you normally [11:05] would and then you'd filter this and [11:07] pass the handle of the script to this to [11:10] this block JSON or this block meta [11:12] filter. [11:13] and then your JavaScript will get loaded [11:15] when the block's on the front end. [11:17] >> Okay, [11:17] >> now that's great and it works for any [11:19] block as long as it has a block JSON [11:21] file because that's what you're [11:22] filtering. So if you've got a very old [11:24] ACF block that was using like ACF [11:26] register block type, it didn't work for [11:28] that. So we and we've got a few blocks [11:30] like that. So we need to update them [11:31] slightly. [11:32] >> Um but they have other functions that [11:34] you can use to to encue assets as well. [11:36] So you can still do this, it's just a [11:38] different method. Um, the one thing it [11:40] doesn't do, which is what I really [11:42] wanted to try and solve, is that I only [11:45] want to encue that um, logo slider [11:50] JavaScript file that you've written when [11:52] that block style is selected. I don't [11:54] want to incue it. If they just had a [11:56] gallery, a normal gallery, there's no [11:58] point. It's a waste. They don't need it. [11:59] >> Yeah. So, that's what we have been doing [12:01] currently. So we we've got scripts for [12:02] example that get loaded on every [12:04] paragraph block because there's a [12:05] certain paragraph style that [12:07] >> correct [12:07] >> does like a little counter. Yeah, [12:09] >> correct that does a little counter. So [12:10] every every paragraph has that which [12:12] essentially means it runs on every page [12:14] because pretty much every page has a [12:16] paragraph. So I went about trying to [12:19] solve that issue of how do we how do we [12:22] only incue uh block assets sorry block [12:26] uh JavaScript when the block is actually [12:29] being viewed. And I'm actually just [12:30] going to load up the post I wrote. Uh, [12:34] hang on. So I can actually get the code [12:35] in front of me. Um, and then we can see. [12:40] So I I asked used a bit of um AI as we [12:44] do and uh got some help from from Bob. [12:48] But essentially what I wanted to do is [12:50] to say [12:52] if this block has this block style then [12:56] I want to somehow incue our JavaScript. [12:59] So we'll use the logo slider as an [13:01] example. [13:03] So and the way in which I'm doing that [13:05] is you you can't you can't do that with [13:10] filtering the block metadata because at [13:13] that point in time the instance of the [13:16] block hasn't loaded. You're just sort of [13:18] saying this is the data for all blocks [13:21] if you know what I mean. [13:22] >> Yeah. [13:23] >> Not the actual instance that's on your [13:25] page. [13:26] >> Yeah. [13:26] >> So the the only method that I found to [13:28] do it with you have to do that using the [13:30] render block filter which if you didn't [13:33] know the render block filter allows you [13:36] to change the block HTML and it also [13:40] allows you to to obviously run your own [13:42] code at the same time. [13:43] >> Yeah. So there is also render block [13:46] filters for each individual block. So [13:48] render_block underscore and then the [13:50] block name will only run your code on [13:53] that particular block. So in the gallery [13:55] one we do render block core slash [13:58] gallery and then we'd run our code. And [14:00] what we're doing with in the code that [14:02] I've got is it's looking for a class [14:04] name called is style whatever your style [14:08] is. Ours is logo slider. If that class [14:10] is not present, then we just return the [14:13] normal block content as it was. We don't [14:15] want to touch it. We just finish there. [14:16] That's it. If that is the case, then [14:20] what we can do is run the WPNQ script [14:23] function, which will encue our logo [14:26] slider JavaScript. Um, and then just [14:29] return the block content as it was. We [14:31] don't we don't want to touch the block [14:32] content. We're not really interested in [14:33] that. We just want to do something at [14:34] the point the block loads. [14:35] >> Yeah. [14:36] >> And that works really well. um the the [14:38] and it the the script gets encued only [14:40] when your style is run. [14:43] >> Haven't tested it on the actual site [14:46] yet. I've been running it on a local [14:47] little test environment, just a simple [14:49] test WordPress. [14:50] >> Um but I've added multiple blocks of [14:53] different styles and it all seems to [14:54] only load when you you've obviously got [14:56] your style selected. [14:58] >> Yeah. [14:58] >> Which is great. So we just need to do a [15:00] bit more testing. But yeah, it's good. [15:01] >> Very cool. Um, few comments I think we [15:04] should go through now while we're fresh [15:06] on the topic. First of all, a little [15:09] wave uh from Mark. Uh, Mark, [15:12] >> nice to have you. Nice to have you here, [15:13] Mark. Um, Courtney uh says, "I always [15:16] registered CSS and JS with each ACF [15:20] block in brackets JSON. However, this [15:23] created too many HTTP requests and [15:25] caused its own issue. Um, do you use [15:28] asset bundling?" [15:31] have to say I don't know what asset [15:33] bundling is. [15:34] >> I don't know. No. [15:35] >> Um but yeah, so obviously this will [15:38] create more HTTP requests. Um if we're [15:41] breaking up stylesheets and JavaScript [15:44] files into you know smaller smaller [15:46] chunks um that [15:51] was that HTTP2 [15:53] can handle that [15:54] >> and I'll bring in Mark uh for for for [15:57] that. So Mark then comments if the site [15:59] is loaded over HTTP2 [16:02] then it's more efficient to load [16:04] separate files than one merged file. If [16:06] the path attribute is passed the WP and [16:10] Q block style then the CSS is inlined [16:14] which makes the issue of separate asset [16:17] loading moot. Okay. So that is what I [16:21] kind of thought as well. I mean, does it [16:23] get to a point where even with HTTP2, [16:27] you know, like you can have too many [16:30] requests? I I don't know because [16:32] presumably it can only kind of handle a [16:33] certain number at a time. Um [16:36] >> I don't I don't know. My my [16:37] understanding with HTTP one or whatever [16:40] it was it 1.1 can't remember. [16:42] >> Was that the browser can only handle one [16:44] request at a time? So, it requests the [16:47] JavaScript file. It waits for the server [16:49] to respond. the server responds with a [16:51] JavaScript file and it requests the next [16:53] one and so on. Whereas with HTTP2, [16:56] I understand was it it can like open a [16:58] connection and then it can say like give [17:00] me this one, this one, this one, this [17:01] one, this one, this one and then it can [17:02] just send them to you. [17:03] >> Yeah, you can see that in the network [17:05] tab on most websites now. So if if you [17:07] open the network tab and you can see [17:09] that kind of waterfall view, [17:10] >> they'll quite often just be like it gets [17:13] to the kind of right, I need to load my [17:14] CSS or JavaScript files now and they're [17:16] all just stacked exactly vertically like [17:19] >> they happen at the same time in instead [17:21] of like one after another. So instead of [17:24] like the step effect that you used to [17:25] get, it's just a single kind of line. [17:27] It's just like bang, they're all done in [17:29] in in one go. Um Elliot then says, hi [17:34] Elliot. He says, "Agree. SAS compilers [17:37] aren't great for blocks work as they [17:40] need to only load if the block is loaded [17:42] on the page." So, yeah, not compiling [17:44] all of your I guess he's saying agreeing [17:46] that not compiling all of our block CSS [17:49] into one uh into one file is is the [17:52] right is the right thing to do. Uh and [17:54] he says, "Just so happens I created a [17:56] PHP class for extending block assets for [17:59] CSS and JS in my GitHub." Go. Uh I think [18:03] we've kind of biged up Elliot before, [18:05] but he puts out a lot of really great uh [18:07] WordPress developer content. So please [18:09] do go and check out his stuff uh [18:11] including his GitHub and his YouTube [18:13] channel. Um and then one more from [18:16] Elliot Hook WP and Qcript 2 and QB block [18:21] assets should work. [18:24] You might have to help me with that one. [18:26] Mark Hook, I'm not quite sure what he [18:29] means there. So, uh, NQ block assets is [18:33] a hook that will run on both the front [18:35] end and the back end. [18:37] >> Mhm. [18:38] >> So, if you want if you want your [18:40] JavaScript to load in the editor as well [18:42] as in on the front end, then you'd want [18:44] to use ENQ block assets [18:47] >> rather than something like render block. [18:49] I would imagine that's what he's [18:50] meaning. [18:51] >> Most of the time with these things, we [18:53] don't want to load these in the in the [18:55] editor because it actually makes editing [18:59] JavaScript. [19:00] >> Yeah, we don't load the JavaScript [19:02] because actually if you turn it into a [19:03] slider in the back end, [19:05] >> how do you click on an image to then [19:07] start replacing it and stuff like that? [19:09] >> It depends what you're doing. I think [19:12] the time, but I find most of the time [19:15] you probably don't want to load the [19:17] JavaScript in the back end, but that is [19:20] very specific to what you're doing. [19:22] Yeah, that's exactly what Courtney's [19:23] asking here. She she said, uh, how do [19:25] you render sliders in the admin? Do you [19:27] write admin CSS to just show one slide [19:30] for example the way we've done it so uh [19:34] there's lots of different ways uh it [19:37] depends on the slider um you know we [19:39] we've built kind of custom blocks with [19:42] uh that are sliders and in that case [19:44] we're often just using ACF to build the [19:46] block and then just using like a [19:48] repeater field so there is really no [19:50] what you see is what you get kind of [19:52] experience [19:53] um [19:55] or we're using a current block like the [19:58] gallery block for example. And in the [20:00] back end in the editor, we just leave it [20:02] as a gallery so that the client, the [20:06] user, the editor can see all of the [20:08] images uh and just click on them and [20:10] change them and and move them around [20:12] like they would with a normal gallery [20:14] just knowing that on the front end it's [20:16] not going to look like that. that that's [20:18] the compromise that we've found because [20:19] I think having a proper slider interface [20:22] and having to kind of as a gallery would [20:24] be [20:25] >> could be pretty horrible as a as a user [20:27] interface. [20:28] >> This is where the block editor often [20:30] conflicts with this what you see is what [20:32] you get. Like sometimes it just isn't [20:35] easier to to handle what you see is what [20:37] you get in the back end. Like you it [20:39] doesn't make sense. Like with this [20:40] slider, it'd be so difficult to sort of [20:42] like change images because often would [20:44] be off the screen cuz they're on a [20:45] slider. [20:46] >> Yeah. Yeah. [20:46] >> So you'd have to slide everything across [20:48] and then it just doesn't really make [20:50] sense. [20:50] >> And actually [20:52] despite some of its limitations which [20:54] are obviously changing that's one of the [20:57] reasons I actually really like building [20:58] blocks with ACF because you're getting a [21:01] very kind of datacentric editing editor [21:04] view. [21:05] >> Uh and then you can you could switch [21:07] across to the like the preview mode [21:09] which will show what it looks like. [21:11] >> Yeah. And you've got this edit mode [21:13] which is a better sometimes editing [21:16] experience. Um [21:17] >> it is now with the new ACF. [21:19] >> Certain yeah certainly like coming on [21:21] leaps and bounds at the minute. So [21:23] >> two two of the new features of ACF 6.7 [21:27] are inline editing. So you can just edit [21:30] things by clicking on them kind of like [21:31] you're doing a block editor. I think [21:33] that only works for a limited number of [21:34] blocks at the moment ACF blocks. Um, and [21:38] then the other one is that you have this [21:39] new sort of like panel that can come out [21:41] on the right hand side rather than fill [21:43] in the block sidebar. So have a look at [21:45] those things. They're quite nice as [21:46] well. [21:47] >> Yeah, it's interesting. So Elliot says [21:50] here, [21:51] take the interactivity API. It's only [21:54] available in the front end. So there is [21:57] no uh Wizzywig [22:00] with the interactivity API. So I wonder [22:02] I haven't really played with [22:03] interactivity API so I don't know kind [22:07] of what that what that then looks like [22:09] in the editor. I don't really even know [22:10] how to kind of how to use it yet. But [22:12] that that is interesting. That's [22:13] something bit of bit of a potential [22:16] limitation there. But I'm sure that's [22:18] something that they'll look at in the [22:19] future. Um [22:20] >> yeah true. [22:21] >> But yeah so so kind of fun stuff. So, [22:23] I've I've not now got to rewrite my npm [22:27] scripts to uh to save my instead of [22:30] compiling all my CSS into one uh theme [22:34] file, I need to get them all saving in [22:37] the right places. So, that's that's my [22:38] little challenge. I don't think that's [22:39] going to be too difficult. Um but [22:41] hopefully I'll have that ready to talk [22:43] about maybe for next week or early in [22:45] the new year. [22:46] >> Um [22:48] >> we we also don't minify it yet, do we? [22:50] As well, which we could do. The saving [22:52] on that wasn't particularly massive [22:53] though, was it? [22:56] >> We should. [22:57] >> We should. We should do it. It wasn't [22:59] groundbreakingly. Oh my god, that's [23:00] harvest time. It was a tiny amount. But [23:04] >> makes sense. [23:05] >> You're automating it anyway with with [23:06] SAS. Makes sense. Just squash it all. [23:09] >> Yeah. Yeah. Yeah. Same same with [23:12] JavaScript. So, yeah, probably probably [23:15] look at that as well. Um, there's one [23:17] more kind of technical one that I just [23:18] want to cover. Just an interesting issue [23:21] that we came across today [23:24] uh which is one of our job relay [23:27] customers um and a and a rack press [23:29] customer actually. So we built their job [23:31] board uh hooked it up to Bullhorn for [23:34] them and I got an email this morning [23:38] saying one of our one of our jobs is [23:40] 403ing and I was like that's kind of [23:42] weird and writing off that one 403ed and [23:44] all the other jobs didn't. Um and I had [23:48] a The thing that just jumped out at me [23:50] almost as soon as I saw it was that the [23:54] the job that had the issue, the 403 um [23:57] had an uml in the uh title of the job. [24:01] Uh and it was making the URL look very [24:04] very strange. Um so we we've kind of dug [24:08] into that a little bit this morning. How [24:11] have we actually kind of found the [24:12] solution or figured it out or or do you [24:15] are we still a bit confused? I haven't [24:17] tested it yet. [24:18] >> Yeah. [24:18] >> But I'll explain what happens. So [24:21] >> yeah, [24:22] >> when a job gets delivered from or gets [24:25] delivered to the website, wherever it's [24:27] coming from, whether it's Bullhorn or [24:29] Broadbean or Logic Melon or whatever it [24:30] is, um we simply use the WP insert post [24:34] function to sort of create the post in [24:36] WordPress, the job post. And obviously [24:40] we pass the uh the job title into there [24:44] when you create the post. And WordPress [24:46] automatically generates the post name if [24:49] you don't specify it. And it'll generate [24:51] it by taking the title and essentially [24:54] separating it with dashes um and doing a [24:56] few other checks and things. One of [24:58] those checks that WordPress does is to [25:00] check for I'm just going to call them [25:02] weird characters. [25:04] I'm I'm sure that uh Germans and French [25:07] don't call them weird, but apologies for [25:08] that. [25:09] >> Special characters. [25:10] >> Special characters. Are they special? [25:12] They're not special to those anyway. [25:14] >> Non-standard [25:16] >> English characters. I don't know what to [25:17] call them, but you [25:18] >> There is an official word for this, but [25:19] we haven't got it. So, [25:21] >> yeah. And what it does is it it strips [25:23] those out. So, for example, in this [25:26] particular case, it was the letter A [25:28] with an over, which if you don't know, [25:29] it's got two little dots over the top of [25:31] it. Um, and it just strips out for a [25:33] normal A and then saves the the post [25:35] name. Um, but then in in my code, what [25:38] we do next is we actually update the [25:41] post name once the post has been created [25:44] with appending the post ID. So I can't [25:47] do it when the post is created because [25:49] at that point I don't know the ID. So I [25:51] append the post ID at the end of it in [25:53] an update. And the reason we do that is [25:54] so every job has a unique URL because [25:57] lots of recruiters they recruit the same [25:59] sort of jobs. So they end up posting a [26:02] job and it's like [26:03] marketing-manager-london [26:06] and then that job gets deleted and [26:08] another one comes in and it has the same [26:09] URL as the original and it just confuses [26:12] ATS systems. It confuses lots of things. [26:15] >> Yeah. [26:16] >> So long short long story short is we put [26:18] the post ID on the end so they're always [26:20] unique. And when I'm doing that update, [26:23] so say WP update post and I'm changing [26:26] the post name, I needed to sanitize the [26:29] title. So, I used sanitize title with [26:33] dashes, which it kind of does what it [26:35] says on the tin. It puts dashes in the [26:36] title that that was given. [26:38] >> However, it would appear that that does [26:41] not convert the accents [26:44] or [26:46] special characters or whatever we're [26:47] calling them. It doesn't do that. It [26:49] doesn't do that at all. So, then it left [26:52] that in the URL and then when you view [26:54] it, again, I'm not entirely sure why it [26:57] 403s. Is that a server thing? Is that a [26:59] I don't know, but it's 403s and it it's [27:01] clearly the problem because you replace [27:02] it and it doesn't. However, what I've [27:05] since worked out I think today is that [27:08] you should use sanitize title and the [27:12] reason for that is because sanitize [27:14] title I believe calls sanitize title [27:18] with dashes and it calls the function [27:22] called remove accents which is does this [27:24] little replacement between the special [27:26] characters to normal ones. So, I need to [27:29] update our plugin to swap that sort of [27:31] sanitization function out. And I think, [27:34] as I said, I haven't tested it, but once [27:35] I do that, it will actually solve this [27:37] problem. [27:39] >> Yeah, we'll see. [27:40] >> It's a weird one. I can't believe we [27:41] haven't come across it before. [27:43] >> Yeah, that's what I was I was amazed [27:45] that this hasn't been a problem before. [27:46] So, [27:47] >> and you're thinking maybe that is [27:48] because there's some kind of like server [27:50] level configuration or even something [27:51] within WordPress that's kind of [27:55] >> like a security plugin or something that [27:56] isn't isn't loving the the character but [27:59] >> yeah basically trying to again I'm [28:02] completely making this up as a guess but [28:04] if the server is seeing that in the URL [28:07] is it sort of some firewall saying that [28:10] looks a bit weird I'm just going to [28:11] block it 403 access denied unauthorized [28:13] whatever I don't know. Yeah. [28:16] >> Yeah. So Marcus said make sure that the [28:19] saved value part of the post name has [28:21] been run through sanitized title. [28:24] That will convert characters. [28:26] >> Exactly. [28:27] >> And most browsers understand special [28:29] characters, but if they're not converted [28:31] properly, eg UTF8, [28:34] uh then that may well cause a problem. [28:37] So yeah, that's I think that's what [28:39] we've been uh experiencing. So yeah, [28:41] hopefully we'll get a fix out for that. [28:43] But [28:44] >> essentially, it's me using the wrong [28:46] function. [28:47] >> But like [28:48] >> my brain thought sanitiz title with [28:50] dashes was the right function because [28:52] that's literally what I want to do. I [28:53] want to take the tile and put the dashes [28:54] in the right place. So it's not you know [28:56] what I mean? But apparently no. You [28:58] should use sanitize title. [29:00] >> You learn something every day. [29:01] >> Yeah. Yeah. Yeah. Yeah. It's that was [29:03] interesting. But yeah, hopefully a [29:05] little fix there, a little improvement [29:06] to the product. So that's good. Um, last [29:10] thing on the list and I don't think well [29:11] well maybe we will won't take too long [29:14] on this I don't think um is sale pricing [29:17] and discounts. So sale Why did why did [29:22] you put this one on the list? What was [29:24] uh [29:25] >> well I think I was watching [29:27] >> I was watching WP Builds earlier this [29:29] week and they were sort of chatting [29:30] about Black Friday deals and things like [29:32] that. [29:32] >> Yeah. [29:33] >> Um and then we had a customer actually [29:35] which has kind of brought it up again. [29:37] So I we had a customer earlier this week [29:39] and they were I'd sent them everything [29:40] that they need to buy the product. They [29:42] decided to buy the product and then um [29:46] interestingly on the call they'd already [29:48] said oh I spoke to you three years ago [29:50] and then it was like your product was 35 [29:52] quid and you know now it's 49 quid. So [29:56] immediately I'm thinking you know [29:58] they're thinking about discounted prices [30:00] and and I just said well you know the [30:02] world's moved on since then the price is [30:04] what it is now sort of thing. And then [30:07] the customer uh I sent them everything [30:10] they need to buy it. They said, "Yeah, [30:11] yeah, I'm going to go ahead and buy it [30:11] now." And then they sent an email about [30:13] like two minutes later says, "Oh, I can [30:14] see there's a discount code box on your [30:16] checkout page, you know, is there a [30:17] Christmas discount that I can use?" You [30:18] know, you know, all feeling of goodwill [30:20] and stuff. So, I was just thinking and [30:23] it got me thinking about Black Friday [30:24] prices as well, you know, like [30:28] why offer a Black Friday deal? I don't [30:30] quite understand it because why are you [30:33] offering this sale? Because if people [30:36] want the product, then surely they will [30:39] they will pay for it. And if [30:41] >> if you're not selling them unless you [30:45] offer a discount, then isn't your [30:47] pricing just wrong? As in make the price [30:50] the Black Friday discount [30:52] rather than having to run these sales [30:54] and discount codes. I don't understand [30:55] it. [30:56] >> Yeah. [30:56] >> But then we we were talking earlier, [30:58] weren't we about businesses have [31:00] different models, don't they? How they [31:01] sell things. You know, if you think [31:03] about um you know, sofa companies in [31:05] this this country, [31:07] they constantly have offers on. Like you [31:09] you you'd never buy a full price sofa in [31:12] this country because they've literally [31:14] like [31:15] >> they always got a sale on. So [31:17] >> do do a lot of businesses run [31:19] >> which is technically illegal by the way. [31:22] >> I'm pretty sure [31:23] >> I'm I'm sure they're not being illegal [31:25] because they'll be pricing them at the [31:26] right price for certain periods just [31:28] long enough and so on. [31:30] >> Yeah. Yeah. Exactly. Yeah. So is is the [31:33] customer and I'm taking this customer in [31:36] particular for us are they seeing like [31:38] oh it's it's £419 a year is job really [31:41] yeah but we're not going to pay that way [31:42] because there's always going to be some [31:43] sort of like discount that they're going [31:44] to give us on the call you know and that [31:46] sort of thing and a lot lot has that you [31:48] know is that the best price you can do [31:49] and everything like that and I'm like [31:51] yeah because that that's how much it [31:53] costs whereas I think other custo other [31:55] companies might be yeah but if you buy [31:58] it today we can give you a discount code [31:59] for 20% off and and and so on. So, is [32:02] the customer that was asking us in the [32:04] mindset that if they pay £419, [32:08] then they're they're losing out like why [32:10] are they paying that much when there's a [32:11] discount code box on the checkout and [32:13] everyone else will be putting a discount [32:14] code in there and I'm not. [32:16] >> So, it's an interesting [32:18] >> I just think it's a really interesting [32:19] like mindset. My my my thought process [32:24] is that we shouldn't offer discounts. We [32:27] shouldn't offer discounts for for the [32:29] product and because we value well we we [32:33] price the product at what we think is a [32:35] value to the customer and they either [32:38] think that's valuable or not. Now if we [32:40] experience that and like you know 75% of [32:43] the customers book calls they love the [32:45] product and then they I'm not buying it [32:46] because the product is the price is too [32:48] expensive then we'd have to think about [32:50] whether it's the right price. [32:52] >> But I don't think that's the case with [32:53] our product. I think the price is the [32:55] right price. [32:56] So why would we want to offer discounts? [32:58] I don't quite understand why that would [33:01] be the right thing to do. [33:02] >> And it's so I think our product is so [33:04] niche as well that we don't have a lot [33:06] of kind of direct competition. There [33:08] isn't we we actually do have some [33:10] competition in in our in our space for [33:12] job relay, but it's not like [33:15] it's not like buying a a hi-fi or like a [33:19] TV and you're and you're like you could [33:21] buy the same Panasonic TV from a million [33:25] different places and you're going to [33:26] search through all through them all to [33:27] find the one that's giving you the the [33:29] best deal. [33:30] >> Like [33:31] >> yeah, I I I've got kind of different [33:33] experiences, I guess, with sales and [33:35] discounts. So, for example, I just [33:38] bought a soundbar for my home, my my TV [33:42] in my living room. [33:43] >> Uh, and I've I've waited for nearly two [33:47] years actually for a Black Friday sale [33:48] because I forgot to buy it last year. [33:51] Um, so like Black Friday came along and [33:53] I was like, right, I I'm actually going [33:55] to like troll about and see if I can [33:57] find a good sound bar for a good price. [33:59] And I did and I bought it. So having a [34:03] Black Friday sale at this point in time [34:05] meant I bought that particular thing. So [34:08] but [34:08] >> but if they never had a Black Friday [34:10] sale, would you have waited two years to [34:13] get a Black Friday deal or would you [34:15] have decided [34:16] I'm going to buy? [34:17] >> No, cuz I Well, I didn't have a specific [34:21] model in mind until now. So, I just I [34:24] just knew that like electronic equipment [34:27] is [34:29] is sold on Black Friday. It's nearly [34:31] always discounted around this time of [34:32] year, but like do people think of think [34:34] like that with WordPress products and [34:36] plugins and web SAS stuff [34:39] >> as wait for Black Friday. [34:41] >> Yeah. So, there's the Black Friday [34:42] thing. I think Katie Keith has loads of [34:44] like thoughts on this. She's run like [34:46] experiments and put stuff out into the [34:48] world. to maybe like try to track down [34:50] some of her content on whether Black [34:52] Friday works or not. I think it's been a [34:54] bit hit and miss. I think they sell a [34:55] lot because it's discounted. It's not [34:57] quite right. I don't know. [34:59] >> It'll it'll work. I mean, why won't it [35:02] work? Like, you're probably going to [35:04] sell products around Black Friday if [35:06] you've got a Black Friday discount. [35:07] Like, it's not rocket science, is it? [35:08] People are going to anyone who was in [35:10] two minds and like they jump on, oh, [35:12] they've got a black, oh right, okay, [35:13] I'll buy it now. So, I don't I don't [35:15] quite understand like that will work, [35:16] but you're selling it for less than you [35:19] thought it was worth. [35:20] >> Yeah. [35:21] >> And and if if the cases, well, actually, [35:23] Hang on, most customers aren't buying [35:25] it. They're just waiting until Black [35:26] Friday. Why not just make the Black [35:28] Friday price the price? [35:32] >> And then you'll sell them all year. [35:34] >> Yeah. [35:36] Yeah. [35:36] >> Because that's the price we want to pay [35:38] for it. [35:39] >> I really don't I really don't know. [35:41] Yeah. One company that I think jumps [35:44] into mind is is Apple. Like they don't [35:45] do sales. [35:47] >> Yeah. [35:47] >> They just don't do sales. So no one [35:49] feels they're missing out because they [35:51] never do sales. So the price you see on [35:53] the website is the price I pay, you pay, [35:56] everyone pays. [35:57] >> Yeah, that's true. [35:58] >> There's no feeling of missing out or [36:00] anything. The only thing they do is like [36:01] the student thing, don't they? Get like [36:03] a AirPods if you buy something for [36:05] students. [36:06] >> But that's it. That's that's [36:07] >> all. Yeah. Yeah. Yeah. We we have priced [36:10] our MacBook Pro at this price and that's [36:12] it. [36:12] >> I remember when I was going to going to [36:15] buy a car. Uh I think it was maybe the [36:18] first time I'd ever like gone to like a [36:20] dealership to like to buy a car. [36:22] >> And I I'm I'm an introvert. I'm a [36:25] conflict avoider. The thought of like [36:27] haggling on a price is just like [36:29] kryptonite to me. But I thought I'm [36:30] going to I'm going to do it. I'm gonna [36:33] like I'm gonna be brave and I'm gonna [36:34] like so like the salesman sits us down [36:38] and he goes right and this is the price [36:39] and like outlines and everything and I [36:40] was like okay so you know can you you [36:43] know what kind of what kind of deal can [36:45] you do like what's what's the lowest you [36:47] can go he's like no that's that's it I [36:49] was like no seriously come on and he [36:51] just I was I was certain I was in a car [36:55] dealership I was certain there was a [36:57] lower price to be had and it really [37:00] really annoyed me that he just wouldn't [37:02] budge [37:03] And in the end, like [37:04] >> did you walk away? [37:05] >> No, I think I told this story. [37:07] >> She just walked away. [37:10] >> I can't remember if I threatened to, but [37:12] I didn't. I actually did it. And I [37:14] remember that's not for me. And just [37:16] walk off. [37:16] >> I got so desperate that um I'm a cycling [37:20] fan and I was buying a scooter and [37:22] scooter sponsored the tour to France and [37:24] they had like the scooter tour to France [37:27] green jerseys up in the in the thing. [37:30] And I was like, "Okay, would you just [37:32] give me just would can I just have a [37:33] turn of France jersey? Like I'll pay [37:36] full price, but can I just have one of [37:38] those turn?" No, no, you can't have [37:40] that. I was like, "Oh my god." I bought [37:42] the thing. Bought the thing because I [37:43] wanted it and it was a good deal. But [37:46] yeah, but I Yeah, that was that was a [37:48] horrible experience. I just I I felt [37:50] like I was uh just not very skilled that [37:52] Oh, I'm not I'm not skilled at that. I [37:55] should have left that to my wife. She's [37:56] she's really good at that kind of [37:58] >> Yeah, I can imagine she is. [38:01] She loves a haggle. [38:02] >> Yeah. Elliot says, "Not a Black Friday [38:05] related, but I think offering a discount [38:07] for early adopters is a viable reason [38:09] for discounting." I [38:10] >> I like that. I like early. [38:12] >> I don't disagree with you. Yeah. Yeah. [38:14] >> But these are like the nothing to do [38:15] with early adopters. This is just, hey, [38:17] this arbitrary day has happened in the [38:20] year where you can have a discount. [38:23] >> I'll tell you something else. This isn't [38:24] Black Friday related. I used to work for [38:26] Adidas uh in one of their retail [38:28] outlets. Um I was like assistant manager [38:31] of of of the shop. Um and we we were [38:35] just basically told if someone asks for [38:36] a discount, you can give it to them. So [38:39] like you it was just all they have to do [38:42] is say, "Are there any discounts?" And [38:44] you and you could basically make it up [38:46] up to a point. So you could say, "Yeah, [38:47] I'll give you 10% off [38:49] >> or yeah, I'll give you 15% off." Like we [38:52] we had that power. So there is stuff out [38:55] there where if you just ask you will [38:57] get. I was going to say if you don't ask [38:59] you don't get do you? [39:00] >> Yeah. So like you can literally walk up [39:02] to a I don't know if they still do that [39:03] kind of thing. So at Adidas outlet shops [39:05] give it a go. That was a long time ago. [39:07] But uh [39:08] >> but but that's so so if so if I I meet [39:11] up with a friend at night and we've [39:12] we've both been shopping in the day and [39:14] so let's say yourself you've been into [39:16] the adidash shop and you bought a [39:18] beautiful pair of trainers for 100 quid [39:19] and you've asked you say oh is there any [39:21] discounts and yeah oh yeah get 10% off [39:23] then you go so if I buy we bought the [39:25] same product and I've paid 100 quid for [39:27] them because I didn't ask and then we [39:29] both have a chat afterwards. I come away [39:30] with a really bad feeling about that [39:32] company. [39:33] >> Why didn't I get a 10% off? Like we we [39:35] bought at the same time, literally. [39:38] >> So, how's that good? [39:40] >> I don't know. I don't know. I guess like [39:43] No, I guess partly the purpose of an [39:45] outlet shop is to get rid of stuff. [39:47] Like, they're literally just like if you [39:49] can sell it, sell it because, you know, [39:51] this is stuff that's going in the bin [39:53] otherwise. So, [39:54] >> yeah, maybe that's a bit different than [39:55] that sort of type of stuff is. Yeah. [39:58] >> Yeah. Yeah. Yeah. [40:00] got a bit away from the WordPress there, [40:02] but uh but yeah, [40:03] >> as you can tell, I'm not a fan of uh [40:06] discounts and really [40:08] >> Black Fridays and [40:09] >> I think they have their I think they [40:10] have their place, but I do find I do [40:12] find them to be a bit weird sometimes [40:13] and bit arbitrary and [40:15] >> the whole Black Friday thing I find [40:16] absolutely bizarre, but there you go. [40:18] >> Set your price, stick to it, review it [40:21] if it's not working. [40:23] >> Yeah, [40:23] >> that's my that's my my chance. [40:25] >> Early adopters, I'm with Elliot on that. [40:27] I think that's a I think that's a really [40:28] good That's that's a different one. I [40:30] get that. But I think that's a different [40:32] conversation to the one we're having. I [40:33] think if you're starting out, you want [40:35] some that I Yeah, that makes sense. That [40:37] makes sense. [40:37] >> Didn't even get into lifetime discounts. [40:39] Let's not get you started on that. [40:40] Anyway, [40:42] moving on. Moving on. In fact, not [40:44] moving on. Let's finish up there that [40:46] we've done uh done about 40 minutes. Uh [40:49] covered a lot. So, let's finish up for [40:51] this week. As always, thank you so much [40:53] for joining us, for listening, for [40:55] watching. Uh if you do enjoy the show, [40:58] please do consider leaving a little [41:00] like, just click that little thumbs up [41:02] and uh if you want more of this kind of [41:03] thing, you can subscribe and you will [41:05] get notified if you also click the bell [41:07] on YouTube or if you uh follow us on [41:10] your favorite podcast player. Um and if [41:12] you do like it as well, maybe there's [41:14] someone else in your network that would [41:16] enjoy this show. Uh if you could [41:18] possibly just send them a link, uh let [41:20] them know about us, that would be [41:21] superb. Uh are we doing a show next [41:24] week, Mark? Are we? It's getting very [41:26] close to the Christmas holidays. We [41:28] should do [41:29] >> do a little festive number. [41:31] >> Um, so we should be we should be here [41:33] next week. So again, if you want to uh [41:35] get notified of that, please do [41:37] subscribe and hopefully we will see you [41:39] there. Have a great week. [41:41] >> Bye-bye.