Live data from Hacker News

How I fixed my blog's performance issues by writing a new Jekyll plugin

arclight.run

1–10 of 49 posts

Re: How I fixed my blog's performance issues by writing a new Jekyll plugin

#2
Honestly, I believe you have made it a tad complex than it needs to be. I migrated to Jekyll from WordPress about 4 years ago. It does have all 100s in Google PageSpeed. I used Jekyll as just another tool so I can stick to GitHub Pages. There is nothing tied to anything, and I can move all the Markdown contents to another system within hours, if not minutes. I can also upload the generated HTML via FTP, and it will work as well.

Almost 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).

https://brajeshwar.com/2021/brajeshwar.com-2021/

Re: How I fixed my blog's performance issues by writing a new Jekyll plugin

#3
I 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.

[1] https://www.magiclasso.co/

Re: How I fixed my blog's performance issues by writing a new Jekyll plugin

#4

I 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

#6
post #4

I 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??

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

#9
post #6
post #4

Earlier 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.

1gb is huge even for a whole website. Unless there are videos or hundred of high definition photos. Curious to know what makes up this space.
Post reply on HN