TECHNICAL SUITE · PERFORMANCE

Don't just tell me the page is slow. Tell me why.

Core Web Vitals measured per page, tied to the specific element or resource causing a failing score, an unsized image, a render-blocking script, not a single hidden site-wide number that leaves you guessing.

You are here · the workflow

CRAWL → DIAGNOSE → PRIORITISE → FIX → VERIFY → MONITOR

The technical surface · this page covers

Crawl & discoveryIndexabilityRenderingRedirectsSchemaContentInternal linksPerformanceCrawlabilityAssets

Part of Technical Suite's six-stage loop. See the full system →

Common challenges

A score tells you it's slow. Not why.

  • A speed tool reports a single number for the whole site. It doesn't say which template, which resource, or which 1,900 pages are responsible.
  • Unsized gallery images cause layout shift across an entire product template, and nobody connects the dots until someone manually inspects individual pages one at a time.
  • A render-blocking script gets added for a marketing feature, and Largest Contentful Paint quietly gets worse sitewide, with no obvious link back to the cause.
  • Fixing performance becomes a guessing game: swap an image here, defer a script there, without confidence any of it addresses the actual problem.

What needs to happen: a failing score needs to be traced to the specific cause, grouped by shared pattern, so a fix on one template can be confirmed to move the number.

How SEORCE does it: Core Web Vitals are measured per page, and each failing score is tied to the resource or element responsible. Fixing the cause, resizing an image, deferring a script, restructuring a template, touches design or code, so it's diagnosed for your team rather than applied automatically. What SEORCE removes is the guessing.

Where it shows up

Core Web Vitals, per page.

Pass rates, this crawl41,208 pagesDemo data
LCP under 2.5s78% pass
INP under 200ms91% pass
CLS under 0.164% pass
!Product pages are the worst offenders on CLS. Unsized gallery images are the shared cause across 1,900 of them: one template fix, not 1,900 separate ones.
Root cause

One template. 1,900 pages.

1,900 pages fail CLS
↓
Same product gallery template
↓
Gallery images missing width/height

One template fix addresses all 1,900 pages at once. That is the finding worth having, instead of 1,900 individual line items.

What you'll see

Inside performance.

Metrics

Per page, not site-wide

● LCP ● INP ● CLS
  • LCP, INP and CLS, measured per page
  • The specific element or resource behind each failing score
Root cause

Grouped, not repeated

1,900 pages→1 template
  • Root causes grouped by shared template or pattern
  • Pass-rate trends by section, crawl over crawl
Verification

Did the fix work

  • Confirmation once a template fix moves the number

What does Performance check?

Performance measures Core Web Vitals, Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift, per page during the continuous crawl, and ties each failing score to the specific element or resource responsible rather than reporting a single site-wide number. Root causes are grouped by shared template or pattern, so a fix affecting a thousand pages shows up as one finding. Applying the fix, resizing an image, deferring a script, restructuring a template, touches design or code, so it's diagnosed and left for your team; SEORCE provides the exact cause, not a guess.

Key facts

  • Measures LCP, INP and CLS per page, not a single site-wide score
  • Ties each failing score to the specific element or resource responsible
  • Groups root causes by shared template, so one fix can address many pages
  • Fixes are diagnosed for your team: performance changes touch design and code, not a mechanical correction

Last reviewed 15 October 2026 by the SEORCE team.

Common questions

Frequently asked about performance.

Updated 18 September 2026

The actual cause. A single score tells you a page is slow; it doesn't tell you why. Performance ties each failing Core Web Vital to the specific element or resource responsible.

No. Performance root causes are diagnosed, not auto-applied. Resizing an image, deferring a script, or restructuring a template are changes that touch design or code, and stay a decision for your team.

Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift, measured per page against current pass/fail thresholds.

Yes. Root causes are grouped by shared pattern, so if 1,900 pages fail CLS for the same reason, that shows up as one finding, not 1,900 separate ones.

Free to start

Find out what's slowing your pages down.

Core Web Vitals per page, tied to the cause, grouped by shared template.

3,000+ users · Free forever plan, no card needed