Google Lighthouse Tips: Importance of web page speed

Google Lighthouse tips

Mobile Focus 

  1. 75% of global mobile users were on 2G and 3G as of 2016 (Source: GSMA Mobile) 
  2. 1MB takes minimum of 5 seconds to download on a typical 3G connection. (Source: WebPageTest & DevTools 3D definition) 
  3.  19 seconds is the average time a mobile web page takes to load on a 3G connection. (Source: Google DoubleClick blog) 
  4. 70% of mobile pages take nearly 7 seconds for visual content above the fold to display on the screen. (Source: Think with Google) 

UX & UI Performance 

  1. As the number of elements on a page increases from 400 to 6000 the probability of conversion drops 95%. (Source Think with Google) 
  2. Site takes >1 sec to become interactive, users lose attention, and their perception of completing the page task is broken. (Source: Google Developers Blog) 
  3. As page load time increases from 1 sec to 7 secs, the probably of mobile site visitor bouncing increased 113%. (Source: Think with Google) 
Proven Results 

  1. Walmart saw 1% increase in revenue for every 100ms improvement in page load. (Source: WPO Stats) 
  2. Rebuilding Pinterest pages for performance increased conversion rates by 15%. (Source: WPO Stats) 
  3. By reducing the response size of JSON needed for displaying comments, Instagram saw increased impressions (Source: WPO Stats)

Comments

Post a Comment

Popular posts from this blog

Decision tree for selecting the best cloud hosting option (App service, VM, Containers, Serverless)

Image
While working on a project last year, we were looking at various options for our Microservices hosting strategy. My colleague came across this decision workflow from Microsoft for their Azure hosting service options and I thought of sharing it here. This decision workflow can help in the following scenarios (and others): Hosting options for new build vs migration Overall cloud migration strategy Web & API hosting options IaaS vs PaaS vs serverless Microservices deployment and scaling strategy Feel free to comment on ways in which this may have helped you.
Read more

SOLVED: Sitecore Habitat Home Sync-Unicorn fails with the error: GetResponse" with "0" argument(s): "The remote server returned an error: (403) Forbidden.

Image
When executing  .\build.ps1 or .\build.ps1 -Target "Post-Deploy" commands to deploy Habitat Home build, the PS script fails with the error message; "GetResponse" with "0" argument(s): "The remote server returned an error: (403) Forbidden." ======================================== Sync-Unicorn ======================================== Sync Unicorn items from url: https://sitecore93sc.dev.local//unicorn.aspx Executing: &"C:/Code/HabitatHome/scripts/Unicorn/Sync.ps1" -secret 749CABBC85EAD20CE55E2C6066F1BE375D2115696C8A8B24DB6ED1FD60613086 -url https://sitecore93sc.dev.local//unicorn.aspx Sync-Unicorn: Executing Sync... An error occurred when executing task 'Sync-Unicorn'. Error: One or more errors occurred.         Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (403) Forbidden." The key to solving the issue lies in the following lines of code in Unicorn.p
Read more