For me it’s: Just make the mobile web fast again - framework agnostic.

1. AGREE:
AMP ≠ SILVER BULLET.
JUNG VON MATT/NEXT ALSTER

2. 2
AMP ==
JUST A GOOD WEB COMPONENT FRAMEWORK WITH SOME
ADDITIONAL FEATURES FOR THE SEARCH ACCESS
(PRELOADING FROM SEARCH).

3. 3
ONE GOAL:
JUST MAKE THE MOBILE WEB FAST AGAIN, FRAMEWORK
AGNOSTIC!

4. 4
BUT TO BE FAIR,
YOU MISS SOME AMP ADVANTAGES.

5. 5
• AMP helps to keep the performance standards save in a
project - that is sometimes very hard in a multi stakeholder
environment.
• These standards are in particular:
Minimizing Round-Trip’s, max. 50kb inline CSS, no iFrames in
the Viewport, no custom JavaScript, etc.
AMP advantages:

6. 6
Feedback on your BMW.com
bashing ;-) - slide19.

7. 7
BMW Performance on
webpagetest.org (3G
1,6 Mbps,
https://goo.gl/dHejzA
and Page Speed
Insights
https://goo.gl/NeVwGv

8. 8
According to Chrome User
Experience Report we have a
first contentful paint of 0.5s
and DOM Content Loaded of
0.6s - which is definitely in the
upper third of the pages
(#realdata).

9. Of course we used WOFF2 in the bmw.com, WOFF is only from backward
compatibility in the CSS. The modern browsers ONLY load the WOFF2 file.
WOFF / WOFF2:

10. We already used the Akamai Image Manager for optimal image
delivery. JPEG 2000 for iOS and Chrome for the WebP format.
Proper compression:
iOS Response Chrome Response

11. 11
THANK YOU FOR YOUR
CACHING HINTS, ALWAYS A
MOVING TARGET IN THIS BIG
INFRASTRUCTURE
PROJECTS :-).
CACHING STRATEGIES:

12. Incidentally, bmw.com is missing on page 9 ;-).

13. LET'S SAVE THE OPEN WEB!
JUNG VON MATT/NEXT ALSTER