5 WordPress Performance Metrics to Track (and What to Do When They Drop)

Ask ten site owners what “performance” means and half of them will talk about load time while the other half will talk about traffic and sales. Both groups are right. A WordPress site that loads in one second but never shows up in search is underperforming, and so is a popular site that makes mobile visitors wait four seconds before they can tap a button.

WordPress performance metrics are the numbers that show how fast your site feels to real visitors and how well it turns those visits into search traffic, engagement and leads. This guide covers the five we think every site owner should check: one for speed, three for search and engagement, and one for results. For each one you will see what it measures, where to find it in Google Analytics 4, Search Console or PageSpeed Insights, what a healthy number looks like, and what to check first when it drops. All five are free to measure.

Short answer: the five metrics that tell you the most about WordPress site performance are:

1. Core Web Vitals (LCP, INP and CLS), which show how fast and stable your pages are for real visitors.
2. Engagement rate in GA4, the metric that replaced the old bounce rate.
3. Organic landing pages, meaning the pages that earn search traffic and hold attention.
4. Search queries in the Google Search Console performance report: clicks, impressions, CTR and average position.
5. Form conversion rate, tracked as key events in GA4.

Speed or results? WordPress performance means both

Most WordPress analytics guides list traffic numbers and skip speed. Most speed guides list Lighthouse scores and skip what happens after the page loads. In practice the two are linked. A slow Largest Contentful Paint sends people back to the results page before they read a word, which shows up later as a lower engagement rate. Fewer engaged visits means fewer form submissions. And when engagement and conversions fall at the same time across many pages, the cause is often technical rather than editorial.

That is why this list of metrics to track on a WordPress site starts with speed and ends with conversions. Read it as a chain: when a later metric looks bad, check the earlier ones before you start rewriting content.

This guide stays close to the site itself. If you also need the business view, such as traffic sources and campaign attribution, our overview of website metrics to track for growth covers those.

The 5 WordPress performance metrics at a glance

Metric	What it tells you	Where to find it	Healthy signal	Check first when it drops
Core Web Vitals	Whether real visitors get a fast, stable page	Search Console (Core Web Vitals report) and PageSpeed Insights	LCP of 2.5 s or less, INP under 200 ms, CLS under 0.1	Server response, page cache, hero image, third-party scripts
Engagement rate	The share of visits that were more than a quick exit	GA4: Traffic acquisition and Landing page reports	Stable or rising against your own baseline	Landing page speed and search intent match
Organic landing pages	Which pages earn search traffic and keep it	GA4 Landing page report filtered to Organic Search	Top pages holding or growing, no busy page with weak engagement	Outdated content, intro that misses the query
Search queries	What people typed before they found you	Search Console: Performance, Search results	Impressions and clicks trending up, CTR in line with position	Title tag and meta description
Form conversion rate	Whether visits turn into leads or sign-ups	GA4 key events	Stable or rising, small gap between form starts and submissions	Field count, spam protection, mobile layout

1. Core Web Vitals: LCP, INP and CLS

Core Web Vitals are Google’s three field metrics for page experience. They come from real Chrome visitors rather than a test machine, which makes them the most honest speed numbers you can get for a WordPress site.

• Largest Contentful Paint (LCP) measures how long the main content takes to appear. Good is 2.5 seconds or less.
• Interaction to Next Paint (INP) measures how quickly the page responds when someone taps, clicks or types. Good is under 200 milliseconds. INP replaced First Input Delay as a Core Web Vital in March 2024, so any guide that still talks about FID is out of date.
• Cumulative Layout Shift (CLS) measures how much the layout jumps around while it loads. Good is below 0.1.

These thresholds come straight from Google’s Core Web Vitals documentation, which also says good scores line up with what its core ranking systems seek to reward. Google judges each metric at the 75th percentile of visits, so a fast experience on your own laptop does not count if most visitors are on mid-range phones.

Where to find them: in Search Console, open Experience and then Core Web Vitals. The report groups URLs that share the same problem, so one fix in a theme template can clear hundreds of posts at once. After you ship a fix, open the issue and click Validate fix. Google then monitors the affected URLs for 28 days, which is why improvements show up slowly. For a single page, run PageSpeed Insights and read the real-user section at the top before you look at the score.

What usually breaks each metric on WordPress:

• LCP: an oversized hero image, a slider, a background video without a poster image, or a slow server response.
• INP: heavy JavaScript from page builders, chat widgets, ad scripts and analytics stacks that load on every page.
• CLS: cookie banners and promo bars injected after load, images without width and height attributes, ads with no reserved space and late-swapping web fonts.

We walk through the fixes in order of impact in our guide to improving PageSpeed Insights on WordPress, from caching and the hero section down to fonts and plugin cleanup.

Time to First Byte: the number behind a slow LCP

Time to First Byte (TTFB) is not a Core Web Vital, but it sits underneath LCP. It measures how long the server takes to start sending the page. On WordPress, a slow TTFB usually points to one of three things: no full-page caching, an overloaded hosting plan, or plugins running expensive database queries on every request. Google’s web.dev guidance on TTFB treats 0.8 seconds or less as good, as a rough guide rather than a strict rule. If your TTFB is well above that, compressing images will not rescue your LCP, because the browser is still waiting for the HTML.

Caching is the usual first fix. Our guide to speeding up a WordPress site without a developer shows how to set it up without breaking logged-in pages or carts.

Field data versus lab data

PageSpeed Insights shows two kinds of data. Field data is what real visitors experienced over the previous 28 days. Lab data is a single simulated Lighthouse test, run by default on an emulated mid-range phone with a throttled connection, and the 0 to 100 performance score comes from it. Use lab data to debug and field data to judge.

Smaller sites often see “no data” in the field section, because Chrome only reports URLs with enough real traffic. When that happens, check the origin summary for the whole domain, test your most important templates in the lab, or add a real user monitoring plugin so you collect your own numbers.

2. Engagement rate: what replaced bounce rate in GA4

Sessions tell you how many visits you got. They do not tell you whether those visits were worth anything, which is why a raw session count makes a weak headline metric. Engagement rate does a much better job.

Under Google’s own definition of engagement rate and bounce rate, a GA4 session counts as engaged when it lasts longer than 10 seconds, includes a key event, or includes at least two page views. Engagement rate is engaged sessions divided by all sessions. GA4 bounce rate is simply the opposite: the share of sessions that were not engaged. If your engagement rate is 62%, your bounce rate is 38%.

The definition change matters. Universal Analytics, which stopped processing data in July 2023, counted any single-page visit as a bounce, even if the reader spent five minutes on a tutorial. GA4 counts that same visit as engaged. Bounce rate benchmarks written for the old metric, including the widely repeated “aim for 40% or lower” advice, do not translate to GA4 bounce rate.

There is no universal good engagement rate either. A recipe blog, a SaaS pricing page and a help center article behave differently. Compare each page type against its own history, and watch the trend after every design, theme or plugin change.

Where to find it: in GA4, open Reports > Acquisition > Traffic acquisition to see engagement rate by channel, or Reports > Engagement > Landing page to see it for each entry page. Keep average engagement time next to it. When engagement rate looks healthy but engagement time is very short, visitors may be clicking around without finding what they came for.

3. Organic landing pages: where your traffic actually starts

Landing pages are the pages where visits begin. Filter them to organic search and you get the short list of URLs that earn your search traffic. This is the metric that tells your content team where to spend its time.

In GA4, open Reports > Engagement > Landing page and add a filter for Session default channel group exactly matching Organic Search. Sort by sessions, then read the table in four groups:

• High traffic, strong engagement: protect these. Keep them current, make sure related posts link to them, and never change their URLs without a redirect.
• High traffic, weak engagement: the page ranks but disappoints. Compare the intro with the queries it ranks for in Search Console, then check its Core Web Vitals.
• Low traffic, strong engagement: good content that few people see. Add internal links from related posts and test a clearer title.
• Pages losing traffic month over month: refresh candidates. Update them before they slide off page one, not after.

A worked example: reading the landing page report

Here is how the four groups play out on a small agency site. The numbers are illustrative, but the pattern is one you will see on almost any WordPress site:

Page	Organic sessions	Engagement rate	Group	First move
Service page	900	64%	High traffic, strong engagement	Keep it current and link to it from related posts
Blog post about slow mobile pages	1,400	31%	High traffic, weak engagement	Move the answer to the top and fix a slow mobile LCP
Long technical guide	120	71%	Low traffic, strong engagement	Add three internal links from busier posts and test a clearer title
Old tools roundup	Down 40% in three months	48%	Losing traffic	Refresh outdated tools and screenshots before it drops off page one

