Quick answer
Core Web Vitals are field and lab performance measurements such as loading, interactivity, and visual stability. Markup heuristics identify patterns that might contribute to work, such as render-blocking resources or missing image dimensions. NOTABIS reports the latter as review signals; they are not substitutes for real user or browser timing data.
What the issue means
A page can contain a synchronous stylesheet or script and still render quickly on a modern device. Another page can have no obvious markup warning yet suffer slow server time, a large image, or layout shifts caused by runtime code. Heuristics suggest where to investigate; Core Web Vitals measure outcomes for users.
Why it matters for SEO
Performance affects usability and is part of Google’s page experience systems, but no single markup pattern guarantees a ranking change. Field data reflects real visitors and devices, while lab tests help reproduce controlled conditions. Optimise the largest user-visible problems rather than clearing every heuristic.
How NOTABIS detects it
NOTABIS classifies stylesheet links and scripts without async or defer as potential render-blocking candidates and records render-blocking resource review evidence. It flags missing image dimensions, duplicate resource references, slow sampled responses, and large HTML separately. The service marks render-blocking impact as unmeasured; it does not collect Core Web Vitals in this check.
How to check it yourself
Use browser Performance and Network panels, Lighthouse or PageSpeed Insights, and Search Console’s Core Web Vitals report. Compare field and lab results, inspect resource timing, and identify the largest contentful element, long tasks, and layout shifts. Re-test on representative mobile hardware and network conditions.
How to fix it
Start with measured bottlenecks: improve server response and caching, prioritise the main content, reserve image space, split or defer non-critical JavaScript, and remove duplicate assets. Keep critical CSS and required scripts working, then validate changes with before-and-after timings and field data.
<img src="hero.webp" width="1200" height="800" alt="Trail shoes on a rocky path">
Do not add defer or lazy loading to code that must run before the page is usable. Recheck accessibility, consent, and interaction flows after performance work.
When this is intentional or does not need fixing
A small site may have too little field traffic for a stable dataset, and a third-party widget may be outside your control. A heuristic can be harmless when timing proves no user impact. Keep a resource that is required for correctness and document the trade-off.
Related issues
Read render-blocking resource candidates, missing image dimensions, duplicate resources, slow server responses, and large HTML responses.
Run a NOTABIS audit
NOTABIS identifies markup and response patterns worth measuring, helping you choose where to use real performance tools rather than treating a heuristic as a score.