• Resolved max

    (@amanauxano)


    Hi everyone,

    I wanted to start a discussion about the Web Story Plugin in WordPress and the issues it might be causing with performance metrics such as First Contentful Paint (FCP), Largest Contentful Paint (LCP), and the use of passive listeners for scrolling performance. I’ve noticed several issues with the plugin, including those related to FCP and LCP, as well as the use of passive listeners, and I’m wondering if anyone else has experienced the same thing.

    For those who aren’t familiar with FCP and LCP, they are two of the metrics that Google uses to measure the user experience on websites. FCP measures the time it takes for the first piece of content to appear on the screen, while LCP measures the time it takes for the largest piece of content to appear. Both are important factors in user experience, and can have a significant impact on search engine rankings.

    Unfortunately, since I started using the Web Story Plugin, my website’s FCP and LCP scores have dropped significantly. Additionally, I’ve noticed that the plugin does not use passive listeners to improve scrolling performance, which can also impact the user experience.

    I’ve also noticed issues related to the use of Google Fonts, specifically with the URL https://fonts.googleapis.com/css2?display=swap&family=Poppins%3Awght%40400%3B700, which seems to be causing FCP issues on my website.

    If anyone else has experienced similar issues with the Web Story Plugin, I’d love to hear about your experiences and any solutions you’ve found. Is there a way to optimize the plugin for better FCP, LCP, and scrolling performance? Are there any alternative plugins or tools that can help improve these metrics?

    Let’s share our insights and solutions for improving performance with the Web Story Plugin, including passive listener issues and font-related issues like the one I’ve experienced.

Viewing 1 replies (of 1 total)
  • Plugin Author Pascal Birchler

    (@swissspidy)

    Thanks for your thorough post! Are you referring to metrics for your actual stories, or your other parts of the website that embed stories (using the Web Stories embed block for example)?

    If it’s for the former, I’d just like to mention that the story format itself is open source and developed by the AMP project. So if you have any feedback in that regard, you should report this directly on the AMP GitHub repository, as we can’t influence this on the plugin side.

    As for fonts, you can also add custom fonts on the dashboard in addition to the built-in fonts served from Google Fonts.

    Additionally, I’d just like to highlight that the Google Search Central help community is usually the recommended place to discuss core web vitals in general.

Viewing 1 replies (of 1 total)
  • The topic ‘Web Story Plugin Performance Issues with FCP, LCP, Scrolling, and Google Font’ is closed to new replies.