4 ms·
AMP literally has a built in 1 second delay to render outside of Google, non AMP content, that is the "Nice comparative boost". It has nothing to do with "pre
by throwaway2048 5y ago
AMP literally has a built in 1 second delay to render outside of Google, non AMP content, that is the "Nice comparative boost".
It has nothing to do with "pre rendering" its built right into the CSS.
- cerved 5y agohow is this done in CSS?
- DocTomoe 5y agoI think there is confusion about the term "rendering" here. The term "rendering" is used (a) to describe the actual translation of textual-instructive HTML/CSS/Javascript into a graphical representation within a browser window and (b) to describe stuff being loaded into a page via Javascript, most prominently ads, and more oriented towards load time ("How long until the page has finished loading" = "rendering time"). With CSS, you can define pixel-perfect areas for stuff to be rendered into, which makes the browser not having to decide on the size of the area after it has loaded further material from third-party sources. Doing so reduces "screen flickering", which is generally annoying (and the major reason why I block ads with a vengeance). This can be described as "pre-rendering" when you understand rendering as (a).
- MichaelJanssen 5y agoAMP sites have a 8 seconds-delayed CSS animation on the body element, turning visibility from hidden to visible. This animation is turned off instantly (as far as I can say) by Javascript. However when you block Javascript entirely or block ampproject.org you have to endure the whole 8 seconds. I inject "body {animation: none !important}" into all pages to remedy this.
- cerved 5y agoIs it possible to see this in action on desktop?
- lern_too_spel 5y agoThat slows down AMP pages relative to nom-AMP pages when JavaScript is disabled. This is not in the complaint.