Hi everybody, although I believe there is another thread regarding website performance, I am throwing my 2 cents as someone who has been into website development for many years.

Option to disable SPA mode:

It becomes a pain with some types of internet.

For example with mine, it is slow and slow connection means it will take forever to navigate to a different page. In regular pages even if it fails, it will show the reason for why it has failed but it is not the case with SPA (especially on mobile)

Use server side program to merge layers of wolves before displaying:

Admittedly I am not pushy on this one, it definitely will take server power to render the images before displaying so it is for when the population grows and there becomes a need for server upgrade (Why Azure? There are cheaper and better VPS providers which provide Windows IIS as operating system)

But this is really needed for multiple reasons:

1. Less bandwidth consumption (both client and server side)
2. No need to download and save the wolf image every time (easier to directly link the wolf image)

A work around to the issue with server power is "caching" the wolf image, which means merging the layers and saving it in server hence there will be no need to merge the layers every time (unless there is a new modification in apparel or patterns)

Allow viewing website images in website:

I am not sure if this is a "my issue" but if you right click on a website image and select "Open image in new tab" you will notice that the image gets downloaded into the user's device, which is a pain if you want to link the image somewhere.

The images such as vouchers don't need to be this big:

It is displayed as small right (15x15)? Let's see the actual image (400x400)

This is ~711x bigger! It really does not need to be.

Is there concern regarding resizing such assets? Use SVG file format, especially the voucher images are very simple which can be easily converted.

Keep assets in one domain:

I monitored the loaded assets and these are the external websites which lorwolf fetches assets from:

• lorwolf.azureedge.com
• code.jquery.com
• 64.media.tumblr.com

Although considerably non-issue, there is a problem. Different load time and risk of website being broken because the client's internet provider has blocked one of these domains.

My suggestion is to host those content in one place, at most in a subdomain of same site (e.g cdn.lorwolf.com or static.lorwolf.com)

Conclusion: Lorwolf has become my favorite web game to play during free time, but I found the need to address some of the performance problems.

There is an option to disable the SPA canvas! It’s under account settings.

@Synesthesia I meant to disable it for loading pages, not just the canvas rendering part.

Support for SURE on the wolf image point especially. I use firefox and the copy to clipboard button does not work on firefox and ngl im sick of screenshotting my wolves cause the feature seems to only be available on chrome and idk man i want a slightly more secure web browsing experience.

Idk why or how the devs managed to turn off copying and pasting the images normally but they did and it drives me crazy

Just a quick note in terms of the assets:

The azureedge domain is likely the domain that lorwolf uses to serve static assets such as images.
I'm not sure where the tumblr domain is from exactly, but if users have images in their signatures it may be that someone has an image from tumblr there.
The jquery domain is an external javascript framework that is commonly used by various sites. Although it is recommended, best practice, that jquery is self hosted instead in case the jquery domain goes down.

@crotanite tumblr one comes from the home page, the images linked in dev updates are from Tumblr.

I should have been specific.