Step by Step Implementation

1. 1

   Step 1:

   Install Shopify CLI and run theme pull on local machine to access all Liquid files in the theme directory.
2. 2

   Step 2:

   Use PurgeCSS or Shopify's built-in critical CSS tool to extract above-the-fold styles from styles.css located at cdn/shop/t/835/compiled_assets/styles.css.
3. 3

   Step 3:

   Create a new snippet file named critical-css.liquid in snippets folder and paste extracted CSS rules for header and hero sections.
4. 4

   Step 4:

   Edit theme.liquid in layout folder to inline the critical CSS using {{ 'critical-css' | asset_url }} before closing head tag.
5. 5

   Step 5:

   Add defer attribute and async loading to the main stylesheet link tag using JavaScript in theme.liquid for all remaining CSS.
6. 6

   Step 6:

   Configure Shopify theme editor to disable unused app styles by navigating to Online Store > Themes > Customize and removing unused sections.
7. 7

   Step 7:

   Test with Lighthouse in Chrome DevTools using mobile emulation and verify FCP drops below 1.5s on repeated runs.
8. 8

   Step 8:

   Deploy via git push to Shopify theme store after staging validation on a duplicate theme.
9. 9

   Step 9:

   Monitor with Google Search Console for mobile usability improvements over 7 days.
10. 10

    Step 10:

    Validate no layout shifts occur post-deployment using WebPageTest with 3G throttling.

Step by Step Implementation

1. 1

   Step 1:

   This fix takes about 1 hour.

   Start by going to Online Store > Themes > Customize in your Shopify admin.
2. 2

   Step 2:

   Click on Theme Settings and find the Performance section.

   Turn on "Lazy load images".
3. 3

   Step 3:

   Count how many sections you have on your homepage.

   Try to keep it under 10 sections.
4. 4

   Step 4:

   Enable "Defer JavaScript loading" in theme settings.
5. 5

   Step 5:

   Check your product page template and remove unused blocks.
6. 6

   Step 6:

   Test your store on a mobile phone after making these changes.

Step by Step Implementation

1. 1

   Step 1:

   Install Shopify CLI and run theme pull on local machine to access all Liquid files in the theme directory.
2. 2

   Step 2:

   Use PurgeCSS or Shopify's built-in critical CSS tool to extract above-the-fold styles from styles.css located at cdn/shop/t/835/compiled_assets/styles.css.
3. 3

   Step 3:

   Create a new snippet file named critical-css.liquid in snippets folder and paste extracted CSS rules for header and hero sections.
4. 4

   Step 4:

   Edit theme.liquid in layout folder to inline the critical CSS using {{ 'critical-css' | asset_url }} before closing head tag.
5. 5

   Step 5:

   Add defer attribute and async loading to the main stylesheet link tag using JavaScript in theme.liquid for all remaining CSS.
6. 6

   Step 6:

   Configure Shopify theme editor to disable unused app styles by navigating to Online Store > Themes > Customize and removing unused sections.
7. 7

   Step 7:

   Test with Lighthouse in Chrome DevTools using mobile emulation and verify FCP drops below 1.5s on repeated runs.
8. 8

   Step 8:

   Deploy via git push to Shopify theme store after staging validation on a duplicate theme.
9. 9

   Step 9:

   Monitor with Google Search Console for mobile usability improvements over 7 days.
10. 10

    Step 10:

    Validate no layout shifts occur post-deployment using WebPageTest with 3G throttling.

Step by Step Implementation

1. 1

   Step 1:

   This fix takes about 1 hour.

   Start by going to Online Store > Themes > Customize in your Shopify admin.
2. 2

   Step 2:

   Click on Theme Settings and find the Performance section.

   Turn on "Lazy load images".
3. 3

   Step 3:

   Count how many sections you have on your homepage.

   Try to keep it under 10 sections.
4. 4

   Step 4:

   Enable "Defer JavaScript loading" in theme settings.
5. 5

   Step 5:

   Check your product page template and remove unused blocks.
6. 6

   Step 6:

   Test your store on a mobile phone after making these changes.

Step by Step Implementation

