MWPW-157573 Optimize EdgeWorker for Mobile Widget

[TsayAdobe]

• Enable different caches for desktop, tablet, and mobile devices.
• If the metadata mobile-widget is true and the client device type is mobile, the DC converter widget is not required. Eliminate unnecessary preloads and embedded scripts.
• The change has been deployed to the stage environment.

Resolve: MWPW-157573

Test URLs:
https://www.stage.adobe.com/acrobat/online/sign-pdf.html
https://www.stage.adobe.com/acrobat/online/pdf-editor.html

[aem-code-sync]

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.

• Re-run PSI checks
• Re-sync branch

Commits

• c502e91 ✅ (latest)
• 33cc867 ✅
• f899819 ✅
• 69fc267 ✅
• 51bc0ed ✅
• e4a65d2 ✅
• 199657d ✅

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.18%. Comparing base (59f7ed8) to head (c502e91).
Report is 10 commits behind head on stage.

Additional details and impacted files

@@            Coverage Diff             @@
##            stage     #785      +/-   ##
==========================================
+ Coverage   90.15%   90.18%   +0.03%     
==========================================
  Files          43       43              
  Lines        5494     5512      +18     
==========================================
+ Hits         4953     4971      +18     
  Misses        541      541              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[peller]

looks like this will hurt our performance. There are fetches in there that would otherwise be done in parallel with the first request

[TsayAdobe]

We need to know if mobile-widget is true or false to decide what scripts to be inline and preloads. Therefore, they have to be separated.

[peller]

scripts.js is loaded regardless.

loading dc-conversion-widget.js conditionally, blocked by the first Promise, will hurt Frictionless performance on production where it is used. It might be better to load it, in parallel, and not use it where you don't need it.

[peller]

perhaps we could break fetchAndInlineScripts into two separate methods - fetchScript and inlineScripts. Then we could still fetch the frictionlesspage and fetchscripts in parallel, and then call inlineScripts(mobileWidget)

[peller]

need to make fetch requests in parallel where possible

[peller]

Also, if we add a conditional to generate a different result for the same url, we can no longer cache it. That would be a huge performance loss.

[TsayAdobe]

Also, if we add a conditional to generate a different result for the same url, we can no longer cache it. That would be a huge performance loss.

onClientRequest adds device type to the cache key. Mobile, tablet, and desktop have different caches.