CertificationAnswers

 

Which is true about calls-to-action usage on mobile homepages?

 

Calls-to-action should be prominent on the visible area of the mobile homepage

 

Use only menus

 

Keep call to action on the second page

 

Same calls-to-action should be used both on mobile and desktop sites

 

Explanation:

 

It can be easy for mobile users to miss menu items, so your clients should always put their key calls-to-action where users will see them. Study participants had an easier time completing tasks on sites that clearly displayed primary calls-to-action in the main body of the site, with secondary tasks available through menus or below the fold.

Read more here: https://support.google.com/partners/answer/7336289

 

 

 

True or false: Images should never change when rotating a device screen or between different device sizes

 

True

 

False

 

Explanation:

 

Design your mobile site so that users won’t ever need to change the size. Some mobile sites even disable pinch-to-zoom on their screens; if your site is designed correctly, users will never notice it’s gone.

Read more here: https://support.google.com/partners/answer/7336290

 

 

 

Why do CSS @imports harm performance?

 

They create a less efficient CSSOM

 

They require additional CPU time to parse

 

They can introduce unwanted dependences

 

@import loads files less efficiently than <link>

 

 

 

The first step to optimize the critical rendering path is to:

 

minimize number of critical resources: eliminate them, defer their download, mark them as async, and so on

 

analyze and characterize your critical path: number of resources, bytes, length

 

optimize the order in which the remaining critical resources are loaded: download all critical assets as early as possible to shorten the critical path length

 

optimize the number of critical bytes to reduce the download time (number of roundtrips)

 

Explanation:

 

The general sequence of steps to optimize the critical rendering path is:

• Analyze and characterize your critical path: number of resources, bytes, length.
• Minimize number of critical resources: eliminate them, defer their download, mark them as async, and so on.
• Optimize the number of critical bytes to reduce the download time (number of roundtrips).
• Optimize the order in which the remaining critical resources are loaded: download all critical assets as early as possible to shorten the critical path length.

Read more here: https://support.google.com/partners/answer/7336280