Ensuring Seamless Performance: When to Update Your Speed Kit Configuration

‍

Key Takeaways

• Proactive Communication: Inform your Customer Success Manager and development team about planned website changes to ensure Speed Kit's continued optimal performance.
• Critical Areas: Be aware of specific website modifications, such as A/B tests, architectural shifts, and URL changes, that require configuration adjustments.
• Continuous Optimization: Adapting Speed Kit's settings in response to these changes is crucial for maintaining acceleration and a smooth user experience.

Introduction

To ensure your website continues to perform optimally with Speed Kit, it's crucial to adapt its configuration when planning certain website changes. This document outlines key modifications that necessitate a review of your Speed Kit settings. Please share this information with your development team and notify your customer success manager about any planned modifications.

Key Website Changes to Notify Us About

Server/Client-Side A/B Tests (Above the Fold)

If you begin conducting A/B tests in the above-the-fold area, please inform us. These tests can impact how content is cached and potentially cause flickering. We'll adjust your Speed Kit settings to ensure a smooth and consistent user experience.

Mobile/Desktop Differentiation

If you decide to move from a responsive design to using separate HTML versions for mobile and desktop, or vice versa, please let us know. This allows us to tailor the caching strategy and content delivery specifically for each device type.

Frontend Architecture Changes

• Navigation Type Changes: For example, switching from a multi-page application (hard navigation) to a single-page application (soft navigation).
• Client-Side Rendering: If you transition from server-side to client-side rendering.
• Critical Inline Scripts: Changes involving inline scripts that are critical for the initial rendering, such as those used for loading fonts, CSS files, or other assets required for the First Meaningful Paint.
• CSS System Changes: If you're updating your CSS system or renaming CSS classes that are used for identifying dynamic or personalized content.
• Framework Updates: If you're updating to a new major version of your JavaScript framework or switching to a different one.

Server-Side Logic Changes

• Dynamic List Ordering: For example, changing the order of product lists to show different items based on user preferences or behavior.
• Location-Based Content: Displaying different content based on the user's geographical location.

URL Structure Changes

If you plan to change the structure of your URLs. For example, if you currently use /category/ in the URL of your product listing pages and plan to switch to /c/.

Design Tweaks of Critical Elements

Any layout changes to critical elements above the fold, such as your hero image, pricing information, or the add-to-cart button.

Adding New Service Workers

If you plan to introduce a new service worker on your site, please consult with us to ensure it will integrate seamlessly and work effectively with Speed Kit.

Waiting Room/Maintenance Periods

The introduction of periods where customers see a maintenance page or are redirected to a waiting room instead of the actual HTML content.

Changing Content Security Policies

This potentially can stop the Speed Kit JavaScript or service worker from working.