Absence of trailing slash causes 301 and suboptimal loading

[MartinMalinda]

The client side router create url like this: https://demo.wallacetheme.com/2016/11/23/engineering-informatics

While WordPress expects a URL with trailing slash like so:

https://demo.wallacetheme.com/2016/11/23/engineering-informatics/

Absence of trailing slash causes a 301 redirect and usually adds a few hundreds of milliseconds to the initial page load.

I had to deal with this in Scribe recently so I noticed it's an issue here as well.

[bradleykirby]

Interesting, thanks for the report.

I'll take a look at appending a trailing slash in the client router. I seem to remember there being some issue with trailing slashes in the angular router which is why they're not currently included. I'll see if that's been resolved.