I get this comment from my client last night…
“… couldn’t use it on an ongoing basis because of the speed. As you know I mentioned speed a couple of days ago. Attached [video] is my iPad 2, which is pretty fast, and very fast on the normal website and every other website. PCs are slightly faster, but [this new system is] still unusable.”
What are your thoughts on this video? I have have my ideas.
WhatsApp Video 2021-07-15 at 22.32.57
So the problem on this page is that the bacskpace is having a delay in a textarea?
Wait … is that an ipad2? The one released exactly 10 years ago? What iOS version does it run? What Safari version?
Yes, iPad 2 !
It has the most up-to-date IOS that is allowed to be loaded, so that is probably 5 years old.
This issue is surely not down to the website or textarea, is it?
Is there an Action occurring on every key release/key down? What does the Developer Console display?
No actions on any key.
Try adding spellcheck="false" to the text area see if that helps Riggers?
Or try with the full shebang:
<textarea autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false">Does the site have a lot of App Connect components? Form elements (input/textarea) also count as components. When the value of an input changes it checks with each component if it requires an update, normally this goes fast enough when there is nothing to update, but older cpu and having a lot of components on the page can slow down it a bit.
On complex sites, you should use conditional areas (dmx:if) to hide inactive content that doesn’t need to be rendered. This will speed up the whole site because then this content parts will be just ignored.
If you hide them with simple css styles - they will still participate in the whole render flow and slow down you site.
So in general try to make only the currently view components visible - and hide inactive ones behind a conditional regions.
Also separating in content views in NodeJS might help as well.
@Dave unfortunately that made no difference but interesting all the same.
@UKRiggers that’s unfortunate, sometimes it helps. Sorry it didn’t help mate.
@patrick yes it has components but I guess you would say it doesn’t have too many. This page has a large multi page form and the user needs to flirt from one section to another and back again when completing it.
From what you are saying, I think it is too complex (clever) for slower machines.
I have been battling with him for years to try and get him to buy new(er) devices but he won’t. He then spends thousands on them when they fail and or become problematic. He still uses Windows 7 with 2Gb of RAM and 120Gb Hard Drives on alot of his machines because they are not powerful enough to upgrade.
I will send you a PM
@George I am using PHP, MySQL so no NodeJS.
I have been using some conditional regions but I suspect on his devices things will be slow irrespective of whatever I do. I appreciate your comments and will make an effort to refine things.
I will send you a PM
Keeping aside the fact that the machine being used to run the app is not suitable for 2021… Here’s how I try to fix slowness issues:
Remove big repeats or components from the page.
Re-add them one by one.
Move things into CR (conditional region)
Move client side formatters to server side.
Deploy and test between each step to identify what works and what doesnt.
There’s such a thing as bad customers. They’re bad for business