Craig Debbo: check the 2nd Q within the above FAQ section - tried to give a little front-loading to this common question as the publishing/communication portfolio grows from Microsoft and partners. We certainly are focused on performance throughout the platform for whatever sites you build, with great emphasis on how quickly they provision, and how easy it is to add content (pages, news, web parts (custom and 1st party), etc.. We publish network optimization guidance at http://aka.ms/tune where the SPO materials at that site focus on best practices and troubleshooting for portals built on SharePoint Online sites with the publishing features turned on. This, too, is an area of investment so that any site built on the publishing infrastructure will receive performance gain on both how we'll update the service with items we can adjust, plus bolstering any guidance and best practices we can put forth via the aka.ms/tune site. Your root site, in the way you describe, is focused on your company intranet portal. We, too, at MS support our copany intranet (we call it MSW) running in SPO using the publishign infrastrucutre, and we're all excited - including our Microsoft IT team - about using communication sites in parallel to existing team site and portals. In fact, we - the SharePoint, OneDrive and Yammer marketing team - propped up a the first commercially used SharePoint Communication site so that we could help spread awareness about what we announced at #SPSummit, and ongoing as a solid destination for our field sellers and partner teams to learn more about SP, OD and Yam; we call this site our SOY site. Want a little SOY sauce. Beyond the pun fun, it's a crucial tool for us to inform and engage our internal peers on all things SOY!