WEBVTT

00:00:00.080 --> 00:00:05.920
have you ever been driving around at rush hour and seen an incredibly

00:00:03.760 --> 00:00:10.400
expensive supercar wondering to yourself what is the point

00:00:07.839 --> 00:00:14.880
of buying a high-performance six-figure vehicle if you can only go a few miles

00:00:12.639 --> 00:00:19.119
an hour during the evening commute well that actually tends to happen a lot

00:00:16.960 --> 00:00:22.400
here in vancouver but no matter where you live this is probably how you feel

00:00:20.960 --> 00:00:27.519
if you've ever had a fast internet connection yet your favorite website

00:00:24.640 --> 00:00:31.760
still often takes a long time to load so in this age of gigabit fiber service 4k

00:00:30.240 --> 00:00:37.200
video streaming and massively multiplayer online games why are we

00:00:34.239 --> 00:00:42.000
still so often waiting around for pages that might only consist of text and

00:00:39.200 --> 00:00:46.800
images to hit our screens well ultimately most issues that cause pages

00:00:44.320 --> 00:00:51.440
to load slowly can be classified as some form of latency a concept we've talked

00:00:49.360 --> 00:00:56.399
about quite a few times here on techwiki simply put latency is the delay between

00:00:54.000 --> 00:00:59.440
an input and the corresponding action something you've probably noticed if

00:00:57.680 --> 00:01:03.280
you've ever tried to watch a video with an out of sync bluetooth speaker but

00:01:01.520 --> 00:01:07.680
when it comes to loading websites latency is often caused by something

00:01:05.439 --> 00:01:12.400
either server side or on your own end that needs to be handled independently

00:01:10.240 --> 00:01:17.280
of your 100 megabit internet connection thus creating a bottleneck you might not

00:01:14.720 --> 00:01:20.720
be able to avoid no matter how fast your connection is

00:01:18.479 --> 00:01:25.280
one frequent culprit is a page that relies heavily on scripts such as

00:01:22.880 --> 00:01:29.280
javascript that require additional processing by your device you see with a

00:01:27.520 --> 00:01:33.920
reasonably fast connection it doesn't take long for a browser to understand a

00:01:31.280 --> 00:01:38.560
command to load up some text or images and place them in the appropriate spots

00:01:35.840 --> 00:01:42.640
on your screen however web page scripts are almost like little programs that

00:01:40.240 --> 00:01:46.720
your computer has to run in addition to loading the page's actual content

00:01:44.560 --> 00:01:50.479
meaning additional time is often required to process them scripts are

00:01:49.040 --> 00:01:54.560
responsible for handling certain interactive elements of web pages but

00:01:52.399 --> 00:01:59.360
perhaps unsurprisingly many of them are put there for advertising purposes ad

00:01:57.280 --> 00:02:03.680
scripts both fetch ads to place on web pages and send information back to ad

00:02:01.600 --> 00:02:08.239
servers to keep track of analytics and user browsing habits so a marketer

00:02:06.159 --> 00:02:13.040
tracking the embarrassing music that you might like to listen to could be behind

00:02:10.720 --> 00:02:17.760
your favorite site loading slowly or responding slowly when you try to click

00:02:15.520 --> 00:02:22.000
on something but even if you're loading up a site that's mostly free of big

00:02:19.760 --> 00:02:25.680
clunky scripts a page can still be written poorly asking the browser to

00:02:23.920 --> 00:02:29.840
make tons of requests for different elements like scripts and images aside

00:02:28.000 --> 00:02:34.560
from the intricacies of how web pages are written another frequent source of

00:02:31.760 --> 00:02:38.959
frustration is ping the time it takes for a packet to leave your computer

00:02:36.640 --> 00:02:43.519
reach the server and the response to be returned to you packets used to measure

00:02:41.280 --> 00:02:47.599
ping time are very small just a few dozen bytes so ping time really is not

00:02:45.920 --> 00:02:52.239
dependent on how many megabits per second your isp is offering it's better

00:02:50.319 --> 00:02:57.360
to think of high ping time as another form of latency that's usually caused by

00:02:54.640 --> 00:03:01.040
a server being very far away because even though the electrical impulses that

00:02:59.360 --> 00:03:05.760
carry information over the internet travel at incredibly fast speeds they

00:03:03.280 --> 00:03:09.360
still take time to reach servers and if you're sitting in los angeles trying to

00:03:07.360 --> 00:03:12.159
access a server in london that amount of time is going to be

00:03:10.959 --> 00:03:16.080
noticeable any ping above about 100 milliseconds

00:03:14.319 --> 00:03:20.400
will probably cause web browsing to feel at least a little bit slower thanks to

00:03:18.480 --> 00:03:25.200
the additional delay caused by these vast distances and although this video

00:03:22.879 --> 00:03:28.640
is about why websites load slowly this is also part of the reason why gamers

00:03:26.879 --> 00:03:33.760
prefer servers that are geographically closer to them as a ping higher than

00:03:30.640 --> 00:03:36.159
just 50 milliseconds can cause lag due

00:03:33.760 --> 00:03:40.480
to the real-time nature of many games but back to websites are there any ways

00:03:38.640 --> 00:03:44.959
that developers can get around slow loading times well yeah both by coding

00:03:43.360 --> 00:03:49.280
their pages efficiently to cut down on how much work your browser has to do and

00:03:47.280 --> 00:03:52.959
by caching frequently accessed data through schemes like amp which you can

00:03:50.879 --> 00:03:56.640
learn about more in this video with these best practices developers can make

00:03:54.799 --> 00:04:02.159
your life a little bit easier and that's important as a recent survey indicated

00:03:58.799 --> 00:04:04.480
that 40 of users give up if a website

00:04:02.159 --> 00:04:07.680
takes just just three seconds or more to load

00:04:05.840 --> 00:04:11.599
given how impatient many of us are these days i'd hate to be the developer who

00:04:09.519 --> 00:04:14.879
got can because their website wasn't loading fast enough

00:04:13.360 --> 00:04:18.639
but you know what is fast enough freshbooks freshbooks cloud accounting

00:04:16.799 --> 00:04:22.079
solution is great and works anywhere with a freshbooks mobile app you can

00:04:20.320 --> 00:04:26.080
create professional looking invoices on the go or snap pictures of your receipts

00:04:24.000 --> 00:04:29.440
so you don't lose them stay on top of important conversations and never miss

00:04:27.680 --> 00:04:33.680
an update see when a client has viewed their invoice or when an invoice has

00:04:31.040 --> 00:04:38.400
become overdue start your 30 day free trial right now at freshbooks.com

00:04:36.320 --> 00:04:41.199
forward slash Techquickie so thanks for watching guys if you like this video

00:04:39.680 --> 00:04:44.320
give it a thumbs up give us a subscribe and be sure to hit us up in the comments

00:04:42.720 --> 00:04:47.840
with any suggestions that you might have for future episodes