Skip to content
By using Twitter’s services you agree to our Cookies Use. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.
  • Home Home Home, current page.
  • About

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
slightlylate's profile
Alex Russell
Alex Russell
Alex Russell
@slightlylate

Tweets

Alex Russell

@slightlylate

Chrome Project 🐡 & Web Standards TL; Blink API OWNER Named PWAs w/ @phae; probably making her ☕ DMs open. Tweets my own; press@google.com for official comms.

San Francisco, The Internet
infrequently.org
Joined December 2010

Tweets

  • © 2020 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Imprint
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    1. Andy Davies‏ @AndyDavies 15 May 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @addyosmani @johnwilander and

      Did something similar for my SmashingConf talk - basically grab timeline JSON for HTTPArchive run, and run it through 3rd-Party-CPU abuser (https://github.com/andydavies/3rd-party-cpu-abuser …) @paulcalvano’s approach might be quicker though

      1 reply 0 retweets 13 likes
    2. Paul Calvano‏ @paulcalvano 15 May 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @AndyDavies @addyosmani and

      @AndyDavies 3rd-party-cpu-abuser modification is super useful. I occasionally combine it with an analysis of requests and byte sizes from WPT. For example, how much 3rd party content loaded before start render, or first meaningful paint, or in this example before a interstitial.pic.twitter.com/oMQhhNPytC

      1 reply 0 retweets 5 likes
    3. Paul Calvano‏ @paulcalvano 15 May 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @paulcalvano @AndyDavies and

      There are a few @HTTPArchive discussion forum posts on 3rd party content - and we can do some deeper analysis to try to understand how performance trends based on % of 3rd party content. Would be really interesting to combine HA analysis w/ CrUX response times for this...

      1 reply 0 retweets 3 likes
    4. Paul Calvano‏ @paulcalvano 15 May 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @paulcalvano @AndyDavies and

      This graph illustrates the ranges of load times for the top 10K Alexa sites. I used @igrigorik's regex for 3rd party classification (https://discuss.httparchive.org/t/what-is-the-distribution-of-1st-party-vs-3rd-party-resources/100/11 …) + CrUX onLoad metrics. There is definitely a strong correlation between % of 3rd party content and load times!pic.twitter.com/MSmDieqdKE

      2 replies 4 retweets 18 likes
    5. Addy Osmani‏Verified account @addyosmani 15 May 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @paulcalvano @AndyDavies and

      So great to see this with CrUX data factored in. Thanks for investigating, Paul!

      1 reply 0 retweets 3 likes
    6. Alex Russell‏ @slightlylate 15 May 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @addyosmani @paulcalvano and

      What metric was being used for "load time" here?

      2 replies 0 retweets 1 like
    7. Addy Osmani‏Verified account @addyosmani 15 May 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @paulcalvano and

      CrUX has FP, FCP, DCL and onLoad (no TTCI/FID just yet). We can cross reference origins with their metrics in Lighthouse from WPT (TTCI) which should show sites with higher TTCI are referencing more third parties.

      2 replies 0 retweets 7 likes
    8. Alex Russell‏ @slightlylate 15 May 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @addyosmani @paulcalvano and

      yeah, I expect the correlation to hold (strongly) as we use more-inclusive metrics (TTI/FID). Was just wondering how so many of those reports seemed to show < 2s ;-)

      2 replies 0 retweets 4 likes
    9. Andy Davies‏ @AndyDavies 15 May 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate

      What’s FID? guessing First Interactive something?

      1 reply 0 retweets 0 likes
    10. Alex Russell‏ @slightlylate 15 May 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @AndyDavies

      First Input Delay:https://developers.google.com/web/updates/2018/05/first-input-delay …

      2 replies 1 retweet 3 likes
      Alex Russell‏ @slightlylate 15 May 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @slightlylate @AndyDavies

      Basically, we were never able to agree about how to measure TTI well in the field, so FID is our closest proxy metric.

      12:48 PM - 15 May 2018
      0 replies 0 retweets 0 likes

      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.

        Promoted Tweet

        false

        • © 2020 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Imprint
        • Cookies
        • Ads info