Siteimp is coming soon

As I wrote a few weeks ago, Siteimp is coming back , but in a very different form than before.

The old version taught me a lot. Some of those lessons were technical. Some were architectural. Some were the sort of lesson that arrives by kicking your shins for two years and then asking whether you are ready to learn anything yet.

The new Siteimp is being built as a desktop-first application. It runs locally, stores its own evidence, and is designed to help people answer a much more useful question than “how do I get one more dashboard?”

The question is this: is my website structurally healthy, available, and behaving the way I think it is?

What the new Siteimp actually does

Siteimp is not trying to become an all-purpose SEO suite. It is not trying to do keyword research, backlink analysis, trend prediction, or any of the other things that turn good software into a storage locker full of side quests.

Instead, it focuses on website integrity.

That means the application is being built around a few core ideas:

  • crawl the site politely and store real evidence
  • run Lighthouse and extract useful contract-level metrics
  • show pages, links, images, and issues in table-first interfaces
  • surface important problems as clear signals
  • monitor websites over time to catch outages and failures
  • keep everything local and understandable

Two sides of the same coin

One of the things I like most about the new version is that it treats website integrity as two related problems.

The first is structural analysis. Can the site be crawled? Are the pages healthy? Are there broken links, broken images, sitemap mismatches, accessibility problems, or pages that are technically present but practically buried?

The second is monitoring. Is the site actually up? Are important URLs returning successful responses? Has a target started failing quietly while everybody is busy doing something more glamorous?

Those are different questions, but they belong together. A website that is perfectly optimized and unavailable is still broken. A website that is available but structurally chaotic is wasting part of its own uptime.

Why I am building it this way

I no longer have much interest in building tools that require a cloud control tower, a pricing spreadsheet, and the emotional resilience of a medieval tax collector.

The new Siteimp is local-first on purpose. That means:

  • you keep your data
  • you can inspect what the tool is doing
  • you are not uploading your site intelligence into somebody else’s SaaS
  • the architecture can stay focused on useful work instead of platform theatrics

I also wanted a tool that feels calmer. The web has enough noisy software. Siteimp is being built around facts, tables, signals, and evidence. It is meant to help you understand what happened, not dazzle you with a fake galaxy graph and a wellness quote.

What you will be able to inspect

The application already has a strong internal model for the sorts of things I care about when I am trying to understand a website properly.

That includes:

  • website-level dashboards
  • scan history
  • page-level drilldowns
  • inbound and outbound link evidence
  • image inventories and usage data
  • Lighthouse performance, accessibility, best practices, and SEO summaries
  • derived issue views
  • monitoring targets and recent monitoring results

In other words, this is not being built as a toy report generator. It is being built as a practical workbench for people who need to understand their own sites.

Who it is for

Siteimp is for people who build or maintain websites and want truth more than theater.

That includes:

  • indie developers
  • consultants
  • small agencies
  • technical site owners
  • people who have been burned by “all-in-one” tools before

It is especially for the sort of person who has a sinking feeling that something is wrong on a site, but does not want to spend half a day proving it to themselves.

What happens next

The application is now far enough along that it feels real. The core scan flows are in place. Monitoring is being built out. The interface has moved well beyond “developer staring at raw JSON and nodding grimly.”

There is still work left to do, of course. There always is. But Siteimp is no longer a vague someday project drifting through the fog in a bathrobe. It is becoming software.

I will be sharing more about the architecture, the monitoring side, and the philosophy behind the tool as release gets closer.

Coming soon

Siteimp is coming soon as a desktop application built around website integrity, local ownership, and practical evidence.

No fluff. No rented cloud throne. Just a serious tool for understanding what your website is actually doing.

About the Author

Greg Hluska is a performance-obsessed developer focused on improving Core Web Vitals and real-world speed. He built Siteimp to make optimization faster, easier, and more reliable. Learn more about performance on the Performance Optimization blog. Currently working primarily on the Fitness Tracker application and 78solutions, Greg is busy. But not too busy to spend his free time with his child.