When school software is slow or stuck loading, the cause is usually local — the browser, the device, the office internet line, or a large background job still running. Try a refresh, a second device and a second connection first, then report the exact screen, time and campus so support can trace it.
Is it the platform, your connection, or just one screen?
The first job is to narrow the problem down. A cloud platform reaches you through several layers: the servers, the internet path, your office router, the device, and the browser tab itself. Any one of them can make the software feel slow while the rest are perfectly healthy.
EDUBase Cloud's web portal is a React single-page application served over HTTPS, with PHP/Laravel APIs and MySQL behind managed cloud servers that run containerised behind Cloudflare. The EDUBase team runs external monitoring of the servers, the resolver and the messaging gateway with alerting, so platform-wide trouble is detected and acted on by the team rather than by one school's office.
Before assuming the platform is down, check whether the slowness follows the screen, the device, or the person.
- Does the same screen load on another computer in the same office? If yes, the first device is the problem.
- Does the same computer load on mobile data instead of the office Wi-Fi? If yes, the network is the problem.
- Is only one screen slow, or every screen? One slow screen usually means a very large report or date range.
- Is it slow for one user only? Check whether that user's device has many tabs, updates or antivirus scans running.
What should admin staff check on the device and browser first?
Most "stuck loading" reports from a school office are solved at the desk. A single-page portal keeps a lot in the browser's memory, so a tab that has been open since morning, with a dozen other tabs beside it, will feel heavy on an older PC.
Go through these in order and note what changes after each step, so you can tell support what you already tried.
- Do a hard refresh of the page, then sign out and sign in again with your school code and username.
- Close unused tabs and other heavy applications; restart the browser, then the computer.
- Use an up-to-date Chrome or Edge browser rather than an old, unpatched one.
- Clear cached site data for the portal if a screen still shows old figures after a refresh.
- Try the same task in a private/incognito window to rule out extensions and ad blockers.
- If a shared counter PC is old, test the same task on a newer machine before blaming the software.
How do we tell a network problem from a platform problem?
A school office often runs on one shared broadband line that also carries CCTV uploads, staff phones and streaming. When the line saturates, every cloud service becomes slow at once — the portal, email, WhatsApp Web and video calls together.
A simple test settles it: switch one computer to a mobile hotspot. If the portal becomes responsive on mobile data while the office Wi-Fi is still slow, the fix is on your side of the wire.
Also check that no local filter, firewall or DNS setting is blocking or delaying the portal and app traffic. All portal and app traffic runs over HTTPS, so a proxy or content filter that inspects encrypted traffic can add noticeable delay.
- Test one device on a mobile hotspot and compare.
- Check whether other cloud sites are equally slow at the same moment.
- Ask whether anything new was added to the network — a new camera system, a new router, a filtering box.
- Note the time of day: many offices slow down during the fee-collection rush because everyone is on the same line.
Could a big job still be running in the background?
Some actions in a school system are genuinely large: generating challans for a whole school, importing thousands of students, exporting a full-year report. In EDUBase, school-wide challan runs are queued in the background and you are notified in-app when they finish, and large bulk imports are queued the same way with an in-app notification on completion.
That is by design — it stops the browser from sitting on one request for a long time. If you clicked generate and the screen did not change, do not click again. Wait for the notification, then check the result before repeating anything.
Fee automation also has a run history, so each scheduled run is logged with what it did. If you are unsure whether a run happened, read the history rather than re-running the job.
- Do not press a bulk action twice; wait for the in-app notification.
- Check Run history for scheduled fee automation before re-generating.
- Narrow date ranges and campus or class filters on heavy reports, then export to Excel instead of paging through the screen.
- Run whole-school operations outside counter hours where you can.
What should we send to support so it gets fixed quickly?
Vague reports take the longest to resolve. Support can move much faster with the exact screen name, what you clicked, the campus, the date and time, and a screenshot or short screen recording including any error message.
EDUBase support is available by WhatsApp group, phone and in-app requests from 9:00 AM to 5:00 PM on working days for live help, while the in-app AI assistant, tutorial videos and documentation are available round the clock. The assistant answers how-to questions from EDUBase's own knowledge base in English or Roman Urdu, with links to the exact screen and tutorial video, which often settles "is this screen supposed to take this long?" straight away.
- Screen name and the exact steps you took.
- Campus, class and date range selected.
- The date and time it happened, and whether it was during the fee counter rush.
- Whether it affects one user, one device or everyone in the office.
- What you already tried: refresh, different device, different connection.
- A screenshot or recording of the message shown.
What does EDUBase run on its side to keep the platform available?
Hosting, backups and monitoring are run by the EDUBase team, not by the school. The platform is hosted on managed cloud servers, containerised, behind Cloudflare, with each school's data in its own database rather than mixed with other schools' records.
External monitoring covers the servers, the resolver and the messaging gateway with alerting, and regular database backups are kept off the application servers. New features and app updates ship regularly to every school without any installation on the school's side, so there is nothing for your IT person to patch locally.
Because each school has its own database, one school's heavy report run does not sit inside another school's data. Your office's job is therefore narrower than it looks: keep the devices, browsers and internet link in good shape, and report precisely when something is genuinely wrong.
- One database per school, per-school credentials.
- Regular backups kept off the application servers.
- External monitoring with alerting on servers, resolver and messaging gateway.
- HTTPS for all portal, app and integration traffic.
- Updates delivered centrally, with no installation at the school.
Common slowness symptoms, likely causes and first checks
| Symptom | Most likely cause | What to check first | Who usually resolves it |
|---|---|---|---|
| Every screen slow on one PC only | Device or browser load | Restart browser and PC, close tabs, test on another machine | School IT / admin staff |
| Every cloud service slow in the office | Shared internet line saturated | Test one device on a mobile hotspot, check other sites | School IT / internet provider |
| One report takes very long | Very wide date range or whole-school scope | Narrow campus, class and dates; export to Excel | Admin staff |
| Bulk challan or import appears stuck | Job queued in the background | Wait for the in-app notification; check run history | Admin staff, then support |
| Page loads but data looks old | Cached page in the browser | Hard refresh, sign out and sign back in | Admin staff |
| Login fails or session ends often | Session expiry or wrong school code | Re-enter school code, username and password; ask admin for a reset | School admin / support |
| Parent says the app is slow | Parent's own phone or mobile data | Ask the parent to test on Wi-Fi and update the app | Support, with parent |
| Portal fine but messages not arriving | Messaging path, not the portal | Check SMS, WhatsApp and app notification delivery logs | Admin staff, then support |
Related
- Cloud & Infrastructure Services — Managed hosting, one database per school, backups, monitoring and secure networking for education workloads.
- Training & Support — Live Google Meet training, module video playlists, in-app docs and an AI assistant, with WhatsApp and phone support in working hours.
- Integrations: Bank, SMS, WhatsApp & Biometric — Bank fee collection with HBL, Bank Alfalah, Meezan, PayPro and KuickPay; SMS and WhatsApp gateways; QR, biometric and face devices.
- Hosting security on edubaseems.com
- Users privileges security on edubaseems.com
- Fee automation on edubaseems.com
- Bulk data import on edubaseems.com
- Owner dashboard reports on edubaseems.com
- Face attendance on edubaseems.com