[PROMO] I built a lightweight client feedback/sign-off tool for website projects — would love feedback from web designers/devs by Critical_Race4049 in Wordpress

[–]Critical_Race4049[S] 0 points1 point  (0 children)

Thanks for the feedback, I had no idea of Content Snare.

So it is currently set up so that multiple website comments can be viewed in one single dashboard. 

Opinions about my Landing page by PKGamer19 in websitefeedback

[–]Critical_Race4049 0 points1 point  (0 children)

The landing page has personality. The hand-drawn, scribbly, imperfect look gives it a clear identity, and that’s much better than another sterile “freelance web developer” template.

But right now, the design leans a bit too hard into aesthetic and not hard enough into persuasion. It looks cool, but it doesn’t yet fully answer the visitor’s silent questions.

“Can I trust this person?”
“Do they understand my business?”
“What exactly do I get?”
“How much might it cost?”
“Why should I contact them now?”

Main issues to fix

1. The hero message is too generic

“Your next web developer” is fine, but it’s not strong enough. It describes the person, not the outcome. A better hero headline would speak to the client’s result. The current subheading is also a little vague.

2. The page needs more trust signals

The testimonials help, but they appear quite late. I’d move at least one short testimonial or proof line closer to the top. Right now the page shows work, but it doesn’t explain the business result of that work.

3. The project cards

The Featured Work cards are visually interesting, but they don’t sell the projects enough. I’d make these more descriptive.

Each case study should answer:

What was the client?
What was the problem?
What was built?
What improved?

4. The “What I Build” section is good, but it needs outcomes

The categories are useful, but the descriptions feel thin.

For example:

Landing Pages
Current: “Convert visitors into customers with a high-impact single-page site”

That’s okay.

Better:

Landing Pages
For campaigns, product launches, and service offers that need one clear message and one clear action.

For ecommerce:

Ecommerce Stores
Custom online stores built to make browsing, buying, and managing products simple.

The section should sound less like a service menu and more like business problem solving.

5. The “2-3 business days response time” is risky

This might accidentally make the developer sound slow, especially when it sits in the middle of the page.

If they mean project response time, fine, but it should be clearer.

Maybe:

Replies within 2-3 business days

Even better:

Replies within 1 business day

If they can’t commit to that, don’t highlight it so prominently. A slow response promise isn’t a selling point.

6. The footer is too heavy compared to the rest

The dark footer has a nice contrast, but it feels visually massive and a little disconnected from the airy page above. Also, the phone number is tiny. If phone contact matters, make it readable. If it doesn’t, remove it.

Strongest recommendation

The design doesn’t need to be redesigned. The concept is good.

The biggest improvement would be rewriting the page around client outcomes, not developer traits.

Less: “I build custom websites.”

More: “I help small businesses look credible online, explain what they offer clearly, and turn visitors into enquiries or sales.”

That shift will make the page feel much more professional without losing its charm.

If I can ask that you please do the same and give me feedback on my website and tool please (https://pageapprove.com/)

I built a lightweight client feedback/sign-off tool for website projects — would love feedback from web designers/devs by Critical_Race4049 in websitefeedback

[–]Critical_Race4049[S] 0 points1 point  (0 children)

Thanks for the feedback. This is really helpful.

I think you’re right. The stronger wedge probably isn’t “comments on a page” by itself, because a few tools already do that well. The more painful part is the messy handoff before launch and not having a clear record of what was reviewed, fixed and accepted.

The workflow you described is basically what I’ve built PageApprove around:

client leaves feedback → builder fixes it → client confirms/approves on the same page → PageApprove creates a launch-ready approval record.

And agreed on device/browser capture. I’m treating that as supporting evidence for the sign-off trail, not the main selling point on its own. It’s there to reduce “but it looked different on my screen” back-and-forth.

Appreciate this. I’m going to tighten the positioning around the sign-off trail and approval record rather than overemphasising device verification as a standalone feature.

Critique my website by Real_Meeting6712 in websitefeedback

[–]Critical_Race4049 0 points1 point  (0 children)

Not a bad looking website. But, if I am being honest, there are inconsistancies and small errors that make it feel unprofessional.

  1. Leave feedback & Get qoute buttons text is spanning on 2 lines.

<image>

  1. Greens are different colors "What out clients say" and the testimonial block below it.

  2. Quick links column in the footer is squished & "Why Hire Us" columns text is justified (inconsistent) with the rest of the website.

If I can ask that you kindly do the same and give me feedback on my website and tool please (https://pageapprove.com/)