6 ms·

I like how you kept the site and dependencies simple. 34.7KB of js (~21 is mostly color definitions), and 4.2KB of css. Just FYI: 1. You could save ~15.75kb

I like how you kept the site and dependencies simple. 34.7KB of js (~21 is mostly color definitions), and 4.2KB of css. Just FYI: 1. You could save ~15.75kb by minifying your JS/CSS (a bit nit-picky since your resources are a fraction of what most sites have) 2. The 1MB background image comes out to 570.6 KB through tinypng.com (47% off!). If lossless is more your thing, you could save about 5% by running it through something like imageoptim.

coreymaass 9y ago
If you're willing to go lossy, also look at PNGQuant - https://pngquant.org/ https://pngquant.org/ I've started using it on all of my web images. I've yet to see the loss on a couple dozen images, but the size drops by up to 66%, even after being run through imageoptim.
- tehlike 9y ago
  Webp is much better for compression, but is support does not exist.
- kookiekrak 9y ago
  tinypng is actually based on pngquant + more optimizations not in pngquant
mizaru 9y ago
30MB for the app itself seems excessive, though.
- trevor-e 9y ago
  Most of that is probably due to Swift's runtime library.
  - developer2 9y ago
    Surely if you're using core Swift, or core Objective-C, the runtime is a shared lib shipped with the OS? I can't imagine that every single app built on Swift or Objective-C is bundling the exact same foundation? That seems so unlike Apple to miss such a massive optimization to reduce the download size of nearly every app. I can understand there being exceptions with some apps that use custom setups, but surely the majority of apps are written in XCode using exactly what is provided as a toolset.
    - simonbarker87 9y ago
      I'm not an expert in the why, but as far as I am aware the whole of Swift is shipped as part of each app as it is still being developed. There is a road map to ship with the OS I believe but it's not for a while
      - connoljo 9y ago
        It's because swift doesn't have ABI stability yet.
        simonbarker87 9y ago
        Thanks
    - nicky0 9y ago
      > I can't imagine that every single app built on Swift or Objective-C is bundling the exact same foundation In fact, every single app built on Swift is bundling the full set of runtime libraries, both on iOS and Mac. This will continue until the Swift ABI is finalised. This is why I don't ship Swift yet.
_kush 9y ago
Usually, my website projects have a couple grunt tasks running for image compressing, minimizing files, etc., but for this landing page, I just went with the basic HTML and CSS workflow. I realized how easy it was to create a website when there was no grunt or other dependencies haha. However, I'll definitely be optimizing the files. Thank you for the tip!

coreymaass 9y ago

If you're willing to go lossy, also look at PNGQuant - https://pngquant.org/ https://pngquant.org/ I've started using it on all of my web images. I've yet to see the loss on a couple dozen images, but the size drops by up to 66%, even after being run through imageoptim.

tehlike 9y ago
Webp is much better for compression, but is support does not exist.
kookiekrak 9y ago
tinypng is actually based on pngquant + more optimizations not in pngquant

mizaru 9y ago

30MB for the app itself seems excessive, though.

trevor-e 9y ago
Most of that is probably due to Swift's runtime library.
- developer2 9y ago
  Surely if you're using core Swift, or core Objective-C, the runtime is a shared lib shipped with the OS? I can't imagine that every single app built on Swift or Objective-C is bundling the exact same foundation? That seems so unlike Apple to miss such a massive optimization to reduce the download size of nearly every app. I can understand there being exceptions with some apps that use custom setups, but surely the majority of apps are written in XCode using exactly what is provided as a toolset.
  - simonbarker87 9y ago
    I'm not an expert in the why, but as far as I am aware the whole of Swift is shipped as part of each app as it is still being developed. There is a road map to ship with the OS I believe but it's not for a while
    - connoljo 9y ago
      It's because swift doesn't have ABI stability yet.
      - simonbarker87 9y ago
        Thanks
  - nicky0 9y ago
    > I can't imagine that every single app built on Swift or Objective-C is bundling the exact same foundation In fact, every single app built on Swift is bundling the full set of runtime libraries, both on iOS and Mac. This will continue until the Swift ABI is finalised. This is why I don't ship Swift yet.

_kush 9y ago

Usually, my website projects have a couple grunt tasks running for image compressing, minimizing files, etc., but for this landing page, I just went with the basic HTML and CSS workflow. I realized how easy it was to create a website when there was no grunt or other dependencies haha. However, I'll definitely be optimizing the files. Thank you for the tip!