I fully agree to what Randell said, I think that is very good advice.
I’ll give some feedback from my experience of reading and judging over 100 CVs and conducting over 50 technical interviews last year. These numbers in the 10s and 100s are common at big tech companies.
Before I go into details, I want to emphasize that I’m going to critique the presentation & communication style of your CV. This is not a comment on you as a person or your skills, personality etc.
My first piece of advice is: Avoid copy-paste and sentence templates. For example the below quote from your objective statement (highlight added by me):
motivated self taught web developer and a fast learner who can transition easily into any new work environment
You mention 3 skills: motivation, quick learning, adaptability. Those sound nice but I don’t see evidence to support those claims. (Seemingly) empty claims are a bad sign.
Even if you don’t have professional experience in software development you may have examples of motivation, quick learning or adaptability in other contexts. Did you run a club in school/university? Did you volunteer for something? Have you been in a challenging work situation that you had to adapt to? If so giving a concise account (2-3 sentences) shows that you are not just making things up and it is a great entry point for conversation during an interview.
Secondly: You have projects to show off what you learned - that is great. Linking to the source code is also great (I always look at source code that candidates submit to gain an understanding of their development style & practices).
However with study/learning projects I would like to see them deployed as a fully functional application/demo (e.g. on heroku). Showing off a web application, even if it is just a prototype, will convince the technical reviewer of your CV high confidence in your skill - it shows that you learned a lot (motivated, quick learner).
Lastly the visual presentation is a bit bland & loveless (maybe some of it got lost when you transferred it to google docs).
This may seem a bit nitpicky but it has a big impact.
Typography: You use more different font sizes than necessary. You mix serif and sans serif fonts. There’s a gray background behind the motivational statement. Maybe go easy on the bold type. I suggest you keep it simple: 1 font, 2 font sizes, user bold rarely.
Visual noise & white space: Your CV is visually busy. In addition to simplified typography adding some white space to visually group sections that belong together makes it a lot easier read. Especially When the reader comes back to the CV to quickly find a piece of information that she remembers from the first read through (that happens 2-10 times for every CV that I receive)
Hyperlinks: You are sending a digital document to apply for a position in tech. Nobody will type out the urls you put on the CV. They will click it. Therefore I suggest put in clickable links behind descriptive titles:
Chat Application
Technologies: Python Socket (IP/TCP) Programming, Git
Description: Allows users to communicate with each other via a server and a client
Or if you have a functional demo of it
Chat Application (GitHub, Live Demo)
Technologies: Python Socket (IP/TCP) Programming, Git
Description: Allows users to communicate with each other via a server and a client
This got a bit longer than I intended, I hope it’s not too much 
Moreover I hope it makes sense and is applicable.
