DEV Community

yassine
yassine

Posted on

Sharing something I’ve been building

#showdev #webdev #buildinpublic

Hi,

I’ve been working on a project called JaizTools, a collection of free browser-based tools for everyday digital tasks.

I’m planning to share some of what I’ve learned while building it, especially around creating useful web tools, SEO, and the challenges of building a small tool platform from scratch.

I thought DEV would be a good place to share the journey and hopefully learn from other developers here as well.

Would it be okay if I shared an article about the project and what I’ve learned from building it?

Thanks!
[Yassine]
Founder, JaizTools
https://jaiztools.com

Top comments (2)

Collapse
 
amitfeldman profile image
Amit Feldman •

115+ tools with no sign-up is a solid catalog play — congrats on the launch.

Quick public check of jaiztools.com (headers + public config only):

  1. All six standard security headers are unset: HSTS, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy. For a tools site that runs everything client-side, CSP + X-Frame-Options are the two I'd start with — they cost nothing in functionality and close the clickjacking/script-injection surface. If you're on a static host, it's usually one config block (Netlify _headers, Vercel vercel.json, or a Cloudflare Transform Rule).
  2. Two small on-page items: the homepage renders no

    (the "115+ Free Online Tools" title isn't an h1 in markup), and there's no canonical tag — both matter for a catalog site where every tool page competes in search.

TLS 1.3, meta description and response time (166ms TTFB) are all in good shape. Happy to re-run the scan free once the headers land. Good luck with the launch!

Collapse
 
yassine_channel_fb5f5bf40 profile image
yassine •

Thanks a lot for taking the time to check JaizTools and for such a detailed review.
The feedback is genuinely helpful, especially the points about the security headers, the homepage H1, and canonical tags. We’re going to review these carefully and make the improvements without affecting the browser-based tools or their functionality.
I also really appreciate you checking the performance side — good to know TLS 1.3, the meta description, and the 166ms TTFB are in good shape.
We’ll work through the recommendations and would definitely appreciate the free re-scan once the headers are in place.
Thanks again for the thoughtful feedback and for supporting the launch! 🙌