Google Analytics and Microsoft Clarity load only after you accept. Clarity runs on selected public marketing pages. PostHog and Vercel site-level analytics and performance measurement may run independently of this choice.
Website Performance Testing and Core Web Vitals | Forge The Stack
Learn what Core Web Vitals measure, how to test a website, and how to prioritize performance work based on observed results.
Page performance is one part of a website's technical quality and user experience. Core Web Vitals provide measurements that can help identify issues, but they do not predict a site's rankings, inquiries, or revenue.
Start by measuring the pages and devices that matter to your project.
Measure the Current Site
Run comparable tests on representative pages and record the device, network, and measurement method. Field data and lab tests answer different questions; use both where available and avoid treating one score as a business forecast.
What "Slow" Actually Means
When we talk about site speed, we are measuring specific metrics that Google calls Core Web Vitals:
Largest Contentful Paint (LCP): How long it takes for the largest visible content element to render. Google's current good threshold is 2.5 seconds or less at the 75th percentile.
Interaction to Next Paint (INP): How quickly the page responds to user interactions. Google's current good threshold is 200 milliseconds or less at the 75th percentile.
Cumulative Layout Shift (CLS): How much the page layout shifts unexpectedly. Google's current good threshold is 0.1 or less at the 75th percentile.
These metrics help diagnose user-experience issues. Search visibility depends on many signals, and a Core Web Vitals result does not guarantee a ranking change.
Investigate the Causes
Performance depends on the page, assets, scripts, hosting, and network conditions. Hosted builders and custom implementations can both include code and third-party services; inspect the specific site before drawing conclusions about its platform.
Use a network waterfall and browser performance tools to identify which resources are requested, how large they are, and when they load.
Compare the performance controls available in the current plan with the site's actual requirements. A platform choice alone does not establish how a site will perform.
Prioritize Changes
List the measured issues, affected pages, and project constraints. Estimate implementation effort and test the result after each meaningful change. Do not infer a specific increase in traffic, inquiries, or revenue from a performance score alone.
How to Fix It
If your site is slow, you have two options: optimize what you have, or rebuild with performance as a foundation.
Optimizing an existing site: - Compress and convert images to WebP format - Defer non-critical JavaScript - Remove unused plugins and widgets - Enable browser caching - Reduce font file sizes (subset to characters you use)
The effect of these changes varies by page and implementation. Retest after each change and check that functionality and accessibility remain intact.
Considering a rebuild: - A defined implementation that meets the project's content and feature requirements - Images optimized at build time (WebP, proper dimensions, lazy loading) - Minimal JavaScript (vanilla ES6, no jQuery, no heavy libraries) - Hosting and delivery settings selected for the project's operational requirements
Compare the estimated rebuild scope and ongoing ownership costs with the optimizations available on the existing platform.
How to Test Your Speed
Run your site through these free tools:
1Google PageSpeed Insights (pagespeed.web.dev) — The definitive test. Shows Core Web Vitals, specific improvement suggestions, and mobile vs desktop scores.
2WebPageTest (webpagetest.org) — Detailed waterfall analysis showing exactly what loads and when.
3GTmetrix (gtmetrix.com) — Visual timeline and performance grades with historical tracking.
Use a low score as a prompt to inspect the underlying diagnostics. Prioritize issues by user impact, affected pages, and implementation effort rather than treating a single score as an emergency threshold.
The Bottom Line
Performance work can improve technical measurements and the experience of using a site. Its effect on search visibility or business outcomes varies and cannot be inferred from a lab score alone.
Measure the current site, address the issues relevant to its users, and document the results.
Sources & Citations
Industry
Google Core Web Vitals— LCP, INP, CLS definitions and pass/fail thresholds used in Google's ranking algorithm
Google defines a good Largest Contentful Paint as 2.5 seconds or less at the 75th percentile. Results vary by page, device, network, and measurement method; use field and lab data to identify issues for the specific site.
How do I test my website speed for free?
Use tools such as Google PageSpeed Insights and WebPageTest to inspect field and lab measurements. A score is diagnostic information, not a direct measure of customers, rankings, or revenue.
Can I speed up my Wix or Squarespace site without rebuilding?
Image sizing, third-party scripts, app usage, and page layout may be adjustable depending on the platform and plan. Measure the current site and check the provider documentation before deciding whether a rebuild is needed.
Ariel Karagodskiy
Founder, Forge The Stack
Building custom-coded websites for local businesses in Tucson, Arizona. No page-builder lock-in, no monthly platform fees — just fast, clean code you own.
Ready to upgrade your site?
Let us put these insights to work for your business. Free consultation, no obligation.