Piperic
similar sites
‹ ProfileAI ReportTools

Sites similar to jamesabe.com

James Abe - Web3 Frontend Developer · ranked by shared content topics & relevance
80match
ethansnj.com
Ethan - Frontend developer
1 shared topicsweb-development
80match
kogucki.com
Wojciech Kogucki | Frontend Developer
1 shared topicsweb-development
78match
ivanpardo.com
Ivan Pardo — Frontend Developer
1 shared topicsweb-development
77match
mohitthakur.com
Mohit Thakur | Frontend Developer
1 shared topicsweb-development
77match
issydennis.com
Issy Dennis - Frontend Developer
1 shared topicsweb-development
77match
nurdanvayni.com
Nurdan — Frontend Developer
1 shared topicsweb-development
77match
swenyein.dev
Swe Nyein | Frontend Developer
1 shared topicsweb-development
77match
animan.io
Animan Amit - Frontend Developer
1 shared topicsweb-development
77match
nxndi.com
Nxndi - Frontend Developer
1 shared topicsweb-development
77match
anupminj.com
Anup Minj - Frontend Developer
1 shared topicsweb-development
76match
eugevin.dev
Eugene Vinokurov | Frontend Developer
1 shared topicsweb-development
76match
evanjenkinsdev.com
Evan Jenkins | Frontend Developer
1 shared topicsweb-development
76match
mafuzur.com
Mafuzur Rahman - Frontend Developer
1 shared topicsweb-development
76match
angellgonzalez.com
Angel Luis Gonzalez - Sr Frontend Developer
1 shared topicsweb-development
76match
ivanzayko.dev
Ivan Zayko | Frontend Developer
1 shared topicsweb-development
76match
andersonmalheiro.com
Anderson - Frontend Developer
1 shared topicsweb-development
76match
israeliyanda.com
Israel Iyanda | Frontend Developer
1 shared topicsweb-development
76match
herecomesthecode.com
Daniel Polak — Frontend Developer
1 shared topicsweb-development

How the match score works

Each match is a 0–100 similarity score — the higher it is, the more two sites resemble one another. It’s computed automatically from our own crawl data (never from what a site says about itself) by combining several independent signals, so a high score means several of them point the same way:

No single signal decides the result — they’re blended together. Treat the score as a way to rank candidates rather than an absolute percentage; the chips on each result show which signals contributed.