How to Improve Funnel & Website Page Speed

Modified on: Sat, 14 Nov, 2026 at 1:42 AM

A fast-loading funnel or website helps visitors navigate pages, complete forms, and take action without unnecessary delays. Large images, complex layouts, videos, and third-party scripts can affect loading speed, user experience, and SEO. HighLevel includes built-in performance optimizations that help reduce page weight and improve loading behavior. Follow these best practices to optimize your funnels and websites, test performance, and troubleshoot slow-loading pages.


TABLE OF CONTENTS


What is Funnel and Website Page Speed?


Funnel and website page speed refers to how quickly a page loads and becomes usable for visitors. Page speed is influenced by image sizes, videos, animations, custom code, tracking scripts, and the number of elements a browser needs to process.


HighLevel provides built-in features such as Image Optimization, Optimize JavaScript, and automatic image lazy loading to help pages load more efficiently.


In addition to these features, optimizing your page content and reducing unnecessary elements can improve loading times, especially for visitors using mobile devices or slower internet connections.


Note: Page speed results vary depending on page content, third-party integrations, browser conditions, and device performance. Optimizations can improve loading behavior, but specific PageSpeed scores are not guaranteed.

Key Benefits of Improving Page Speed


Optimizing page speed helps reduce unnecessary loading delays and creates a smoother experience for visitors. Faster pages can make it easier for customers to browse content, submit forms, and complete important actions.


  • Improved User Experience: Visitors can access page content and interact with important elements with fewer delays.

  • Better Conversion Opportunities: Reducing loading friction can help visitors complete forms, bookings, and purchases.

  • Improved Mobile Performance: Optimized images and lighter page layouts help reduce loading demands on mobile devices and slower connections.

  • Better SEO Performance: Faster loading and improved user experience can support search engine optimization efforts.

  • Reduced Page Weight: Smaller files, fewer unnecessary elements, and optimized code reduce the amount of data a browser needs to process.

  • Easier Troubleshooting: Regular performance testing makes it easier to identify large files, slow scripts, and other loading issues.

Optimize Images


Images are often among the largest resources on a funnel or website. Using appropriately sized and compressed images reduces the amount of data visitors need to download while preserving the visual quality of your pages.


  • Resize Images Before Uploading: Avoid uploading oversized images. Keep image dimensions close to the size at which they will appear on the page.

  • Use Compressed Image Formats: Use JPG or WebP for photographs and PNG for graphics that require transparency.

  • Limit Unnecessary Images: Remove decorative images that do not provide meaningful value. For example, use one strong hero image instead of multiple large images.

  • Optimize Above-the-Fold Images: Keep images visible when the page first loads as lightweight as practical. As a best practice, aim for images under 200 KB to help improve mobile Largest Contentful Paint (LCP).

  • Review Image Clarity: After enabling image optimization, check that images remain clear and readable on desktop and mobile devices.


Automatic Image Lazy Loading


HighLevel automatically applies lazy loading to image elements so images can load as visitors move through the page rather than requiring every image to load immediately.


Automatic lazy loading applies across:

  • Funnels
  • Websites
  • E-commerce Pages
  • Webinar Previews


HighLevel applies the loading="lazy" attribute to image elements independently of the Image Optimization setting.


Note: Image Optimization and automatic image lazy loading are separate performance behaviors. Turning off Image Optimization does not disable automatic lazy loading.

Limit Heavy Elements


Videos, animations, embedded widgets, and third-party scripts can increase the amount of processing required before a page becomes usable. Reducing unnecessary resource-heavy elements helps keep the initial loading experience lightweight.


  • Reduce Video Backgrounds: Use short loops and compressed video files when background videos are necessary.

  • Limit Animations: Avoid excessive motion effects or animated elements that increase rendering demands.

  • Reduce Third-Party Widgets: Remove unnecessary embedded tools, maps, calendars, and other external widgets.

  • Keep Tracking Scripts Minimal: Avoid installing unnecessary tracking scripts or multiple copies of the same script.

  • Keep Above-the-Fold Content Lightweight: Prioritize essential text, images, and calls to action in the first visible portion of the page.

  • Move Heavy Elements Below the Fold: When appropriate, place resource-heavy forms, calendars, maps, or widgets farther down the page to reduce initial rendering demands.

Clean Up Your Pages


