Cumulative Layout Shift – How to fix?

  • Resolved irdeto

    (@irdeto)


    3 years, 2 months ago

    Google has rolled out Core Web Vitals in the last 6 months. The purpose of this is to measure usability of a website.

    One of the metrics that causes a bad score is CLS (cumulative layout shift).

    Is NextGen team working on resolving this? Either reserving the space so as not to cause a jump or something like that?

    CLS does / will influence rankings as will other Core web vitals.

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

    (@mihaiimagely)

    Hi @irdeto,

    Good question and thanks for asking. We had a discussion around this subject sooner this year but as a conclusion we haven’t moved that far since then due to it requiring a pretty big code refactoring that’s sort of heavy for our small team. We have found that the main way that’d allow our gallery display types comply with CLS standards would be implementing some sort of pre-loaders and Lazy Loading for all of the gallery display types that are available.

    I’m afraid that there’s no immediate progress going on regarding this aspect but that’s something our dev team is aware of so hopefully things will improve at a future point in time.

    Thread Starter irdeto

    (@irdeto)

    Even if you implemented something like inline css to reserve space using a min-height: parameter it would be better than nothing.

    as an example, in a pro mosaic layout, we already specify how many images to show as well as row height.

    in other options we also specify default thumbnail dimensions.

    you could at least reserve space using min-height based on all the above settings we already set in nextgen to estimate at least some reserved space?

    just a thought ??

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Cumulative Layout Shift – How to fix?’ is closed to new replies.

Tags