What is Page Speed?
Page speed is the time it takes for a web page to fully load and become usable for a visitor. It is a confirmed Google ranking factor and a direct driver of conversion rates. A page that loads slowly loses visitors before they see the first line of content, ranks below faster competitors in search results, and scores poorly on Core Web Vitals, the performance metrics Google uses to assess real-world page experience. Page speed is not a single measurement. It is a combination of loading time, interactivity, and visual stability that together determine how a page feels to a real user on a real device.
Why does page speed matter for SEO and conversions?
Page speed matters for two reasons that operate simultaneously: it is a Google ranking factor and it is a conversion factor. Both are measurable and both work against slow pages in ways that compound over time.
On the SEO side, Google confirmed page speed as a ranking factor in 2010 for desktop and in 2018 for mobile. The 2021 Page Experience update brought Core Web Vitals into the ranking system, which made speed measurement more precise. Google now uses real user data collected through Chrome to assess how pages actually load for real visitors on real devices, not just how they perform in a controlled lab test. Pages that consistently score poorly on Largest Contentful Paint, Interaction to Next Paint, or Cumulative Layout Shift are at a measurable ranking disadvantage against faster competitors with equivalent content quality.
On the conversion side, the relationship between load time and user behaviour is well-documented. Pages that load in under two seconds convert significantly better than pages that take four seconds or more. Every additional second of load time increases the probability that a visitor leaves before engaging with the content. For service businesses where the website is the primary lead generation channel, that drop-off translates directly into lost enquiries regardless of how strong the SEO is above it.
The two effects reinforce each other in a pattern that is worth understanding. A slow page ranks lower, receives less traffic, generates fewer engagement signals, and accumulates less ranking authority over time. A faster page ranks better, receives more traffic, generates stronger engagement signals, and compounds its ranking advantage. Page speed is not a one-time fix. It is a baseline that needs to be maintained every time a new app, script, image, or design element is added to the site.
For the specific speed issues found across 894 Wix website builds, the Wix website speed guide covers the seven most common causes and how to fix each one.
What causes slow page speed?
Page speed problems follow consistent patterns across every platform and business size. The same causes appear in Wix audits, WordPress builds, Framer sites, and custom-coded websites. Knowing which cause produces which symptom makes diagnosis significantly faster than running blanket optimizations and hoping for improvement.
Oversized images are the most common cause of slow page speed by a significant margin. In audits across 894 websites, images that are too large, uploaded in heavy formats like PNG or JPEG instead of WebP or AVIF, or placed above the fold without loading priority are the single most consistent speed bottleneck. A full-width hero image that has not been compressed or converted to a modern format can push Largest Contentful Paint past the two-and-a-half second threshold on its own, regardless of how well everything else on the page is optimized.
Third-party scripts are the second most consistent cause. Every external script running on a page, marketing pixels, chat widgets, cookie banners, analytics overlays, A/B testing tools, adds execution time that delays the browser's ability to respond to user interaction. Each script loads from an external server, which introduces network latency outside the site owner's control. A page with eight third-party scripts loading simultaneously will consistently produce poor Interaction to Next Paint scores regardless of how clean the rest of the build is.
Heavy animations and video backgrounds placed above the fold delay the moment the main content becomes visible. An entrance animation that fires before the page is fully loaded, a parallax effect that runs across a large hero section, or a looping video background all increase the time before a visitor can read or interact with the page. The design element that looks impressive in a mockup is frequently the element that produces the worst Core Web Vitals score in production.
Render-blocking resources, fonts, stylesheets, and scripts that must load before the browser can display the page, delay first paint for every visitor regardless of their connection speed. For the full breakdown of Wix-specific speed causes and fixes, the Wix website speed guide covers each pattern with data from real site audits.
How do you measure page speed?
Page speed measurement uses several tools, each providing a different perspective on performance. Using more than one gives a more accurate picture than relying on any single source, because different tools measure different things and no single score tells the complete story.
Google PageSpeed Insights is the most widely used starting point. It combines lab data, a controlled test run under standardised conditions, with field data, real user experience aggregated from Chrome visitors. The lab score produces a number between 0 and 100 and highlights specific issues. The field data section shows how real visitors experienced the page over the last 28 days. For SEO purposes, field data is what matters most because it is what Google actually uses in its ranking calculations. A high lab score with poor field data means real users are experiencing something the lab test did not capture, which is common when third-party scripts behave differently in production than in a controlled environment.
Google Search Console shows Core Web Vitals field data at scale across the full site rather than one page at a time. The Core Web Vitals report groups pages into good, needs improvement, and poor categories based on real user data. Pages flagged as poor here are the ones where Google's ranking signal is actively working against the site. This report is the right place to identify which pages need attention first rather than testing every URL individually in PageSpeed Insights.
Google Lighthouse runs a detailed lab audit accessible through Chrome DevTools without any account or subscription. It provides specific recommendations for each failing metric and identifies the exact resources causing delays. It is the most granular diagnostic tool available at no cost and the right tool for developers who need to understand precisely which image, script, or font is causing a specific performance issue.
For Wix websites specifically, the Wix Site Speed dashboard inside the Wix dashboard provides platform-specific performance data alongside the standard Core Web Vitals metrics. For a full walkthrough of how to use these tools to diagnose a slow Wix site, the Wix website speed guide and the Wix SEO diagnostic guide cover the full measurement and diagnosis process.
How do you fix page speed issues?
Page speed fixes follow a consistent priority order regardless of platform. Address the highest-impact causes first, verify with field data after changes go live, and treat optimization as an ongoing process rather than a one-time project.
Images are always the first priority. Convert every image to WebP or AVIF format before uploading. Set explicit width and height attributes on every image so the browser reserves the correct space before the image loads, which prevents layout shift. Use lazy loading for images below the fold so they do not compete with above-the-fold content for bandwidth on initial page load. For the hero image or the largest visible element above the fold, ensure it loads with high priority rather than being deferred. On Wix, uploading images through the Wix media manager automatically applies some compression, but oversized source files still need to be resized before upload rather than after.
Third-party scripts are the second priority. Audit every external script running on the site and remove any that are not actively contributing to revenue or operations. A chat widget that receives no conversations, a heatmap tool from a subscription that lapsed, or a social sharing script that adds a button nobody clicks are all adding load time without adding value. For scripts that are genuinely needed, defer loading until after the main page content is visible so they do not block the initial render.
Animations and video backgrounds above the fold are the third priority. Moving heavy design elements below the fold, replacing video backgrounds with static images, or removing entrance animations from the hero section consistently produces measurable LCP improvements without requiring any technical changes to the underlying code. For the full Wix-specific fix list covering images, scripts, animations, and layout shift, the Wix website speed guide covers each fix with the diagnostic step that confirms it is the right intervention before making the change.
How does page speed differ by platform?
Page speed potential and the path to improving it both vary by platform. The ceiling is high on every major platform when configured correctly. The floor is low on every platform when it is not. What changes is where the default settings sit and how much control you have over the elements that drive performance.
Wix manages hosting, CDN delivery, and core infrastructure automatically. That removes an entire category of speed problems that affect self-hosted platforms. A poorly configured hosting environment, missing caching, or a CDN that is not properly set up are not Wix problems because the platform handles all three. What remains within the site owner's control on Wix is image weight, app load, animation choices, and design decisions that affect how much the browser has to process before the page becomes usable. For the specific patterns that cause slow Wix sites despite the managed infrastructure, the Wix website speed guide covers the seven most common causes in detail.
WordPress gives more control over the hosting and caching layer than any managed platform. A WordPress site on quality managed hosting with a well-configured caching plugin and a CDN can achieve strong Core Web Vitals scores. The same site on shared hosting with a bloated theme, twenty plugins, and no caching will consistently produce poor scores. The control is real but so is the responsibility. Speed on WordPress requires active management decisions that Wix handles automatically.
Framer and Webflow both produce strong baseline performance through managed hosting and CDN delivery, similar to Wix. The speed risks on both platforms trace primarily to third-party scripts, custom animations, and heavy media. Shopify's managed infrastructure performs well by default for product and collection pages, with speed degradation typically introduced through app scripts and theme customization rather than the platform itself.
The practical implication across all platforms is the same: managed infrastructure raises the floor but does not guarantee strong performance. Build decisions, media weight, and script load determine where a site actually lands within the range the platform makes possible.
When does it make sense to work with a page speed specialist?
Page speed optimization is one of the areas where self-service fixes produce the most consistent results for the most common problems. Compressing images, removing unused apps, and moving heavy animations below the fold are all owner-level interventions that do not require specialist involvement. For a site where the main speed issues are image weight and unnecessary scripts, a focused afternoon with PageSpeed Insights and the fixes above will produce measurable improvement.
Where specialist involvement becomes the rational choice is when the obvious fixes have been made and Core Web Vitals field data in Google Search Console is still showing poor ratings across important pages. At that point the problem is usually in the build rather than in the content. Render-blocking resources, layout shift caused by font loading or dynamically injected elements, or INP failures driven by overlapping script execution all require a more detailed diagnostic than surface-level PageSpeed Insights recommendations provide.
Migration and redesign projects are the highest-risk moments for page speed regression. A site that had passing Core Web Vitals scores before a platform migration or visual redesign can regress significantly if the new build introduces heavier images, additional third-party scripts, or layout structures that shift during load. Speed should be part of the pre-launch checklist for any migration, not a post-launch audit item. By the time poor scores appear in Search Console field data, the ranking impact has already started.
Ecommerce sites are particularly exposed to speed regression because every new product, app integration, and marketing script adds cumulative load. A Shopify or Wix store that launched with strong performance scores and has since added five apps, a loyalty programme widget, and a live chat integration may have degraded significantly without the owner noticing until rankings or conversion rates decline.
We Optimizz includes page speed auditing and Core Web Vitals optimization in every SEO engagement. If your site is underperforming on speed or you are planning a migration and want performance protected through the transition, book a free discovery call and we will review your current scores live. The free SEO scan identifies the most visible technical issues including speed across your current setup.