1. 1

   Step 1:

   Open the production page in Chrome DevTools and filter Network and Performance traces for "GeoPro (Geolocation)".

   Capture transfer size, blocking time, initiator, and whether the component loads before the first meaningful product content.
2. 2

   Step 2:

   Identify the exact owner and configuration surface for GeoPro (Geolocation).

   For Shopify apps, check the app admin and theme app embeds.

   For theme code, search theme.liquid, section files, snippets, and app blocks before changing anything.
3. 3

   Step 3:

   Decide whether GeoPro (Geolocation) must load on every page.

   If it is only needed for checkout, reviews, analytics, personalization, or marketing capture, restrict it to the specific template or user action where it creates value.
4. 4

   Step 4:

   Change the loading strategy to async, defer, lazy, consent-triggered, or interaction-triggered wherever the component does not need to block initial rendering.

   Keep a rollback copy of the previous tag or app embed setting.
5. 5

   Step 5:

   Re-test mobile and desktop after the change with Lighthouse, PageSpeed, and a real browser trace.

   Confirm LCP, TBT, total requests, and total JavaScript bytes improve without breaking the component's business function.
6. 6

   Step 6:

   Monitor conversion rate, revenue per session, checkout starts, and the component's own success metric for 7 days.

   Keep the optimization only if the performance gain does not reduce the component's measurable contribution.

Step by Step Implementation

1. 1

   Step 1:

   This fix takes about 15 minutes to complete.

   Open your Postscript app from your Shopify admin.
2. 2

   Step 2:

   Go to the popup settings and change when it appears.

   Set it to show "After 5 seconds" or "On Exit Intent" instead of immediately.
3. 3

   Step 3:

   Choose a simple popup template without fancy animations.

   Smaller popups load faster and work better on mobile phones.
4. 4

   Step 4:

   Run an A/B test to compare conversion rates with different timing.

Step by Step Implementation

1. 1

   Step 1:

   Open the production page in Chrome DevTools and filter Network and Performance traces for "Tolstoy Video Ads".

   Capture transfer size, blocking time, initiator, and whether the component loads before the first meaningful product content.
2. 2

   Step 2:

   Identify the exact owner and configuration surface for Tolstoy Video Ads.

   For Shopify apps, check the app admin and theme app embeds.

   For theme code, search theme.liquid, section files, snippets, and app blocks before changing anything.
3. 3

   Step 3:

   Decide whether Tolstoy Video Ads must load on every page.

   If it is only needed for checkout, reviews, analytics, personalization, or marketing capture, restrict it to the specific template or user action where it creates value.
4. 4

   Step 4:

   Change the loading strategy to async, defer, lazy, consent-triggered, or interaction-triggered wherever the component does not need to block initial rendering.

   Keep a rollback copy of the previous tag or app embed setting.
5. 5

   Step 5:

   Re-test mobile and desktop after the change with Lighthouse, PageSpeed, and a real browser trace.

   Confirm LCP, TBT, total requests, and total JavaScript bytes improve without breaking the component's business function.
6. 6

   Step 6:

   Monitor conversion rate, revenue per session, checkout starts, and the component's own success metric for 7 days.

   Keep the optimization only if the performance gain does not reduce the component's measurable contribution.

Step by Step Implementation

1. 1

   Step 1:

   Open the production page in Chrome DevTools and filter Network and Performance traces for "Friendbuy Loyalty Referrals".

   Capture transfer size, blocking time, initiator, and whether the component loads before the first meaningful product content.
2. 2

   Step 2:

   Identify the exact owner and configuration surface for Friendbuy Loyalty Referrals.

   For Shopify apps, check the app admin and theme app embeds.

   For theme code, search theme.liquid, section files, snippets, and app blocks before changing anything.
3. 3

   Step 3:

   Decide whether Friendbuy Loyalty Referrals must load on every page.

   If it is only needed for checkout, reviews, analytics, personalization, or marketing capture, restrict it to the specific template or user action where it creates value.
4. 4

   Step 4:

   Change the loading strategy to async, defer, lazy, consent-triggered, or interaction-triggered wherever the component does not need to block initial rendering.

   Keep a rollback copy of the previous tag or app embed setting.
5. 5

   Step 5:

   Re-test mobile and desktop after the change with Lighthouse, PageSpeed, and a real browser trace.

   Confirm LCP, TBT, total requests, and total JavaScript bytes improve without breaking the component's business function.
