SEO

[niteshkumar2000]

When people search for freakyos, we have to make sure our website comes on top :)

This is current status of the search results. Let's do something to increase our page rank!

[niteshkumar2000]

Yaay! Our web page passed mobile friendly test :0

[aakashhemadri]

Test on WebPageTest.org requires us to serve static content as cached.

[aakashhemadri]

Test on WebPageTest.org requires us to serve static content as cached.

In essence fetching github assets can give us lower load times.
https://webpagetest.org/performance_optimization.php?test=200813_9B_1128916857103363d8a1fe48fad920c0&run=3#cache_static_content

We can resolve this by caching all cross site request within the repositories assets everytime we make a commit and trigger a build.

This being a hack, and requiring human intervention when state changes, we can try using a webhook to trigger a travis build that will fetch all assets and publish to gh-pages branch.

As for use of images and assets from github like avatars that aren't added in a repository.
Using <link rel="preconnect" href="https://<subdomain>.github.com"> and <link rel="dns-prefetch" href="https://<subdomain>.github.com"> can increase first content paint.
@niteshkumar2000 @jeivardan

[aakashhemadri]

Test on WebPageTest.org requires us to serve static content as cached.

As for SEO we do conform to all basic SEO requirements. All we need to do is Increase content. Do test using Lighthouse

[niteshkumar2000]

But maintaining assets is an additional overhead and it breaks the dynamic nature also since ota mobile app and website all fetches same json, now if any fixes need to be done in future then we've to modify website assets too. But the existing page seems to be fast enough. Google test said no issues while loading 😅

So anything can be done regarding SEO?

[niteshkumar2000]

Probably let's move this caching part to another separate issue and we will see how can we improve the page rank of this react app in this issue :)

[aakashhemadri]

But maintaining assets is an additional overhead and it breaks the dynamic nature also since ota mobile app and website all fetches same json, now if any fixes need to be done in future then we've to modify website assets too. But the existing page seems to be fast enough. Google test said no issues while loading

So anything can be done regarding SEO?

About SEO, asfaik all we need to do is increase content, Otherwise for our simple webpage anything else will have no impact.
About the caching we can simply do client side caching with a service-worker if you do not want to increase complexity. Also adding a robots.txt file can be done

[niteshkumar2000]

But maintaining assets is an additional overhead and it breaks the dynamic nature also since ota mobile app and website all fetches same json, now if any fixes need to be done in future then we've to modify website assets too. But the existing page seems to be fast enough. Google test said no issues while loading

So anything can be done regarding SEO?

About SEO, asfaik all we need to do is increase content, Otherwise for our simple webpage anything else will have no impact.
About the caching we can simply do client side caching with a service-worker if you do not want to increase complexity. Also adding a robots.txt file can be done

Okay let me see how can I increase content for SEO.

For caching you can proceed let's try it out :D