 So just to start off, I'd like to get a show of hands. How many people primarily use WordPress as developers? And then how many are primary business end users? OK, just trying to get a feel how to spin this talk a bit. So they already made an intro, so I won't bother going through my own intro. So my talk is thinking out of the box themes. The whole point of it is kind of as a marketer and someone who sells web design, I tend to have to make the argument of why someone should use a custom built theme over just buying a cheap theme out of a theme forest and running with it. And a lot of times you can have performance and other things, and so I'm kind of going to go through that. So as you probably also know, there's no shortage of pre-made themes. You've got 100 sites selling themes. TemplateMonster has over 1,200 themes right now. ThemeForce is like somewhere around $11,000. So you can go buy a theme for $50 and get your site going. So there's nothing wrong with that. It's quick, it's easy, it's, as you saw, a flu buy. It's quick and easy. It's the proverbial lipstick on the pig. But a lot of times those themes don't know what you're building, so they give you the kitchen sink. So that makes them often bloated, and it makes them fairly slow that ever shows up. So why do we care about a fast site? Because people like speed. They want a fast site. They want to get there. They want to get their content. They want to move on with their life. And slow kills. It affects your SEO. It affects your conversion rate. It affects the ability to make money with your site. So a few years ago, a couple of different sites did redesigns, and they did a performance test. ShopZilla did this. They found that when they reduced page load time from six seconds to 1.2 seconds, they increased page views by 25%. And more importantly, they increased revenue by 12%. So that's quite a lot. Amazon and Walmart also did this redesign back in 2015. And they attributed 1,000 millisecond change in speed to 1% change in revenue. When you're doing $1 billion in revenue, 1% is a lot of money. But most people, you're not building sites that are doing billions of dollars in revenue. So what does it matter? Well, next month, Google is going to start using your mobile site speed as a ranking indicator. So if you don't have a fast site, you're going to be sad, Keanu, because it's going to affect your ability to be found. So like I said, I've had this conversation with clients trying to convince them why they should do a custom theme. So I was like, OK, let's do an experiment. So what it is, it took a popular theme off of Theme Forest and I rebuilt it from scratch. Just to take one of their sample sites, rebuilt it to say, OK, here's what you get out of the box. Here's what you get looking the exact same. What's the difference? I'm just going to quickly see if I can jump over. I'll just show you the out of this. I'll bring this over to this, or maybe I just don't know what site I'm on. I think I'm actually over here in terms of, yes. So this is a theme. It's called Bridge. It's available on Theme Forest. Fairly popular. So it's fairly nice, fairly basic. Nothing too crazy, right? The about us, same thing. A little JavaScript counter, nothing too crazy going on. No sliders. I've made 2018 of the year of no sliders, personally. I will not build anyone a slider because, first of all, they're not accessible. And they're terrible to deal with and responsive. So I've made it the exact same. Exactly. So I've said 2018 is the year of no sliders. So I just can't see the other tab. Here we go. This is my version. You can see the brown's a little different because it didn't make accessibility requirements. So I fixed the accessibility colors in it. But it just can't see where my cursor is. It looks about the same. Still got your little JavaScript counter. Still got your stuff, right? All works. Same little JavaScript effects. Everything like that's still working. It took me about a weekend, like 16 hours to recreate from scratch. So the tools I'm using kind of test is webpagesptest.org and Chrome Lighthouse. If you're not familiar with Chrome Lighthouse, it's a built-in feature that basically lets you test your site for performance on mobile. So it'll give you a perceived speed index. It'll give you your accessibility score, everything. Right in Chrome, you just open the developer tools, go to Lighthouse, and you can just run your test on your site. And it'll simulate connecting with a slow connections and everything. And webpagesptest, for the tests, I ran nine tests out of the Dulles Center. And I also tested the site running on a high-performance AWS instance and a GoDaddy shared hosting, just to see what the difference is. And surprisingly, the GoDaddy shared hosting performed very close to the AWS. But there's other problems with the GoDaddy hosting other than just speed. But I was actually really surprised that the speed was close. WordPress, I followed fairly standard best practices, installed WP cache, lazy loading images, SSL certificate HTTP too, just trying to get the basic speed things that anybody can do done. So at least everyone's starting at something that everybody can do even with an out-of-the-box theme. So once again, here's the original theme. Like I said, it uses Visual Composer, has about 95,000 sales right now on ThemeForest. And it's got a 4.7 out of 5 rating from 4,800 ratings. So it's a fairly well-rated theme. And it sells fairly well, 95,000 sales, right? And then I rebuilt it using Advanced Custom Fields and Timber, as the developers are familiar with it. It basically gives you the closest you can get to an MVC framework in WordPress. And I built it on Foundation instead of Bootstrap, just because I'm more familiar with Foundation. I like it a little more. But performance-wise, Foundation, Bootstrap, they're on par. There's no real differences. And in terms of if you use it straight out of the box, it's probably a 10K difference in size for a default build. So anyway, we're going to go into the results, the actual experiment. The out-of-the-box theme had a page load time of 5.1 seconds. The custom version, 2.6. So if you're trying to hit that magic three-second load time on a desktop, that's right there, Google Lighthouse, 19.2 versus 6.2 seconds. That's a lot, and that's their mobile test. And that's what Google uses for doing their mobile speed testing. So how do we get two themes that look visually similar to have such different performance characteristics? Come down to two main things. Payload size and payload complexity. So payload size, the actual size of the files, everything. And the complexity is the number of files and the time it takes to render that page with those files. So if we look at the out-of-the-box theme, it's 2.5 megabytes for the home page. My version was 930 kilobytes. And then in terms of requests, the out-of-the-box theme had 115 requests. To the server, I had 34. So you can cut down a lot by knowing what you're doing. Because one of the things with an out-of-the-box theme is they don't know what you're building with it. They give you everything. And especially visual composer. Visual composer has a lot of JavaScript dependencies. That's where you get 115 requirements or downloaded files, because no matter whether or not you're using a plugin on the page, it's loading the JavaScript. With Advanced Custom Fields, I can create my own blocks and I know what JavaScript is going to be needed on that page and only load that JavaScript. So basically it comes down to building yourself a well-tailored suit. So let's go a little deeper into the payload size. So 2.5 megabytes of content kind of breaks out this way in what's being served. The custom wasn't much different, actually. Like in terms of ratios, but the size is a lot different. And so as I was building the site, I noticed that it uses only three column types, four column types, like a full width, a six column grid, and then a five and a seven. So why am I loading all the whole bootstrap grid? I will just use a mixing, create those three column types. It's now only have three different designs, right? And then I just create those options in Advanced Custom Fields. I want an even split. I want a 60, you know, 70. It's a golden ratio split with a bigger on the left and a golden ratio split with a bigger on the right. I also optimized a little bit of size of the CSS because I used a flex base grid and it's using older version of bootstrap, which is a float base grid. So you do save a little bit by going down a flex box. And then the JavaScript weight, once again, they had 550 kilobytes of JavaScript by 230. And this is unminified. Or sorry, that's a minified thing. And that's, you know, I wasn't even trying. Like I said, this isn't a weekend. Like, you know, like this isn't even trying hard to make it smaller. And once again, they don't know what you're building, so they give you everything in a theme. I know what I'm building. I only pulled the JavaScript libraries I need. I run through the template in Advanced Custom Fields. I say, oh, well, you're not using that block, so I won't start with that JavaScript. You can even do it if you wanted to with the CSS. You could totally componentize it and just say, I'm only learning these CSS files. Had a little bit of a larger HTML weight in my version. Not much was like 3K. But image size really changed. It had 1.6 megs of image versus 609 kilobytes of images. So because once again, I know what the max column width I have set to, I can make sure I'm never serving an image bigger than that. So when an image is being dumped into a full page width, I know, OK, well, I'll go 1,600 pixels and I'll be the maximum size I'll serve. 2 column 1, well, I know the maximum width for a column is never more than 800 pixels. So never serving an image more than 800 pixels. Same thing with only those three column in there. I know it's never going to be bigger than this, so I set my maximum width. And then if you want to get really complicated, you do responsive images. So on mobile, I'm serving even smaller images because I know it's never going to be bigger than a certain thing. And a lot of themes I find, even to this day, don't use responsive images. And then now the payload complexity issue. So because you're loading a lot more JavaScript and you're loading a lot more CSS, it's taking a lot of time longer to render your pages. When I did my CSS audit, that's the difference in the amount of rules between the out-of-the-box theme and my theme. So the time to render a page is drastically different. You're serving 11,000 rules that are all being ignored. I don't need 506. That's a crazy reduction in complexity. So how does this affect the bottom line? How does this affect the bottom line? As a website owner, as a business owner, how does this speed affect your bottom line? So go back to our Google Lighthouse score, right? 19.2 versus 6.2. Google has a tool called Think With Google. In it, they have a mobile performance calculator or a mobile cost impact calculator. It'll be basically putting your site load speed at mobile and you put in what your average visitors a month are for mobile, what your average conversion rate is, and what the average deal size is. And I'll tell you how much money you'll gain a year by speeding up your site. It's got a slide where you can say, if I speed my site up to this site, I know how much money I'm going to get. So I used our values from the experiment. So I took these from these values from a client. So they're getting 5,500 mobile visits a month. Their average deal size is $5,000. And their average conversion rate on mobile is 0.1%. That's the amount of extra money they get by speeding up their site from 19.2 seconds on mobile to 6.2 seconds. That more than covers the cost of the extra development time to develop a custom theme. But you think, OK, well, I'm not a big company. That's not my average deal size. I'm doing e-commerce, all right? So here's another kind of average site. You're doing, say, 1,500 visits a month. The average deal size is $150. And your conversion rate is a little high, because it's a lower price point, right? You're still making $6,000 extra by speeding up your site by that percentage. So that's one of the best business cases for it, depending on your, yeah, all right. But there's other effects, right? SEO. So page speed, once again, it's an important ranking factor. It's becoming more important next month. And one of the better ranking factors is time to first byte. Less complex site, you're going to have a faster time to first byte. So in any SEO strategy you implement, the first thing it will do is they will audit your site. They'll audit your speed, and they'll audit your text to code ratio. Once again, with a smaller payload, your text to code ratio is better. The out-of-the-box theme comes in at 5% text to code. So it's mostly code. The custom theme came in about 20%. So you have a much better code to text ratio. It's something an SEO expert's going to look at when they're looking at your site to do SEO. User experience, so once again, faster site, happier users, better conversions. And then you get, this is like the actual out-of-lighthouse. So this shows your perceptual speed index of the two sites. That's how fast it feels. And if you look at the difference, the out-of-the-box theme feels twice as fast. You get your interactive much faster before you are on as opposed to the box. So once again, faster response, happier, your perceptual speed index is 8 versus 79. You can't compete. Accessibility is another issue, which previous talk was talking about. And a lot of the themes on ThemeForce right now aren't accessible. Color contrast is usually wrong, and sometimes you can't fix certain color contrast issues. I find a lot of times I'll implement a custom or out-of-the-box theme, and I'm fighting it. I've got to use important tags everywhere. And as a front-end developer, no one wants to use important. But where's this one they've already used before? That's it, right? And then after, yeah. And part of that comes down to you because they're using Bootstrap out-of-the-box, right? And Bootstrap 4 is much better. Bootstrap 3 was a very hard, and Bootstrap 3 was even worse, for having to override styles to customize. So in accessibility, the out-of-the-box theme scored an 83 out of, in Google, mine scored 100. Because once again, I build from accessible from the ground up whenever I can. And a lot of that comes down just the way the icons are rendered because they'll use icon fonts or whatever, or I replace those icons with SVGs and inline titles and so that makes it a responsive color choice once again. Like I said, I darken the brown because it didn't meet contrast ratios. And then there's a long-term security and maintenance benefit. When you buy these out-of-the-box themes, they have a lot of plugins. And you're basically putting your long-term maintenance in the theme developer's hands. Because so you buy a theme with Visual Composer in it. WordPress gets updated. This is actually an issue I'm going through with the site client right now is WordPress gets updated. It breaks the older versions of Visual Composer. You update the new version of Visual Composer because you have a license. It breaks the theme. So you can't update this client's site without rebuilding, say, 100 pages. And they don't actually break the rules. Yeah, exactly. And then there's other plugin dependency. Like you are now dependent on other developers to make sure you can update your site. Because a lot of them, they're not as critical as I would be in terms of what plugins they use by default. So once again, like core updates or plugin updates, it breaks the site. And you've got to roll back. And that means you're using an outdated version of WordPress Core or using an outdated version of a plugin just to maintain the site to be usable. And while with a custom theme, like a good developer you have a relationship with, you keep them on maintenance contracts. And they'll make sure it's moving forward and keeping up to date. And a lot of times with a custom theme, you're not doing as many crazy things. So a lot of those plugins, a lot of those security holes are coming from interface things that they're doing. But if you're using my ACF, it keeps up to date. It doesn't break. It's fairly good for backwards compatibility. So if you're using ACF to build your sliders or other things like that, you can usually be fairly safe on the ACF. It won't break it. And so once you build all of them together, it's, oops. It went out of my last slide. That's OK. It's 100% counterweight-approved. So I thought I'd just open up to questions. Because I know this is kind of a dense, crazy topic. I can do with that foundation probably pretty quickly as well. I use foundation more in terms, because I just want to get it done in a weekend. I haven't retried it. Like I know that, because even with foundation, I didn't use the mixins. So I didn't use straight foundation. I just like, OK, I need these three column widths. I will just create custom classes with those three column widths. So I reduce the size a lot there. But yeah, totally you could make it a little even a lot smaller if you went with. I know that two seconds is considered a very long time for a mainframe to respond. And now we accept two seconds as an acceptable time for a website. Yes. Yes. Two seconds is the bare minimum. You sort of get impatient. The line of God is the norm of time. Yeah. But your average page size right now is about two megabytes. And you saw mine was 930k. And it looked exactly the same. There's people with the same size. Yeah. Anybody else? It's more history. Like I said, older versions of Bootstrap, you had to do a lot more important tags and things to override default styling. And so I just started using foundation because it needed less of it. So I was doing a lot less overriding with older version of foundation than I was with older versions of Bootstrap. So I'm just more comfortable using now foundation than Bootstrap. But both, like I said, I've checked performance stats on both and size stats. And they're within a couple of k of each other and a couple of milliseconds of each other. Their performance is pretty close. Most of my clients now are on maintenance contracts. So we're maintaining their site for them. But the beauty of advanced custom fields is that they can't do custom layouts. And realistically, most of the time, once you've sat with a client and worked through their content, they're only using three or four variations on a block. So even with using something like Composer, you can give them those pre-made blocks and give them shortcuts anyway. But with advanced custom fields, I'm like, pick one of these five blocks and use it. And then they don't have as much option to balance it. Yeah, because it's not their job to design the site, right? I will give them, here's the best way it's going to look. Use these. There's a lot of sites out there right now. Oh, sorry. So he was asking if there are any recommendations for sites or things to help develop themes. I also like, I've been promoting a lot, is Canada Learning Code. So Ladies Learning Code, if you just need a good introduction, basic introduction to theme development or even writing HTML, CSS, their introduction to HTML, CSS, and their introduction to theme development is a really good starting point. Canada Learning Code, it used to be the Ladies Learning Code program. And it's one of the best, in terms of the way they teach, I've taught a couple of their courses. I've mentored a bunch as well. And I find it's one of the best beginner intro courses to anything. And I tell most of my clients, if you're going to be managing a website, take their intro to HTML and CSS, because it'll at least give you enough knowledge and enough confidence that you can at least talk about it intelligently if you do need help. And their WordPress theme one is actually very good as well. But on that, it's CSS tricks, Lidia.com. They're all really good. Linda, that's what it is, yeah. So anything else? Yeah. What are you doing here in the site from the ground up? Are you routing it through WordPress? Are you using WordPress whatsoever? My usual, well, yeah. So am I building the site from the ground up using WordPress or am I writing it through a press? My usual workflow is I start with a content map and a content outline from the client. I build them wireframes based on that. In HTML, I do in browser. I then style it and give them static HTML mockups. So it's responsive the whole way. And then I turn it into a theme at the last step. And that's kind of a fairly standard way, I think, of working for most developers. And you just kind of keep building on it so that way you have client input at all stages and you're not kind of here's something and they're like, oh, we don't like that at all. So, yeah. So there, can you still make use of the WordPress? Can you still make use of WordPress plugins? Yes. So with that theme, she was asking if we can use a regular WordPress ecosystem. And yeah, with that, normal short code stuff works. Everything works with advanced custom fields. You can dump any content in. There's usually a plugin you add to help with search for it. There's a advanced custom field search plugin that helps just to make sure your full text search is working. But yeah, you can copy paste any short code in and install any plugin and it'll work. That's the other benefit of it. Go ahead. What do I use to check my themes are up to WordPress standards? For me, I just I've been doing it long enough that I don't do too much checking anymore. And like I said, I use Timber as a base. And what Timber does is gives you a templating language. So you're using mustache or twig, yeah, as your basis. So it's just feeding your variables into a twig template parser. So that way, once again, your visuals are separated from your business data. And the other thing I like about Timber is that I never have to write a menu walker because they have them built in. Yeah. Yeah. All I've done for the last 10 years is I've got piles of stuff, and it's good, and it's raining. But you know what? And I thought, OK, maybe I'll get a theme for it. A lot of themes, you know, everybody says that's the one that we need. But now that I'm listening to this, I'm thinking, you know what? If I do that, maybe I'll have to backtrack a little while and start again and do whatever. Because I will get wiser. And I'm going to get involved in this. But maybe I should be talking to someone like yourself or another person who just provides this service and then just slowly work from there as opposed to starting with a theme like it's already with, say, an old box. What do you suggest to a guy like me who has content and who's going to get re-involved? And I think fairly largely, but I think it's a, you know, what do I start with? So the question is, as a content developer, someone already has a large content repository and they want to update their site, should they buy another box theme and just re-skin it, put the lipstick on the pig, or should they talk to a developer? One thing I can tell you is a lot of the cost in developing a new theme is the discovery portion. So it's figuring out what the client likes and how the content works. Like I said, I put that theme together in 16 hours. It's because I knew what the content was going to look like. And like I didn't have to do all the discovery kind of thing. Okay, do I want red buttons or do I want blue button? Like all that back and forth you do with a client, that little, to figure out what they like and what they don't like. And one of my recommendations is to clients when we're doing rebuilds and they've already had another box theme. Like, okay, if you're happy with this theme, we will rebuild it as a custom theme, updating it slightly, saying, okay, well, we'll use this as a starting point. We'll update to new coding standards. We'll update the styling to be a little more modern, but we won't change too much. Because like, you don't want to totally change your site. You don't have a site. Okay, yeah, the best thing is talk to a developer, see what they'll charge you. Because like the price difference is significant, right? Like, building a site from an out-of-box theme and finding the size. You're looking at two to five grand is what I would charge using out-of-box theme. But as soon as you go to custom, you're looking at 10, right? Because there's a lot more back and forth in the discovery section, right? Trying to figure out what we need the site to look like, how the content needs to lay out that there's a lot more back and forth there. So, yeah. But that's why I bring up the testing tool. Because if you know how much money you're making off it, you look at that, you can say, okay, this is gonna save me or cost me this much in revenue. So, you know, you can make a decision, right? Right, and for most people, I'm like, do the out-of-box theme right now. Start somewhere. Because it's better to start somewhere with something slow than it is to not do anything at all and then just move on when you can afford it. What theme is it? What theme is it? What theme is it? What do you do? Somehow you take water and you jump on something. But, yeah, and that's it. And a lot of times, that's what I'll do for a client is I'll just walk them through. I'm like, look, if you can't afford me, I'll happily, I'll take a couple hours. I'll look at your content. I will give you some suggestions. Because a lot of times I'll give a price to a client and they'll go, I can't afford that. And that's my cheap price. So, I'll go, okay, look, I will take an hour or two. I'll look at your content. I will give you a bunch of, one of these three themes will probably work for you. Six months later, they come back and they go, I can't get through. I don't have the time to deal with this. Right? Because it's what the, yeah. You're making money, I'm happy to start. No, but that's it. Is it like a lot of times, I'm like, I can give you themes to use and say use this theme, but like there's still a certain amount of design knowledge and tool familiarity need to actually be productive with it, right? Like, you can sit there, yeah. Yep. Yes. With it, yeah, number five. And I really don't know what's gonna happen when five comes out. Yeah, I don't know what's gonna happen with those things. Yeah, I really, I can't find any documentation on what their upgrade strategy is. So, that tells you one thing about Visual Composer right there. Like, I can't find any documentation. What is your plan for WordPress five with blocks? I haven't tested doing the blocks yet as a, like a speed test. As a developer and a designer, I'm looking forward to it just because moving to a component-based model is, where design is moving anyway, so it makes sense as a designer and developer to do a component-based graph QL thing. So, yep. One private couple of other things that these blocks, is the dual-multi-cation of this. I like MVC personally, that's my thing. I like to keep my code separate, so that's just me. In terms of, like I said, I like to do, yeah, I like Foundation. Use Webpack out of the box for its front-end build. Other than that, like I'll do stuff because I'm on a Mac, I'll use CodeKit sometimes just to let, just have a gooey for it. You know, most times I just develop and map and push it to a dev server. And right now, my big problem with WordPress is it needs a better migration process to migrate from dev to thing. And it needs draft, it needs draft changes because clients like, they wanna make a change to your page but they don't want it to be live yet. Once a page is published, it needs a staging, so. For just a speedy impact on WordPress, like, of course it's a separate request of a different server, but is there still advantage from doing that opposed to packaging that in with your CD? With the CDN, you're gonna get, you might, oh, sorry, we're asking if using a CDN when using a framework is beneficial, it can help. But I find with HTTP2, a lot of that paralyzing of requests it negates that CDN ability, like that benefit you used to get other than you're getting the latency benefit, which, because you're serving from a closer server. But I find even with jQuery loading from a CDN, I'm like, I'm surprised at how often it's not cached on a user's browser. So I just, like I said, I just run all my servers with an SSL certificate, HTTP2, and paralyze those requests. I find that's usually enough to, you know, compensate for any speed difference. So, anyone else? Back to the, on reducing the amount of, let's say, CSS, JavaScript, do you know of any good cross-reference tools that will tell me what CSS is used for this? There are a couple of tools, they'll scan your site and find your unused CSS that you can run it through. Try and remember what they're called off top of my head. And they'll, like, but they will, there are a couple of tools that will run your JavaScript and CSS. And you just, there's even a couple of webpack and gulp-based ones where you can run it from the command line and it'll run through your templates and your JavaScript and look for CSS, like, for classes and see if they're used or not. Yeah, I can't think of one off top, I can't think of a tool off top of my head that'll, like, look for even frequency of use. Yeah, yeah, and there's three instances or four instances or whatever, so you can see if you should refactor and, yeah, I can't think of anything else on my head, but, good. So the question is, if you have a client who already has an out-of-the-box theme and they want you to mitigate any speed issues, would I tell them to start from scratch or would I actually try to do something? I would try to do something, because there are things you can do, like, because a lot of times these sites won't be running on a site with an SSL certificate and HTTP too. So I'm like, okay, well, let's first step, let's upgrade your server to Apache 2, put an SSL certificate because what that'll do is with, I don't know if you're familiar with HTTP 2, it will paralyze requests. So in a traditional HTTP one model, all your requests happen one after the other. Under HTTP 2, anything from the same domain can be served in parallel. So that means instead of waiting for the CSS to fully download for you to let down the JavaScript, it's downloading in parallel and that does a lot. A lot of times they won't even be running a cache. So I'll run a caching plugin and just, you know, WP cache runs a static version. That does a lot. There's not a lot, like, if you already have visual composers, not a lot you can do to reduce its JavaScript footprint other than combine and minify, like run a plugin to combine and minify, which, you know, it also helps. Like, there's stuff you can always do to speed it up, but, well, HTTP 2 will only run, the problem is, yes, HTTP 2 will only run via secure connection. So you need the SSL certificate to run Apache 2.4. Mine was ACFS. Yeah, yeah, because I've upgraded all my servers to run on, use Let's Encrypt and just run a free SSL certificate at least. It never works well, yeah. Like, MAP does not even, like, you always get a warning that it's not secure even though you're running an SSL certificate and self-signed and, yeah, go ahead. So do I use a separate program to minify my images because I got the size? There are a couple of decent plugins that forward press that, like, Image Optimum for one. Is it Image Optimum? There are a couple, Smush It will do your image compression, but I find a lot of it is uploading properly compressed images to begin with. So I do a lot of education with my clients on how to save images out of Photoshop for the web. And just, because it's one of those things, with the plugin, it's just gonna apply bulk compression, which, you know, every image is gonna be different and, like, ahead of Image, you may want less compression because you want to look better, right? So I always kind of do a lot of education and training with the client saying, okay, when you save it, use a save for web, watch Slider and see where it breaks down and see if you're happy with it. Because, like, if you have a client who's a photographer, they don't want all their things artifact-y. So they're gonna be a little bit less tolerant of compression. Yes, yeah. Sorry, they're in there, so would you? Yeah, I think there are a couple of plugins that will respond, sorry, asking if there's an easy way to deal with themes that aren't using a responsive image. And I think there's a couple of plugins that will mitigate that. Yeah, but it still, it tends to usually deal only with what's in the content field. And so depending on how the short code processes that image, it doesn't do it. And that's, so you're kind of out of luck. You'll create a zip file. Yeah. Sorry, which one? PageSpeed Insights? Yeah. When you run that, it'll give you all your report. Yes. And it'll give you all your things. Yeah, PageSpeed Insights will give you a zip file of your images compressed. But like I said, I tend to recommend a much more hands-on approach. Only because, like I said, I deal with a lot of clients where the image is really important. Like, I have clients who run art galleries and things like that. So the image quality is important. So anything that does like a bulk. Like compression doesn't work. Yeah, but yeah, like if quality isn't as big an issue, where you can get away with slightly lower quality images, anything like a small shirt or using some of the bulkly downloads images and optimizing for you is good to use. So, but it's on a case-by-case basis. So, okay, any other questions? So, asking how I would optimize an image? Generally, I will save for screens out of Photoshop. And then I will adjust the slider and look at the quality difference because it'll give you the side-by-side of, here's the original image, here is the optimized image. And as you adjust the slider, you'll see how much artifacts you get. And then, like other, there's the basic thing, it's just making sure you save the JPEG as progressive. Helps. Things like that help. There's a couple of tools for the Mac. There's an image-optim plugin, which you can just drag and drop your images in, and it'll do some basic compression to pings and JPEGs. It's called image-optim. I find it's really useful and it doesn't add too much artifacting. So, ones like that help. I just don't know if there's a PC equivalent for it. Which resize or crop tool? Asking if I resize and crop in the media library if I do it. I do it all from my desktop. Because of that way I know exactly what I'm getting. Like I don't trust the, I don't trust, you know. Theme image users providing. Yeah. Are you still allowing them to do that? Well, I don't stop them from it. I don't stop users from doing it the way they want. I will show them, here's what I think is the best way for you to do it. And like, if they're like a startup or like they're not image dependent. I will show them, yeah, like just use the, you just use the in browser tools and use these tools because I know they're not gonna notice the difference. But when I'm talking to a client as a photographer or an art gallery, I know that the quality images is paramount. So I'm like, okay, here, use this tool, try to get your image size to like try to get your head images down to say 150K or what, like I try to give them even size, like, you know, play by year, like look at the image and look at the quality image but try to hit these size targets. Just to get, so they have a, at least the baseline. Cause, yep, that's time, I guess. I can, yeah, yeah, yeah. But also like a white image versus a, a image with a lot of black is gonna compress differently because white is 255, 255, 255 it's still, it's a bigger number than zero comma, zero comma, zero and you'll see a different compression ratio between an image that has a lot of black and an image that has a lot of white. So, yeah, the color value actually matters. So if, I'm happy to talk after I'm getting, I'm getting the, the, the old.