The PageSpeed Modules optimize your images to minimize their size and thus reduce their load time. They remove non-visible image information and apply high-efficiency compression techniques. This can result in a data saving of 50% or more.
Using PageSpeed Modules, you can focus on the content of your site, knowing your visitors will receive images in the best format and dimensions for their device and browser while using minimum bandwidth.
PageSpeed Modules can optimize most common image formats, including GIF, PNG, and JPEG, and convert them to PNG, JPEG, or WebP. GIF, PNG, and JPEG are supported by all browsers. WebP is a modern image format that can compress images over 25% more than older formats, and is currently supported by many browsers, including Google Chrome, Android 4.0+, and Opera. PageSpeed-optimized images are converted to the best format supported by the target browser, i.e., to WebP if it is supported, or PNG or JPEG if not.
PageSpeed can also maximize compression based on image content. Lossy formats compress images far better than lossless formats, but sometimes introduce visible and undesirable "compression noise". PageSpeed examines the content of images to see whether they are sensitive to compression noise and, if so, converts to PNG or the lossless mode of WebP; if not, it converts to JPEG or the lossy mode of WebP.
In-place optimization vs. tag rewriting
PageSpeed is capable of doing all this without changing your HTML or CSS, known as In-Place Resource Optimization (IPRO). However, if you allow PageSpeed to modify your HTML and CSS, it can do even more. For example, PageSpeed can shrink images to their actual rendered dimensions, thereby using fewer pixels and offering additional byte savings. It can also inline small images into HTML or CSS to avoid additional round trips to your server for fetching the images.
This table shows some examples of how PageSpeed can modify your HTML.
|Explanation||Image converted from GIF to PNG format and cache-extended.|
|Explanation||Image resized to 256 x 192 pixels, recompressed to PNG, and cache-extended.|
|Explanation||Image resized and then inlined into HTML as Base64 data. Because the inlined data has the desired dimensions, width and height are no longer needed.|
Tip: There are multiple ways to tell PageSpeed Modules not to modify certain images.
- To avoid modifying a group of images, e.g., images under a certain folder or images named after a pattern, you can use the Disallow option.
To avoid modifying the contents of an image, you can add a
Cache-Control: no-transformresponse header to the image. This header can be overridden by the DisableRewriteOnNoTransform option.
To avoid modifying an
imgtag, you can use the
<img src="do-not-modify.png" data-pagespeed-no-transform/>.
PageSpeed Modules support the most common image formats used on the web.
|GIF||A legacy but still popular image format. GIF is a lossless format, so the compressed image is visually identical to the original. It supports both single frame (still image) and multiple frames (animation). Despite its popularity, GIF often has poor compression performance, so PageSpeed converts GIF images to other (better) formats, unless the images are tiny.|
|PNG||A more recent lossless format designed as a successor to GIF for single-frame images.|
|JPEG||A lossy format where the compression process removes image detail that is difficult for the human eye to see. How much data to remove depends on the quality level. JPEG has two modes, baseline and progressive. Progressive mode can be used to render the image incrementally and has a higher compression ratio for large images.|
|WebP||A cutting-edge image format. While it is not yet supported in all browsers, it is becoming increasingly available. In addition to superior compression performance, it includes features of all other formats: lossy mode, lossless mode, transparency, and animation. WebP has added support for these features over time, so your visitor’s browser may support all, a subset, or none of these features. PageSpeed automatically detects the features which your visitor’s browser supports and only uses the supported features in optimization.|
PageSpeed Modules provide specific filters so you can control exactly how your images are optimized. For each visitor, PageSpeed Modules choose the best format and mode from the ones you allowed and the ones supported by the visitor’s browser.
To simplify configuration, PageSpeed Modules provide rewrite_images, a filter group that consists of the most common image optimizations. It allows recompression, transcoding to optimal formats, reduction of image dimensions, and inlining of small images into HTML or CSS. If you want to make more detailed adjustments, you can also enable or disable the individual filters:
- To PNG format: convert_gif_to_png, recompress_png.
- To JPEG format: convert_png_to_jpeg, convert_jpeg_to_progressive, recompress_jpeg.
- To WebP format: convert_jpeg_to_webp, convert_to_webp_lossless, convert_to_webp_animated, recompress_webp.
- General: inline_images, resize_images.
You can use any combination of the filter group and individual filters for your site. In each case, images are optimized only to the formats that are supported by your visitor’s browser, and images are replaced only when the optimized one is smaller than the original.
For images that are sensitive to compression noise, PageSpeed Modules always use lossless compression; for other images, PageSpeed Modules use the more aggressive lossy methods. For the lossy formats you can specify up to three quality levels, indicated by specific situations:
- When the user indicates a preference for reduced data usage.
- When the user visits your site from a mobile device. Mobile devices usually have a high device pixel ratio, so compression noise is less visible. In addition, mobile devices are more likely to use an expensive data channel.
- For all other cases, e.g., when the user visits your site from a desktop or tablet.
If your visitors have high transfer costs, slow connection speeds, or for other reasons, they may prefer reduced data usage. Some browsers, including Chrome, Opera, and Yandex, let visitors choose to send a Save-Data header when they request pages. You can honor their preference by allowing lower image quality for such requests.
The image quality levels can be specified using various parameters, listed here in order of precedence.
- Format-specific qualities for save-data: JpegQualityForSaveData and WebpQualityForSaveData.
- Format-specific qualities for mobile: JpegRecompressionQualityForSmallScreens, WebpRecompressionQualityForSmallScreens, and WebpAnimatedRecompressionQuality.
- Format-specific qualities for all other cases: JpegRecompressionQuality, WebpRecompressionQuality, and WebpAnimatedRecompressionQuality.
- Format-generic quality for all other cases: ImageRecompressionQuality.
Each parameter has a range of 0 - 100, representing lowest to highest quality. They can also be set to -1, indicating that the parameter should be ignored and the parameters of the lower precedences should be used. If all of the quality parameters are set to -1, images will not be optimized to any lossy format.
Tip: If you do not want to recompress lossy-format images or convert images to lossy formats, it is best to disable any filter that would optimize to JPEG or WebP. Setting all of the qualities to -1 wastes CPU to achieve the same result.
PageSpeed Modules can shrink an image to its actual display dimensions based on the design of the page, the visitor’s device, and the visitor’s actions, to ensure the best user experience without wasting pixels.
You can use the
resize_images filter to
shrink the image to the dimensions specified by the
height= attributes in the
<img> tag or by the
You can use the
filter to ensure your visitor sees full-resolution images, whether they are
using a retina-based or regular device. Sending full resolution images to all
devices is challenging because different devices may use a different number of
pixels (known as device pixels) for displaying a region of the page
(measured by CSS pixels). For example, a region of 100x100 CSS pixels in a
page is displayed using 100x100 device pixels on an iPhone 3, 200x200 device
pixels on an iPhone 6, and 300x300 device pixels on an iPhone 6+. For the best
visual effect using the least bandwidth, you can resize your image to 100x100
for iPhone 3, to 200x200 for iPhone 6, and to 300x300 for iPhone 6+. Using this
filter, PageSpeed generates images at all of these dimensions, and then
<img> tags so your visitor’s browser uses the
In addition to making the images smaller, PageSpeed Modules can help your page load faster by inlining images or previews into your HTML or CSS.
PageSpeed can inline small images directly into the HTML or CSS, reducing server requests. This is enabled by the inline_images filter, and is controlled by the ImageInlineMaxBytes and CssImageInlineMaxBytes options.
As well as inlining small images, PageSpeed can inline a reduced-quality version of large images into the HTML or CSS and, after the page is loaded, replace the low-quality image with the original. See Inline Preview Images for details.
PageSpeed Modules provide controls to make sure that your server is stable, your proxy/CDN (if any) is fully utilized, and your images are delivered to the user in the format you want.
Image optimization is an expensive process. To ensure the stability of your server, you can use ImageResolutionLimitBytes to limit the maximum dimensions of images to optimize, and ImageMaxRewritesAtOnce to limit the maximum number of images that are concurrently optimized.
To ensure that your proxy/CDN can handle the optimized images correctly, you can use AllowVaryOn to tell PageSpeed which request headers can be used to control image optimization. You can also use NoTransformOptimizedImages to instruct proxies not to further compress the images.
option can be used to tell PageSpeed how to respond to a request asking for a
WebP image when the browser does not appear to support WebP. In this case,
PageSpeed will normally return the image as a PNG or JPEG (whichever is most
ServeRewrittenWebpUrlsToAnyAgent is enabled,
PageSpeed will instead return the WebP unconditionally. Returning the image
depending on the headers ensures that your visitor sees the image correctly.
Returning the image unconditionally in WebP format is useful if you want to
serve WebP but your CDN or proxy removes headers from the request.
You can also ask PageSpeed to insert the image dimensions into
<img> tags so the browser can compute the layout of the
page before downloading the images. See
filter for more information.
Image optimization is not perfect, and its use can have some downsides. Here are some potential issues and suggested solutions.
Image optimization is both CPU- and memory-intensive.
You will probably see your server load increase while images are being rewritten, particularly immediately after server start. If the load increases too much, you can alleviate it by setting ImageMaxRewritesAtOnce and ImageResolutionLimitBytes. After the images have been optimized once, they will be cached for future use.
Reducing the dimension of an image or compressing it to a lossy format causes some image details to be lost.
This is sometimes noticeable, though usually not; you should inspect the optimized images to ensure their quality is acceptable.
PageSpeed removes metadata, such as copyright information.
If you want keep a specific image's metadata, add
It is possible to craft an image that, after re-compression, looks like HTML to certain browsers.
While PageSpeed adds proper content-type headers and headers that forbid content-type sniffing, some ancient browsers can still be tricked into rendering them as HTML. If you have user-submitted images, you should filter them before using them in your site.
Your beacons may need a new attribute.
If you use images as beacons to monitor page activity, you should add
Images may incur stretching distortion if you ask PageSpeed Modules to insert image dimensions.
If you use
Color profiles are removed by PageSpeed.
If your images contain color profiles, they are removed to save data. This is usually not a problem since most images with a color profile render indistinguishably when the color profile is removed.