Issue: Splash Page is slow

Description

When I connect to the access point, the Splash Page is very slow

When users encounter a slowness in the splash page loading while connecting to the access point on the Cloud4Wi platform, it is essential to understand the typical user experience and the reasons behind the issue. Here's a detailed explanation of the problem and how to troubleshoot it:

User experience

The typical user experience is that when they attempt to connect to the Wi-Fi network through the access point, they are redirected to the correct Splash Page URL, but the page is slow to load. Some seconds are needed before the page is correctly loading

 

Why does this happen?

Possible Causes: The slowness in the splash page loading can stem from various factors, including network-related issues or problems with the customization of the page. The main reasons for this issue are outlined below:

1. Slow Connectivity: Insufficient network speeds can result in delays in loading the splash page, causing frustration for users.
2. Missing Walled Garden Entries: If essential entries are not included in the walled garden settings, certain resources required for the splash page may be blocked or inaccessible, leading to slow loading.
3. Heavy Images in Customization: Overly large or uncompressed images used in the customization of the splash page can significantly slow down its loading speed.

Troubleshooting

To efficiently debug and identify the root cause of the slow loading issue, follow these steps:

1. Check Network Speed: Perform a speed test on your network to ensure that the slow loading is not due to a lack of internet connectivity or inadequate performance.
2. Optimize Media and Images: Verify that all uploaded media and images used in the customization of the splash page are appropriately sized, aiming to keep them under 200 KB to improve loading times.
3. Verify Walled Garden Entries: Double-check and ensure that all necessary entries have been added to the walled garden, based on the configurations and capabilities you have set. For a comprehensive list of requirements, refer to the documentation on Enabling the CDN.
4. Use Browser Dev Tools: Utilize the browser's Developer Tools to identify any resources that may not be opening within the walled garden or are causing delays in loading.

Where can I find browser Developer Tools?

Example with Chrome:

click the button to the right of the address bar and select More Tools > Developer Tools.

In the Network section, you can visualize the opening time of each component:

5. Check Custom CSS: If you have applied custom CSS to the page and included references to external resources (e.g., background image URLs), ensure that the walled garden on your access point is configured to allow these resources to be displayed correctly. 

Example:

If you applied a CSS to your Splash Portal to add a new font from fonts.googleapis.com it is necessary to add the Google domain ”googleapis.com” or the hostname “fonts.googleapis.com” in the walled garden section of your Controller:

By following these troubleshooting steps, you can identify the root cause of the slow page loading issue and take appropriate actions to resolve it. This will ensure a smooth and seamless user experience for Wi-Fi users on the Cloud4Wi platform.

Best Practices to prevent Issue from occurring

• Make sure to follow the Vendor configuration guide
• Make sure to test the full customer experience during the roll-out test

What information to provide on a support ticket if all the above does not work

If you have troubleshooted and debugged using hte recommendations above, please open a ticket on https://cloud4wi.zendesk.com/hc/en-us/requests/new.

Please make sure you provide the following information in the ticket related to this issue:

• Tenant ID: Tenant id or Name
• Type: Issue
• Subject: brief description 
• Attachment: Screenshare of the end user experience, Internet speedest screenshot once online, screenshot of the walled garden section configured on the Controller
•  Description: 
  • Location name or AP MAC address
  • Tests already performed based on troubleshooting guides
  • CCs if needed