That's fair. I was under the impression that when places give you the chance to put a portfolio/personal website link, the people reading your application glance through them.
I took a look at your resume. I feel I agree with most of the decisions you made (like prioritizing the projects).
Some comments on this (same disclaimer as before):
I have to wonder whether you would get more mileage out of shortening your summary statement to "Full stack web developer who will help your company succeed by completing projects on time and under budget." or eliminating it entirely. Certainly at least the large font "Summary Statement" can go, which would make room for you to add another project.
I can believe the other commenter here who said that not having a 4-year CS degree will make it more difficult to stand out. So I can agree with putting your education last. But also I have this feeling that most resumes I've seen put it first. So I'm wondering whether it would make more sense to just own it. Again, your projects seem pretty legit to me, which I think can help compensate.
Finally, I would spend some time trying to play with the wording of your bullet points. It can be easy to sell yourself short and just say things like "Built using the React.js library and Typescript." but like your portfolio website is actually really cool and I feel saying something like that doesn't convey how cool it is. Maybe to get you started you can try something like "Designed and built an interactive portfolio page with interactable elements that simulate terminal windows." The JSON part is pretty good but I bet you could embellish it a bit more too. Sorry I don't have great suggestions for this one - I struggle with it too. The other tip I can give is to write impressive numbers where you can. The canonical example is like if you can say "made processing widgets 25% faster" or "increased revenue by 10%," but I think there are ways you can be creative about this.
One miscellaneous point: have you been grinding leetcode/reading cracking the coding interview? Much like the SAT, a lot of these technical interviews are just testing how familiar you are with the format and questions. It's a kind of bogus indicator of competency if you ask me. If you do the grinding, you should be ready for most the tech interviews that come your way.