Skip to main content
Zonely is installed on the first opening of your site (preloader/dom screen), it is not an ordinary visual animation or aesthetic standby effect. This screen, Private Zonely WAF (Web Application Firewall) The engine is a critical security shield that runs the rear-ground milliseconds browser verification (browser challenge) and Layer 7 bot protection.
Precise Safety Rule: From the management panel, theme editor or custom CSS/JS codes (display: noneload screen with septic blocking etc. should not be closed strictly. Closing this screen leads to locking your site and blocking legitimate visitors.

What Do The Load Screen On The Background?

The following processes are taken in the background when the visitor enters your site:
  1. Browser Verification (JavaScript Challenge): If the visitor is a real human/seer or an automatic attack bot, scraping tool or SQL Injection browser, it scans in 0.2 to 0.5 seconds.
  2. Production of Security Session Switches: A special encrypted CSRF and WAF session token (token) is assigned to the session of the visitor.
  3. The provision of Page Security: Verification is successful, the moment is loaded on the screen itself disappears and the visitor directly log into the site.

What happens if the uploaded Screen is closed?

When the load screen is hidden with special CSS or disabled, these critical problems arise in the system:

1. 403 Forbidden and Infinite-Adding Cycle (Challenge Loop)

  • Problem: WAF browser verification tries to open page DOM without completion.
  • Conclusion: The security motor detects the request from the incoming as unaffected suspicious boat traffic. Visitors HTTP 403 Forbidden error is given or the page enters endless loop by continuously reloading.

2. Token Loss on Store purchases and Entry Forms

  • Problem: Logs and CSRF security tokens that must be produced during the loading screen cannot be produced.
  • Conclusion: When users receive products from the store, upload balance or fill in the registration/input form “Security verification fails” or “Required request” error; payment and order flow are interrupted.

3. Definsiveness Against Layer 7 Attacks and Bot Blitz

  • Problem: Every raw request from the server is directly sent to the database and PHP core as bot filtering filter is skipped.
  • Conclusion: Your server is completely vulnerable to HTTP flood, brute-force account trials and automated spam bots; slows or crashes from site over-source consumption.
  • Problem: The style and script assets of the theme are structured to work synchronize with security verification.
  • Conclusion: When the screen is forced, the browser cache is crocheted with WAF; a blank white screen (White Screen) can be seen against visitors.

Accurate Use and Solution

  • Drop As Display: Zonely WAF is loaded screen is completed as soon as one of the tens of seconds for legitimate users and does not negatively affect user experience.
  • Add Custom CSS: Management panel -> Theme Settings -> Custom CSS field .preloader { display: none; } or do not add like hide codes. If you haven’t added these codes immediately remove.
  • Cache Cleanness: From keyboard to your users who live in jewelry on the load screen Ctrl + F5 (For Mac Cmd + Shift + R) Recommend browser cache cleaning.