[Support request] Idea: Implement CSS’ New “content-visibility” for Dramatic Performance Boost

Home Forums Support Idea: Implement CSS’ New “content-visibility” for Dramatic Performance Boost

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • #1424754


    According to this article, there is a new CSS property,which is “content-visibility” that dramatically boost the rendering performance.

    content-visibility: the new CSS property that boosts your rendering performance:

    The web.dev portal is operated by Google and is aimed at Chromium related browsers and the web in general.

    With the recent change of Microsoft serving an Edge browser that uses the Chromium engine, I think the market share of the already dominant Chromium browsers family is growing even more.

    It is important to mention that the crawling and rendering of the web content from the biggest search engine – Google is also happening with a the Googlebot running on a headless evergreen Chromium.

    With the already release Web Core Vitals that would become a ranking factor, performance is getting even more important than before.


    As GeneratePress always strive for performance excellence, I think implementing the content-visibility CSS property would dramatically boost the SEO and UX for the users.

    Someone already mentioned that in the Facebook group and described that after a developer implement it, the performance boost was very solid, yet the implementation was not that hard.

    https://web.dev/measure/ – This is web based Google Lighthouse performance test.

    https://developers.google.com/speed/pagespeed/insights/ – Google PageSpeed Insights

    As an internet marketer I urge you to implement this thing.

    Thanks very much in advance!

    Customer Support

    Hi there,

    yes, the CSS Containment spec is pretty exciting stuff. It is something we are keeping a close eye.


    If the words of the FB group user was that implementing it is just few lines of code for the theme, could we expect this to ship soon?

    Customer Support

    Main concern:
    Chrome has implemented what is still a draft specification CSS property. Firefox have deemed it ‘prototype worthy’, and other browsers are yet to implement this. This leads to an overarching concern that implementing Chrome specific CSS today ‘may’ create future issues if other browsers adopt the specification in a different way.

    Implementation concerns:
    Where exactly the required CSS is placed will vary from one layout to another.

    For archives it could be applied to each individual post element. This would probably work quite effectively. But would require testing when ajax, infinite scrolling or masonry is in place.

    Other layouts – not so easy. Applying content-visibility to a single post or page container would probably provide no benefit as on intial load, part of that container is generally visible ( unless the user has a Full Screen hero above the post content ). Instead you would want to pass the property to elements within the content – that leads to the question as to whether this should be passed to Blocks rather then theme templates.

    So there are a lot of things that need consideration and testing to implement what may only be a few lines of CSS. Of course there is nothing stopping users from applying the CSS themselves at this time.

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.