Live data from Hacker News

Getting Postmark’s Lighthouse Performance Score to 100

wildbit.com

1–10 of 39 posts

Re: Getting Postmark’s Lighthouse Performance Score to 100

#6
post #4
post #3

I am not sure whether 20 development days invested for a postmark score is a good time investment.

It looks like the accessibility score went down , too.

Hi, author here. Accessibility score went from 87 to 96. The second screenshot with a score of 86 was a preliminary result after introducing the fake widget. (Best Practices went from 86 to 100.)

Re: Getting Postmark’s Lighthouse Performance Score to 100

#8

https://lighthouse-dot-webdotdevsite.appspot.com//lh/html?ur... web.dev says 66 though

https://developers.google.com/speed/pagespeed/insights/?url=... shows 99-100 every time I load it ¯\_(ツ)_/¯

Our mobile score is lower (86 according to PageSpeed), but I mention that in a blog post.

Re: Getting Postmark’s Lighthouse Performance Score to 100

#10
The problem with being a slave to these Lighthouse scores is the test is only concerned with the one page you are testing. If you assume your visitor will only visit a single page on your site that's fine, but even if they visit a second page, nearly everything it suggests you do will make that second page load slower than if you had developed the page using the traditional methods- external CSS/JS files that apply to your entire site and can be cached.
Post reply on HN