Unused sections, duplicated elements, and unnecessarily complex layouts can make pages harder to maintain and may increase loading work. Keeping your page structure organized helps visitors focus on important content and makes performance issues easier to identify.


  • Remove Unused Sections: Delete hidden, outdated, or duplicated sections that are no longer needed.

  • Simplify Layouts: Reduce unnecessary rows, columns, and nested elements.

  • Review Page Length: Remove repetitive content or elements that do not support the page's purpose.

  • Optimize Downloadable Files: Compress PDFs and other downloadable resources before uploading.

  • Remove Unused Custom Code: Delete outdated custom CSS, JavaScript, or embedded integrations that are no longer required.

Use HighLevel Performance Features


HighLevel includes built-in page-building and optimization tools that can help improve loading behavior and simplify page management. Reviewing these features helps you reduce unnecessary external resources and manage page performance more effectively.


Global and Universal Sections


Saved Sections allow you to reuse content blocks without manually rebuilding the same layouts. Global Sections synchronize changes within a single funnel or website, while Universal Sections synchronize changes across the account.


These features primarily improve content management and consistency. Actual page speed still depends on the images, scripts, and elements contained within each section.


For more information, see Saved Sections - Funnels, Websites, Webinars and E-Commerce Store.


HighLevel Forms and Surveys


Using HighLevel-native Forms and Surveys can reduce reliance on third-party embeds that introduce additional scripts and network requests.


When possible, use native elements and test the published page to confirm the effect on loading performance.


Image Optimization


The Image Optimization setting helps images load more efficiently. Keeping this option enabled can reduce loading demands, particularly on image-heavy pages.


Image optimization can affect image quality, so review important images after making changes.


Optimize JavaScript


The Optimize JavaScript setting delays nonessential JavaScript and tracking-code hydration to reduce blocking work during page loading. This can improve Total Blocking Time (TBT) and overall page responsiveness.


However, custom scripts that depend on immediate execution may require additional testing.


Important: Optimize JavaScript may need to be disabled when critical custom code must run immediately on page load. Always test forms, tracking scripts, and custom integrations after changing this setting.


For more information, see Hydration Event in Custom Code in Funnels.


Inspect Network Requests


Browser developer tools can help identify large files, slow third-party scripts, and other resources that affect loading speed.


Open the browser's Developer Tools > Network tab, reload the published page, and review requests that take a long time to complete.


Review Browser and Hosting Optimizations


Page performance also depends on how browsers retrieve and reuse resources. Reviewing caching, domain configuration, and redirects can help eliminate unnecessary delays outside the page's content.


  • Use Browser Caching: Cached assets can help returning visitors load pages faster without downloading every resource again.

  • Use a Custom Domain with SSL: Configure a secure custom domain to provide a consistent, trusted visitor experience.

  • Avoid Unnecessary Redirects: Make sure visitors reach the intended page without passing through multiple redirects.

  • Review Resource Delivery: HighLevel uses a global content delivery network (CDN), but large assets and external requests can still affect loading performance.

Test and Monitor Performance


Performance testing helps identify the resources and page behaviors that contribute to slow loading. Regular testing also makes it easier to compare improvements and confirm that optimization changes are working as intended.


Use Page Speed Testing Tools


Use performance testing tools to evaluate published funnel and website pages:


For accurate comparisons:

  1. Test the published page URL.

  2. Run tests on both desktop and mobile.

  3. Review recommendations related to images, JavaScript, and resource loading.

  4. Make targeted changes based on the reported issues.

  5. Run the tests again and compare the results.


Builder Preview and Tracking Script Optimization


HighLevel has introduced an optimization that delays tracking-script hydration in Builder Preview. This reduces the likelihood of tracking scripts blocking initial page loading.


This improvement applies specifically to pages containing tracking scripts. Pages without tracking scripts are outside the scope of this particular optimization.


The supplied release information reports a 15–25-point improvement in PageSpeed scores associated with this change.


Note: The reported 15–25-point improvement is not guaranteed for every page. Actual results depend on page structure, tracking scripts, and other performance factors. Individual examples may show results above or below the reported range.


Desktop PageSpeed Performance Examples


The following examples show before-and-after desktop PageSpeed Performance scores from the supplied update. These comparisons illustrate how measured improvements can vary between pages.


CF Track Performance Example


The CF Track example shows a desktop Performance score increase from 70 to 98, representing a 28-point improvement.



HighLevel Website Performance Example


The HighLevel website example shows a desktop Performance score increase from 71 to 97, representing a 26-point improvement.



Prime Performance Example


The Prime example shows a desktop Performance score increase from 75 to 88, representing a 13-point improvement.



SaaS Performance Example


The SaaS example shows a desktop Performance score increase from 74 to 91, representing a 17-point improvement.



