The tcp/ip network protocol suite is what is known as 'self healing' - it is capable of detecting errors and requesting retransmissions for packets containing errors, and it does so, for the most part, transparently - ie, without the knowledge of, or any action by, the user.
Unfortunately (or fortunately, depending on your point of view), this 'self healing' property masks the errors - on a lightly loaded network - for example, one used primarily for web browsing, you could have error levels into the 90% percentile and the users would be none the wiser - untill they attempted to transfer data files of a few MB or more (the files used in webpages are usually just a few KB) across that network, at which point it would fail, and unfortunately, many of the file transfer protocols are not quite as accomodating - the user will have to restart the transfer which may fail again, and again, and again - unless/untill the underling cause of the failure is identified and fixed.
So - a wireless network being close to failure would/could be classified as one with high levels of errors and retransmissions. The most common cause is interference, and that interference can come from many sources - other wireless networks, other 2.4 GHz radios, weak signals, etc.
When wireless works, it can work well - but the exact same equipment that works well for me, out in the middle of the rainforest, might not do so for you in an apartment building in the suburbs of Metropolis where you have a few dozen other networks, plus baby monitors, wireless door viewers, surveillance cameras, and whatever else, in close proximity