Free tool
Site Check*
Paste in a web address and get a plain answer on what is holding the page back. Search visibility, technical setup, content and speed, checked in about ten seconds. Nothing to install, nothing to sign up for.
Takes about ten seconds. This reads the page you give us the same way a browser would. Nothing behind a login gets touched, and nothing about the scan is saved.
This reads the one page you give it, the same way a visitor's browser would. It does not crawl your whole site and it does not need a login. Eighteen checks run across four groups, and every one of them is read straight from the page itself, not guessed.
01
Search visibility
The title, the description, the main heading, and the tags that decide how a link looks when it is shared. This is what search engines and social platforms actually read.
02
Technical setup
HTTPS, robots.txt, a sitemap, a favicon, and the tag that lets a page adapt to a phone screen. Small things, and each one is either there or it is not.
03
Content quality
Alt text on images, a declared page language, and resources that quietly break because they load over plain HTTP on a secure page.
04
Speed signals
How fast the server answers, how heavy the raw page is, and whether scripts in the head are holding up the first paint.
Is this actually free?
Yes. Type an address, get the report, download it if you want it. No account and no email required.
Does it check my whole website?
It checks the one page you give it, the same way a browser would load it. It does not crawl every page on your domain. If you want every page looked at, that is a job for a person, not a ten second scan, and it is exactly the kind of work I do.
Where does the score come from?
Every check either passes, needs a look, or needs fixing. The score is just those three counts turned into a number out of a hundred, so you can compare two scans at a glance.
Do you store the sites people check?
No. The page is fetched, read, and the result is sent back to your browser. Nothing about the scan is written to a database.
What if a check comes back wrong?
Every result here is read straight from the page itself: the actual HTML, actual response time, actual file size. Nothing is guessed or simulated, so if a check looks wrong, the fastest way to be sure is to view the page source yourself and compare.
Can you fix what it finds?
That is the point of the tool. I am a full stack engineer, and most of what shows up here, a missing tag, a slow response, a page that is not secure, is a normal week of work for me. Send me the report and tell me what you want fixed.
Open to new work
Tell me what you are trying to build.
If I am the right person you will get a scope and a number in writing. If I am not, I will say so and point you somewhere better.