Notice that only one of the four rows needs a real rewrite. The blog post with weak engagement is the urgent one: it already wins the click, and Search Console shows it ranks for a question that its first screen does not answer. The technical guide needs links, not words. That is the main value of this report. It tells you which kind of work each page needs, so you stop rewriting pages that only needed a link or a faster template.

Track AI referral traffic as its own channel

Visits from AI assistants such as ChatGPT, Perplexity, Gemini, Copilot and Claude arrive as referral traffic, and the default GA4 reports mix them in with every other referring website. To see them clearly, go to Admin > Data display > Channel groups and create a new channel group. GA4 starts it as a copy of the default channels. Add a channel called AI assistants with the condition Source matches regex chatgpt|openai|perplexity|gemini|copilot|claude, then reorder the list so the new channel sits above Referral. Order matters, because GA4 puts each visit in the first channel whose rule it matches.

Two caveats. Some AI apps send no referrer at all, so part of this traffic still lands in Direct, and new assistants keep appearing, so review the regex every few months. The good news is that custom channel groups apply to your reports retroactively, so you can look back at earlier months as soon as you save.

Once that AI referral traffic has its own row, you can see which of your pages AI tools cite and send people to. If you want more of those visits, the page structure that helps is covered in our guide to optimizing WordPress for AI search.

4. Search queries: clicks, impressions, CTR and position

The words people type before they find you are the closest thing you have to hearing your audience think out loud. The Google Search Console performance report (Performance > Search results) shows them, with four numbers for every query and every page:

• Clicks: visits that came from Google Search.
• Impressions: how often your pages appeared in results.
• CTR: clicks divided by impressions.
• Average position: your typical ranking for that query.

Search Console keeps 16 months of data, so compare the last 28 days with the previous 28 days and with the same period last year. Three patterns are worth acting on:

• High impressions, low CTR: the page appears but does not get chosen. Rewrite the title and meta description so they match the query more closely. Keep in mind that AI Overviews and other result features can lower CTR on informational queries even when your snippet is fine.
• Average position between roughly 8 and 20: these queries sit close to page one. A focused new section, a sharper heading or a few internal links can be enough to move them.
• Queries the page was not written for: if a post ranks for questions it barely answers, add a section that answers them properly or give the topic its own post.

Change one thing per page and give Google a few weeks before you judge the result. If the data shows the site is barely ranking at all, speed is rarely the only reason. Our guide to higher SEO rankings for WordPress websites covers the other foundations, from hosting and theme choice to your SEO plugin.

5. Form conversion rate and key events

For most business sites, the form is where performance turns into revenue: a quote request, a demo booking, a newsletter sign-up. Form conversion rate is the share of visitors to a form page who submit it.

In GA4 you track it by sending a form submission event and marking it as a key event, the name GA4 has used for conversions since March 2024. Be careful with the automatic form tracking in GA4 enhanced measurement. It can miss forms that submit through JavaScript and can count failed submissions, so its numbers are often wrong in both directions. The reliable options are a thank-you page that fires its own event, or the GA4 integration built into your form plugin.

Track form starts as well as submissions. The gap between the two is your abandonment rate, and it tells you whether the problem is the form itself or the page that leads to it. Many starts and few submissions point to the form. Few starts point to the page, the offer or the traffic.

Form fixes that usually move the number

• Cut every field you will not use in the follow-up. Each extra field is one more reason to quit.
• Place the form where intent is highest, usually beside or right after the offer it supports, not only at the bottom of a long page.
• Use a single column on mobile and the right input types, so phones show the number pad for phone numbers and the email keyboard for email addresses.
• Check each field when people leave it, not while they are still typing and not only after they press the button. Once an error is showing, clear it the moment the input becomes valid. In Baymard Institute’s form usability research, 31% of the ecommerce sites it benchmarked had no inline validation at all.
• Write button text that says what happens next, such as “Get my quote” instead of “Submit.”
• Add proof close to the button: a short testimonial, a response-time promise or a one-line privacy note.
• Keep spam protection but make it invisible. A honeypot field or an invisible challenge removes the puzzle without letting bots flood your inbox.
• Label optional fields clearly, or better, remove them.
• Check the INP of the form page. A form that lags while people type is a form people abandon.

