WARM-UP VIDEO FOR COMPARATIVES

Instructions. Listen and type useful expressions with comparatives

------------------------------------

Exercise. Complete each gap with suitable words and expressions you hear from the video.

And when I look at the overall size of the page, first of all, an average page is about 700 kilobytes. So it's actually (1) ………….. a desktop version, which is good news. But then, this number actually shocked me. types, images are basically 70% of the data on the wire. STEPHEN KONIG: That's pretty typical. It's actually (2) ………….. on mobile than what we see on desktop, but the fact that it's the single largest component of the page size is very consistent with what we don't look so good. And so it's putting a lot of pressure on publishers to update their sites and their images to (3) …………..on these hiDPI devices. ILYA GRIGORIK: And that's a really hard one, right? Because to your point earlier, my bandwidth is not going to up magically by four, or latency decrease by four, but all of a sudden, the images are getting (4)………….. . STEPHEN KONIG: Exactly. ILYA GRIGORIK: And I think, actually, the four is worth So if you're using a lossy format like JPEG, in addition to that, what you're probably going to see is a demand for (5) ………….. images with your compression artifacts. So that in itself will also play a part in increasing the size. format is actually a challenge. STEPHEN KONIG: It is. ILYA GRIGORIK: So (6) ………….. , when I talked to a lot of web developers and designers, they say, great, I took my image, I optimized it. formats in the background. And then we figure out that, hey, this image file is actually much (7) ………….. if we use JPEG, for example. So we don't assume anything about your decisions. ILYA GRIGORIK: So at least in theory in the long term, as a person who's authoring this content, as a designer, for example, it actually it makes my job (8)………….. . STEPHEN KONIG: Correct. ILYA GRIGORIK: I just save it as-- smaller than PNG. There are a handful of cases, less than 2%, where it's (9) ………….. than one. ILYA GRIGORIK: So that's this peak right here? STEPHEN KONIG: That's that little peak right there. significantly less, like 80%, 90%. STEPHEN KONIG: You're looking at (10) ………….. . ILYA GRIGORIK: Which is actually representative of kind of the larger number that we saw, which is for certain And so far, it looks like it's they're competitive, both WebP and JPEG. But you scroll (11)………….. , like 200 milliseconds later, and you can see that a whole bunch of WebP images have fully loaded, more getting pulled in, et cetera. And that's where WebP clearly, in this example, shines. Even though we're spending a little more time on one part of the process, we're spending (12) ………….. in another and the net effect is definitely positive. ILYA GRIGORIK: So hopefully by shipping fewer bytes and We'll talk about tooling in a second. But Android and iOS, ready to go. In fact, it's actually (13) ………….. to deploy WebP today on native platforms, on Android and iOS, than it is on the web to some degree, although it's still definitely STEPHEN KONIG: Definitely. Well, it's one of the things you want to look at because obviously, with (14) ………….. , you get smaller file sizes. So as you're trying to improve speed, that's a knob you can tweak that will definitely have an impact. compression artifacts. And the kinds of artifacts you see between JPEG and WebP are different, especially as you get into (15) ………….. . So you do need to do visual comparison at that level to understand, am I comfortable with the kinds of artifacts versions of Android. So you can pull that in if you need to. And there's (16) ………….. Android devices out there, unfortunately, so that's a handy thing to have. And then for iOS, same thing. But we find, at least in all of our case studies at Google, that this is definitely a worthwhile investment because it gives such a (17) ………….. to the user. STEPHEN KONIG: Correct. And I think the thing I'd point out on that is it's a question of who should be paying the cost and where is that best paid for? And I would argue that it's (18)………….. on the part of the web developer and the site author. It's better for them to pay for a little bit more storage And then alongside that, we're going to continue to focus on optimization and trying to bring that encode and decode time down (19) ………….. . But you know, we're at a point today, we're ready to really push the gas pedal and make some great progress with WebP. So we have to sort of work this in a stepwise manner. And so getting WebP adopted across the web will make it a (20) ………….. for us to go to consumer electronic device manufacturers-- camera makers, phones, et cetera-- ILYA GRIGORIK: So yeah, if the camera saved it directly as WebP, that would be great. STEPHEN KONIG: (21) ………….. . ILYA GRIGORIK: But it'll probably take some time before we get there. everybody's considering just because the mobile web is shooting through the roof. Pages are (22) …………... You saw the number of bytes on the wire. So they're all looking at this in some way or another. And that's not to say that user agent is the only way to do it. I think there are (23) ………….. . In fact, we've been talking with the Chrome team about fixing some of the accept headers and (24) ………….. such that you don't have to write these crazy user agent detection functions. alternative formats, but if you find JPEG Mini is a good choice, then that's fine. We think WebP offers a much (25) ………….. for the vast majority of use cases that are out there today. ILYA GRIGORIK: At the end the day, make the web fast.

Key: Look at the key and say aloud the script from the video to improve your English.

And when I look at the overall size of the page, first of all, an average page is about 700 kilobytes. So it's actually (1) (a little bit less than) a desktop version, which is good news. But then, this number actually shocked me. types, images are basically 70% of the data on the wire. STEPHEN KONIG: That's pretty typical. It's actually (2) (a little bit higher) on mobile than what we see on desktop, but the fact that it's the single largest component of the page size is very consistent with what we don't look so good. And so it's putting a lot of pressure on publishers to update their sites and their images to (3) (look better) on these hiDPI devices. ILYA GRIGORIK: And that's a really hard one, right? Because to your point earlier, my bandwidth is not going to up magically by four, or latency decrease by four, but all of a sudden, the images are getting (4) (four times bigger) . STEPHEN KONIG: Exactly. ILYA GRIGORIK: And I think, actually, the four is worth So if you're using a lossy format like JPEG, in addition to that, what you're probably going to see is a demand for (5) (higher quality) images with your compression artifacts. So that in itself will also play a part in increasing the size. format is actually a challenge. STEPHEN KONIG: It is. ILYA GRIGORIK: So (6) (as I mentioned earlier) , when I talked to a lot of web developers and designers, they say, great, I took my image, I optimized it. formats in the background. And then we figure out that, hey, this image file is actually much (7) (better compressed) if we use JPEG, for example. So we don't assume anything about your decisions. ILYA GRIGORIK: So at least in theory in the long term, as a person who's authoring this content, as a designer, for example, it actually it makes my job (8) (a lot simpler) . STEPHEN KONIG: Correct. ILYA GRIGORIK: I just save it as-- smaller than PNG. There are a handful of cases, less than 2%, where it's (9) (slightly higher) than one. ILYA GRIGORIK: So that's this peak right here? STEPHEN KONIG: That's that little peak right there. significantly less, like 80%, 90%. STEPHEN KONIG: You're looking at (10) (between 70% and 80% smaller) . ILYA GRIGORIK: Which is actually representative of kind of the larger number that we saw, which is for certain And so far, it looks like it's they're competitive, both WebP and JPEG. But you scroll (11) (a little bit further) , like 200 milliseconds later, and you can see that a whole bunch of WebP images have fully loaded, more getting pulled in, et cetera. And that's where WebP clearly, in this example, shines. Even though we're spending a little more time on one part of the process, we're spending (12) (far less) in another and the net effect is definitely positive. ILYA GRIGORIK: So hopefully by shipping fewer bytes and We'll talk about tooling in a second. But Android and iOS, ready to go. In fact, it's actually (13) (probably easier) to deploy WebP today on native platforms, on Android and iOS, than it is on the web to some degree, although it's still definitely STEPHEN KONIG: Definitely. Well, it's one of the things you want to look at because obviously, with (14) (lower quality) , you get smaller file sizes. So as you're trying to improve speed, that's a knob you can tweak that will definitely have an impact. compression artifacts. And the kinds of artifacts you see between JPEG and WebP are different, especially as you get into (15) (lower quality levels) . So you do need to do visual comparison at that level to understand, am I comfortable with the kinds of artifacts versions of Android. So you can pull that in if you need to. And there's (16) (a lot older) Android devices out there, unfortunately, so that's a handy thing to have. And then for iOS, same thing. But we find, at least in all of our case studies at Google, that this is definitely a worthwhile investment because it gives such a (17) (better experience) to the user. STEPHEN KONIG: Correct. And I think the thing I'd point out on that is it's a question of who should be paying the cost and where is that best paid for? And I would argue that it's (18) (better paid for) on the part of the web developer and the site author. It's better for them to pay for a little bit more storage And then alongside that, we're going to continue to focus on optimization and trying to bring that encode and decode time down (19) (even further) . But you know, we're at a point today, we're ready to really push the gas pedal and make some great progress with WebP. So we have to sort of work this in a stepwise manner. And so getting WebP adopted across the web will make it a (20) (lot easier) for us to go to consumer electronic device manufacturers-- camera makers, phones, et cetera-- ILYA GRIGORIK: So yeah, if the camera saved it directly as WebP, that would be great. STEPHEN KONIG: (21) (Even better) . ILYA GRIGORIK: But it'll probably take some time before we get there. everybody's considering just because the mobile web is shooting through the roof. Pages are (22) (getting bigger) . You saw the number of bytes on the wire. So they're all looking at this in some way or another. And that's not to say that user agent is the only way to do it. I think there are (23) (better ways) . In fact, we've been talking with the Chrome team about fixing some of the accept headers and (24) (making this easier) such that you don't have to write these crazy user agent detection functions. alternative formats, but if you find JPEG Mini is a good choice, then that's fine. We think WebP offers a much (25) (better alternative) for the vast majority of use cases that are out there today. ILYA GRIGORIK: At the end the day, make the web fast.

Sources: 

Channel: Google Developers. Faster, smaller and more beautiful web with WebP: https://www.youtube.com/watch?v=4tu2SJfSalA&t=34s

---------------------------------------------

Compiled by Top Grade Edu