Your website is pretty much blank. Only words on the home page are about, login, and Elyxel. Also this post didn't explain what your project is. The about page contains a vague one sentence description.
You need to explain what problem you are fixing and how your product fixes it if you want to get any traction. People aren't going to signup if they don't know what they are signing up for.
I think you need to make it easier for people to get started. I almost didn't signup because I had to create an account before I could view any of the photos for sale. It would have been much easier to jump in if I could have just started browsing photos. Make make me signup after I have gone through a few pages of pictures.
The real kicker was when you asked for my credit card right away. I am a big fan of credit card up front on subscription services with a free trail. But I just wanted to see the product. There ins't anything for me to be excited about yet. Luckily I noticed that I could just click something in the menu to skip this step. I would put of asking for the card until you they go to make a purchase. You have my email address so you can already follow up if I abort at the CC step later.
Using important is only going to fix the problem if you have defined a style for that element. For example, if you have not defined a border then the client will still be able to add one.
Most sites use iframe for embeded widgets for this reason.
I think Stripe's checkout doesn't use iframe. They just define every single style with very specific rules. From what I remember.
He didn't find customers. He found 2K looky-loos. Customers are people who are paying for the product (or meet some activity threshold in a free product). He found 2K people who were willing to give their email address to learn more about what was being offered.
That is a positive sign, but they aren't customers. It seems like 2,00 people logged in and then found out the product wasn't what they were expecting.
I know this was the case for me. I signed up hoping for a really nice online IDE. I found a bunch of ssh stuff that made no sense to me.
It might be worth talking to the 2000 people and finding out why they signed up and what type of product they were hoping to find.
It's a service that solves SEO for javascript driven websites.
For the most part, Google can't crawl sites that manipulate the DOM using javascript (AngularJS, Backbone.js, Ember.js, etc). The solution is to use a headless browser to make html snapshots for all your pages and serve those to Google instead of the page that requires javascript.
This turns out to be a bit of a pain in practice. So, BromBone does it for you. It generates, hosts, and updates the html snapshots. When Googlebot visits your site, you proxy the snapshot from BromBone and serve it to Google. Now Google can see the same thing your users see.
You can get it faster than 15 seconds, but you can't really get it fast enough. We precache everything. I would strongly recommend against trying to process the pages in realtime.
Certainly cool that Google is working on this. I suspect someday it will all work perfectly.
However, from working with customers of BromBone, I know this. People have javascript powered webpages that were not getting indexed by Google. Google would crawl the page, and see no content. The pages were not in Google. After creating prerendered snapshots and serving them when the _escaped_fragment_ parameter was present, the pages showed up in Google.
You need to explain what problem you are fixing and how your product fixes it if you want to get any traction. People aren't going to signup if they don't know what they are signing up for.