Test every change on a phone before you check it on a desktop. Mobile visitors are usually the least patient with long or fiddly forms, and they are often the majority of your traffic.

Outbound clicks and other secondary signals

Outbound clicks are often promoted as a key metric, but for most sites they are a supporting signal. GA4 enhanced measurement records them automatically as a click event with an outbound parameter, so you can see which external links people use without installing anything extra.

They matter most in three cases: affiliate sites, where the outbound click is the conversion; publishers who report referral value to partners; and resource pages, where clicks show which recommended tools readers actually trust. Linking to good sources helps readers check your claims, and that is reason enough to do it. It is not a ranking shortcut, and knowing who you link to will not earn you backlinks on its own.

Other numbers worth a quick monthly look:

• 404 errors in the Not found list of Search Console’s Pages report, especially after a redesign or URL change.
• Site search terms from the view_search_results event in GA4, which reveal content people expect to find on your site but cannot.
• Uptime alerts, because no other metric recovers while the site is down.
• Site Health under Tools in the WordPress dashboard, which flags an outdated PHP version, failed scheduled events and a missing persistent object cache.
• Slow database queries, which the free Query Monitor plugin shows page by page. Turn it on while you investigate a slow TTFB, then deactivate it.
• PHP errors after plugin, theme or PHP version updates. Our guide to WordPress debug mode and the debug.log file shows how to turn logging on and off safely.

A 30-minute monthly WordPress performance review

You do not need a data team to keep these numbers healthy. This routine is a simple way to measure WordPress performance without living inside dashboards. Block 30 minutes once a month and work through it in order:

1. Core Web Vitals report in Search Console (5 minutes). Note any URL group that moved from Good to Needs improvement or Poor.
2. PageSpeed Insights on four page types (5 minutes). Test the home page, a popular blog post, a key service or product page and an archive page.
3. GA4 landing pages filtered to Organic Search (5 minutes). Flag pages with falling sessions or weak engagement.
4. Search Console queries in positions 8 to 20 (5 minutes). Pick two to work on this month.
5. Key events and form conversion rate (5 minutes). Compare form starts with submissions on your main forms.
6. Change log (5 minutes). Write down every plugin update, theme change, new script and hosting change from the month.

The change log is the step most teams skip, and it is the one that makes the other five useful. When TTFB jumps or INP gets worse the week after an update, the log tells you where to look. If the culprit turns out to be a custom plugin, our notes on performance optimization for custom WordPress plugins show where the usual slowdowns hide.

Tracking mistakes that make WordPress metrics lie

Good decisions need clean data. These setup problems are common on WordPress sites and quietly distort every number above:

• Counting your own visits. Editors refreshing pages all day inflate sessions and distort engagement. Define internal traffic in the GA4 tag settings and activate the matching data filter.
• Loading the GA4 tag twice. A theme option, an analytics plugin and Google Tag Manager can each add the same tag. Duplicate tags double page views and make engagement rate meaningless. Check your page source or Tag Assistant for more than one copy.
• Delaying analytics too aggressively. Performance plugins that hold back JavaScript until the first scroll or click can stop GA4 from loading on short visits. Those quick exits never get recorded, so engagement rate looks better than reality. Exclude the analytics tag from the delay list, or accept the trade-off knowingly.
• Marking page_view as a key event. Nearly every session has one, so engagement rate jumps close to 100% and stops meaning anything.
• Ignoring consent. Where a cookie banner is required, visitors who decline may not appear in GA4 at all, or only in modeled data. Compare GA4 organic sessions with Search Console clicks to understand the size of the gap.
• Judging speed by the lab score. A 95 on a fast office connection says little about a visitor on a mid-range phone. Field data decides.

What site owners ask about GA4 bounce rate, AI traffic and PageSpeed scores

Measure less, fix more

The point of tracking WordPress performance metrics is not a prettier dashboard. It is a short, honest list of what to fix next. Start with Core Web Vitals, because a slow page drags every other number down with it. Then use engagement rate, organic landing pages and search queries to decide which content deserves your attention, and use form conversion rate to confirm that the work is paying off.

Run the 30-minute review once a month, keep a change log, and change one thing at a time. That habit will do more for your WordPress site performance than any single plugin.