Tip: Use these results as examples rather than expected performance benchmarks. Always test your own published pages to measure the impact of optimization changes.

Reduced Initial HTML Size


The size of a page's initial HTML document affects how much information a browser must download before rendering content. Reducing unnecessary page data can help improve loading performance, particularly for visitors using slower internet connections.


HighLevel has optimized the data used to render pages by removing unnecessary fields from the page data response.


This optimization reduces the average final HTML document size by approximately 10%, helping make initial page delivery more efficient.


Note: The reduced HTML document size is an automatic performance optimization. No additional configuration is required in most cases. The reported 10% reduction is an average and may vary by page.

How to Optimize Funnel and Website Page Speed


Optimizing your funnel or website involves reviewing page assets, removing unnecessary elements, checking available performance settings, and testing the published page. Following a consistent process helps you identify improvements without disrupting essential functionality.


  1. In your HighLevel sub-account, navigate to Sites > Funnels or Sites > Websites.

  2. Select the Funnel or Website you want to optimize.

  3. Open the page in the Page Builder.

  4. Review the images on the page. Resize, compress, or replace oversized images where necessary.

  5. Remove unnecessary videos, animations, widgets, duplicate elements, and third-party scripts.

  6. Simplify the page layout by removing unused sections and unnecessary nested elements.

  7. Open the relevant funnel or website settings and review the available Image Optimization and Optimize JavaScript controls.

  8. Keep optimization settings enabled where appropriate, and verify that required custom scripts and integrations continue to function.

  9. Save or publish your changes, then copy the published page URL.

  10. Run a performance test using PageSpeed Insights or GTmetrix.

  11. Review the results on both desktop and mobile, then make further adjustments based on the recommendations.

  12. Retest the page and verify that forms, buttons, tracking scripts, navigation, and other important interactions continue to work correctly.


Tip: Make one group of optimization changes at a time and retest the page. This makes it easier to identify which adjustments improve performance.

When to Contact Support


If your funnel or website remains unusually slow after applying these optimizations, collecting relevant diagnostic information can help HighLevel Support understand the issue and identify appropriate next steps.


When contacting Support, provide:

  • Funnel or Website URL: Include the published link to the affected page.

  • PageSpeed Test Results: Share desktop and mobile results from PageSpeed Insights or GTmetrix.

  • Steps Already Taken: List the images, scripts, layouts, and settings you have reviewed or adjusted.

  • Issue Details: Describe the loading behavior and any affected devices or browsers.


This information helps the Support team review the problem more efficiently.


Note: HighLevel's troubleshooting guidance indicates that direct development-team debugging for improving page-speed scores is not provided. Performance testing tools and the recommended optimization steps are the primary resources for identifying page-speed improvements.

Frequently Asked Questions


Q: Does turning off Image Optimization disable lazy loading?

No. HighLevel automatically applies lazy loading to image elements independently of the Image Optimization setting. Turning off Image Optimization does not disable automatic lazy loading.


Q: Will every funnel or website receive a 15–25-point PageSpeed improvement?

No. The reported improvement is associated with delayed tracking-script hydration in Builder Preview. Actual results vary depending on page content, scripts, and other performance factors.


Q: Does the tracking-script optimization apply to pages without tracking scripts?

No. The specific Builder Preview improvement described in the release applies to pages containing tracking scripts. Pages without tracking scripts are outside the scope of this change.


Q: Can Optimize JavaScript affect custom scripts or integrations?

Yes. Optimize JavaScript may delay script execution or hydration. Custom code that depends on immediate execution may require additional testing or changes to the setting.


Q: Do Global Sections automatically improve page speed?

Not necessarily. Global Sections primarily support reusable content and synchronized updates. Page speed still depends on the content, images, scripts, and other elements contained within those sections.


Q: Do I need to enable the reduced HTML document size optimization?

No. The reported reduction in average HTML document size is an automatic HighLevel performance optimization and generally does not require additional configuration.


Q: Why might mobile PageSpeed scores be lower than desktop scores?

Mobile performance can be affected by device processing capabilities, network conditions, image sizes, and resource-heavy page elements. Testing both device categories helps identify differences.


Q: Why does my published page perform differently from Builder Preview?

Preview and published pages may have different loading conditions, scripts, or integrations. For visitor-facing performance measurements, test the published page URL and review the results.


Q: Should I focus only on improving my overall PageSpeed score?

No. Review the diagnostic recommendations and confirm that visitors can load and interact with important page elements. An improved score should not come at the expense of required functionality.


Related Articles


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article