Q: Why did you decide to rewrite the whole image handling instead of just relying on the jekyll_picture_tag gem (https://github.com/rbuchberger/jekyll_picture_tag) - I am using that since years and it just works just fine.
How I fixed my blog's performance issues by writing a new Jekyll plugin
11–20 of 49 posts
Re: How I fixed my blog's performance issues by writing a new Jekyll plugin
#12I use Jekyll for my company website [1] and managed to get a lot of speed optimisations simply by using a post-processing tool on the statically generated output. The tool I use is Jampack and I'd highly recommend it: https://jampack.divriots.com For my product website, it reduced the overall size by 590MB or approximately 59% in size, along with changing the HTML/CSS to make the optimisations that this article notes…
Re: How I fixed my blog's performance issues by writing a new Jekyll plugin
#13Just sharing another approach where you keep the YouTube embed iframe, but replace the domain "youtube.com" by this specific domain "embedlite.com". It loads only the thumbnail of the video and when someone clicks on it, it loads the full YouTube player.
More info: https://www.embedlite.com
Re: How I fixed my blog's performance issues by writing a new Jekyll plugin
#14I have a blog with pagespeed score of 98 but still got several pages de-indexed from google. Guess my content isn't that important.
Re: How I fixed my blog's performance issues by writing a new Jekyll plugin
#15Re: How I fixed my blog's performance issues by writing a new Jekyll plugin
#16So I let Claude write it. I told it I wanted a simple static website without any js frameworks. It made the whole thing. Any time I add a blog post, it updates the blog index page.
The site is, of course, very fast. But the main gain, for me, was not having to figure out how to get the underlying tech working. Yes, I'm probably dumber for it, but the site was up in a few hours and I got to go on with my life.
Re: How I fixed my blog's performance issues by writing a new Jekyll plugin
#17While that may be great for Google Pagespeed, it leads to issues that wouldn't exist with a static page and a degraded experience for the end user. I'm not sure if the issue is related to the plugin discussed in the article.
With this being said, I can see many use-cases for such a plugin. Having compile-time image transformation/compression is really nice.
Re: How I fixed my blog's performance issues by writing a new Jekyll plugin
#18Re: How I fixed my blog's performance issues by writing a new Jekyll plugin
#19Why is the automatic assumption foe something not being updated for a few years to be abandoned instead of done? Are libraries not allowed to be stable/done?
Re: How I fixed my blog's performance issues by writing a new Jekyll plugin
#20> And at this point, the library seems to have been abandoned as it hasn't been updated in over 5 years. Why is the automatic assumption foe something not being updated for a few years to be abandoned instead of done? Are libraries not allowed to be stable/done?