Fix Slow LCP on Simvoly (Speed Guide) | OpsBlu Docs

Fix Slow LCP on Simvoly (Speed Guide)

Reduce Simvoly LCP by compressing section background images, limiting embedded widgets, and removing unused funnel page elements.

General Guide: See Global LCP Guide for universal concepts and fixes.

What is LCP?

Largest Contentful Paint measures when the largest content element becomes visible. Google recommends LCP under 2.5 seconds. Simvoly is a hosted website and funnel builder with a drag-and-drop editor. Since you cannot modify server configuration or access the underlying code directly, LCP optimization focuses on content choices, image preparation, and minimizing builder-injected overhead.

Simvoly-Specific LCP Causes

  • Uncompressed section backgrounds -- Simvoly sections with full-width background images serve whatever you upload with limited automatic optimization
  • Funnel page complexity -- multi-step funnel pages load all step assets upfront, including forms, countdown timers, and payment widgets
  • Builder framework overhead -- Simvoly injects its own CSS/JS framework for the drag-and-drop layout system on every page
  • Third-party embed widgets -- embedded forms (Typeform, Calendly), chat widgets, and video players block rendering
  • Google Fonts loading -- custom font selections load via render-blocking CSS

Fixes

1. Optimize Images Before Upload

Simvoly has limited server-side image processing. Prepare images locally:

# Resize hero images to max 1920px wide, compress to 80% quality
mogrify -strip -quality 80 -resize "1920>" hero.jpg

# Convert to WebP for smaller file sizes
cwebp -q 80 hero.jpg -o hero.webp

# Target: hero images under 200KB, content images under 100KB

In the Simvoly editor:

  • Use the Image Settings panel to set width to match the section width (avoid oversized images)
  • Prefer JPEG for photos, PNG only for graphics with transparency
  • Avoid using video backgrounds on hero sections -- use a static image with a play button overlay instead

2. Simplify Above-the-Fold Sections

  • Limit the first visible section to one image + one headline + one CTA
  • Move testimonial carousels, counters, and multi-column layouts below the fold
  • Remove decorative background images from header/hero sections if text is the primary content
  • Use solid color or gradient backgrounds instead of large image backgrounds where possible

3. Minimize Third-Party Embeds

  • Delay chat widgets (Intercom, Drift) -- set them to load after 5 seconds or on scroll
  • Replace embedded videos with thumbnail images that load the player on click
  • Move Calendly/Typeform embeds to dedicated pages instead of embedding in the main page
  • Limit to one embedded widget per page above the fold

4. Reduce Funnel Page Weight

For Simvoly funnel pages:

  • Remove unused steps from multi-step funnels
  • Disable countdown timers and animated elements on landing steps
  • Use Simvoly's built-in forms instead of embedding third-party form tools
  • Minimize the number of sections per funnel step

5. Choose Lightweight Font Options

In the Simvoly design settings:

  • Limit to 2 font families maximum (one for headings, one for body)
  • Prefer system-safe fonts (Arial, Georgia, Verdana) for body text
  • If using Google Fonts, choose fonts with fewer weight variations (Regular + Bold only)

Measuring LCP on Simvoly

  1. PageSpeed Insights -- the primary tool since you cannot access server configuration
  2. Chrome DevTools Network tab -- identify the largest image or resource loading in the critical path
  3. Compare pages -- test your simplest page vs. your most complex page to identify which elements add the most load time
  4. Mobile testing -- Simvoly's mobile rendering may serve the same image sizes as desktop

Analytics Script Impact

  • Add analytics via Simvoly's Settings > Custom Code > Header/Footer section
  • Place GA/GTM scripts in the Footer code section, not Header
  • Avoid adding multiple analytics platforms -- each adds 50-200ms to page load
  • Simvoly's built-in analytics (if available on your plan) add minimal overhead compared to external scripts