Ask HN: Roast My Website: Rewrote the Copy Hi guys,
I was having trouble with a lot of people not understanding the key points my product seeks to address. Can I ask you to roast it? https://fastmonitor.io Thanks! |
Ask HN: Roast My Website: Rewrote the Copy Hi guys,
I was having trouble with a lot of people not understanding the key points my product seeks to address. Can I ask you to roast it? https://fastmonitor.io Thanks! |
"The Web's Best Collaborative Monitoring Tool" The only words that make sense in this sentence are "monitoring tool".
Which stakeholders are collaborating? In what way is it the best?
How are charts going to "continuosly [sic] improve performance" << continuously is the word, you should use a spell-checker.
I couldn't find "continuosly" in the dom - where is it?
"Continuous Monitoring & Alerts for Downtime and Page Speed. Share Notes, Discuss Changes, and More."
best → easiest? simplest? most straightforward?
I always found that when i was working in any type of data analysis, and there was an anomaly, i would figure out what was up, and then... a few days later forget. So having notes on charts and whatnot and being able to share with colleagues is the collaborative part. Especially around outages and slow downs, (or speed ups) we want to know why.
My approach would be more like this:
Pitch : "Continous page speed monitoring."
Call-to-Action: "Slow page loads lose business"
Explain-fix(es): "FastMonitor showed me which images were too big"
Explain-fix(es): "find a tricky intermittent problem "
I would explain these basic points within the initial viewport (without requiring scrolling), then if you scroll down you can explain the charts and whatnot. Also small-caps can make headers look sharp.
Also good luck and I wish you the best.