Skip to main content

Site Speed CVR Next Steps + Actions

Here's what to do when the strategy team produces a site speed CVR analysis, and how to consult your client to use it

S
Written by Strategy Organization
Updated over 2 years ago

Overview

  • The purpose of the site speed analysis is to show revenue lost due to site issues

  • Some websites are easier to optimize for speed than others

  • If the revenue lost levels are high enough, it opens up conversations around:

    • Service expansion for a total site rebuild

    • Conversion rate optimization

    • UX and UI flow, heat mapping (e.g. Heap or similar tools)

    • Landing pages and testing (e.g. Unbounce)

    • Optimizing what elements we can for speed

Before the Presentation

  • The strategy team will create the site speed analysis and estimate lost revenue

  • A deck will be created that highlights these issues

  • The Account Manager or Account Director verifies what platform the site uses:

    • We can do development work in Shopify, Wordpress, and WooCommerce

    • We can’t do dev work in other CMS platforms

  • The account team will present these findings to the client

After the Presentation

  • If the client is on a CMS that we can do dev work in (Shopify, Wordpress, Woo)

    • PDM can help

    • Internal development and CRO teams to get expert opinion

    • Follow the Asana process and loop in the appropriate teams (Annie T, etc)

  • If the client is on a CMS that we can’t do dev work in

    • We don’t offer dev support for the CMS your site is built in

    • But we can look for other opportunities to improve conversion rates

      • CRO

      • UX/UI recommendations

    • If interested, we can loop in the appropriate teams and get their opinion

    • Follow the Asana process and loop in the appropriate teams (Will H, etc)

Some Sample Shopify Optimizations

  • Audit all installed Shopify Apps and disable features or apps that aren’t impactful

  • Audit Theme features: reduce any unnecessary bloat or custom theme elements

  • Optimize Liquid Code: adjust load order of elements, reduce complex operations

  • Compress and optimize images and videos: reduce file weight, use lazy loads

  • Reduce unnecessary videos, images, or embellishments

  • Use well-known fonts or “font families,” prevent users from downloading new font

  • Reduce code requests (HTTP requests, CSS scripts, JavaScripts, API buttons, etc)

Did this answer your question?