Performance Issues

Quixli is built for speed, but various factors — from your internet connection to page complexity — can affect performance. If you're experiencing slow loading, editor lag, or general sluggishness, this guide walks you through diagnosing and fixing the most common performance problems.

Diagnosing the Problem

Before applying fixes, it helps to narrow down the cause. Ask yourself these questions:

• Is it just Quixli? If other websites and applications are also slow, the issue is likely your internet connection or device, not Quixli. Test by opening a few other websites

• Is it just this page? If other Quixli pages load fine, the problem is specific to the page content (probably too many images or blocks). If all pages are slow, it's a browser or network issue

• Is it just this browser? Try a different browser. If the issue goes away, it's browser-specific — usually caused by extensions, cache, or an outdated browser version

• Did it start suddenly? A sudden performance drop might indicate a service issue on our end. Check status.quixli.io for current status

Slow Page Loading

If pages take a long time to load or show a spinner for extended periods:

Network Fixes

• Check your connection speed: Run a speed test at fast.com. Quixli works best with at least 5 Mbps download speed. If your connection is slower, the editor and page content will load slowly

• Switch networks: If you're on Wi-Fi, try your phone's hotspot or a wired Ethernet connection. Public Wi-Fi and congested networks are common causes of slow loading

• Disable VPN: VPNs add latency to every request. If you're using a VPN, temporarily disable it to test if it's affecting Quixli's performance

Browser Fixes

• Clear browser cache: Corrupted or outdated cached files can slow down page loading. Clear your browser cache (just for the last hour is usually sufficient)

• Close unnecessary tabs: Each open tab consumes memory. If you have 30+ tabs open, your browser may be running low on memory, causing all tabs to slow down

• Disable heavy extensions: Ad blockers, privacy extensions, and development tools consume CPU and memory. Temporarily disable them to test performance

• Update your browser: Outdated browsers lack performance optimizations. Update to the latest version of Chrome, Firefox, Safari, or Edge

Editor Lag

If the editor loads but feels laggy when typing, scrolling, or interacting with blocks:

Page Complexity

The most common cause of editor lag is page complexity. The editor maintains a real-time data model that becomes heavier as you add more content:

• Break long pages into smaller ones: Pages with 100+ blocks or 10,000+ words can strain the editor. Split content into multiple pages within a collection — this also improves the reading experience

• Optimize images before uploading: Large, high-resolution images (5MB+ each) slow down both loading and editing. Compress images to under 500KB using tools like TinyPNG or Squoosh before uploading

• Reduce embedded media: Each embedded video, iframe, or interactive widget adds rendering overhead. If a page has more than 5 embeds, consider moving some to separate pages

• Remove unused blocks: Empty blocks, unused tables, and hidden content still consume memory. Delete any blocks that aren't contributing to the page

Collaboration Lag

If lag occurs specifically during real-time collaboration:

• Check how many editors are active: While Quixli supports up to 50 simultaneous editors, performance is optimal with 10 or fewer. If many people are editing at once, cursor and presence updates can cause overhead

• Close and reopen the page: Occasionally, the collaboration connection may degrade over long sessions. Closing the tab and reopening the page establishes a fresh connection

• Check your connection latency: Real-time collaboration is more sensitive to latency than regular browsing. If your ping to Quixli's servers is above 200ms, you may notice delays in cursor updates

System-Level Optimizations

• Enable hardware acceleration: Most modern browsers can offload rendering to your GPU. Check your browser settings for "Use hardware acceleration" and make sure it's enabled

• Close resource-heavy applications: Video editing software, virtual machines, and other resource-intensive applications compete with your browser for CPU and memory. Close them while using Quixli for best performance

• Restart your browser: Browsers can develop memory leaks over long sessions. If you haven't restarted your browser in several days, a fresh start often resolves sluggishness

• Check available RAM: The Quixli editor works best with at least 2GB of free RAM. If your system is under memory pressure (check Activity Monitor on Mac or Task Manager on Windows), close other applications or consider upgrading your system's memory

When to Contact Support

Contact [email protected] if:

• The performance issue persists across all browsers and networks

• status.quixli.io shows no ongoing incidents but your experience is degraded

• A specific page consistently causes crashes or freezes (include the page URL in your support request)

• You've tried all the steps above without improvement

When contacting support, include: your browser name and version, operating system, a description of the issue, and the approximate time it started. Screenshots or screen recordings are especially helpful.

Frequently Asked Questions

Is Quixli slower on certain browsers?

Performance is most consistent on Chrome and Firefox. Safari is slightly slower for complex pages with many blocks due to differences in JavaScript engine optimization. Edge (Chromium-based) performs similarly to Chrome.

Does the number of pages in my account affect performance?

No. Having thousands of pages in your account does not slow down the editor or page loading. Only the content of the currently open page affects editor performance.

Will upgrading my plan improve performance?

Plan level doesn't affect editor or loading performance — Free and Enterprise users get the same speed. However, Team and Enterprise plans include priority support with faster response times for performance-related issues, and Enterprise plans offer dedicated infrastructure that can be optimized for your specific usage patterns.

How can I check if a performance issue is on Quixli's end?

Visit status.quixli.io to see real-time service status and recent incident history. If no incidents are reported but you're still experiencing slowness, the issue is most likely on your end (browser, network, or device). You can also check the browser console (F12 > Console tab) for error messages — if you see network errors (status 502, 503), the issue is server-side.

Does Quixli throttle users on the Free plan?

No. Quixli does not throttle performance based on plan level. Free plan users have the same editor speed, page load times, and API response times as paid users. The only plan-based limits are feature access and storage quotas, not performance.