Tutorial objective
Technical performance measures the page's real 'diet'. It doesn't just look at speed, but how heavy it is, what blocks it, and which resources are being dragged unnecessarily.
This tutorial explains how to review total weight, HTML, CSS, JavaScript, external scripts, and blocking resources without confusing this check with Core Web Vitals.
What AISEO checks in technical performance
Total weight
Assesses whether the page loads too many resources for the content it provides.
CSS and JavaScript
Detects oversized or unnecessary stylesheets and scripts.
Blocking resources
Checks elements that delay initial load or hinder rendering.
Third-party resources
Monitors widgets, analytics, pixels, fonts, and external libraries.
How to interpret the result
Pass
The page keeps weight, CSS, JavaScript, and external resources under control.
Warning
There are signs of heavy load or blocking, but they do not compromise the entire technical reading.
Fail
The page is oversized, loads excessive scripts, or blocks critical content.
Technical reference example
The review should separate base load from measured experience. This check looks at structure and weight; Core Web Vitals looks at final behavior.
Check 13: weight + CSS + JS + blocking resources
Check 25: LCP + INP + CLSA page may need complex resources, but each resource must have a clear purpose.
Common mistakes
- Loading complete libraries for minimal interaction.
- Using huge global CSS on pages that only need part of it.
- Adding too many external scripts on all URLs.
- Optimizing images but forgetting JavaScript, fonts, or widgets.
How to fix it
- Reduce unused CSS and JavaScript
- Defer scripts that are not critical for initial load.
- Avoid loading external resources on pages where they are not used.
- Control total weight, fonts, images, widgets, and dependencies.