Skip to main content

LCP issues

Completed

Comments

1 comment

  • Official comment
    Support
    • Journey Support Team

    Hi Caitriona Maria McTiernan ! A site without ads will always be faster than one with ads -- no matter what your setup is. But our technology is the fastest in the industry, and we've built it with page speed top of mind. Lazy loading is the Google-recommended way to serve third-party javascript, and they even mention us in this article. A well-optimized site with a lightweight theme can pass all Core Web Vitals while running our ads without issue.

    This is all to say the Journey and Grow scripts are fully optimized for page speed, so they shouldn't be the primary culprit when it comes to slower performance or failing LCP. We have a post here that covers all things page speed with a great help article and page speed resources that should help, and I've included some additional tips for troubleshooting LCP below. 

    Troubleshooting LCP:

    • Ensure all images load below the first screenview if possible since it’s a great first step in troubleshooting and improving LCP
    • Use responsive image sizes (i.e. multiple image sizes so you can serve the optimally sized image for the device) through an image optimization plugin or an image CDN where the image URL indicates not only which image to load, but also parameters like size, format, and quality
    • Use a NextGen image format like WebP
    • Use a web safe font instead of a custom font or a font that requires additional scripts
    • Make sure text compression is enabled
    • Use an optimization plugin to optimize javascript and CSS delivery (just ensure the Journey script is excluded from javascript optimizations)
    • Use an optimization plugin to create critical and non-critical CSS files 
    • Use a CDN and caching plugin

    If you need help with any of the above items, we recommend reaching out to your host or developer.

    Thank you!

Journey is Self Supported

Our support staff is monitoring this forum everyday for bugs related to ad delivery, the display and functionality of the Journey dashboard, and any bugs related to the onboarding process. We are typically unable to assist with non-bug related issues like RPM performance expectations, issues setting up the ads.txt file, and questions already answered by our existing help docs. Read here for a more detailed breakdown of how Journey is self-supported and our recommendations for how to find answers to common issues.

Please sign in to leave a comment.

Powered by Zendesk