Today I'd like to share with you oyato cloud (aka https://oya.to)
We use Google-recommended[1] dynamic rendering techniques and other best practices to automatically optimize your pages and images on a per-page and per-visitor basis. So you can e.g. have your home-page fully statically rendered and everything else as normal like Netflix does/did.
Your React apps and client-side rendered sites are automatically pre-rendered (like SSR) to guarantee search engine and social-network indexability.
Your images are automatically optimized and resized depending the browser window size and image formats it supports.
Even a static server-rendered site like HN can see Lighthouse score improvements[2] :)
[1]: https://developers.google.com/search/docs/guides/dynamic-ren...
[2]: https://perf.oya.to/?url=https%3A%2F%2Fnews.ycombinator.com
I'm actually running a service that does lighthouse checks (amongst other things) so nice to see more people focussing on making things faster. You can see the report for your site here, there are some minor issues it found: https://app.pagewatch.dev/b326ab115e9f00bac779d9851d4687a3fa...
Thanks! I'm especially impressed with the spelling check. It works even better than Sublime Text's builtin spell-checker :)
The layout issue seem to be not supporting 320w viewports: it's intentional (analytics, etc.). It would be nice, though, if the tool was able to show something like the amount of users who still use certain screen sizes.
The broken link issue looks like a 302 redirect which isn't a broken link.
> This looks quite impressive, how does it work with dynamic (per user) content?
It should work completely transparently. We only render text/html content and like everything else, its keys include cookies so if you send cookies with user-specific content everything should be just fine.
> If I have such a vue site for example, do I have to modify anything to get it to work?
You shouldn't need to do anything. We want the whole process to be:
* Sign up * Add your site * Point your DNS at our servers * Forget about it
Of-course you can add page-specific rules or use the (somewhat hidden) API, but everything apart from the the caching and image optimizations are turned off by default for normal users. Search engines and other bots like social networks get a static version of every page requested by default.
> The pricing mentions unlimited bandwidth, but limited requests. what counts as a request?
A request is any request that hits our servers (html, scripts, images, api requests). Of-course, we also do things like changing src urls where we can to include our own content-hash, so we can tell the browser to cache it for a long time which reduces the number of requests even if your caching headers are set up perfectly.
Oyato Optimized Results: 28 perf, 89 SEO
Original Site Results: 34 perf, 96 SEO
We'd love to know what URL it was. Over the last week we've fixed a number of failures as well as actually report more failures without you having to click the report.
Those scores seem to be one of said failures. Possibly the site redirects away from the original URL - an issue that should be fixed now.
