What we learned installing CCTV in a working warehouse
Four things we check before quoting a warehouse camera install — learned the expensive way.
36
0
Read
Article / Blog post
Infrastructure
Why your network is the reason your software feels slow
A diagnostic guide for anyone about to blame the wrong layer
AD
admin
27 June 2026
2 min read
35 views
Updated 1 Aug 2026
Almost every “the system is slow” ticket we investigate turns out to be a network problem wearing a software costume. Here’s how to tell the difference before you pay someone to optimise the wrong thing.
The symptom that gives it away
Software that is genuinely slow is consistently slow. It takes four seconds to load in the morning and four seconds at 3pm.
Network problems are variable. Fast at 8am, unusable at 11am, fine again after lunch. If your users describe the problem in terms of time of day, stop looking at the application.
The five-minute test
Run a continuous ping to your gateway during a slow period. If latency swings from 2ms to 300ms, you have a saturation or duplex problem, not a code problem.
The usual culprits
In rough order of how often we find them
- One flat VLAN carrying cameras, staff, guests and VoIP together
- An unmanaged switch dropped into the chain by someone in a hurry
- Duplex mismatch on an uplink — silent, but halves throughput
- A camera NVR pushing constant multicast across the whole network
- WiFi access points on overlapping channels fighting each other
- The uplink genuinely being too small for the site
What good looks like
Before and after segmentation
Flat network
- All traffic on one broadcast domain
- Camera bursts stall staff file transfers
- Guest devices can reach internal servers
- No visibility into which device is saturating the link
Segmented network
- Cameras, VoIP, guests and staff on separate VLANs
- Per-VLAN bandwidth limits protect critical traffic
- Guest network isolated from everything internal
- Per-port statistics show exactly what's using the link
Typical small-office baseline
Cabling
Cat6, certified, labelled both ends
Switching
Managed, VLAN-capable, PoE where needed
Segmentation
Minimum 4 VLANs: staff, guest, camera, VoIP
Uplink
Sized at 3–5 Mbps per concurrent user, minimum
WiFi
Surveyed placement, non-overlapping channels
Monitoring
Per-port utilisation with alerting
Not sure which layer your problem is in?
We'll audit it and tell you honestly — even if the answer isn't work for us.
0 comments
No comments yet — be the first.
Leave a comment
Comments are reviewed before appearing. Your email is never published.
Keep reading
AIBit IT-Solutions launches its new website
Everything about AIBit in one place — services, case studies, documentation and a direct line to our engineers.
54
1
1
Read
Platform release v1.0
First public release: block editor, SEO layer, reviews, lead pipeline and first-party analytics.
53
1
Read
Let's build it
Ready to modernise your systems?
Tell us what you're trying to solve. We'll scope it honestly, quote it clearly, and build it properly — software, AI, networks or all three.
Prefer to call? 0995 315 0273 · Mon–Sat, 8:00 AM – 6:00 PM