The first thing I'd say is that starting out with blue team (defending networks) will give you breathing room and time to learn pen testing/red team, as blue team IMO is a bit easier (requires less deep and specific knowledge) and you really should have experience there anyways before you do red team so you know how to avoid being detected. You should also learn programming ASAP, as it helps with every aspect of security (Python is a good beginner language, but you will want to learn C as well at some point.) Another piece of the puzzle to consider is learning system and network administration, as you will want to understand computers in every aspect to be more successful in detecting or performing cyber attacks.
For blue team you should get a mirrored switch for home (Amazon Link), and use Security Onion to practice with Suricata and Wireshark. Basically you want to set up a mirror port to send packets to your Security Onion PC (Amazon Link), which you log in to and try your best to understand what is happening on your home network. Go to Test My IDS to see what an alert looks like, and make sure your IDS is working properly. The new Security Onion (Github Link) uses the ELK stack, which I've used professionally, so just learning that is a really good start. If you don't understand Cisco, go out and get your CCNA, as this will also help with both red and blue team.
Also, you can learn a lot by looking at Malware Traffic Analysis, and writing up what you think is going on in the packet captures. If you use Packet Total, you can load up the captures they give you and analyze what's going on in them fairly easily. You could also download the capture files and replay them in Security Onion, so you will see a more real-world example of what attacks look like in "real-time". Use my IPINT Tool to get more context regarding the IP addresses you are seeing.
Finally, although my experience in this arena is limited, you should also consider learning some techniques related to Incident Response and Forensic Analysis. Your first stop should be installing and learning the Volatility Framework, which is used almost universally in memory forensics. Next, you will want to familiarize yourself with the curated Awesome Incident Response repo in Github. Finally, the PoshSec Framework is a good platform to learn, which can help you set up a system to be ready for IR, and it's free so you can do this from your home lab. Try installing it and attacking your systems that have it installed, and then tweaking the settings until you can detect attacks in this way (maybe send PoshSec logs to Security Onion or your preferred SIEM for analysis.) Once you have the hang of running and using PoshSec, go through the code itself to understand how it is constructed and consider writing modules for it.
One of the most important things you can do here, if you haven't already, is switch your primary OS from Windows to Linux. Doing this will help you in a number of ways, but the most noticeable way is that almost every security distribution and hacking challenge uses Linux as its foundation. When you do hacking challenges, you will be expected to know bash very well, and you should be familiar with the filesystem on a *nix computer. Note that you should make an effort to move entirely to Linux as your primary OS, so you can familiarize yourself with the initial struggles and obstacles that come along with the transition away from Windows. The more time you spend at the bash prompt, the more prepared you will be for penetration testing.
With that out of the way - if you want to get a head start on red team, I'd recommend checking out the Github "awesome" repos, which include "awesome-pentest", "awesome-ctf", and "awesome-security". There is a huge amount of good info there - my advice is just to not get overwhelmed, and try to set goals for yourself to stay on track - e.g. "I will review one entry from Awesome Pentest this week", "I will get my S+ in 6 months", "I'll do 15 minutes of programming every day/weekend", "I will finish one CTF challenge per month", etc... Protip - make your goals very simple and repetative, so you can spark your interest, which will quickly grow strong. Everyone can afford to spend 5 minutes programming per day.. what you will find though, is that after 5 minutes you will want to continue programming once you find interesting challenges to tackle.
Root-me.org is also awesome for learning hacking in general, where they give you concrete challenges, and the resources are attached to the challenges to make it easier to learn and understand. Look at awesome-ctf for more platforms, but in my experience the best beginner ones are:
My advice here is to get both certifications and practical experience as soon as possible, because it will prepare you for first passing the initial resume screening/keyword search, and also make sure you are ready for some technical and practical questions during your interview. The above advice should set you on a path to get practical skills and experience, while the below list charts a rough order of which certs you may want in order to obtain employment in the IT Security field.
You can get great training for these certs online, at places like NICCS, Tom's IT Pro, Udemy and Cybrary.
While certs and experience are very valuable, and can go a long ways towards landing you a job, the third thing that will give you the best chances at obtaining a desirable and well-paying job in the industry is networking. No, I don't mean you should grab a firewall and some switches and start subnetting away (although that's never a bad idea).. I mean that you need to start talking with people in the IT Security industry.
Go out and join your local hackerspace/makerspace, and see what people there are excited about. Get on IRC and meet people that are working on Metasploit, PowerShell Empire, Security Onion, Root-Me, and other security projects. Join some local/regional Cyber Security User Groups, and attend conferences like DEFCON, DerbyCon, and Wild West Hackin' Fest. I can speak from experience, that all of the skills in the world can't beat good real-world connections.
Finally, once you get a job interview lined up you have to do a great job making a good first impression. My advice has always been that, even if you lack specific skills or knowledge, you should be prepared to be so confident and personable, that the interviewer(s) don't notice or don't care. In my opinion, there is no excuse for having a bad interview, you just have to treat it like another skill that you are out to master. Here are some tips about preparing for, and making a great impression during your interview.
This last part is crucial: if you encounter barriers, or hit a wall with challenges, go onto IRC or reddit and ask the professionals. The infosec community is a very strong one, with one important caveat. DO NOT ASK TO BE HAND-FED. You must go in and ask questions so you don't get stuck and lose motivation, but do not go and say "hey everyone, I want to hack my wifi so where do I begin", or "I can't get this loop to work, can you tell me what's wrong with it?" You should demonstrate that you have done basic Google searches first, and put in some effort before you start to ask for help, otherwise people will most likely be hesitant to spend their (most likely valuable) time doing your work for you.