Page weight
Checks the total HTML response size (aim for <500 KB).
Why does this matter?
A heavy page takes longer to load, especially on mobile connections. Google's Core Web Vitals are negatively affected by large page weights. Every extra kilobyte delays the Largest Contentful Paint (LCP).
How to fix it?
Minify HTML, CSS and JavaScript. Remove unused CSS classes and JavaScript. Load scripts asynchronously. Use lazy loading for images. Consider a Content Delivery Network (CDN).
This check scores from 0 to 100. Below 50 is a fail, 50 to 89 is a warning, 90 or above is good. After each crawl you see the score per page in your report, with a short note on what we found.
Frequently asked questions
Checks the total HTML response size (aim for <500 KB).
A heavy page takes longer to load, especially on mobile connections. Google's Core Web Vitals are negatively affected by large page weights. Every extra kilobyte delays the Largest Contentful Paint (LCP).
Minify HTML, CSS and JavaScript. Remove unused CSS classes and JavaScript. Load scripts asynchronously. Use lazy loading for images. Consider a Content Delivery Network (CDN).
Example
Copy the code below and adapt the domain name, brand name and content to your situation.
# Vite automatically minifies CSS and JS in production builds
yarn build # or: npm run build
# TailwindCSS: remove unused classes (tailwind.config.js)
module.exports = {
content: [
'./resources/**/*.blade.php',
'./resources/**/*.js',
],
}
# Lazy loading for images
<img src="product.webp" loading="lazy" width="800" height="600" alt="...">
# Remove unused plugins and scripts from package.json