I agree with much of the other constructive criticism you've received. In case it's helpful, your 20 seconds of attention on a first look over a CV would go something like this if I were the reviewer:
1. Made an effort to produce a distinctive on-line CV. Good.
2. Layout at top of page is broken and chose an unusual and poorly rendered web font. Bad.
3. What does he actually do? Generic terms like "building web systems" and "creating beautiful code" don't tell me very much. Neutral (but wasting time).
4. Ah, OK, he's a full stack guy, with a variety of modern tools listed. Better.
5. But despite talking about HTML5, CSS3, and other modern front-end technologies, the layout is completely broken again around that diagram, and neither the typography nor graphics are well done generally. Bad.
6. Despite claiming many years of experience, the practical skills and attention to detail aren't up to professional standards.
7. No hire.
I am left with the impression of a Jack of all trades but master of none. I did read on to the end of your CV after I recorded the above, and to be brutally honest, it reinforces that impression.
You're a contractor and keen to learn new technologies, which suggests that while buzzword-compliant you don't necessarily have much depth behind any of the technologies you mention throughout the CV, and nothing you say anywhere really counters that impression with hard data about years of experience with each tool, how many projects you've done with each tool and what kind of scale they were on, etc.
You're a UX designer, but your CV isn't optimised for scannability at all.
You adapt to change, yet the reason your layout is broken right at the top of the CV is that you're using a static background image to create a bubble that doesn't quite fit the text you wanted to show in it, instead of gracefully degrading CSS3 that would have expanded automatically to fit that text.
You believe in lots of testing and continuous integration, yet you've failed basic cross-browser compatibility on several counts, all of which would be common knowledge to a good web designer/developer.
OK, enough with the negativity. I figure that usually being brutally honest on these occasions is more helpful in the long run than sugar-coating stuff that is bad, but please don't take any of this personally or think I'm just having a dig.
If I were you, I would either spend a bit of time polishing up my front-end skills to get the design into shape or acknowledge the limitation (both personally and by toning down the related content in the CV) and get help from someone who is an expert in that particular area. I would also get help from a professional careers advisor or other CV-writing expert on how to organise your content for the way real people are going to read that CV. You do have a lot of potentially interesting material in there, and I totally respect that you've made the effort to present it nicely, but the rookie mistakes in the design and lack of scannability are letting you down right now.