- Getting Started
Development flow integration
- No small error pages
- AMP HTML validator
- No vulnerable libraries
- Avoid HTTP redirects
- Avoid CSS limits
- Optimal compression
- Correct manifest extension
- Babel configuration hint set
- Correct `Content-Type` header
- Performance budget
- HTTP cache
- Correct viewport
- Disallowed HTTP headers
- External links disown opener
- TypeScript configuration hints set
- Modern DOCTYPE
- Has web app manifest
- Highest document mode
- Manifest has name
- Use HTTPS
- No protocol-relative URLs
- No byte-order mark
- No `P3P` headers
- No broken links
- Use charset `utf-8`
- SSL server test
- Optimize images
- Nu HTML test
- Unneeded HTTP headers
- Use Apple touch icon
- Use `Strict-Transport-Security` header
- Use `X-Content-Type-Options` header
- Use subresource integrity
- Valid `Set-Cookie` header
- Valid `theme-color`
- Valid manifest
- aXe accessibility check
- webpack configuration hints set
- Configuring webhint
- Development flow integration
- Server configurations
image-optimization-cloudinary uses the Cloudinary
service to analyze your images and see if there could be size savings
Note: To use this hint you will need to have an account in this
service and configure it to use those credentials via the
CLOUDINARY_URL environment variable or in
the hint’s configuration. You can create a free account here.
As of September 15th, 2017, and based on HTTP Archive, images account for a bit over 53% of the size of a website in average, or 1,810kB.
By having your images optimized, you will help your users have a better and faster experience when navigating in your website.
This hint will use Cloudinary’s infrastructure to upload any images found and check if they can be optimized maintaining the same resolution and format.
Yes, if you don’t want to use the
CLOUDINARY_URL environment variable
to set up your credentials, you can pass them to the hint via the hint
configuration from the
By default, this hint will notify you even if there is a 1kB savings.
If you want to change the
threshold you can do it by having something
as the following in the
threshold value will be used for the savings per image, and the
total possible savings.
- Having an image that Cloudinary can optimize further.
- Having a
thresholdconfigured and an image whose savings is equal or greater than the configured value.
- Having a
thresholdconfigured and several images whose individual savings is less than
thresholdbut when combined it’s greater. For example, if you configure a
thresholdof 10, and you have one image that could be 6kB smaller, and another one that could be 5kB smaller, this hint will report an issue because the combined savings is greater than 10.
- Having all your images optimized.
- Having a
thresholdconfigured and the combined savings of all images smaller to that value.
To use it you will have to install it via
npm install @hint/hint-image-optimization-cloudinary
Note: You can make
npm install it as a
devDependency using the
--save-dev parameter, or to install it globally, you can use the
-g parameter. For other options see
And then activate it via the
.hintrc configuration file: