Optimize images (`image-optimization-cloudinary`)

image-optimization-cloudinary uses the Cloudinary service to analyze your images and see if there could be size savings on them.

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.

Why is this important?

As of June 1st, 2019, and based on HTTP Archive, images account for a bit over 47% of the size of a website in average.

"Average Bytes per Page by Content Type"

By having your images optimized, you will help your users have a better and faster experience when navigating in your website.

What does the hint check?

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.

Can the hint be configured?

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 .hintrc file:

{
    "connector": {...},
    "formatters": [...],
    "hints": {
        "image-optimization-cloudinary": ["error", {
            "apiKey": "your api key",
            "apiSecret": "your api secret",
            "cloudName": "your cloud name"
        }],
        ...
    },
    ...
}

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 .hintrc file:

{
    "connector": {...},
    "formatters": [...],
    "hints": {
        "image-optimization-cloudinary": ["error", {
            "threshold": 10
        }],
        ...
    },
    ...
}

The threshold value will be used for the savings per image, and the total possible savings.

Examples that trigger the hint

Having an image that Cloudinary can optimize further.
Having a threshold configured and an image whose savings is equal or greater than the configured value.
Having a threshold configured and several images whose individual savings is less than threshold but when combined it’s greater. For example, if you configure a threshold of 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.

Examples that pass the hint

Having all your images optimized.
Having a threshold configured and the combined savings of all images smaller to that value.

How to use this hint?

This package is installed automatically by webhint:

npm install hint --save-dev

To use it, activate it via the .hintrc configuration file:

{
    "connector": {...},
    "formatters": [...],
    "hints": {
        "image-optimization-cloudinary": "error",
        ...
    },
    "parsers": [...],
    ...
}

Note: The recommended way of running webhint is as a devDependency of your project.

Current Tags

3.2.23 ... latest (4 years ago)

Optimize images (`image-optimization-cloudinary`)

Why is this important?

What does the hint check?

Can the hint be configured?

Examples that trigger the hint

Examples that pass the hint

How to use this hint?

Further Reading

Current Tags

48 Versions

Optimize images (image-optimization-cloudinary)

Why is this important?

What does the hint check?

Can the hint be configured?

Examples that trigger the hint

Examples that pass the hint

How to use this hint?

Further Reading

Current Tags

48 Versions

Optimize images (`image-optimization-cloudinary`)