 Hi, everyone. Welcome to Web Day. And welcome to our panel session on Core Web Vitals. I'm Vivek, a product manager on the Chrome team. And in this session, we're going to talk about how Core Web Vitals have made a difference across three very different businesses. More than ever before, businesses rely on the web to serve their customers and grow. And we know from our work at Google how speed and usability can create a great user experience. We've talked to hundreds of web businesses around the world, serving many millions of users. And we found a few common themes which we distilled into the Core Web Vitals metrics, a set of metrics that capture the most important parts of your user's experience, ensuring pages load fast, are responsive, and stable. More importantly, Core Web Vitals allows us to measure progress and share ideas to improve the web as a community using a common language. We use Core Web Vitals extensively within Google and with many of our largest partners to serve our users better and grow their businesses. And we'd like to share their experiences with you today. I'm thrilled to be joined by Ruben Sherwin from Wix, one of the largest global CMS platforms, Fabio Palletti from C-Discount, a leader in e-commerce from France, and Giuseppe Cavotto from GED, one of the largest publishers in Italy. Gentlemen, thank you so much for joining us today. And let's start with you, Ruben. One area you and I have talked about has been the importance of building a performance culture within an organization. Can you tell us about that and about your experience with Core Web Vitals at Wix? So thank you, Vivek. That's a great question. So as mentioned, I'm Ruben Sherwin from the Office of the CTO at Wix. And a little bit of context about Wix, we're about enabling anyone to create their dream online presence with no compromises whatsoever on functionality or design. Our platform is designed so that it will do the heavy lifting so our users can focus on managing their business in online presence. Personally, I'm part of the Wix executive team with my number one focus being making the sites build on the Wix platform load faster. So the performance challenge for us is not about optimizing one single site with one given design. It's about building an infrastructure that enables our users to build any site they can imagine and we will verify that our users get the best possible performance for that given design. Now, as we all know, performance is highly impacted by design and functionality choices the site owner makes. Now, with virtually no limit on design and functionality, there's no one single performance magic number we can aim for. The challenge is that once our user makes their choices, we need to deliver for them the best possible performance for their combination, their choice of UI, design, and functionality. So the way we tackle this is we started with a clear performance vision. We define this as for any given site design, offer the loading experience which is comparable to the best possible implementation of the same design. So it's as if you have certain design and functionality in mind. If you take the best possible implementation at Wix, the performance should be comparable to as if you recruited the best development team in the world to develop this specific site for you. And once we had this vision in place, we realized that a key critical component for it is to have the performance culture in place. We wanted everyone on the team, from software engineers to executives to be on the same focus, including our data teams, our product managers, our customer satisfaction, et cetera. We set up a performance core team that helped us disseminate and create partnerships across all product teams. Since it's critical to have everyone on the team engaged and involved because there's no limit to the permutations of specific sites that our users can build. We realized that a key part, and this connects strongly to core vitals, is having performance data, transparency. We wanted it to be part of everyone's DNA to engage the members and to help them engage the actual changes, progress, both in field and lab data. We've been collecting, we're strongly a data-driven company in many things, and we collect, run real user measurements and field data, which is anonymized from real user sessions. And it effectively lets us know how our sites perform in different geographies, different devices, different networks, totally different infrastructures, what our actual user base feels on a regular basis. We complement that with synthetic and lab data that helps us evaluate what our user base can potentially feel under different situations. So with Google announcing a core with vitals last year, we welcomed it as another important indicator in our performance data to gain and offer additional transparency to field data of real user sessions. And all of this effort gladly showed us amazing results in the past year. But beyond just performance vision and performance culture, there's a critical realization that our team had, and I think all teams should have, and that is performance is a journey. It's not a one-time effort. You must realize that you need to make the commitment, take some leap of faith and great investment. But then, one step at a time, you must continue improving. You must stay vigilant and continue chasing the performance goal. And then you need to do it again, and again, and again. So as I said, we saw an amazing year-over-year improvement, and that was reflected in a 3x improvement in our all-green or past core web vitals and a huge 41% improvement in loading time across all geographies for all users. And the journey is not done yet. I mean, we're continuing on a regular basis on improving this and improving all of our numbers across all of our, as I said, geographies and users. So the recap or takeaway, I'd say, is great performance is always a challenge, but it's a challenge that can be met. It can be done, but you are never done. You have to set a vision, you have to have a focus, and you have to be ready for the journey, and the rest will follow. So let me close by saying thank you for letting us share our performance journey with you. Stay tuned. There is more to come. Thanks, Reuben. Those are some fantastic results, and I'd love to dig more into the Wix experience in the question period at the end. Fabian, I want to go to you next. The e-commerce space is incredibly competitive, but it's also very fast-moving. You had a really great model for thinking about making a rapidly changing site also perform well. Can you share a bit about that and your experience at C-Discount? Thank you, Vivek. Hello, I'm Fabian Polici, city of C-Discount. C-Discount is an e-commerce company with the second largest in France, and it's a challenge to try to be the best in a competitive world. Like Reuben said, web perf is a journey. It's impossible to slow down and do an easy test to evaluate business impact. You only can go forward to always move on to a better web perf. And so at the beginning, we ask ourselves, what is the definition of web performance? Is it an electric car using few energy available every time you need it, or is it a fight of jets? That go fast, but can be unavailable. And at C-Discount, we chose the first approach. So we developed a dedicated roadmap based on incremental optimization and monolith writing action to use less and less compute resources. And we saw a CWV continuous improvements, but it was hard to evaluate the business gain on a day-to-day basis with core web vital input. Customer journey is always evolving with fewer prices, new products, new offers. And so your experience changes every day, and your customer journey changes every day. So how do you find a base to evaluate the impact of web performance? You only can say we are in a good way to achieve a great goal. Business won't allow you to do an AP test and slow down your sites. So we had to find a scale to evaluate all the gain. And we saw during Black Friday that we gained 6% revenue on a day-to-day basis, comparison year to year, thanks to web performance and core web vital improvement. It was done with an uptime that was the better we ever had with 100% uptime on this day. And it was possible because all the work we did on core web vitals was a gain on all of the system. We closed bugs, we improved performance, we had less error, we had a stack trace that was better up to date. And so the gain was really a gain change in our company and our culture. And we know we were in a good way, but it was the proof that web performance is a business gain change. And so I would say to finish, that NPS is rising thanks to WebPerf. Customers are having a good time on our websites. Friend and family is also, and so never keep facing that web performance as a business game changer. Thanks, Fabian. I really like the connection between performance and uptime and NPS there. I want to bring in Giuseppe. GED had a unique approach to starting performance work with a smaller, newer product and then scaling up what you learned to the main properties. Can you tell us a bit about that experience Giuseppe? Hi, Paul. I'm Giuseppe Cobato, head of innovation and new technologies at JD Digital Tech Department. JD is a media company, publisher of 15 new sites, several magazines and web streaming radio stations. Before 2017, we didn't have a strategic path for web performance. And knowledge sharing was really low and inefficient across teams. Then we took the opportunity to develop a new premium content site while experiencing with emerging technologies such as Polymer, AMP, First Progressive Web Apps. And this server has a playground to upskill the team around performance-related objectives. The new site become one of the fastest newspaper sites on the K-metrics such as Time to First Byte and First Content Full Paint. All of these have been possible first by applying a critical rendering path optimization, making sure there is no CSS or JS that could potentially slow down our editorial content rendering time. Then we also spend a great time optimizing our site layout stability, for example, by reserving space for our images based on their aspect ratio. We used what we learned at the scaling this innovation to other main traffic sites such as La Stampa and La Repubblica, and we were able to measure the benefits. On La Repubblica, for example, in the BIAL site, we have measured 77 cumulative layouts shift and 26% almost larger content paint improvements on real traffic. We have been gradually rolling out these changes and this allowed us to measure the benefit on these main sites. For example, we had 8% of mobile bounce rate improvement. Our next steps are now to improve the cumulative layout shift by minimizing the impact of ads on site layout stability. Thanks Giuseppe. It reminds me of the old adage that it's often more profitable to keep an existing customer, or in this case a user, than to go out and find a new one. So I really like the use of bounce rate there and those are some impressive numbers. Let's briefly dive into a few areas each of you mentioned. Ruben, I'm curious about the unique position Wix occupies as a platform serving thousands of merchant sites. What are some of the considerations you faced when improving core revital scores and how do you think about the opportunities platforms have in supporting their customers here? So while I believe users should understand the balance between functionality and design choices they make and that impact on performance, I believe the greater responsibility is on the platform developers such as ourselves. We should and we do work very hard to deliver the best possible performance for our users, for whatever permutations of design and functionality they choose. And adding core web vitals is a good addition to our toolbox for that. From the user's perspective, we'll actually be rolling out the first version of a super cool tool shortly to help our users gain insights into the loading time and performance of their site, including both field data which anonymized from Wix sessions and lab data from Google paid-speed insights. So be sure to check it out. Thanks, Ruben. Fabien, you had a great set of outcomes at SeaDiscount and much of that came from a long multi-year journey across the organization. Can you talk a bit about how you maintain momentum within the organization, even if daily progress was sometimes challenging to observe? Change of culture and face was the essence of success. We had to measure everything on the user point of view to avoid to go in wrong direction. We had to share objective with business owners in order to work as a global team and prioritizing user story easily and commonly. And CO implication was a great boost in difficult times when we thought we were stuck to see business impact on back Friday was also a key achievement and a booster. Thanks, Fabien. Giuseppe, one challenge that always comes up with publishers is how to improve core with vital scores with display ads, particularly when dynamic ads can cause layout shifts. I'd love to hear how you tackle this at GED. Yeah, I mean, it is a big challenge because ad servers often delivery multi-size at the format and finding the right space to reserve. It's really a challenge. We are currently doing a lot of abit testing trying to find the different solutions or test different solutions. Some of them are working for our experience and so the idea is to take them to bigger sites and I think that the solution will come just doing tests and verifying which solution will work best in all the scenarios. Thanks, Giuseppe. And I wanna thank all of our partners today, Ruben Sherwin from Wix, Fabian Palletti from C-Discount and Giuseppe Cavetti from GED. And thank you for joining us. For more information on core with vitals, visit us online at web.dev slash vitals and enjoy the rest of Web Day. Thank you.