Mobile devices account for 53.3% of global website traffic, and 53% of mobile visits are abandoned when a page takes more than 3 seconds to load. This article brings together the key benchmarks behind traffic, speed, security, and operating costs. It covers Core Web Vitals, Lighthouse guidance, OWASP and GDPR requirements, and the infrastructure pricing that shapes site performance at scale.
Key Takeaways
- 53.3% of all website traffic worldwide comes from mobile devices
- 36.0% of global web traffic originated from North America in 2023
- 44.4% of web users are more likely to abandon sites that take longer than 3 seconds to load
- Google’s Lighthouse recommends image optimization as a best practice to reduce load time
- Google reports that 53% of mobile site visits are abandoned if pages take longer than 3 seconds to load
- Web Vitals guidance defines three core metrics for performance: LCP, CLS, INP
- The HTTP Archive report “State of the Web” is updated regularly and provides annual medians and distributions for web features
- Google Lighthouse defines 6 performance categories including Accessibility, Best Practices, SEO, PWA, and so on
- TLS 1.3 is defined in RFC 8446 and supports modern cipher suites
- OWASP Top 10: Insufficient Logging and Monitoring is included among top risks
- The NIST Cybersecurity Framework (CSF) was released in 2018 as version 1.1 for improving security posture
- S3 transfer pricing can materially affect web cost at scale; typical pricing is $0.023 per GB-month (region varies)
- CloudFront data transfer pricing varies by region; typical US price tiers apply to GB
- Fastly charges per request and data transfer; request pricing tiers apply at scale
Improving Core Web Vitals with faster, optimized loading can reduce abandonment and boost engagement.
Related reading
01 · Category
Web Traffic Sources2 stats
Interpretation
Web Traffic Sources Interpretation
For web traffic sources, mobile devices drive the majority with 53.3% of worldwide site traffic, so optimizing for mobile is likely the biggest lever given the way these audiences are distributed.
02 · Category
Web Performance Benchmarks12 stats
01
44.4% of web users are more likely to abandon sites that take longer than 3 seconds to load[2]
02
Google’s Lighthouse recommends image optimization as a best practice to reduce load time[3]
03
Google reports that 53% of mobile site visits are abandoned if pages take longer than 3 seconds to load[2]
04
An HTTP/2 enabled site can reduce page load times by 11% on average versus HTTP/1.1 (industrial tests)[4]
05
Gzip compression can reduce HTML/CSS/JS payload sizes by 60–70% (common web performance engineering results)[5]
06
Core Web Vitals were rolled into Page Experience in Google Search (mobile and desktop) starting 2021[5]
07
HTTP/2 is widely adopted; Statcounter reports HTTP/2 usage increasing steadily (platform stats)[6]
08
The average time spent on-site increases when bounce rate decreases; benchmarks tie lower bounce to longer sessions[7]
09
Largest Contentful Paint is measured as the render time of the largest visible content element[8]
10
CLS measures the sum of all unexpected layout shift scores during the entire lifespan of the page[8]
11
INP measures the latency of page interaction responses, considering the interaction timeline[8]
12
Preconnect reduces latency by establishing early connections; web.dev documents this optimization[8]
Interpretation
Web Performance Benchmarks Interpretation
Across these Web Performance Benchmarks, the key takeaway is that loading speed is directly linked to user abandonment, with 44.4% of users more likely to leave and 53% of mobile visits abandoned when pages take longer than 3 seconds, making performance optimization the most critical lever for Page Experience and search outcomes.
03 · Category
Industry Trends13 stats
01
Web Vitals guidance defines three core metrics for performance: LCP, CLS, INP[8]
02
The HTTP Archive report “State of the Web” is updated regularly and provides annual medians and distributions for web features[9]
03
Google Lighthouse defines 6 performance categories including Accessibility, Best Practices, SEO, PWA, and so on[3]
04
In 2024, performance monitoring via Real User Monitoring (RUM) is widespread among large sites; adoption in vendor surveys often exceeds 70%[10]
05
In 2024, AI is increasingly used for web personalization and search optimization across industries; enterprise adoption exceeds 50% in survey reports[10]
06
Google Search uses mobile-first indexing by default for many sites; the shift began in 2018 and became default later[5]
07
The WebAssembly standard is maintained by W3C and is used by modern web apps[11]
08
ECMAScript 2024 includes features used by modern websites; versioned standard published by ECMA[12]
09
W3C Web Components are standardized; the spec defines 4 core technologies including Custom Elements, Shadow DOM[11]
10
WordPress powers a large share of websites; W3Techs reports a global usage percentage[6]
11
React usage is tracked by W3Techs and is among top JS frameworks by adoption[6]
12
jQuery usage has declined; W3Techs tracks adoption share[6]
13
HTTP/3 adoption remains lower than HTTP/2 but is increasing; W3Techs tracks HTTP/3 usage[6]
Interpretation
Industry Trends Interpretation
Industry trends in web performance are increasingly shaped by standardized user-centric metrics like Core Web Vitals LCP, CLS, and INP, alongside the rapid growth of AI-driven personalization and search where enterprise adoption is already over 50%, showing how both measurement and optimization are moving from lab testing to real-world experience.
More related reading
04 · Category
Security & Compliance19 stats
01
TLS 1.3 is defined in RFC 8446 and supports modern cipher suites[13]
02
OWASP Top 10: Insufficient Logging and Monitoring is included among top risks[14]
03
The NIST Cybersecurity Framework (CSF) was released in 2018 as version 1.1 for improving security posture[15]
04
NIST SP 800-53 Rev. 5 contains 20 security control families and 18? (families) total; the document enumerates controls[16]
05
GDPR sets a maximum administrative fine of up to €20 million or 4% of annual global turnover, whichever is higher[17]
06
US SEC Regulation S-P requires safeguarding customer information and sets incident response rules[18]
07
The Digital Services Act (DSA) applies to very large online platforms and imposes compliance obligations; fines can reach 6% of annual turnover[17]
08
CISA’s Binding Operational Directive (BOD) for certain agencies requires timely patching; known timelines vary by directive[19]
09
OWASP ASVS defines verification requirements and uses a level structure (L1-L3)[14]
10
The CVE program recorded over 200k distinct CVE identifiers since inception (historical totals)[20]
11
NIST SP 800-63B defines authentication assurance levels with numeric levels 1–3 for some contexts[21]
12
FIDO2 is based on WebAuthn; WebAuthn standard supports multi-factor without shared secrets[11]
13
CSP report-only mode allows monitoring violations without enforcement; W3C spec includes directives[11]
14
HSTS (HTTP Strict Transport Security) is specified with a max-age directive; recommended max-age values are often 1 year or more[13]
15
SameSite cookie attribute supports Strict and Lax to mitigate CSRF; defined by RFC 6265bis[22]
16
ModSecurity Core Rule Set (CRS) includes 400+ rules (public project)[23]
17
OWASP recommends secure session management; session timeout policies are included in OWASP Cheat Sheet series (e.g., Session Management)[24]
18
W3C Web Performance Working Group defines loading performance metrics underpinning web vitals measurements[11]
19
The W3C recommends using Subresource Integrity (SRI) to ensure third-party scripts aren’t tampered with[11]
Interpretation
Security & Compliance Interpretation
Security and Compliance efforts are increasingly guided by modern standards and stricter governance, as shown by TLS 1.3 defined in RFC 8446 and by regulations like GDPR that can impose fines up to €20 million or 4% of global turnover, whichever is higher.
05 · Category
Cost Analysis12 stats
01
S3 transfer pricing can materially affect web cost at scale; typical pricing is $0.023 per GB-month (region varies)[25]
02
CloudFront data transfer pricing varies by region; typical US price tiers apply to GB[25]
03
Fastly charges per request and data transfer; request pricing tiers apply at scale[26]
04
Google Cloud Load Balancing egress costs apply per GB delivered (network pricing)[27]
05
Azure CDN pricing is metered by bandwidth (GB) and requests[28]
06
Web application firewall (WAF) services commonly price per request; AWS WAF charges per web ACL rule and per request (depending on model)[25]
07
DDoS protection often priced by protected bandwidth; AWS Shield Standard has no additional charge (baseline)[25]
08
If 10% of traffic is redirected to higher cache hit, bandwidth charges can drop proportionally (CDN billing proportional to egress)[29]
09
Using HTTP keep-alive reduces connection overhead; can reduce CPU and cost on busy servers[13]
10
CDN and edge compute can offload origin work, reducing origin compute spend[4]
11
Content compression reduces egress charges by reducing transferred bytes (cloud networking pricing is per GB)[4]
12
Reducing page weight by 100 KB can save megabytes at scale; savings scale linearly with page views (CDN egress is per GB)[5]
Interpretation
Cost Analysis Interpretation
In the cost analysis view of web spend, data transfer and request based pricing dominate because S3 transfer pricing alone can run about $0.023 per GB-month at scale while CDNs and WAF services add further per GB or per request charges from providers like CloudFront, Fastly, and AWS WAF.
report visual · Comparison
Why website performance matters: user abandonment and mobile impact
Mobile users are much more likely to abandon slow pages—highlighting how critical sub-3-second performance is.
Google reports that 53% of mobile site visits are abandoned if pages take longer than 3 seconds to load53%
44.4% of web users are more likely to abandon sites that take longer than 3 seconds to load
44.4%
An HTTP/2 enabled site can reduce page load times by 11% on average versus HTTP/1.1 (industrial tests)
11%
source-verifiedthinkwithgoogle.com · cloudflare.com
Reference
Cite This Report
This report is designed to be cited. We maintain stable URLs and versioned verification dates. Copy the format appropriate for your publication below.
APA
Marcus Afolabi. (2026, February 13). View Website Statistics. Gitnux. https://gitnux.org/view-website-statistics
MLA
Marcus Afolabi. "View Website Statistics." Gitnux, 13 Feb 2026, https://gitnux.org/view-website-statistics.
Chicago
Marcus Afolabi. 2026. "View Website Statistics." Gitnux. https://gitnux.org/view-website-statistics.
Sources & references
29 sources cited across this report
gs.statcounter.com
thinkwithgoogle.com
developer.chrome.com
cloudflare.com
developers.google.com
w3techs.com
optimizesmart.com
web.dev
httparchive.org
gartner.com
w3.org
tc39.es
rfc-editor.org
owasp.org
nist.gov
csrc.nist.gov
eur-lex.europa.eu
ecfr.gov
cisa.gov
cve.mitre.org
pages.nist.gov
datatracker.ietf.org
github.com
cheatsheetseries.owasp.org
aws.amazon.com
fastly.com
cloud.google.com
azure.microsoft.com
docs.aws.amazon.com