6. 6

   Step 6:

   Monitor conversion rate, revenue per session, checkout starts, and the component's own success metric for 7 days.

   Keep the optimization only if the performance gain does not reduce the component's measurable contribution.

Step by Step Implementation

1. 1

   Step 1:

   Open the production page in Chrome DevTools and filter Network and Performance traces for "Delm".

   Capture transfer size, blocking time, initiator, and whether the component loads before the first meaningful product content.
2. 2

   Step 2:

   Identify the exact owner and configuration surface for Delm.

   For Shopify apps, check the app admin and theme app embeds.

   For theme code, search theme.liquid, section files, snippets, and app blocks before changing anything.
3. 3

   Step 3:

   Decide whether Delm must load on every page.

   If it is only needed for checkout, reviews, analytics, personalization, or marketing capture, restrict it to the specific template or user action where it creates value.
4. 4

   Step 4:

   Change the loading strategy to async, defer, lazy, consent-triggered, or interaction-triggered wherever the component does not need to block initial rendering.

   Keep a rollback copy of the previous tag or app embed setting.
5. 5

   Step 5:

   Re-test mobile and desktop after the change with Lighthouse, PageSpeed, and a real browser trace.

   Confirm LCP, TBT, total requests, and total JavaScript bytes improve without breaking the component's business function.
6. 6

   Step 6:

   Monitor conversion rate, revenue per session, checkout starts, and the component's own success metric for 7 days.

   Keep the optimization only if the performance gain does not reduce the component's measurable contribution.

Step by Step Implementation

1. 1

   Step 1:

   Open the production page in Chrome DevTools and filter Network and Performance traces for "Checkmate Checkout Optimization".

   Capture transfer size, blocking time, initiator, and whether the component loads before the first meaningful product content.
2. 2

   Step 2:

   Identify the exact owner and configuration surface for Checkmate Checkout Optimization.

   For Shopify apps, check the app admin and theme app embeds.

   For theme code, search theme.liquid, section files, snippets, and app blocks before changing anything.
3. 3

   Step 3:

   Decide whether Checkmate Checkout Optimization must load on every page.

   If it is only needed for checkout, reviews, analytics, personalization, or marketing capture, restrict it to the specific template or user action where it creates value.
4. 4

   Step 4:

   Change the loading strategy to async, defer, lazy, consent-triggered, or interaction-triggered wherever the component does not need to block initial rendering.

   Keep a rollback copy of the previous tag or app embed setting.
5. 5

   Step 5:

   Re-test mobile and desktop after the change with Lighthouse, PageSpeed, and a real browser trace.

   Confirm LCP, TBT, total requests, and total JavaScript bytes improve without breaking the component's business function.
6. 6

   Step 6:

   Monitor conversion rate, revenue per session, checkout starts, and the component's own success metric for 7 days.

   Keep the optimization only if the performance gain does not reduce the component's measurable contribution.

Step by Step Implementation

1. 1

   Step 1:

   Open the production page in Chrome DevTools and filter Network and Performance traces for "Microsoft Clarity".

   Capture transfer size, blocking time, initiator, and whether the component loads before the first meaningful product content.
2. 2

   Step 2:

   Identify the exact owner and configuration surface for Microsoft Clarity.

   For Shopify apps, check the app admin and theme app embeds.

   For theme code, search theme.liquid, section files, snippets, and app blocks before changing anything.
3. 3

   Step 3:

   Decide whether Microsoft Clarity must load on every page.

   If it is only needed for checkout, reviews, analytics, personalization, or marketing capture, restrict it to the specific template or user action where it creates value.
4. 4

   Step 4:

   Change the loading strategy to async, defer, lazy, consent-triggered, or interaction-triggered wherever the component does not need to block initial rendering.

   Keep a rollback copy of the previous tag or app embed setting.
5. 5

   Step 5:

   Re-test mobile and desktop after the change with Lighthouse, PageSpeed, and a real browser trace.

   Confirm LCP, TBT, total requests, and total JavaScript bytes improve without breaking the component's business function.
