Landing Page launched: SplitCSS - API for reducing unused CSS

Looks nice!

Pricing:

• The price looks low. If you're driving value for businesses you can charge way more. I may start by offering fewer requests for free and then charging more for premium plans.
• IMO it's unlikely someone is going to sign up for a premium plan to start. They'll likely test it out for free and then go premium. Because of this it might not be necessary to put the pricing on the landing page at all.

Music:
Agreed with XCS on the video - a little cheesy and the music is a bit much. In fact I jumped out of my seat a little bit when I hit play because the music was loud and jarring.

Highlight benefits:

• You have some good benefits you mention in the video that would be worth highlighting on the landing page.

The landing page looks pretty nice. The video feels a bit cheesy and is hard to read, plus it would be better without any music than the current song choice.

I have some question about the product itself:

• Who is the target audience?
• Why would I use this over removing CSS at build time?
• If and how does it detect CSS accessed/used by elements created in JavaScript (as with most single-page-apps) ?