AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Gulp imageoptim11/6/2022 ![]() I have only a few npm dependencies in my package.json ( see the gist): Jekyll does handle SASS out-of-the-box, but falls short as soon as you need concatenation, minification, Javascript dependencies… For that you’ll need something like Grunt and Gulp. You can cut images’ size down by over 50%. #Gulp imageoptim windowsPersonally, I drop my entire Jekyll folder into something like ImageOptim (I’m sure you can find an equivalent for Windows or Linux), and I get lossless compression in a few minutes. With the explosion of screen-wide pictures, retina screens, and the like, you may want to spend a couple minutes thinking about this issue. Most of your pictures are probably not optimized for the Web. Let’s get started, shall we? Step 1: Optimize your pictures It is still, as of today, the most convenient hosting solution for Jekyll websites. Last thing to mention before we delve into the steps necessary to reach these two goals: I’ll be assuming in some cases that you use GitHub pages. Keep in mind that the loading speed of your website also affects your SEO getting a high score on Google’s PageSpeed Insights should be a priority. This is where static generators can really shine. If you’re on Jekyll 3 ( now supported on GitHub pages), you can get some insights on this part using the Liquid profiler with the -profile flag.įast loading: you want your website to load as fast as possible. As the number of pages on your site grows, Jekyll can become painfully slow to build. There are mainly two things we’ll be attempting to reach:įast generation: this mostly impacts your life as a developer (and potentially an editor). ![]() Let me first clarify what I mean by fast. I shared these discoveries at JekyllConf 2016 and I thought I’d offer some more details about what it is that we do to build fast Jekyll websites. Over the past 6 years, we went on to build a ton with it: simple landing pages, developer documentations, Open Source communities, blogs like this very website, and Web apps (for example the subnational data browser for the World Bank).Īnd along the way, we figured out a thing or two when it comes to performance. Getting back to building actual HTML pages and not fighting some “framework” was refreshing, but what made me and my team fall in love with it was its speed. I started using Jekyll (or rather GitHub pages) about 6 years ago after years of disappointment with the CMS space (I’m looking at you, Drupal). ![]()
0 Comments
Read More
Leave a Reply. |