The document appears to be a series of slides by Tim Kadlec on various technical SEO topics. Some key points covered include:
- The benefits of AMP for page speed due to reduced payload and third party requests. However, AMP pages initially render slower due to asynchronous loading of custom elements.
- Caching and pre-rendering pages on a CDN improves AMP performance versus loading from the main domain.
- Google contributes the vast majority of code to the AMP Project and many see it as a way for Google to influence web standards.
- Progressive Web Apps (PWAs) are discussed as an alternative to native apps that can provide app-like experiences through the browser.
79. Tim Kadlec | @tkadlec | #TechSEOBoost
<script async>
80. Tim Kadlec | @tkadlec | #TechSEOBoost
3. Why is AMP on the CDN better?
81. Tim Kadlec | @tkadlec | #TechSEOBoost
• Caching images and fonts
• Restricting maximum image sizes
• Compressing images on the fly
• Uses HTTP/2 and HTTPS
• Strips out HTML comments
• Automates inclusion of resource hints such
as dns-prefetch and preconnect
• Pre-rendering the page on the server
82. Tim Kadlec | @tkadlec | #TechSEOBoost
• Pre-rendering the page on the server
83. Tim Kadlec | @tkadlec | #TechSEOBoost
bit.ly/2AuWNkh
84. Tim Kadlec | @tkadlec | #TechSEOBoost
25%
of contributors
work at Google
85. Tim Kadlec | @tkadlec | #TechSEOBoost
90%
of contributions
come from Google
86. Tim Kadlec | @tkadlec | #TechSEOBoost
bit.ly/2Qt2pp8
87. Tim Kadlec | @tkadlec | #TechSEOBoost
bit.ly/2SkMdns
88. Tim Kadlec | @tkadlec | #TechSEOBoost
Feature-Policy: unsized-media 'none'