Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-128385

As a site admin, I want to configure PageSpeed from Site Settings

    Details

      Description

      Motivation

      With this story, we want to build PageSpeed API configuration at site level. 

      Design

      https://www.figma.com/file/I0BImwTEY740kKEseduLU5/LPS-111803-Page-audit-check-one-page-issues?node-id=413%3A92984

      Technical Requirements

      1. Configuration panel will be in: Site settings > Content and Data > Pages > New section "Google PageSpeed Insights"

       

      2. There will be a check: Enable Google Page Speed Insights. It will be checked by default.

      2.1. There will be help text: Google PageSpeed Insights can find accessibility and SEO issues in your pages, and provide suggestions to fix them.

      2.2. When the check is disabled, the Page Audit icon won't be visible from the view mode of the pages in the site.

      3. There will be a Field to enter the API Key (format: AIzaSyAq-oKsvIhlYHdk1UXCFy63h74ECIgbgbE) 

      There will be a check for setting specific timeout:

      Label: Set Specific Timeout Time. Not checked by default.

      Help text 1 (under the check, above the field): If not checked, system default values for timeout will be applied.

      Help text 2 (under the field): Define the time (in milliseconds) before a PageSpeed Insights request times out.

      Default value: 30000 millisecs

      4. There will be a field for specifying the "strategy" parameter for the API:

      • Label: Preferred Strategy
      • Help text: Select what kind of device you want to audit for. Mobile strategy includes additional checks. Selected strategy will be applied to all page audits.
      • Dropdown to select Mobile or Desktop. Default value: Mobile.

      NOTE.- If the field is kept void, then the default value (desktop) will apply. Additional checks for mobile are: Small Tap Targets, Incorrect Aspect

      • Site settings values overwrite Instance and System values for that particular site, but the feature has to be enabled in both of them for the site settings to show it.

      Acceptance Criteria

       

      Requirements
       
      Acceptance Criteria
       
      Test Strategy
       
      Covered by frontend / backend test? (Yes/No)
       
      Configuration panel will be in: Site settings > Content and Data > Pages > New section "Google PageSpeed Insights"
      • Given the Instance settings page
      • When the users click on Content > Pages
      • Then they can see the tab Google PageSpeed Insights 
      Low  NO 
      2. There will be a check: Enable Google Page Speed Insights. It will be checked by default.
      2.1. There will be a subtitle / help text: Google PageSpeed Insights can find accessibility and SEO issues in your pages, and provide suggestions to fix them.
      • Given the Google PageSpeed Insights settings tab
      • Then there's a check: Enable Google PageSpeed Insights, it is checked by default
      Low  YES
       
      • Given the Google PageSpeed Insights settings tab
      • Then there is a help text: Google PageSpeed Insights can find accessibility and SEO issues in your pages, and provide suggestions to fix them.
      Low  YES
      2.2. When the check is disabled, the Page Audit icon won't be visible from the view mode of the pages in the site.
      • Given the Google PageSpeed settings tab in the Virtual Instance Scope section
      • When the Enable Google PageSpeed Insights check is unchecked
      • Then the Page Audit icon won't be visible from the view mode of the pages in the site.
      Medium   NO
      3. There will be a field to enter the API Key in the Site Scope section: Low  NO 
      4. There will be a check for setting specific timeout: * Label: Timeout Interval.  * Help text (under the field): Define the time (in milliseconds) before a PageSpeed Insights request times out. 
      • Default value: 30000 millisecs
       
      • Given the Google PageSpeed Insights settings tab in the Virtual Instance Scope section
      • Then there's a field "Timeout Interval" to enter a specific value for timeout, it shows 30000 millisecs as default value and the help text says Define the time (in milliseconds) before a PageSpeed Insights request times out. 
         NO 
       4. There will be a field for specifying the "strategy" parameter for the API:
      • Label: Preferred Strategy 
      • Help text: Select what kind of device you want to audit for. Mobile strategy includes additional checks. Selected strategy will be applied to all page audits. 
      • Dropdown to select Mobile or Desktop. It will be set as Mobile
      • Given the Google PageSpeed Insights settings tab in the Site Scope section
      • Then there's a field for specifying the Preferred Strategy, the dropdown shows Mobile and the Desktop value and both can be selected, but it is set as Mobile 
      Low  NO 
       
      • Given the Google PageSpeed Insights settings tab in the Site Scope section
      • Then there's a field for specifying the Preferred Strategy, there's a help text: Select what kind of device you want to audit for. Mobile strategy includes additional checks. Selected strategy will be applied to all page audits.
      Low   NO
      NOTE.- If the field is kept void, then the default value (desktop) will apply. 
      • Given the preferred strategy dropdown in the Site Scope section
      • When the value is void ("Choose an option")
      • Then the call is made for Google Page Speed default value - desktop
      Medium   NO
      NOTE.- Additional checks for mobile are: Small Tap Targets, Incorrect Aspect Ratios and Illegible font sizes.
      • Given the preferred strategy dropdown in the Site Scope section
      • When the value is Mobile
      • Then additional checks: Small Tap Targets, Incorrect Aspect Ratios and Illegible font sizes are retrieved
      High  NO 
       
      • Given the preferred strategy dropdown in the Site Scope section
      • When the value is Desktop
      • Then additional checks: Small Tap Targets, Incorrect Aspect Ratios and Illegible font sizes are NOT retrieved
      High  NO 

       

       

        Attachments

          Issue Links

          There are no Sub-Tasks for this issue.

            Activity

              People

              Assignee:
              support-qa Support QA
              Reporter:
              julia.molano Julia Molano
              Engineering Assignee:
              Alejandro Tardín
              Recent user:
              Luiz Queiroz
              Participants of an Issue:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Packages

                  Version Package
                  7.4.2 CE GA3 DXP 7,4
                  Master