Ilya GrigorikVerified account

@igrigorik

Web performance engineer at Google; co-chair of W3C Webperf WG. In short, an internet plumber.

San Francisco, California
Joined November 2007

Tweets

You blocked @igrigorik

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @igrigorik

  1. Pinned Tweet
    28 Jun 2016

    High Performance Browser Networking @ : {on,off}line perf best practices at your fingertips!

  2. Retweeted
    7h

    -03 versions of the QUIC drafts are dropping in this morning:

  3. 10h

    BBR, the new kid on the TCP block: - an in-depth look at evolution of TCP models. great read.

  4. 20h

    "A more apt name for our species would be Homo prospectus.. we thrive by considering our prospects":

  5. Retweeted
    May 19

    Want to move to HTTPS, but worried about SEO, ad rev, or perf? Check out how the move went for these three big sites

  6. May 18

    Gixy is a tool to analyze nginx configuration & prevent security misconfiguration / automate flaw detection: - nice.

  7. May 17

    kudos to AMP team for a continuous stream of perf improvements: - 50% less bytes on images & Brotli (-10%) for text!

  8. Retweeted
    May 17

    2 billion active Android devices. Quite a PWA platform.

  9. Retweeted
    May 12

    HTTP Archive: breakdown of web font use by format: woff2 70.4% woff 23.3% ttf 5.3% otf 0.9%

  10. Retweeted
    May 16

    This is why HTTP worked -- limited vocabulary of verbs means people can get their heads around it.

  11. May 15

    Tune in live on Thursday.. and level up your security chops!

  12. May 10

    a must read deep-dive on CSS variables: - they're (much) more powerful than you think.

  13. Retweeted
    May 9

    Solid introductory article on how web browsers work!

  14. May 9

    Why are app install banners still a thing? Hint, you're missing the (web) boat: - send this to your product manager.

  15. Retweeted
    May 7
    Replying to

    :) JS parse times on high-end phones + laptops vs. low-end/average are _so_ different. Hope we see more real-device testing as folks realize

  16. May 7

    The myth of a Superhuman AI: - the best rebuttal I've seen to date, courtesy of .

  17. May 5

    octoDNS: DNS as code + tool for managing DNS across providers: - nifty tool, courtesy of GitHub crew!

  18. Retweeted
    May 4
  19. Retweeted
    May 4
    Replying to and

    I did some analysis of this using the Wikipedia release/modification dates: . tldr: The avg age of jQuery is 3 years!

  20. May 4

    webhook: lightweight framework to easily create HTTP hook endpoints @ - useful.

  21. Retweeted
    May 3

    HTTP what? : I drew what HTTP is & how HTTP1.x and HTTP2 are different✨ (tweetzine, drawsplainer, codedoodles…I don't know what to call it)

    HTTP What? page 1 of 3. A browser gets data over the Internet. Internet is like a plumbing pipe of data.
    page 2 of 3. Protocol (P in HTTP) is a communication rule between client (browser)  and server. Explanation of HTTP1.x
    page 3/3 HTTP2 is a different (new) communication rule that use more efficient data transport method. Explanation of HTTP2

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·