OSF Performance Feedback

[martinjoconnor]

OSF feedback:

OSF is a platform for researchers to share their scholarship openly, and they expect when they do so, their scholarship is publicly discoverable using search indexes, such as Google. The team has been currently looking to optimize OSF page performance to be in good standing with Google to remain in the priority pages in search results.

For reference, here are some page speed reports: The current OSF page speed report is here, and there is current development underway to improve the speed. The CEE page speed report is here

We request that CEE page performance meet the Google standard for prioritized indexing.

[martinjoconnor]

Some work from Atti:

Regarding the OSF integration/requests/discussions, I made these changes to the CEDAR Embeddable Editor Demo app: Added meta description - suggested by the report

Added OpenGraph meta tags - not suggested by the report, but suggested by other SEO sources

Added basic robots.txt

Generated source maps for the demo app. The embeddable editor does not have a source map, because generating one for concatenated source files is not trivial. This does not affect the score

Added the used fonts directly into the project rather than loading it from CDN. This was not suggested by the report, but seems like a good practice, and I did this for other angular projects as well recently. The "ensure text remains visible during webfont load" is still there even given my efforts to make it disappear. Not sure how that affects our score.

As a result of these changes our overall score for desktop went up from 71 to 90, which is the green area:

https://pagespeed.web.dev/analysis/https-cedar-cee-demo-egyedia-com/9p6rdwctkd?form_factor=desktop

For reference, these are the links for their website:

https://pagespeed.web.dev/analysis/https-osf-io/7isi8er4g1?form_factor=desktop

And their installation of our demo without my changes (this is what we wanted to improve):

https://pagespeed.web.dev/analysis/https-cedar-lycuesiqpq-ue-a-run-app/0top37w6id?form_factor=desktop

The Mobile versions of all three of these are producing numbers which would need serious thinking, but our new score is still the best among those scores.

At the moment I am trying to replace moment with dayjs in the embeddable editor to decrease the footprint of the app, since that is another warning that is showing up.

[egyedia]

The latest performance test results can be seen here:

https://pagespeed.web.dev/analysis/https-cedar-cee-demo-egyedia-com/j9pd1q33dt?form_factor=desktop