wp_postmeta table and saved path

  • xiaoxian666

    (@xiaoxian666)


    1 year, 5 months ago

    Overall, this is a very good plugin, here are some small suggestions: 😀

    • It is recommended not to use the wp_postmeta table. This may affect website performance, and it may be better to create a new database table.
    • It would be better if can choose the location where the optimized pictures are saved.
    • The optimized image is aa.jpg.webp or aa.jpg.avif. Maybe aa.webp or aa.avif is better for SEO?

    Viewing 2 replies - 1 through 2 (of 2 total)
    • Plugin Support tonyrobins

      (@tonyrobins)

      1 year, 5 months ago

      Hello @xiaoxian666

      Many thanks for your feedback and suggestions.

      I’ve recorded them in my weekly report so the team can discuss them. We are going to keep you posted on any feedback.

      All the best,

      Plugin Support tonyrobins

      (@tonyrobins)

      1 year, 5 months ago

      Hi @xiaoxian666

      The team has discussed your suggestions:

      1. WordPress has it’s own interface to handle data in the wp_postmeta table. Using a custom table means that CompressX will need to take over the function, which may compromise it’s compatibility and stability.
      2. We’ve decided to add the option to our development roadmap. Thanks for the suggestion.
      3. Using aa.webp/avif may cause conflicts. For example, in some cases, the converted version of both aa.jpg and aa.png will be aa.webp or aa.avif. This may cause problems with image loading.

      All the best,

    Viewing 2 replies - 1 through 2 (of 2 total)

    The topic ‘wp_postmeta table and saved path’ is closed to new replies.