1
0
-1

Hi,

My local Joget install is up to test PWA apps but performance is not the same as in your blog post from November.

I double checked the CRUD last (8th) setting page for cache. All are set on to be able to CRUD while offline,  but the published+launched version fails at PWA section:

```

Current page does not respond with a 200 when offline

If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.

start_url does not respond with a 200 when offline

Timed out waiting for start_url to respond.

A service worker enables your web app to be reliable in unpredictable network conditions. Learn more.

Installable

Does not use HTTPS 22 insecure requests foundDoes not register a service worker that controls page and start_urlWeb app manifest meets the installability requirements

PWA Optimized

Does not redirect HTTP traffic to HTTPSConfigured for a custom splash screenSets a theme color for the address bar.Content is sized correctly for the viewportHas a <meta name="viewport"> tag with width or initial-scaleContains some content when JavaScript is not availableProvides a valid apple-touch-icon

Additional items to manually check (3) These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.

Runtime Settings

  • URLhttp://0.0.0.0:8080/jw/web/embed/userview/todo/v/_/todoform_crud
  • Fetch timeJul 21, 2020, 3:26 PM GMT+2
  • DeviceEmulated Nexus 5X
  • Network throttling150 ms TCP RTT, 1,638.4 Kbps throughput (Simulated)
  • CPU throttling4x slowdown (Simulated)
  • User agent (host)Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.116 Safari/537.36
  • User agent (network)Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3694.0 Mobile Safari/537.36 Chrome-Lighthouse
  • CPU/Memory Power1108


Generated by Lighthouse 5.7.1

```

Indeed, there's no service worker at all  (Dev tools > Application > Service Workers).

The PWA page Progressive Web Application - PWA doesn't speak about service workers.

Did I miss something?

Thanks

    CommentAdd your comment...

    1 answer

    1.  
      1
      0
      -1

      My bad, Joget passes PWA test.

      It works when you have custom domain and SSL activated.

      PWA checks are all green.

      Just a few details needs to be fixed though:

      • AFAIK, you can't point to your launched app directly by using redirections (removing /jw/web/userview/crm/crm_userview_sales/_/w in the url) because login and other links are hard coded. If there's a way please let me know.
      • Does not use passive listeners to improve scrolling performance
        • …wro/common.preload.js?build=cd62bb4 (line 0)
        • …wro/progressive.min.js (line 5)
      • Links to cross-origin destinations are unsafe
        • http://joget.org/
      • Browser errors were logged to the console
        • Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more

          URL

          Description

          /jw/csrf
          Failed to load resource: the server responded with a status of 404 ()
          /jw/csrf
          Failed to load resource: the server responded with a status of 404 ()




        CommentAdd your comment...