 Mae'r awkad, hwyrой'r mewn ffasiaethau, ysgrifianthu 74 spau y mae'r meddwl i fynd am Lly combinau. Mae maen nhw'n ei fod yn y gallu'n ddiwedd fel angen i gydigolon. Yn y bod yn merthynol, mae'n ei bod yn golygu'r meddwl yw. Mae'n meddwl Ile ac mae'n meddwl i fynd am enwed, ac mae gwestiwn i'r meddwl. Mae'n meddwl i'r meddwl i'r meddwl i fynd i fynd eich meddwl. Ac mae'n meddwl i'n meddwl i fynd i fwy소�oedd beth rydych yn ddo'r fel ar gyfer. er mwyn eich bod yn dweud. Yn y pethau ar y ddod o'r gwaith, yw rhan o'r bwysig, gwybod i gael gyd, gyda'r sgwm anodd rhywbeth. Dyn nhw'n gwybod i gael gweithiau sydd yng Nghymru sydd gennym wneud o hwnnw i'r sgwmp yn gwneud y mae'r sgwm anodd ac efallai yn gwybod ddod o'r byw'r pipos, gyda chi'n mynd gŷn hefyd. A awarded o'r bwrdd y gallwn i'r ddweud y taith yma felly mae'n bwynt i gyffennu'r blaen o'r ddwylo. Fel allan gofod yr adeg mewn gwirio deimlo, ac mae efallai allan yn gwneud o llwytoedd o ddigon o ddweud syddai'n bwysig nhw'n rhoi'r hollwch a'r hollwch ar gyfer i'ch atdweud, rydych chi'n gwybod i fod yn ymdlinkol a gennych, felly yna wedi fyddiaeth dillun o brydau gwybod i ddonddo i'r gynhyrchu'r cyd-존연. Rwy'n gwybod ar beth oeddwn i ddweud y cyffredin ac i gael eu cychwyn ar bobl chi'n gwybod i gydag i wedi gwelodau i'r ganes y mae brydiol ei gael â'r cymryd hynny, a nhw'n ddwy fydd o'ch gydag gyda hwn i nes TalkingMode o'ch cyflymodd yn ffordd yn bryd, ond a ddod am y swyddfa dysególio'n ddifu'n snod ar y cyflymnyddeni'n ddigion. Y ddweud y cwm! Gwyddo'n gwybod y f Aquí. Gwyddo'n gwybod bwysig o ddweud y cwm yn y ddech chi. Mae hwn i ddweud y twil yma, a un o ddweud o ran gwahodd ac rhywbeth ychydig hefyd yn ffryd i ddiwedd y cwrn o'n pryd. Mae'r cwm yn bwysig o ddweud o'r cwrn o'r brosa Crom. Cymru'n gwneud yn crom yn y web-page, ydych yn cymhreifft mewn cyfnod ac yn fwy o'r twelwch a fyddwch arweithio'r bwysigol. Mae'r cyfrifftau a'r cyfrifftau yn cyfrifftau i'r cwrs. Cymru yw'r cyfrifftau i'r cwrs, dyna'r cyfrifftau yn crom, ac mae'n cyfrifftau'n gwneud bod y cyfrifftau yn cyfrifftau o'r cyfrifftau. a swydd i felw I look like it, it looks a little bit something like this. So I'm on a website, I've opened up the network tab and I've just refreshed my website and it gives me this big list of assets for the site, tells me how long my page took to load and then a bunch of things that were loaded on the site. I can arrange these into, so you can arrange them into size and time is the one that I usually arrange them into because that's how long it took that individual asset to load. So based on this example, I can see that the things that took the most time to load on my site appeared to be things like CSS files, JavaScript files and the odd image, which this is kind of the thing we usually see. Things like images slowing down your website isn't exactly a surprise. But if there's a specific asset that's taking a long time to load, usually the network tab will give us a good idea of where we can look for making some improvements. So that's a really useful tool. Similarly to the network tab, there's other online tools you can use to get an idea of what's slowing down your website rather than investigating yourself using something like the Chrome network tab. You can use a website and there's quite a few popular ones. There's GTmetrics, webpagetest.org and things like Lighthouse. I'm going to show you. And these all tell you what they think can be done to improve the speed on your website. And they're quite useful. They'll give you some stuff that you might not have even thought about and they give you a lot of information as well. And you can try a few of them and you'll find that usually they'll give you the kind of... If something's slowing down your site, all of them will probably point to a similar kind of culprit. So I'm going to show an example of a report on the same website. So I've typed my website into Google's page speed insights here. And I click analyse, it goes away, it takes a look at my website and it comes back with a load of information. The most prominent thing you can see once you go to Google page speed and put in your website is the big score at the top. Now, I got an 86, which to me doesn't seem so bad, but it's orange. It should be green. That's really upsetting, things like that. So straight away I'm like, OK, I would quite like a green score. If you scroll down on Google page speed insights, it'll give you information on why it thinks is making your score not perfect. So for me it was things like unoptimised CSS files, things that were being loaded and that weren't being used, not serving images in specific formats. And you can click the dropdowns and it'll give you suggestions and why it thinks will be helpful for your website. And you can take that information away and maybe optimise some images, maybe install a plug-in that might fix the specific issue it's telling you about. So you can run a test like this. This is the lighthouse test in Chrome, which gives you very similar kind of information. This one also does metrics for things like your SEO and accessibility and things like that. But again, if I look at, this is the same website, I've still got things the same kind of information being displayed, so it still thinks the thing slowing down my website is the need to minify my CSS or do something about that, which this is all the kind of information I already knew because I'd checked in my network to having Chrome, I'd used the Google page speed insights. So having done a few tests I can kind of get the impression, OK, if I do something about that, that might make a difference. The one that I use the most often, sorry I'm showing you a few of these, but this one is my favourite and it's webpagetest.org and the reason I like this one a bit better is because webpagetest.org, when you type in your website, it does three tests on it, it loads the page three times and it'll work out its scores from that and it also gives you, the information is a bit, in my opinion, a bit more clear, so I've got my scores up here, which are very nice, I like this one, obviously I like this one best because it gave me all green, but it also gives me some important metrics at the top here, so things like my terms first byte, the content, fully the first content for paint, things like that. So it's, yeah, there we go. It's also got little tabs with more information, so it's got things like a performance review checklist, so I can clearly see what assets on my site here that aren't optimised, that it thinks I could do with compressing, it's got really clear information for me compared to the other tools I feel, and it's got my waterfall here, which gives me an impression of what is loaded, being loaded in at what time. So a web page test has quite a lot of information and it's all in different sections, which I just think that's a little bit nicer and clearer. So with these scores, you might put your website in and find out that you've got this really low score and it can be a bit worrying because you're like, oh no, is my website really fully optimised? And we get a lot of customers who run these kind of tests. They might have not quite the score they want and they're immediately thinking things like Google are going to kick me off the search engine, I'm going to be ranked really low, oh, this is terrible type of stuff. It's not as concerning in most cases as they should think it is because half the time we'll go to the website and we'll have a look and be luck, but your page loads in like half a second for me. Are you having, is there a specific section of the site that's slow or is it slow for you? And they'll go, no, it's fast for me, but this has given me a really bad score. Basically, there might be things going on on your website which make this score not as important as you think it is because at the end of the day, if your site's loading fine and fast, then the score might not be everything. For example, around the page speed test on Amazon, they got 36, so obviously my site is much better than Amazon and will be ranked at the top above Amazon. That's not the case at all. But it gives you the kind of idea of how important this metric can be in some cases. I think it's not useful because it definitely gives you some insights on how you can improve certain aspects of your site. But if you're chasing after the perfect score, you might not really need to because as long as your page loads and everything loads fine, Amazon loads in everything on the page in like half a second, less than that, it's really fast and it's super high ranked. There's nothing wrong with Amazon despite what this score might say. So, yeah. Don't get too worried about the scores as a point. Use them as more helpful guidelines on how you can speed up your website. A lot of people get kind of hung up on the time to first byte metric as well. I'm just going to talk about that and the first contentful pane and what these metrics are and why they're important. So, the time to first byte is when you first make a request to the server. It's when you get that initial response, so it's how long the server takes to respond, which is an important metric. But arguably, the more important metric I would say is the first contentful pane because what this is. This is when you actually start receiving something in the browser, so you start actually seeing something visual on the website. So, like your images, your CSS, that's the more user-based metric. So, your time to first byte might be two seconds, but then straight after that, you've got everything else loaded. If your first contentful pane is a lot longer than your time to first byte, then the user experience isn't very good because it means that the actual page is taking quite a while to load. So, these are the two metrics that are quite important once you're looking at what's being loaded onto the page and what the user's experience is. Now that we've gone through a few tools and we've got an idea of what's slowing down our website potentially, I'm going to go through a few easy optimisation tips that anyone can do. Just some little bits of things you can do, things you can talk to your host about, and hopefully get the site up to a bit of a higher score, but not so high that one. So, based off my website, the big-speed culprits that I saw, and this is usually the kind of case that we'll see when we run this test on most websites, things like unoptimised images. Images count for a lot of slowdown on websites. That's not a surprise. They're usually the biggest assets on the side. Large JavaScript files and CSS files, and one that comes up when I've been talking to customers is external resources being loaded into the site. So, you'll have your website, but it might be loading a video from another website, or it might be loading a font from somewhere. So, basically, your website is also relying on another server to serve something before it will load properly, and that can affect your score quite a bit. So, with something like that, ideally you'd be loading in your assets on your actual website. So, just going to talk about some easy image optimisation plug-ins. So, maybe you've not thought about optimising your images, making them smaller. There's many plug-ins that can do this for you. Some of the popular ones are Jetpack's Photon. It might be a bit controversial because not everyone likes Jetpack because it has a lot of other features, which sometimes people think might slow it down a little bit. But it has an image optimisation tool where you can use Jetpack's CDN to serve the images for you. There's WP Smosh, which compresses your images, and one of the ones I see most often and quite like is the U Image Optimiser plug-in. Because this one you can set your own compression settings, you can tell it what you want it to do. You can go back and apply all those optimisation options to your current uploads, and then it'll do it going forward for our new uploads. So, it's quite a popular one. You want to talk to your host and provider about potential server and webp images. These are new formats of images that are more optimised for the web. They're compressed a bit better, and they're designed to make the web run faster. Speak to your host and provider because they can potentially help you set up webp images loading onto your website. You want to find out a bit more about things like that as well. If you want to do some image optimisation before you actually get them on your website, there's some tools here that I've used before. My favourite one is the one at the top, which is compressor.io. Basically, you just upload the image to it and it gives you a more compressed version of it. It removes things like metadata. It does lossy and lossless compression. Basically, lossy compression will affect the image quality a bit more, but have a much larger file reduction, and lossless compression is the opposite. It will keep the quality of the image, but have a little bit of a less file size reduction. Anyway, I quite like running my images through that because it's quite a quick and easy tool to use. Of course, you can also do the old just resize your images before you upload them and upload reasonably sized images for the web. Most websites are usually serving all their images at 2,000 pixels wide, so just a few easy ways you can optimise your images, and if you haven't been doing this, it'll make a big difference. The other big culprit that came up on my website once I was getting my reports was that you need to minify my JavaScript and CSS, and this is really easy to do with a plugin as well. What these do is you can get a plugin which takes your CSS file, and if you've ever wrote CSS, you'll know you make it. The files look really pretty because they're all lined down, all the different options, and they look really nice, but this basically just shrinks them all down into one line of code and removes all the white space from them, resulting in a smaller file, and it's just a really easy way to get a little bit of load down on the site. There's a few plugins that can do this. Some themes do this as well, but the plugins that I've seen are to optimise, WP Superminify and WP Fastest Cache will all do this, and there's plenty of other plugins that will do this as well. Something you want to talk to your hosting provider about is making sure that your traffic is being served over HTTP2. HTTP2 is an upgrade to the current HTTP protocol, which, when you visit a website, you're requesting packets from that website, and they're sending them one after another, opening that connection back and forth. This is kind of a hard one to explain properly, but the difference with HTTP2 is when you open that first request, it keeps the stream open so everything keeps going, keeps being transferred, and it's faster for all that reason. So you want your hosting to be giving you this service. It needs an SSL to work, which is also good, because everyone should be having an SSL, and it also kind of gets rid of that myth that SSL slows your site down, because if you've got an SSL and HTTP2 running because of that, your site is faster than when it didn't have the SSL, and it's more secure, which is great, and Google does like SSL, so every site should have an SSL, basically. Another popular way of reducing site load time is to set up caching, and caching is a bit... caching is awesome, but it's also really not awesome, because what caching does is it... I'm distracted. Caching, rather than every time you load up a web page, and you get the individual assets and you load up the page, caching kind of... it takes the image of the full page and stores it in memory, so when you visit the website, if it's cached, it'll just whip it out of memory and display it faster. Now, that's really handy, but it can be a little bit confusing sometimes, because if you're developing a website and you make a change, then you go back to the website. Sometimes you find things like, oh, the changes disappeared, things like that. That's usually because the cache hasn't been flushed, things like that, so you do have to be a little bit careful with it. Most caching stuff will not affect the logged-in user, and it's more something the logged-out user will experience, but there's two ways you can manage caching. Your hosting provider might provide server-level caching, so you might want to speak to them about whether or not they are doing that, because if your hosting provider is already handling your cache for your website, if you add something like a plug-in, you can have two caches and that can get things really confusing. If you don't already have caching, though, you can set up with a plug-in, and these are three of the popular ones, so W3 total cache, WEP rocket and WEP fastest cache. Because of how this works and stores the web page in memory, it will speed up your website, and it's really good. It's worth speaking to your hosting provider about which options are best for you and whether or not they're already providing you with it. I'm just going to go through some other reasons why a website might be slow, because these are the kind of usual things we see and easy optimisation tips that anyone can do. Your website might have a great score and be more or less fine all the time, but there are some other instances where the site is going slow and the issue isn't quite as clear, so I'm just going to go through some problems that might be the case and what we can do about them. Because this is WordPress, one of the main reasons the site might be going a little bit slower than we would want it to, is because it might have too many plug-ins. When I say too many plug-ins, having a lot of plug-ins isn't always a bad thing, but from my experience working with WordPress support quite a bit, we'll see a lot of sites with a lot of plug-ins, and there'll be instances where half the plug-ins are disabled and they're not kept up to date because there's so many plug-ins and they're not needed so they're not kept up to date. So you can get your site into a little bit of a load mess just because there's so many plug-ins installed for no real good reason. If you've got a lot of disabled plug-ins as well, they usually do have some sort of data still on the site that might be being loaded in and causing problems, so things like database table entries, making your database massive, things like that, if you've got a lot of them just sitting there darming. It's a really easy fix though, because the fix is to just make sure that your plug-ins are being regularly updated, get rid of ones that you're not using, but actually delete them. Don't just disable them and leave them on the site for forever. If you're not using the plug-in, there's no point in having it, and if you do decide you need it again, you can just reinstall it. So, yeah, just do regular plug-in audits. Make sure that the plug-ins you are using are being kept up to date as well, because one of the things with plug-ins that could be a problem is the code might be really out of date for a plug-in that's not been updated in several years. That might be the case. The plug-in might be fine from the get-go as well, but yeah, just make sure that the plug-ins on your site are the ones that you actually need and it'll be a lot better for you. Another thing that slows down sites unrelated to anything we've been through is denial of service attacks, and this is when another computer, a bot, things like that, will make lots of requests to your website in quick succession. So, for example, a script or a robot trying to log into your WordPress admin really fast brute-force attacks, where they're just trying to guess the password, and all those guesses in quick succession will run up your memory making your site slow. So, things like this can be a little less obvious because most of the time you just see the end result where the website is really slow and you can't see this person or bot or whatever trying to log in. Usually, you can report something like this to your hosting provider. They'll check your access logs and they'll find out why that's happening and find out that that's the case. It's another one that's not too difficult to start out. In most cases, your hosting provider's probably got you set up with some sort of protection for this. So, something like fail to ban on the server, which will ban IP addresses after they try to do dodgy requests a few too many times. You can install a plug-in called limit login attempt, which does the same thing for the login page. You can set up things like HC access rules on your website, which you can target specific files and limit the access to them. So, that's the kind of thing you can do to prevent this kind of problem. It might be something to talk to your hosting provider about, but you can install plug-ins, which will take a look as well. The security plug-ins like WordFence and things like that, which have these kind of tools in them. So, you can look into stuff like that for DDoS attacks. The worst reason your site might be slow is that it might be hacked. Hopefully, this is not the case, because this is the worst-case scenario and it really sucks when your site's been hacked. Sometimes it's not very obvious that your site's been hacked. You might just find that it's slow one day, it might not be slow at all. This is one of the reasons why your site could be slow. And there's not really a great amount that can be done about it other than cleaning up the hack. So, this is why taking backups is important. Hacks can slow down your website by doing things like installing scripts on your website, which are attacking other sites. They use up a lot of memory, they can be sending out spad mail. So, it's one of those possibilities. The solution is either to restore from a backup when the site wasn't hacked, but even then, the vulnerability could still exist. So, it's best speaking to someone about getting a proper clean-up on your website, getting fresh versions of your plug-ins installed where the hack is definitely not present and going through that process. This is the worst-case scenario and hopefully that's not why anyone's site is slow because it's real pain when your site's hacked. And another thing to talk to your host about is what kind of hosting you're on. This is fairly straightforward. So, quite a lot of websites, they might be using either shared hosting or VPS-based hosting. And on shared hosting, you're in a service space with other clients' websites. So, does this server and all these websites run it, including your website and you don't really know these other websites that you're sharing the service space with. One of them might be a really busy shop website that probably should be on its own hosting, but because shared hosting is usually that bit cheaper, quite a lot of people go for it. And if your site's quite... if the speed of your website is quite critical to your business, then you don't want these other websites on the server taking up all that memory, the resources on the server. So, what you can do is you can switch to VPS-based hosting. And that service space, which you were sharing a bunch of websites with, now you're in your own container space. You've got your own resources that are specifically for your website. And no other website can take up some of the memory and not let you have it. So, if speed is really important to your website, you definitely want to be looking at containerised VPS-based hosting. And usually it's not as dear or as you might think. So, yeah, that's definitely one of the better options for keeping your site up quite fast, regular. Finally, because solving speed issues is quite difficult, because there's so many different reasons it can happen. So, if you're using a hosting provider with a support line, there's useful details that you can get for them to help them kind of help figure out what's going on. A lot of the time it's just a case of going through a page speed test and we can give advice on what kind of things are slowing down your website that you can do. But when it's that little bit less clear, when something a bit weird's going on, there's some useful information that you can grab for us or make note of. And usually the kind of information that helps identify speed issues is the time the slowdown happened. So, if it's not a constant thing, if your site slows down every day at 3am for some weird reason, that's definitely useful to us, because we can check things like error logs, access logs, see if there was anything running on the server at that time, see if there was issues on the host side at that time. So, knowing when the issue happens is really important. It might be happening on a specific section of the website. Maybe that section of the website only has things like, maybe it's your videos page, which is particularly slow, which might point to the issue, things like that might be helpful. Can we replicate the issue as usually the really helpful one? Because if we can see the same issue you're having, it helps us go away and kind of keep trying things and help identify where the issue is coming from. Yeah, if you can take away as much information about unclear speed issues as you can, it really helps your hosting provider, provide you with the assistance you need to get back up to speed. Hopefully that was helpful. You mentioned about the size of the pictures on your site. What is the guidance for the difficult sizes that we should follow? It differs for every website because based on your WordPress theme, you might have different kind of thumbnail sizes, and your images might be being served at different sites, and you might have different kind of thumbnail sizes, and your images might be being served at different sites. You might have been served at different sizes on different parts of your website. When you upload an image to WordPress, it usually divides them up into those thumbnail sizes, so there's no kind of set you should be uploading at this size. You want to make sure that your themes are doing the thumbnails right. I'm not saying you don't want a 2000 pixel image, but it's actually on the website being served at 100 pixels wide. There's no point in having that, you just have the smaller image on the website uploaded and being served. How do these image optimisation things that you told us about compare with programs like Adobe Photoshop, and my room does not have such a series for web, what you do manually. I've always optimised my images manually to people's screen size on my website before I upload them, is that enough? As long as you're doing something, I imagine that's perfectly fine. You can always try taking the image that you've optimised yourself and seeing what something like compressor.io can add to it, because I'm not sure if Photoshop removes things like the metadata from the picture and things like that. I'm not sure if it's helpful for the want. Sometimes you would, some of you wouldn't. I'd say give it a try, but as long as you're doing something, it's better than doing nothing if you're uploading especially things like large photography website type images. Can you tell us some optimising videos? Not really. My kind of advice would be to serve it from YouTube, because chances are YouTube's server, or whatever video streaming service you're using is probably a lot faster and optimised for serving videos, because videos are really huge. Serving them from your whole service is usually not the best option in most cases. Let's say the issue is, so far against what this is for a client, it requires all the clients, even though it has been termed to be small, what's the answer to that? I'm trying to think of a better reply than tell your client off. I think something. Honestly, if they don't want to get rid of the plug, maybe you can offer alternatives. But yeah, if you've found a specific plug-in is slowing down the website, the plug-in is slowing down the website, I don't know if you can contact the developer and get them to do anything about that, but when the cover is clear, there's not a lot you can do, especially if they refuse to get rid of it. I wish there was a, oh, press this button and it'll just make the crap plug-in not crap. I'm going to ask, how do you know if your site is being ruled or HTTP2 or not? I mean, without asking you, we've seen that somehow. It's already on SSR. Network tab. Do you know where it shows you that? Yeah, in the network. Oh, let's go back. Maybe it's showing me. Cos usually that's the kind of thing we check on the server side, so let's have a look. One of these columns will tell you a part of it. Yeah, you haven't got it. Yeah, one of those tabs. If you go along, hopefully it should tell you. Try and get an example, but we don't have it in it. HTTP2, right? Yeah. Cool. There's just one more question. If you do things like that, that's a problem. If you don't have, if you check the minify, I mean, CSS minification javascript, you checked all that, and you want to come up with your PHP or do something on the server side, and the host said, well, that's impossible with that. Would you call it that? Sorry, the host said that's impossible. The HTTP side, right? The one is so zero. Well, you read an interest, and I'd like to provide you my thing or something similar to that. I think so. Oh, I see. And your host doesn't say, well, that's not possible. Well, it depends on what kind of hosting you're on because in most cases, if you're on shared hosting, they probably won't do that for you because it might affect other websites on the server, and some of them will install certain modules and things like that for you. Potentially, obviously, I can't speak for what hosting package you're on and stuff. It depends on what you're after. I would press hosting as a bunch of cool optimisation stuff on it, but yeah, most of our VPS-based hosting, we can make certain customisations that customers want, and I would assume that's a similar case for most places. As long as it's not affecting other people's websites who potentially might not want it. I'd be surprised if they installed anything you wanted on shared hosting.