6. 6

   Step 6:

   Monitor conversion rate, revenue per session, checkout starts, and the component's own success metric for 7 days.

   Keep the optimization only if the performance gain does not reduce the component's measurable contribution.

Step by Step Implementation

1. 1

   Step 1:

   Open the production page in Chrome DevTools and filter Network and Performance traces for "Elevar Conversion Tracking".

   Capture transfer size, blocking time, initiator, and whether the component loads before the first meaningful product content.
2. 2

   Step 2:

   Identify the exact owner and configuration surface for Elevar Conversion Tracking.

   For Shopify apps, check the app admin and theme app embeds.

   For theme code, search theme.liquid, section files, snippets, and app blocks before changing anything.
3. 3

   Step 3:

   Decide whether Elevar Conversion Tracking must load on every page.

   If it is only needed for checkout, reviews, analytics, personalization, or marketing capture, restrict it to the specific template or user action where it creates value.
4. 4

   Step 4:

   Change the loading strategy to async, defer, lazy, consent-triggered, or interaction-triggered wherever the component does not need to block initial rendering.

   Keep a rollback copy of the previous tag or app embed setting.
5. 5

   Step 5:

   Re-test mobile and desktop after the change with Lighthouse, PageSpeed, and a real browser trace.

   Confirm LCP, TBT, total requests, and total JavaScript bytes improve without breaking the component's business function.
6. 6

   Step 6:

   Monitor conversion rate, revenue per session, checkout starts, and the component's own success metric for 7 days.

   Keep the optimization only if the performance gain does not reduce the component's measurable contribution.

Step by Step Implementation

1. 1

   Step 1:

   Open the production page in Chrome DevTools and filter Network and Performance traces for "Triple Whale".

   Capture transfer size, blocking time, initiator, and whether the component loads before the first meaningful product content.
2. 2

   Step 2:

   Identify the exact owner and configuration surface for Triple Whale.

   For Shopify apps, check the app admin and theme app embeds.

   For theme code, search theme.liquid, section files, snippets, and app blocks before changing anything.
3. 3

   Step 3:

   Decide whether Triple Whale must load on every page.

   If it is only needed for checkout, reviews, analytics, personalization, or marketing capture, restrict it to the specific template or user action where it creates value.
4. 4

   Step 4:

   Change the loading strategy to async, defer, lazy, consent-triggered, or interaction-triggered wherever the component does not need to block initial rendering.

   Keep a rollback copy of the previous tag or app embed setting.
5. 5

   Step 5:

   Re-test mobile and desktop after the change with Lighthouse, PageSpeed, and a real browser trace.

   Confirm LCP, TBT, total requests, and total JavaScript bytes improve without breaking the component's business function.
6. 6

   Step 6:

   Monitor conversion rate, revenue per session, checkout starts, and the component's own success metric for 7 days.

   Keep the optimization only if the performance gain does not reduce the component's measurable contribution.

Step by Step Implementation

1. 1

   Step 1:

   Open the production page in Chrome DevTools and filter Network and Performance traces for "Recharge (Subscriptions)".

   Capture transfer size, blocking time, initiator, and whether the component loads before the first meaningful product content.
2. 2

   Step 2:

   Identify the exact owner and configuration surface for Recharge (Subscriptions).

   For Shopify apps, check the app admin and theme app embeds.

   For theme code, search theme.liquid, section files, snippets, and app blocks before changing anything.
3. 3

   Step 3:

   Decide whether Recharge (Subscriptions) must load on every page.

   If it is only needed for checkout, reviews, analytics, personalization, or marketing capture, restrict it to the specific template or user action where it creates value.
4. 4

   Step 4:

   Change the loading strategy to async, defer, lazy, consent-triggered, or interaction-triggered wherever the component does not need to block initial rendering.

   Keep a rollback copy of the previous tag or app embed setting.
5. 5

   Step 5:

   Re-test mobile and desktop after the change with Lighthouse, PageSpeed, and a real browser trace.

   Confirm LCP, TBT, total requests, and total JavaScript bytes improve without breaking the component's business function.
6. 6

   Step 6:

   Monitor conversion rate, revenue per session, checkout starts, and the component's own success metric for 7 days.

   Keep the optimization only if the performance gain does not reduce the component's measurable contribution.