Hi guys,
Further to this – assets that no longer exist on my site are being “cached” in the ServiceWorker, it doesn’t seem to be checking for updated assets? 🙁
Hi Will,
Happy to see you again here.
When I run a Lighthouse test using “Applied 3G”, I get the following response:
Page load is not fast enough on 3G
Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the “Performance” section to learn how to improve.
Interactive at 23s
Any ideas why this is/what I can do about it?
The reason why you are noticing this suggestion is because the website takes more time to load over 3G connection. As you know 3G is slower for users who interact with the PWA need a better experience, and the website should load within 10sec to pass this criteria.
As mentioned within the error you shared, you can notice that more details on how to improve the performance to load the more faster within the Performance section. Optimize and Improve the performance using the suggestions under the Performance over lighthouse report to pass this.
Further to this – assets that no longer exist on my site are being “cached” in the ServiceWorker, it doesn’t seem to be checking for updated assets? 🙁
Over to this, our plugin uses Network First Caching strategy. That means if any changes where made to page/post, those will get reflected/uodated at the user end if they visit the page again after the change over an Internet connection.
Hey again @josevarghese!
RE: 3G performance – I’ve revisited overnight and noticed that the “main” bottleneck is JS performance. I don’t know what I can do to improve this, so I’ll just have to leave it as is for now! 🙂
RE: Cached assets – I cleared my page cache for my site, updated CSS and re-minified via Autoptimize, however when I then jumped into my site (Incognito) and Hard Refreshed the page, I was still seeing the same (old Autoptimize) CSS file being served “From ServiceWorker” – it didn’t go to my site to check whether there was a new one (which there was) until I cleared the ServiceWorker’s storage/unregistered the SW and then it pulled it in. Any ideas?
Regarding the performance, you can easily improve it either manually or using some plugins. A lot of awesome articles are available over the internet, please do refer those.
RE Cached assets – I think it’s because of the cache created either by a plugin or server. Can you please uninstall our plugin and try it again? If the version is changed over the file then the Service worker will fetch the latest file and will be get uodated over next reload.
