r/web_design • u/AutoModerator • 8d ago
Feedback Thread
Our weekly thread is the place to solicit feedback for your creations. Requests for critiques or feedback outside of this thread are against our community guidelines. Additionally, please be sure that you're posting in good-faith. Attempting to circumvent self-promotion or commercial solicitation guidelines will result in a ban.
Feedback Requestors
Please use the following format:
URL:
Purpose:
Technologies Used:
Feedback Requested: (e.g. general, usability, code review, or specific element)
Comments:
Post your site along with your stack and technologies used and receive feedback from the community. Please refrain from just posting a link and instead give us a bit of a background about your creation.
Feel free to request general feedback or specify feedback in a certain area like user experience, usability, design, or code review.
Feedback Providers
Please post constructive feedback. Simply saying, "That's good" or "That's bad" is useless feedback. Explain why.
Consider providing concrete feedback about the problem rather than the solution. Saying, "get rid of red buttons" doesn't explain the problem. Saying "your site's success message being red makes me think it's an error" provides the problem. From there, suggest solutions.
Be specific. Vague feedback rarely helps.
Again, focus on why.
Always be respectful
Template Markup
**URL**:
**Purpose**:
**Technologies Used**:
**Feedback Requested**:
**Comments**:1
u/Medium-Reveal-4917 8d ago
URL: https://alexeiraymond.com/
Purpose: My personal author website, a place to collect and showcase my short fiction, as well as some experimental, interactive pieces.
Technologies Used: Astro, TypeScript, vanilla JS, CSS, GitHub Pages
Feedback Requested: whether it runs smoothly for you, or not (I only tested on Chrome, Firefox, my android phone, my laptop), whether the design seems ok (I still have some inconsistencies to iron out, some visual language commitments to make), whether you think it's conducive for a reader to understand what's what and how to access a story.
Comments: I'm a fiction writer who started writing in early 2025, and I've spent the past six months building and tinkering with this website. I've tried to give it a distinct visual identity and borrowed some video game sensibilities for certain stories, incorporating little interactions, animations, and atmospheric elements. I thought why settle for some wordpress list of blue links when I could put some more effort into it.
If anyone's curious about the interactive stories side of it, a couple of examples:
I'm still learning, fixing, and optimizing, so I'd really appreciate any observations.
1
u/hupcapstudios 7d ago
Purpose
A little browser-based swing trading game I built to help myself learn how to read charts, recognize setups, and practice bankroll management, position sizing, stop-losses, and exit strategies.
The game is pretty simple. You're shown a chart at a particular point in time and decide whether to Trade or No Trade. If you trade, you set your position and risk parameters, then see how things play out.
Technologies Used
Browser-based game built with JavaScript, hosted on Cloudflare Pages.
The original game was built around real historical stock prices, but I ran into data redistribution licensing issues. So I created a deterministic synthetic market with 180 fictional companies and 10 years of daily prices, including bull and bear markets, crashes, recoveries, overnight gaps, and earnings jumps.
Currently working on moving the market data and trade calculations to a Cloudflare backend rather than shipping the entire dataset to the browser.
Feedback Requested
Mostly interested in the UI/UX. Does the game make sense without much explanation? Is it obvious what you're supposed to do, and does the flow from reading a chart to making a decision feel intuitive?
Also curious whether the charts and trading controls feel approachable to someone who doesn't already know much about trading.
Would you change anything about the layout, information hierarchy, or how the results are presented?
Comments
I'm a developer and data nerd who's been trying to learn swing trading over the last few months. After exhausting pretty much every model and backtest I could think of, I realized I needed to actually learn what a good chart setup looks like. So I made this for myself.
The current version uses simulated market data while I work through licensing for the real historical data. It's useful for practicing the game mechanics, but I'm not pretending synthetic charts can teach real-world trading edges.
It's free, no signup required. Just something I've been having fun building and figured I'd share. Would love to hear what you guys think!
DISCLAIMER, THE SYNTHETIC DATA IS NOT LIKE REAL TRADING | I AM STILL AWAITING HISTORICAL LICENSING
1
u/Holiday_Reserve_7851 7d ago
URL: https://nicheoftheweek.ie/
Purpose: A house music discovery site with a weekly community chart, for listeners and DJs browsing tracks and producers submitting releases.
Technologies Used: Next.js, React and Supabase.
Feedback Requested: Visual hierarchy and playback affordance. On first visit, does the featured music look playable, or does it read as a static image? Is it clear what to press to hear a track? I’m also interested in whether the listening and submission actions compete too much on mobile.
Comments: I built and run the site. I’m looking for specific usability feedback; there’s no need to register or submit anything to review the homepage.
1
u/TopBackground9079 5d ago
**URL**: https://deslopmydesign.com
**Purpose**: A design roaster for AI-built websites. Paste your URL or upload a screenshot and you get a letter grade, a roast of what makes it look AI-generated (purple gradients, identical cards, emoji bullets) and a fix prompt you can paste straight back into your AI tool. There are also guides to styles, fonts, colours and the "no-nos" that give AI sites away. It's for non-designers who built a site with AI.
**Technologies Used**: React 19 and TanStack Start, Tailwind 4, Vite, running on Cloudflare Workers. Screenshots come from Cloudflare's Browser Rendering, with Firecrawl as the fallback. The roasts are written by Claude (Anthropic API, vision with structured output). Supabase handles accounts and saved roasts, Cloudflare KV caches each site's roast for 30 days, Turnstile handles bot checks and Kit runs the newsletter. Built with AI throughout, using Lovable and Claude Code.
**Feedback Requested**:
- Is the roast fair? Does it flag things that are actually fine, or miss obvious slop?
- Is the fix prompt something you'd actually use?
- Does the site practise what it preaches, or does it look AI-made itself?
- Anything confusing in the flow from roast to results to sign-up.
**Comments**: Free, and no sign-up needed for your first roasts (3 a day). Roast your own site and tell me where the critic got it wrong. That's the part I'm tuning right now.
1
u/HealthyPicture4905 3d ago
URL: https://sanoj.dev/
Purpose: My personal portfolio and blog. Every letter, picture and line on the home page is drawn from sine waves.
Technologies Used: Plain JavaScript and canvas, a Node build that measures an HTML page in headless Chrome, and Cloudflare Pages. Code: https://github.com/d-sanoj/sine-portfolio
Feedback Requested: Design and usability. Is the loading animation charming or too long? Is it clear the words are drawn and not real text? Are the yellow link underlines and the "click" hint easy to find?
Comments: There's a plain HTML version at /boring/, and phones are sent there automatically. Reduced-motion settings skip the animation. I'd especially like to hear from anyone who reads the site with a screen reader.
0
u/Own_Grand1767 6d ago
URL: https://srm-portfolio-eight.vercel.app/
Purpose: This is my personal developer portfolio, built to showcase my professional experience, technical skills, selected projects, and development journey. I'm currently looking for entry-level software engineering and full-stack developer opportunities, so I wanted to create a portfolio that reflects both my technical experience and approach to building production-ready applications.
Technologies Used: Next.js, TypeScript, Tailwind CSS.
Feedback Requested: General design feedback, UI/UX, visual hierarchy, typography, spacing, responsiveness and overall user experience.
Comments: This is my personal project and I'm continuously working to improve it. I'm open to honest criticism, so please don't hesitate to point out anything that feels unnecessary, confusing, or could be designed better. All suggestions are welcome!
1
8d ago
[removed] — view removed comment
1
u/Routine_Seesaw1095 8d ago
put a "view sample report" link beside the store url field. the hero asks for a store address, but the example is further into the journey; showing one sample finding up front would make what comes back from the free check more concrete.
1
u/ystudio3d 3d ago
That's a really sharp point—thank you. Asking for a store URL before someone has seen what the actual output looks like adds unnecessary friction right in the hero. Putting a "View sample report" link directly beside the URL input so visitors can inspect a real finding up front makes a lot of sense. Adding that to the top of the fix list!
1
u/canardu 8d ago
URL: https://www.atlastech.it
Purpose: Portfolio and services site for my one-person IT consultancy in Italy (Moodle e-learning, automation/AI, custom web apps). The site is in Italian. The whole thing is themed as a ship's bridge: each section has a hand-built nautical instrument — compass, telescope, magnifying glass over a chart, barometer, lighthouse and a lifebuoy.
Technologies Used: Plain HTML/CSS/JS, no framework or build step. three.js for the 3D instruments (custom geometry, canvas textures, a few small shaders: chromatic aberration in the magnifier, the lighthouse beam, rippling water). Each scene is lazy-loaded only when its section approaches and pauses when off-screen; static fallback images when WebGL isn't available. Self-hosted fonts, no third-party requests. Lighthouse 100 on all four categories.
Feedback Requested:
Does the nautical theme help or get in the way of understanding what I actually offer?
Mobile: do the 3D instruments feel smooth, and is anything distracting?
Is the page too long? Which sections would you cut or merge?
Comments: Happy to answer questions about how the 3D parts were built (e.g. the lighthouse beam or the telescope lens reflections).