Ivan Akulov

@iamakulov

JS developer, web performance consultant. Google developer expert. Running . Opinions are my own. 🏳️‍🌈 He/him

Vrijeme pridruživanja: siječanj 2015.

Tweetovi

Blokirali ste korisnika/cu @iamakulov

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @iamakulov

  1. Prikvačeni tweet
    9. velj 2018.

    🎉 Super glad to announce that I & made a web performance guide for webpack! — Making front-end smaller — Improving caching — Monitoring it to stay fast Live at Web Fundamentals:

    Prikaži ovu nit
    Poništi
  2. proslijedio/la je Tweet
    31. sij

    Okay, it’s Friday – let’s have some web perf fun! 1) Run a webpack build with webpack-bundle-analyzer 2) Take a screenshot and reply to this tweet 3) I’ll dig and see what to improve!

    Poništi
  3. 31. sij

    Okay, it’s Friday – let’s have some web perf fun! 1) Run a webpack build with webpack-bundle-analyzer 2) Take a screenshot and reply to this tweet 3) I’ll dig and see what to improve!

    Poništi
  4. 27. sij

    📝 Half-a-year ago, I wrote a blog post – and today, I finally realized how it should look and rewrote it. “Quick apps in 3 steps”: three things that’d help to make an app faster if you have don’t have time for this at all →

    Poništi
  5. proslijedio/la je Tweet
    7. sij

    🚀 New article: how I use service workers to cut my site's HTML payload size (and FCP) in half! This is a fairly advanced technique, but it's one of the best ways I know to improve perf—and users with limited data plans will thank you! 🙏

    Poništi
  6. proslijedio/la je Tweet
    18. pro 2019.

    Announcing Treo Sites – Real user monitoring with zero-setup 🎉 🎊 🔥 🎯 User experience metrics without setup and tracking 🔍 Competitive analysis based on real-world data ⚙️ Powered by Check it out 👇

    Prikaži ovu nit
    Poništi
  7. 13. pro 2019.

    TIL about HTTP/2 coalescing. It’s a way for browsers to re-use a single connection for different domains – and it helps to work around domain sharding (= , , ...). Here’s how it works in practice:

    Poništi
  8. proslijedio/la je Tweet
    10. pro 2019.

    A tale from the ongoing performance journey of . Or, how we got rid of one performance cliff in the Network panel & the workflows and tools that got us there. Starting with: 🧵 by /

    Prikaži ovu nit
    Poništi
  9. 6. pro 2019.

    A different piece of data: Instagram removed all Babel syntax transforms and got bundles that are 6% smaller

    Prikaži ovu nit
    Poništi
  10. proslijedio/la je Tweet
    27. stu 2019.

    I've written some thoughts about what the key technologies of 2020 could be. Spoiler alert: not 5G or HTTP/3.

    Poništi
  11. 22. stu 2019.

    Tip from , hot off the press: When you’re profiling a website performance, type `-has-response-header:Content-Encoding` into the network filter. This will find you all resources that are not compressed with gzip/Brotli (= are a good low hanging fruit to optimize)

    Poništi
  12. 21. stu 2019.
    Poništi
  13. proslijedio/la je Tweet
    20. stu 2019.

    Time for a review of 100 perf-related webpack plugins by so that you don’t have to. Thank you!

    Poništi
  14. proslijedio/la je Tweet

    The --enable-gpu-benchmarking flag exposes a wealth of low-level graphics statistics. Good for CI regression testing

    Poništi
  15. 18. stu 2019.

    4) Lighthouse 6 (coming in Jan) is going to change the scoring algorithm. It will replace two metrics and change their weights. This means that somewhere in 2020, when PageSpeed Insights gets updated to use it, your site’s score can suddenly change.

    Prikaži ovu nit
    Poništi
  16. 18. stu 2019.

    3) Lighthouse is getting three new metrics: — Largest Contentful Paint: — Total Blocking Time: — Cumulative Layout Shift: (Description in screenshots)

    Prikaži ovu nit
    Poništi
  17. 18. stu 2019.

    2) Google released 4 React hooks to help you write different logic if: — the connection is slow — the client asks to save data — the device isn’t powerful (CPU or memory are low) No good SSR support yet though.

    Prikaži ovu nit
    Poništi
  18. 18. stu 2019.

    1) Chrome is going to visually mark slow sites. A possible – not finalized – UX is in the picture. It’s interesting whether this will result in users waiting for slow sites for longer (because they get visual feedback sooner) or for shorter (because they get told a site is slow)

    Prikaži ovu nit
    Poništi
  19. 18. stu 2019.

    Calibre summarized all performance announcements from Chrome Dev Summit: 🖤 Here’re my summary of their summary + extra notes, in one thread ↓

    Prikaži ovu nit
    Poništi
  20. proslijedio/la je Tweet
    15. stu 2019.

    In 2013 I was considering doing a JS/asm talk "from the future". Then 's "The Future of Programming" came out, set in 1973. That made me hurry up and do "The Birth & Death of JavaScript" in case this conceit became overused. (It did not!)

    Prikaži ovu nit
    Poništi
  21. 13. stu 2019.

    TL;DR: polyfills affect the bundle size a lot, whereas syntax transforms almost don’t. Use or serve different bundles for different user agents to ship less code

    Prikaži ovu nit
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·