 Hello again. Remkus is a heavyweight in the WordPress scene. He runs an agency in the Netherlands. He was co-organiser of different word camps and meetups and he's a weight lifter, physical and figuratively and as a WordPress veteran he knows how to tame WordPress and WooCommerce and he also has a newsletter which is not your default news but very opinionated, interesting and worth to subscribe to newsletter. So let's dive in and do WooCommerce but faster. I may need to do the mic a little louder. Is this better? Can everybody hear me well? Thank you. You had me there at... What was it? Heavyweight? I guess I am. The talk of today is WooCommerce but faster. Now before I start explaining what I mean with that besides the obvious thing I kind of would like to get a feel of who's in the room. So can I get a show of hands for people who own a WooCommerce store? Okay there's a few of you who works with WooCommerce a lot. That's a lot more of you who develops inside of WooCommerce and builds custom plugins and all that. Okay out of curiosity if you do nothing with WooCommerce... Okay there's a few. Okay all right. So my presentation is really very very simple. Here's how you make WooCommerce fast. You install a WordPress caching plugin. You turn it on and you're done. That's it. That was it. Thank you. I'm sorry. I thought I'd try my version of April's Fools. It's not my thing and I make terrible jokes so but the the funny thing is for a lot of people this is the truth. A lot of people think by making WordPress slash WooCommerce fast all you have to do is turn on your caching plugin provided you're on decent hosting and you're done. That's it. You can just sit back relax and start seeing the money pour in. Unfortunately that is based on some misconceptions and this is something that most people don't really truly understand and this is what I'm going to explain today. Like what does make a site faster and when can we actually call it faster because caching is not making fast. That's the first thing that we need to make really clear and if you're already at the tip of your seat going like oh I have questions now I'm I'm so not I don't believe this this I have my own opinion and I have my own experience. That's wonderful we have question and answer at the end of this so write them down as we go along. So caching doesn't make a site fast. Here's another one. A large database won't make a site slow. Who here has read over the years the many WordPress tutorials where it said if you have a large database if you have post revisions you need to turn that off or limit it to three or something like that. Who has seen those tutorials? Yeah that's a that's a large percentage of you. So here's me saying that is false. Now are there reasons why you would want to have a slim down database? Sure but performance isn't one of them. I'll explain why later. Here's another great example of what I see happen a lot in terms of here's what you need to do and be sure to do this because if you have a memory limit make sure it's as high as possible because that'll make your site faster. Well spoiler alert it does not. Will it help in certain cases if code is not written correctly? Sure but you can kind of see where this is going. So memory limit does not affect speed and turning cash fragment off is probably the thing I see most happen especially when it comes to WooCommerce. Let's make WooCommerce faster. You know what we do? We turn off cash fragment. Does who here understands what crash fragments are? Not a lot. Okay so inside of WooCommerce there's a few functions especially around the cart experience that are written in a way that full page reload doesn't need to happen but maybe just a small section and that actually makes WooCommerce work smarter I would say. If you're on really bad hosting though you will see that that actually makes your site slower. Does that mean that cash fragment is bad? No it means you're on really bad hosting and that's something you need to fix. I hear myself a little bit. Is that me or does it is? Oh it's been the whole day. I'll try this. So how many of you have heard or seen these things and work accordingly currently? Don't be hesitant all the time. Yeah so this is quite common. This is mostly around not understanding the base principles and this is not me coming off of my high horse saying you don't understand what's going on. This is me saying we've been fed the wrong type of information for a very very long period of time in the tutorials that we find in the presentations we've seen and there is really no limit in terms of what is possible but you most likely need to start thinking in a little bit different way than you currently know what you've currently been doing. So there are some base principles you need to invest some time in to truly understand what it means to make WooCommerce faster. So you need to understand the layers. There's a way of working I don't know why they all went like this number two three and four they're supposed to go gently but I guess I'm not a gently person. I'm just fast there you go. The way of working so the things that you do how you do it how you start a project what tools you're using how you're measuring the success of your end result the understanding that there's a place and time for everything you do with your WooCommerce site and that boils down into having a foundation. So it's a little bit more than a template but you kind of get the idea that if you have a foundation of something that's been tested and proven for you and your clients then you can build off of that and move to a better version off of that in a continuous fashion. So that is essentially these are the four base principles it's all starts here. So let's start with the first one understand the layers. This is a really bad echo. Well possible try yeah I'm not gonna hold that. So your server stack your PHP and your database are the largest components to making your site fast. There is no other way around it. Does that mean you can discard HTML CSS JavaScript and all your other assets? Absolutely not. But the emphasis should be on the first portion right. So does this mean you then have to I have a WooCommerce store I love using WooCommerce but does that then mean you have to invest a lot of time into understanding server configurations? No it shouldn't. PHP no same thing and database yeah if you're lucky you never have to touch it that's fine. But it does mean you understand that these layers determine what is actually happening in terms of performance for your WooCommerce site. So HTML CSS JavaScript and assets if you've ever done any type of optimization in the browser you know what that is right. That's either Google Lighthouse or PageSpeed or any of those metrics. Not all of them are good. Not all of them are really telling you what you're supposed to be using or what the data says because it depends on where you are what you do what you're testing everything matters but that's relatively straightforward in optimizing what you are what I would say most of us are not built who's building servers for fun to try and optimize and do that and who's actually using them in production. Just Joe and Florence. So that's a relatively small crowd is what I'm trying to say right. I've built VPS's and I've had a lot of fun doing it I do not care to do that anymore. There's people much much smarter than me and way more dedicated and hardcore in the optimizing a server. It's a different it's a different trade and I'm grateful for having some experience in it but it's not something I want to fill my day with. So where do I focus? I focus on HTML and all the rest. So what does that mean for the first portion? That means I look at hosting companies from a different perspective. I don't necessarily look at them and go what is your manage this look like what is your response time here? What is it? It's also important but my main thing that I look for is a proven test where you can actually look into how it's performing under stress, under load, under a lot of whatever it is you're measuring and for that there are ways that you can do this yourself but it's much easier to look at a service that does this for you and that's called review signal. Review signal if you've not heard of it before. It is a yearly comparison of all not all existing WordPress hosting but it's hosting that has said you know I'm happy for you to test me and honestly test me all the ways you can possibly think of and if you then look at who surfaces on top that is the prime tier you should be looking at in terms of any time you have a site that needs performant hosting. Right so that means that a lot of your budget or cheapish type hosting and that's roughly in the range from five euros to 30 euros I generally avoid for the simple reason is not that I like to pay more but I know what I'm getting if I pay more. So that is one way to start and that's different than I like working with this host because X reason Y reason whatever we all have our reasons there are certain hosts I love there's certain hosts like I'm okay with working with it and sometimes the performance is better on the ones I am okay working with it's a small sacrifice if it means I don't have to worry about the next burst of traffic. So the second principle is your way of working so understanding your stack so that means you have spent some time investigating what your stack looked like and it's not just your PHP layer it's not just your database layer it's not that's your server but it's whatever you're using inside of WordPress as well everything has an impact so a common misconception is that if you keep on adding plugins to WordPress it'll become slow also not technically true it depends what that particular plugin does and if you're approaching about a hundred there's a fair chance your site is becoming slower but it's not a given I manage sites that have over a hundred plugins and it's fast like proper fast even under stress even on the load it just depends on what you're doing in those plugins so understanding your stack lightweight anybody get this reference by the way am I alone in this okay nice nice nice I'm a big fan of Ronnie Coleman that this means that whatever you're introducing in your stack needs to be lightweight first this is a big one because we like the fancy plugins that solve a lot of stuff for us but they read I need to stay away from those okay oh is that okay so the the the lost my entire train of thought so lightweight means you look at plugins mostly because that's what you're introducing to your stack and you're testing what it does before and what it does after and this is not a difficult thing you can do this on your own so what I'm not doing today is getting in high specificity on what you need to do exactly because that's too much what I'm getting at is there's a train of thought that you need to follow whenever you're doing something that has a performance requirement that's hard you can't not think about it so lightweight means your functions your plugins will do mostly one or two things that's it when you're introducing something larger you need to be sure that whoever introduces that larger thing has a performance mind has been thinking of how the code has been written is it actually done in a way that okay if I keep doing this over a million page requests is that performance going to be same or is it going to add up right so that's simple things as validation checks if the plug-in needs to be loaded at all so check out early exit early things like that impact testing this is literally testing what happens before I turn the plug-in on what happens after and there's even a difference between when I turn it on when I configure it and when I think I'm done right that means you need to do a little bit more than find the plug-in install it activate it that's the first step you then start measuring before once you're done activating once you're done configuring so impact testing needs to happen that is a way of working you need to make yourself familiar with automating is as simple as that whatever you can automate automate because if there's stuff that you don't have to think about anymore it'll be done and you'll see the results anyway so what is the thing you can automate if you install a plug-in on your either on your local site or on your production site there are ways you can automatically get services look at it and give you feedback on what the impact is it's a very simple very lightweight version but it tells you something so the third principle there is a place and a time I guess that's probably life as well but in terms of WooCommerce in terms of what you're doing inside of WordPress there is a lot of stuff that's happening that is not supposed to be in WordPress my first thing to mention here is security so security plugins and I know there's a whole bunch of them security plugins do not belong inside WordPress that is a black and white line for me I'll explain later exactly why caching is the same thing a plug-in inside of WordPress should not be caching as caching for WordPress like HTML caching they simply don't belong there and I'll explain you in the very simple example why that is every single page load on your WooCommerce site so when somebody has not put something in their cart yet you are you are able to fully cache the entire experience what most folks don't realize is that once they add something to cart you invalidate cash right you can't work with a cached WooCommerce site because you end up if we were to do that you would end up with somebody else's cart right there's more people on the site at the same time as you are or maybe not but it's been an hour and you're within that hour and voila and if you've ever had a badly configured WooCommerce cached site you've seen this I've had it once didn't make me happy so caching doesn't belong there why because every single thing that is happening inside of WooCommerce needs to go through the normal loading sequence so what does it what does that mean a page request by any one of you visiting a site that is powered by WordPress slash WooCommerce means it's loading the entirety of WordPress the entirety of all the plugins the entirety of the theme and all the functions that go with it then it needs to process the functions inside the plugins and I'm not this is not the exact sequence but just to give you an idea of how that works then the function needs to execute and then it needs to produce whatever is doing so if you're a caching plugin you need to do all of that so WordPress is still working your server still working other things loading everything is happening and then it needs to decide if you can it can serve this page in HTML but WordPress is already being loaded so I'll this is to the extreme that you can have a fully cached WordPress site being brought down because it's serving PHP powered HTML caching does that make sense Milan says yes the dobro so the same thing happens for security like you need to hold the whole stack before the security plugin can actually determine whether this is a legit visitor whether it should take any actions if it needs to take action it'll need to do some more so you can imagine that as you keep adding different stuff on that site more traffic maybe you sent out a newsletter burst 15,000 people and oh crap my site goes down I don't know why I'm cached I'm doing okay here aren't I no but you're doing so much you shouldn't be doing in there that invalidates caching all that and here we are so I think this is a hot take I think most people will reluctantly kind of disagree with me until they actually start measuring and when you are actually measuring you will slowly but surely find yourself on my side of the table it's just data that will tell you so your foundation is essentially the culmination of everything that you found to be working to be working efficiently to working fast and it is your template of stuff that you work with or don't work with so there's plugins I'll use that I am not happy about but given the yeah they're only doing this little thing over here relatively lightweight I can I can live with this because if the traffic explodes it's still doing that little thing in a little corner it's fine but if there's a plug-in doing everything and I add load this is not ending up in my foundation stack right this does not make sense for me to build my business on this is not sensible for me to say to somebody having a WooCommerce store hey you know what this is nice and easy it's great go ahead and use that because it'll solve all your problems so if a client asks me can I add this plug-in my answer will be yes comma but no that is my default answer and I'll just wait to see what they'll say but I really need this functionality I really want this I really need that great but let me see what the options are here and what are the consequences right if it if it is introducing stuff that I don't want it does not go into my foundation and I'm so I have clients who have like extreme high maintenance high volatility high traffic sites I can't just go and install whatever they like and they asked me nonetheless and they're making really good money with these sites and they'll ask me the same questions as well so this is this is not me saying I'm better or that but it's more of a thing of I understand this layer they're really good at their business and you hire me to do that part and this is my feedback so work with that this is what I include hosting your base theme fast plugins optimization where you do what all of that so when it is time to build your actual site how many of you who are building sites are using version control nice are we all using github or Bitbucket or anything like that yeah awesome so what the great thing about hosted version controllers which is git and then services like github and Bitbucket is that you have an opportunity to hook into whenever you're doing a deployment it's called continuous delivery or innovation or there's there's different ways of explaining the same thing but it's essentially about if I push code to the server new plugin update or or anything I want to do an automated test of what the impact of that is so this is something you need to have in there because I've seen I I've been called in the meeting like yeah but he just introduced or they just introduced a new plugin and now it's sites not working anymore well was that done any testing yeah we tested it before we deployed but did you actually test the impact and then it becomes a different conversation so testing is development if you're not including that in your current way of producing a site then this is the moment you start thinking okay what can I do to integrate any version of testing before I actually move on to the next so this is what you need to test at bare minimum uncached performance that means you're not testing the caching of your site that makes zero sense you want to test uncached you test checkout after each little change that you introduce on your site you will not be the first one to have a change move to production and then 48 hours later your client tells you I'm not seeing any money coming in anymore what's going on here and you're going like yeah but 48 hours that must be the client side because my deployment was done 48 hours ago can't be that this is why you test so checkout needs to be tested and especially check out on mobile mobile if you're not aware your phones are caching harder than your desktop machines are because caching not only happens inside your phone it happens at the carrier level it happens at proxies the carrier level uses depending on who you're using it there's way more involved and combine that with generally lower speeds on your phones you have something that is a high value thing to test because why high value do we know what the percentages of mobile versus desktop purchases are in general sorry 70 30 any others 80 80 80 yeah so it roughly depends a little bit on the the market you're in but there is there's known examples of almost 95 percent and if your client is one of those obviously you will know because you're doing hopefully some version of analytics that will tell you this but if you don't know and you just deploy and you make everything slower and fields and complicate it's not gonna help and for the record this is why Shopify is winning on a lot of people converting them in because they have that taken care of you don't need to think about having an optimized cart an optimized cart for mobile Shopify takes care of you for that so this is something we need to do extra when we're talking WooCommerce and what is that extra start with testing it's very simple so again testing is developing if you're testing test all the pages not just the product but the checkout and the shop pages you will not be the first person to only test the front page or maybe the shop page no you test them all because they all work together and you need to test the whole flow so this is generally so far me saying you probably need a different mindset than what you were doing and I'm not saying you didn't have the right mindset but I am suggesting that maybe there's some few things you're not currently using in how you're developing your WooCommerce sites now obviously most of this also works for WordPress in general but WooCommerce is finicky there's a lot more going on it's a complex thing you can't just treat it the same way you would treat WordPress because you have logged in people and you have commercial value with what those logged in people do so who knows what the edge is beside the band member from YouTube besides I you know what somebody said browser I don't that's not even in my world but that's a good point besides besides the guitar player from YouTube and that browser from those who we don't speak about this who knows what the edge means so this is too many sorry too few hands this is three people I see do I see that correctly one two three yeah four four people okay so the edge is essentially a term that has been introduced at the time Cloudflare became really really popular the they I think they coined it or somewhere around there but it essentially means anything you can do with your site before your actual server needs to do anything the the example we all know is a cdm right that is configured at dns level so traffic goes through your dns level so server and it is then controlled where it's get it its assets that's the one you all know what cloudflare but there are the players my favorite is cloudflare so I'm just going to stick with the word cloudflare for now but do your due diligence in terms of looking what is working for you but cloudflare introduces a whole layer of stuff it's doing on the fly meaning literally as your traffic is entering the stream to your server it has an array of stuff it can do one of the things I love that it's doing there is caching one of the things I love that they're doing over there is a web application firewall security one of the things I love that they're doing over there is image optimization on the fly um there's some folks from human made they built something in php is it still do you still use it tacky on is it written in node okay so that's something that's happening on server level but it's happening before it hits WordPress correct so cloudflare offers this on the large scale for anybody willing to shell out $20 a month or 25 it's as of today it's 25 now this is money this is real money and it costs you something but the level of optimizations that it provides just by having you move that off the server in front of the site means you get a whole array of extra sweets and candy and stuff that is just absolutely delicious because it makes your server do more what it's supposed to do it makes your WordPress and WooCommerce site do more of what it's good at so offload where you can um let the server handle your cron is a very simple one but essentially WordPress uses a cron to activate certain things it needs to do cleanup publish posts all of that sort of stuff this is typically handled by WordPress but you're smarter uh by uh well listening to me right now I guess a little bit maybe there's a way to move the cron away from WordPress you can turn it off in WP config and you can then set it up on your server and your server is better at this faster and efficient and more efficient than WordPress is if you don't know how to do it ask your hosting company because they should know do it how to do it in fact they should be telling you to do this um this is on the database level so an index adding to the meta-value database column if this doesn't mean anything to you ask your hosting company to service you with this but adding an index to your meta-value database column will make your WooCommerce site faster and I've seen cases where you go damn that's a lot faster an index is nothing more than this is my huge database and I have this table here that I want to go quickly at but I can't because I have to scout through the whole thing your index is an indexation of this big thing so the traffic to it will be faster if there's a middle index layer telling you here's where it's at redis if you have heard the name redis before it's a smart thing to use but you have to be sure to use it when to use it it is not something you turn on but by default you'll use it when it's actually providing a benefit and when you're using it you have to use it with object cache pro because that makes sense object cache pro with redis is one of the smartest you can do for high database volume going back and forth from the browser to the database itself use responsive images I don't think I need to explain this this makes no sense to download a image of 3mb when you're actually only using 100kb how am I on time by the way we have time so even more tips offload search elastic algollia are the two names you should probably want to investigate in if you have so one of my clients has an 18 year old database of 13 posts a day for 18 years long you can imagine the size of that database doesn't make a whole lot of sense to actually use wordpress to search within that I think the database is about 60 gigabytes doesn't make a lot of sense you can use indexes and all that and it'll be faster wonderful but this is a good example of if you can offload that outside of wordpress and make it more efficient do it it'll make your site faster don't use large plugins for small tasks so a cf who knows a cf that's a really popular plugin a cf recently introduced custom post type creation when they did I replied on twitter like this makes zero sense to me for the simple reason is there is that's not something you want to have in your database if I need to load the whole wordpress thing and then your database and then inside that database is something telling me to load a custom post type I think we're in the wrong place doing the right thing so custom post type declaration happens on php level in the file you can use the a cf to generate it but please use the output code and place it in your site plugin it's just a smarter way of doing it so many more tips so wp plugin manager is an actual plugin that when turned on it's one of the rare plugins where I site by adding another plugin you're actually creating something better because what it'll allow you to do is you're loading only what you need to load on which page load of your site so you'll get to be very specific like who's not seen uh contact form seven or gravity forms load there all of their assets on the front page and you have no contact form there does that make sense it's kind of stupid yes um I don't know about the second one but see what you do with that um block what you can so if you're using a web application firewall I highly recommend cloud for no I don't have shares um no I'm not being paid to say this but it's comes from somebody who's been optimizing sites for eight nine years quite intensively it allows you to block traffic you don't need uh Yoast default from Yoast wrote an article I think about uh six months ago where he explained if in your robots text you're not saying uh and your site is not servicing russian or or or uh mandarin uh then it doesn't make a lot of sense for those search engines to index your site so why don't you just block them any traffic that you don't need keep it out all the small things help final steps and this is this is the tldr you have to put in effort to keep your WooCommerce site fast it is not something you set and forget I see too many very smart developers thinking it's a set and forget because they paid attention at the beginning they paid attention while building it and delivering it to the client and then it's like here you go a client on it on their own will add plugins we know this who's not ever seen that there you go so make sure you're offering some type of retainer not just to get money out of but to help the client understand that your line of business is thinking for the client helping them do the smarter thing and that means there's a lot of automated testing that's not going to cost you a lot but you can charge for you know it's it's okay to make money with it but don't don't make that the main argument the main argument is I'll keep your site fast I'll keep your site lean I'll keep your site conscience of what it's doing what its ecological footprint is everything everything counts I think that goes um automated testing these are three things I highly recommend you look into uh deployment arc user flow and speed guard the last one is the WordPress plugin that if you really want to go low effort you install this plugin it'll tell you once you've done an update whoa we're seeing like a two minute increase of loading time per page this is probably not the right plugin it'll tell you it uses an external pinging service that checks what's going on um any of these three depending on what your uh proficiency is is something to investigate into um and that's it that's that's essentially what I have to say um yeah thank you no questions no questions whatsoever Milan yeah so um in terms of hosting do you have any recommendations you usually make or a specific coaster you pick in general this is this is uh that you're not getting paid from I'm currently not being paid by any hosting company so we're good I did work at a hosting company for two and a half years uh and uh it is not a very well known hosting company but it is one that I would recommend but it comes with a budget so that if you have high demanding clients there is no other thing that I would recommend other than servo bolt s e r v e b o l t servo bolt having said that there are more options out there of course um um I think Kinsta in general is solid yeah um I say in general because um rocket net is a good one seravo it's also okay um w p engine in some cases works wonders um but it's it's a very loaded question because my answer truly is it depends yeah Ramcus thank you educational as always you opened up a lot of topics and I'm sure there's gonna be a lot of questions and thank you so much but what is the one thing that you would never do on a wordpress or wordpress slash book commerce website what is the one thing that you would say like oh hell no I thank you um I think the thing you want to avoid most is um I think the combination of the security and and the caching that I cannot stress that enough um w p rocket is a plugin that I really enjoy using what do I turn off inside w p rocket the caching do I have a way to do that inside the UI I don't so I have a function that literally deactivates the caching I'll take have the server take care of the caching in a smart way and then have w p rocket do all the front end optimization it's really good at that's the way of using something smart so caching is doing that and for security I highly recommend you look into the web application firewall of of cloud 3 because it offers so many extra stuff that you're just not aware of that's of its existence uh it'd be ashamed to not look into that anytime you're running a site that makes money simple as that thank you any other questions oh yeah okay yeah yeah yeah I think you need to come over here and at what stage or from what load you would recommend to use redis um I don't think load is the right word uh redis is something that you need to understand what redis does redis essentially has two functions it allows you to queue stuff and if you have jobs if you for instance if there's stuff you build in Laravel and you need to have it interact with WordPress on a regular basis it makes a lot of sense to use redis because you'll then use the queuing system of redis so then load is a nonsensical thing to add um if you have properly configured databases MariaDB highly optimized the boundary for when load becomes the thing for redis to be used is quite far away so server both for instance uh has known cases where their database interactions are eight times faster than normal and that's high so that means whenever you need to introduce redis it's quite late but the things to look for are let's say you have a site that has a lot of comments and there's a lot of interaction let's say there's a site that is high traffic in terms of uh bulk WooCommerce uh newsletter going out right so 15, 20, 50,000 people jumping on that site wanting to get that fastest deal using coupons is a great example that's a high traffic thing going in and out of the database that's more of the the territory where I would look at okay now redis makes sense and when you're adding that absolutely add WP object cache pro those two go together do not install redis without that one that makes zero sense because WordPress will need to be optimized for that new interaction and there are other plugins but this is by far the best I'm also not being paid to say that but hey till how you don't uh yeah um if you need to optimize a website like a e-commerce website what is the thing that you do you think is going to give more impact in the performance and which which performance the the actual fastness of the site yes and which other thing is you think the most common people do it but you think no don't waste time here because it doesn't give you thank you so one of the things I mentioned in the beginning was uh if you if you if you think you need to remove data from your database to make your site faster you're being lied to so that's the one thing that I would say if your host is telling you or strongly enforcing you to remove post revisions and clean up this and that on otherwise their site your site won't perform as it should that's a red flag for me I will move my client away from that hosting company and and for the record I have a list of yes and no types of hosting companies the thing that will have the biggest impact is it depends on two things so in general sites are either really well optimized on the front end or really well on the back end I rarely see the combination of the two at the same time so it depends on what you need to do on the front end and for that I would say WP rocket helps you a great deal it's a simple solution for a rather complex thing what it is doing but turn off caching if it's on the back end side of things it's mostly poorly written php and by poorly I mean if you have a file that is I don't know 2000 lines and everything everything from line 10 to 2000 is executing a function and you didn't check before line 10 if it should be running at all that's those things I see the most in terms of oh wow this could save a lot because it's doing that on every single page load for every single person but that's not uh that's the best answer I can give one last questions yeah so um I play around with a vps which is a far too dangerous tool for me to play around with um for me as well now and um now I wonder because you speak a lot about server side optimization yep and I'm just trying to get the definitions right because if you make changes to your hdxs file in order to to speed things up is that on the side of WordPress or is that on the server side that is server side okay I am of the opinion that you generally shouldn't be concerned with server optimization I think that is the domain of your hosting provider and I am also of the opinion that your hosting provider should be proactive towards you instead of you chasing am I doing this right yeah so they're they're in total environment should be fully optimized for whatever you're adding to it and maybe they have an integrations plugin to activate a few things fine do that but that's that's that's how I look at it so I um I know my way around the command terminal I use it uh uh in a great many ways and deals and versions but I don't want to do that anymore because it's not my domain yeah I get that now yeah it is too much going on do I know how to install a web application firewall sure can I configure it fine do I want that responsibility no and it's as simple as that because the time that I don't have to spend there I can spend on optimizing and fine tuning and trying to get the lighthouse metrics on mobile as close to 100 as possible yeah yeah so it's just a matter of where do I put my energy thank you sure thank you very much we're at the time for the picture now so you can go outside to have you on a picture let's thank you very much thank you