Changelog: May 26, 2017

Updated Caching Options

To make best practices for caching with imgix easier and clearer, we made a couple of changes:

  • Introduced new caching options on the Source configuration page, so you have more granular control over how imgix interacts with any Cache-Control: max-age headers present on your Master images.
  • Updated the Source setup guides (Amazon S3, Web Folder, and Web Proxy) to more clearly explain the behavior of each caching option and how best to set it.

imgix-core-js 1.0.6

  • Fixed a pair of bugs when signing URLs where the path component contained URL-encoded characters.

Dashboard

  • Fixed an issue with the URL signing tool where full URLs with query strings provided as the “path” component of the URL were getting their query strings appended to the resultant signed URL rather than encoded and signed properly.
  • Fixed a bug in the source editing & creation views where error messages were not being shown properly when submitting invalid S3 credentials.

Docs

  • Fixed font readability issues on Windows.

Changelog: May 12, 2017

New Edge Nodes

  • Expanded our CDN with a new node in São Paulo, Brazil, following recent nodes in Dubai, Madrid, Paris, Johannesburg, Montreal, and Toronto.

Updated Page Weight Tool

  • Refreshed Page Weight with improved feedback & suggestions about how to optimize your website’s images.

Expanding the Reach of Your Images

Today, we’re announcing expansion of our network to 33 edge nodes worldwide, with support for a new node in São Paulo, Brazil. We now have nodes in more than 16 countries worldwide, including recent additions in Dubai, Madrid, Paris, Johannesburg, Montreal, and Toronto.

Read the rest >

Find and Fix Your Heaviest Images with Page Weight

Page load speed continues to be a primary concern for websites. With increasing numbers of customers accessing sites on mobile connections, and markets expanding into areas with uneven broadband coverage, load times have a big impact on conversion.

But “speed” can be a nebulous measure. We recommend using page weight, or the combined file sizes of every element on a page, as a proxy. Unlike speed, it’s objective, measurable and actionable. Slow because of a heavy page? Find the heaviest elements and try to shrink them.

Images are often up to 70 percent of a page by weight. That means image optimization is usually an easy win. Yet it’s not always easy to know where to start. Last year, we launched Page Weight, a tool designed to guide you to your worst-performing images quickly and provide straightforward optimization suggestions. Today, based on feedback from users, we’re launching an improved version that makes picking that low-hanging fruit even easier.

Read the rest >

Changelog: April 21, 2017

Dashboard

  • Fixed a bug that was preventing AWS credentials from being updated when re-enabling a source.

 Next Page