Not Planned Use client side router instead of server side.

[v1rtl]

It is better to use client side router so browsing in Webwide will be smooth and comfortable. Now we have to wait until each page to load which is not very awesome because it is a bit annoying.

The solution to this problem is using JavaScript-based client side routing. There are some framework-agnostic libraries here:

router.js
navigo

and even an article on how to build your own router:

Router with vanilla JavaScript

There is also InstantClick that doesn't require any bundling

<script src="instantclick.min.js" data-no-instant></script>
<script data-no-instant>InstantClick.init()</script>

 

[AndrewDavidJ]

It is better to use client side router so browsing in Webwide will be smooth and comfortable. Now we have to wait until each page to load which is not very awesome because it is a bit annoying.

The solution to this problem is using JavaScript-based client side routing. There are some framework-agnostic libraries here:

router.js
navigo

and even an article on how to build your own router:

Router with vanilla JavaScript

If you check the footer, you'll notice that this forum is just a server running an instance of a pre-built forum solution (XenForo). So implementing their own systems like client-side routing would defeat the purpose of using an existing solution.

 

[Gummibeer]

It doesn't have to defeat but it's harder to do. And I would say that there are bigger problems.

 

[adam]

Thanks for the suggestion @v1rtl! As @AndrewDavidJ kindly mentioned yes we’re running on an existing solution solidified heavily in server side routing. I believe there’s some things that can be done to help make things feel a little smoother so I’ll add looking in to that on the list.

I have to say I’ve not experienced much load time waiting, pages seem to load fairly instantly for me though perhaps I am spoiled being physically close to the server (UK) and with fairly fast internet.

Would love to hear other people’s experiences of current speed. UK servers have good connections to both US and Europe and I am using Cloudflare to help deliver static assets more efficiently.

 

[Gummibeer]

Hamburg, Germany
The page loading time is okay. But adding a reaction (like) takes "endless". It's around 1-2 seconds until the reaction shows up. For a simple Ajax post it's super slow. 🤔

 

[adam]

Hamburg, Germany
The page loading time is okay. But adding a reaction (like) takes "endless". It's around 1-2 seconds until the reaction shows up. For a simple Ajax post it's super slow. 🤔

Interesting! It's instantaneous for me. I will do some testing on a VPN. Could you also let me know browser & OS version?

 

[v1rtl]

If you check the footer, you'll notice that this forum is just a server running an instance of a pre-built forum solution (XenForo). So implementing their own systems like client-side routing would defeat the purpose of using an existing solution.

There are other options for not implementing client side routing but speeding up browsing pages - InstantClick.

This portion of this code will add SPA routing to non-SPA app:

<script src="instantclick.min.js" data-no-instant></script>
<script data-no-instant>InstantClick.init()</script>

 

[Gummibeer]

This script is great. But only works as long as the scripts don't rely on window.onload and so on and you use the same scripts/styles (in head) on every page.

Events and script re-evaluation in InstantClick

I have no idea how the JS in this forum is structured - but it could get a mess to make them compatible. But thanks for sharing it, could be an idea for my own page! :)

 

[adam]

Hamburg, Germany
The page loading time is okay. But adding a reaction (like) takes "endless". It's around 1-2 seconds until the reaction shows up. For a simple Ajax post it's super slow. 🤔

@Gummibeer please can you let me know if reactions are sped up for you now?

 

[Gummibeer]

@Gummibeer please can you let me know if reactions are sped up for you now?

Are faster. 😊