WEBVTT 00:00.180 --> 00:00.960 All right guys. 00:00.960 --> 00:01.950 Welcome back. 00:01.950 --> 00:07.080 Now if you've been following me from the previous lecture you will also have set up your CloudFlare. 00:07.080 --> 00:08.340 See the end by now. 00:08.370 --> 00:10.410 If not go ahead and do that. 00:10.590 --> 00:14.610 If that is what you're looking to do to optimize in this section. 00:14.610 --> 00:21.090 Now before we go ahead and do a speed test and a loading page test I want to talk about the next issue 00:21.090 --> 00:26.810 we're facing what it is what we can do about it and then we're gonna go ahead and test our new CloudFlare 00:26.820 --> 00:33.520 sedan for the server response time and also check out how to affect the leverage browser caching. 00:33.550 --> 00:36.210 OK so what is leverage browser caching. 00:36.210 --> 00:38.250 Well basically it is the cash. 00:38.250 --> 00:39.840 We know what our cash is already. 00:39.840 --> 00:40.530 Right. 00:40.530 --> 00:47.520 It's about leveraging a browser cache meaning we catch a lot of the things such as the see says javascript. 00:47.640 --> 00:53.580 A lot of our images are background et cetera to the browser to the user to their computer so everything 00:53.580 --> 00:55.350 will load much quicker. 00:55.350 --> 00:59.680 Now the issue that we have right here and it's a small issue because you can see that it's actually 00:59.680 --> 01:05.040 in the lowest part in the priority list right here is that if you scroll down there is no expiration 01:05.340 --> 01:07.590 dates or expiration time. 01:07.590 --> 01:13.530 Rather it's specified and this is usually not really that big of a problem because we're going to go 01:13.530 --> 01:17.160 ahead and set up a matter anyway so that's going to take care of this problem. 01:17.670 --> 01:23.220 But what it means is that it does not have a date or a time for when it's going to expire. 01:23.220 --> 01:30.360 So if you're updating your site it does not automatically remove itself from the cache and for some 01:30.630 --> 01:35.320 a lot of people use different times for the caches depending on what kind of Web site depending on how 01:35.320 --> 01:36.960 they want to leverage et cetera. 01:36.960 --> 01:42.630 But what is important to know is that you're still going to get the updated site if you take care of 01:42.630 --> 01:44.910 the cache on your Web site. 01:44.910 --> 01:50.250 Now if we have a look at Pat Flynn here on his Web site smart passive income this is the first test 01:50.250 --> 01:56.010 that we did earlier on in the section you're going to see that he also has this leveraged browser caching 01:56.010 --> 01:58.060 as an error if you click on it. 01:58.170 --> 02:03.990 He actually has the same thing as we do exploration not specified on a lot of the things in here. 02:04.710 --> 02:12.300 But anyway his Web site is performing very well and is loading super quickly and it's a small size. 02:12.300 --> 02:17.010 Now the most important of all this of course the loading time itself. 02:17.010 --> 02:20.950 And we're not here to get hung up on all the numbers getting everything perfect. 02:21.060 --> 02:25.280 We want to have a great loading time for the user experience and for the SC. 02:25.290 --> 02:26.370 All right. 02:26.460 --> 02:32.370 But what I want you to do is actually go to your cache plug in and if you've been following along you 02:32.370 --> 02:36.290 should be having the WP super cache and if you don't that's fine too. 02:36.300 --> 02:39.000 There are a lot of great cache plugins out there. 02:39.000 --> 02:47.610 And I wanted to go down to this one in the advance section so you go to Settings WP super cash advance 02:47.850 --> 02:54.180 and then go to this one this has three or four not modified browser caching indicate when a page has 02:54.180 --> 02:56.710 not been modified since it was last requested. 02:57.120 --> 03:02.370 So what this is going to do is that it's always when they're entering our Web site they're going to 03:02.370 --> 03:08.610 check their catch towards the current cache on the Web site to see if they are matching just to check. 03:08.640 --> 03:08.930 Okay. 03:08.940 --> 03:14.280 Is there anything that is updated that needs to be updating or if it is the same if it is the same then 03:14.280 --> 03:19.080 nothing needs to be done if something is up that is going to update us it's just something that's really 03:19.080 --> 03:20.720 worthwhile to have activated. 03:20.760 --> 03:22.100 So we're going to click it in. 03:22.290 --> 03:29.610 We're gonna go down and click on update status and now with this tiny difference that we have made with 03:29.610 --> 03:35.360 this tiny update we're gonna go ahead and we're going to do in New speed test to our Web site. 03:35.360 --> 03:40.230 Now of course there are a lot of more things that we could be doing in here you could actually go into 03:40.230 --> 03:47.450 your HD access files and set certain expiration times for each of these files. 03:47.460 --> 03:50.310 And I'm gonna show you how to do that as well. 03:50.340 --> 03:57.420 Now you could also go ahead and go to your h t access file and write in a certain code to set an expiration 03:57.420 --> 04:00.440 date but that file is very sensitive. 04:00.450 --> 04:03.230 If something goes wrong it's going to break your website. 04:03.240 --> 04:08.260 I've been using it before but I have not really seen any difference in performance in my web sites. 04:08.290 --> 04:11.430 So I don't really bother doing that anymore. 04:11.430 --> 04:17.200 So we're not going to be touching that is just unnecessary work and also slightly risky work. 04:17.250 --> 04:21.640 We're gonna go ahead and we're gonna do another speed test so I'm going to click on Start testing. 04:21.810 --> 04:22.370 All right. 04:22.380 --> 04:29.430 So the numbers are in and as we can see there's a really nice improvement going on the loading time 04:29.760 --> 04:37.510 is improved the requests are lowered the size now just as a disclaimer none of these is an exact science. 04:37.560 --> 04:41.090 If you run multiple tests you might have noticed that goes a little haywire. 04:41.250 --> 04:47.430 Also depending on where the test is coming from but it gives you a very good estimate that as we can 04:47.430 --> 04:54.030 see in the previous tests are loading time was hovering at eight zero point eight seconds and close 04:54.030 --> 04:57.950 to zero point nine and now it's hovering at zero point six. 04:57.960 --> 05:00.630 This is incredible the are lowered. 05:00.720 --> 05:03.060 We can see 31 to 18. 05:03.150 --> 05:08.010 The size is slightly increased but again these this might not this is not pitch perfect. 05:08.010 --> 05:14.520 This is not pitch perfect none of this is but a total score has gone up to seventy one from sixty three 05:15.060 --> 05:18.330 and this is just really really great guys. 05:18.720 --> 05:24.930 Now if we scroll down you're going to notice that the leverage browser catching it's still a problem 05:24.930 --> 05:31.560 going on here but it's gonna be until we set an expire time and in my opinion looking at these fantastic 05:31.560 --> 05:37.320 scores I don't think we need to and I don't think you should worry too much about perfecting these either. 05:37.370 --> 05:39.780 Now this one is of course super interesting. 05:39.780 --> 05:40.560 Look at this. 05:40.680 --> 05:46.410 Now we're still getting a reduced server response time warning but before that one was actually in the 05:46.410 --> 05:49.520 top of the hierarchy it was the biggest current problem. 05:49.530 --> 05:53.780 Now it's at the bottom even lower than leveraging browser caching. 05:53.820 --> 06:00.720 So if I click on this one we can see that the server has responded in zero point three seconds and this 06:00.780 --> 06:08.620 is fantastic whereas before it was responding in zero point seventy eight seconds right. 06:08.640 --> 06:15.360 And if we look all the way from the beginning when our speed was lonely at four point two seconds almost 06:15.360 --> 06:16.570 four point three. 06:16.650 --> 06:19.330 Remember this was from Sydney Australia. 06:19.410 --> 06:24.000 We also had a server response time of one point one second. 06:24.000 --> 06:30.040 So almost over a second we had to wait before the server responded and anything happened and that was 06:30.040 --> 06:32.060 the time to first buy it. 06:32.100 --> 06:32.930 Remember that. 06:32.970 --> 06:39.090 So right now guys we actually have a fantastic Web site going on and if we compare ourselves with Pat 06:39.090 --> 06:46.380 Flynn you're going to notice that his loading speed is of course faster and chances are that he is using 06:46.410 --> 06:53.550 expert to properly utilize his Web site minimizing the image sizes even further and off course maybe 06:53.550 --> 06:59.640 he's using dedicated servers or VPN hosting while we're using this shared hosting in the most basic 06:59.640 --> 07:00.340 plan. 07:00.510 --> 07:03.390 And to be honest we're doing really great even for that. 07:03.390 --> 07:09.060 He is at zero point almost zero point four and we are at zero point six and the point is to be under 07:09.060 --> 07:10.530 two seconds. 07:10.530 --> 07:12.750 So we're doing really fantastic. 07:12.750 --> 07:13.540 Total size. 07:13.530 --> 07:15.920 Now our performance is at 7 to 1. 07:16.050 --> 07:17.730 And he is at 73. 07:17.730 --> 07:24.270 And again these are just abstract estimates from this site uptime dot com and nothing here is perfect 07:24.450 --> 07:26.770 no need to go all crazy to perfect this. 07:26.790 --> 07:32.570 He also has these things going on but one of his problem is not server response time you can see he 07:32.570 --> 07:38.100 says Green and you're gonna get green if you serve response time is better than sero point two and we're 07:38.100 --> 07:43.710 going to have to upgrade either go from blue hose to for example site ground we should really fast host 07:44.220 --> 07:51.330 or improve our hosting at Blue host to maybe a VPN or pro plan or just be really happy that we're paying 07:51.330 --> 07:58.590 very little money for a fantastic service and our website is working perfectly fine guys but as always 07:58.800 --> 08:01.350 the actual proof is in the pudding right. 08:01.350 --> 08:06.780 So if we go ahead and we we're going to load Robin and Jesper dot.com like this we're gonna notice that 08:06.780 --> 08:12.390 it loads really quickly of course but if you notice that smart passive income at pamphlets website it 08:12.390 --> 08:17.440 loads faster but these two while there is a difference the difference is not huge. 08:17.640 --> 08:23.580 Both websites are loading really really quickly and this is fantastic if you're under two seconds you 08:23.580 --> 08:25.380 can have a fantastic Web site. 08:25.470 --> 08:27.900 Fantastic SCA are happy visitors. 08:27.900 --> 08:32.370 You have a great UI user interface and great you ex. 08:32.490 --> 08:38.700 Now in the next lecture guys what we're going to go ahead and do is actually look at all of these other 08:38.700 --> 08:45.270 estimates going on in here right now for me right now and chances are for YouTube they might be green 08:45.780 --> 08:51.780 but they may not be so let's talk about what all of these other things are and if they would have this 08:51.780 --> 08:54.600 warning sign what to do about them. 08:54.730 --> 09:01.110 Now one last thing I want to tell you about that as always these sort of tests are not perfect and different 09:01.110 --> 09:02.550 tests give different results. 09:02.550 --> 09:08.790 We have the we have a test from Google and we also have the pinged test and those are going to give 09:08.790 --> 09:11.680 you different suggestions different results. 09:11.970 --> 09:15.270 But as always guys don't go crazy on this. 09:15.270 --> 09:21.960 The main point is to have a good score a beautiful user interface beautiful user experience and then 09:21.960 --> 09:25.810 you are all good to go we don't need to have perfect scores in everything. 09:25.860 --> 09:32.810 Look at Patrick clean he has an amazing website amazing business going on and he's doing 73 out of 100 09:32.840 --> 09:35.340 not 100 out of 100. 09:35.400 --> 09:39.800 So let's talk about these other things and then we're going to move on okay. 09:39.930 --> 09:41.130 See in the next lecture guys.