PageWatch is a service I built over the last year to help find some recurring issues in websites. It can detect CSS issues such as container overflows, overlapping text or bad wrapping, spelling mistakes, slow pages and a few more.
Built using Hasura (realtime GraphQL), Django for the backend, scrapy (crawling) and spaCy (language model).
I'm injecting https://markjs.io/ into the page and then highlight all the misspelled words, then I crop it out of the screenshot. (it does mean I have to take basically two screenshots, one with the spelling mistakes highlighted, and one for the normal preview)
I actually only added lighthouse recently, it is a very minor part of the tests.
Everything besides the 'performance' and 'vulnerabilities' tab are custom built 100%. These are:
* The layout tests and fullscreen rendering engine
* Spelling tests and highlighting
* Broken links check
* Structure visualization
* Error/console logs
* Broke resources / images
Lighthouse does have some nice SEO related information that I'm planning to expose in an easier way.
Great idea, but I'm not creating an account just to see if it works. I don't want "hey, it's Josh from PageWatch" emails every few days during the trial period.
Yeah I get that, I need some way to though to limit usage to an account, running these tests takes a decent amount of processing time / storage (cheap, but not free).
I do hope to have just a URL box available sometime, when I have some better runway.
7 comments
[ 4.4 ms ] story [ 16.9 ms ] threadTo see what it looks like, here is a report on the SpaceX site: https://app.pagewatch.dev/bc10b8fdefd9cfbaca5626f6483515fb5c...
* The layout tests and fullscreen rendering engine
* Spelling tests and highlighting
* Broken links check
* Structure visualization
* Error/console logs
* Broke resources / images
Lighthouse does have some nice SEO related information that I'm planning to expose in an easier way.