“But I already have a fast site!” or: For That Instant Feel
Articles,  Blog

“But I already have a fast site!” or: For That Instant Feel


[MUSIC PLAYING] PAUL BAKAUS: After
hearing about AMP, you might be
thinking, wait, I get that AMP solves performance
issues for sites that don’t know better, but I do. My site is already pretty fast. And hey, good for you. If everyone was
like you, maybe we wouldn’t need AMP
in the first place and the mobile web would have
been fast and user-friendly from the get-go. So why can’t you, who built a
perfectly fine mobile site, be in Google’s top stories
carousel, or anywhere else AMP has surfaced? And the answer is that platforms
would love to, but they can’t. Even though I can see that your
page is fast with my own two eyes, it’s actually
surprisingly hard to measure it reliably
with a computer. A bit like it’s relatively
easy for humans but crazy hard for computers to
distinguish between a snake from a shoelace. Web developers and
platforms everywhere are working hard at solving
the problem of reliable speed measurement with promising
projects like Lighthouse, but in reality we’re
simply not there yet. And even in the future
where we, the web community, is able to reliably measure
your site’s performance, we’re still only halfway there. AMP has a few
tricks up its sleeve that go far beyond simple
performance improvements. Take, for example, the static
layout system used in AMP. It ensures that every
element on the page has a known width and height,
even before external assets have finished loading. Something that’s
done at HTML can’t guarantee, as any picture
without its defined size could push content down. And here’s the key. By doing that, AMP
can make a prediction of what the user actually sees
when they arrive on a given AMP page. With that intelligence,
a platform like Google can request a preloading
of multiple AMP pages at the same time
because each just preloads the first viewport,
making it very cheap to do so. This explains ultimately why
AMP pages don’t just feel fast, but near instant. In order to achieve this
intelligent viewport preloading on normal websites, we’d have to
quite heavily change or extend the CSS specification, which
isn’t impossible per se but will take a
little bit more time. In the meantime, in the spirit
of the extensible web manifesto, we’re
sticking to a solution that offers these capabilities
and many more today. And that’s AMP. The perfect is the enemy of
the good, as the saying goes. But we want to get to perfect. If you’re a developer,
help us find the right long-term solutions,
maybe even web standards, that will upgrade
not just AMP pages, but every site on the web. Subscribe for more of this and
get in touch via the comments below on Twitter. Onwards. [MUSIC PLAYING]

2 Comments

  • Jay Holtslander

    I think the key to adoption is idiot-proof WordPress and CMS integrations.
    All too often I see AMP errors using the official AMP plugin for WordPress.

  • Luis Chávez

    Hola, una pregunta muy importante. Porque ustedes no facilitan un script de estilos, en los cuales los webmaster tengan la facilidad de obtener los estilos desde AMP. Hablo de implementar un poco de Bootstrap y de material design. Espero que haya entendido mi pregunta. Para ello le remito una direccion URL creada en Blogger.com, es la siguiente: http://ampcolibri.blogspot.com/ he implementado una plantilla de Blogger en AMP HTML. Espero su respuesta. Buen trabajo los felicito. Me gusta Amp HTML.

Leave a Reply

Your email address will not be published. Required fields are marked *