How I fixed my blog's performance issues by writing a new Jekyll plugin
1–10 of 49 posts
Re: How I fixed my blog's performance issues by writing a new Jekyll plugin
#2Almost all audio, images, and videos are rather ornamental, and the content will be OK without them. I try to have all content as standalone on its own as possible. For instance, the posts follow the pattern "_posts/YYYY/YYYY-MM-DD-url-goes-here.md," so I know where the yearly content is, despite each post having its own designated published date. I also have a folder "_posts/todo" where published (but work-in-progress) and future dated posts live.
For images, I stopped worrying about serving multiple sources. I optimized it somewhere between good enough for both mobile and higher (I now consider tablet and desktop the same).
Re: How I fixed my blog's performance issues by writing a new Jekyll plugin
#3The 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
#4I 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
#5Re: How I fixed my blog's performance issues by writing a new Jekyll plugin
#6I 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…
Do you mean KB or do you have a 1GB website??
Re: How I fixed my blog's performance issues by writing a new Jekyll plugin
#7Re: How I fixed my blog's performance issues by writing a new Jekyll plugin
#8And yet when I open the page it first loads without CSS and then after 0.5s applies the style.
Re: How I fixed my blog's performance issues by writing a new Jekyll plugin
#9Earlier quoted context omitted.
Do you mean KB or do you have a 1GB website??
They are most likely referring to the overall size of the whole website including all generated HTML for posts, static content, styles etc.
Re: How I fixed my blog's performance issues by writing a new Jekyll plugin
#10And yet when I open the page it first loads without CSS and then after 0.5s applies the style.
This is deliberate FOUC. Why, I have no notion whatsoever. It should read: