The free test at DoSieci Speed Check returns an overall score from 0 to 100, a breakdown into six categories, and a prioritized list of issues. The number itself isn't the point — it's there to help you quickly see where the biggest problem is and where to start.
What the overall score means
A score of 80 or above means the site is in good shape, 60–79 is an area to improve, 40–59 signals real problems, and below 40 means something worth fixing as soon as possible. The overall score summarizes six categories: Performance, Technical SEO, Meta & Indexing, Accessibility, Social / Open Graph, and Best Practices. The “Performance” category covers how fast the page loads and responds — the rest show additional technical issues picked up during the same scan.
Real-user data vs. lab results
The report distinguishes between two data sources. Real-user data (Chrome UX Report) shows how visitors actually loaded the page over the past few weeks — this is the most reliable picture, but it needs enough traffic for Google to have collected the data at all. If a site doesn't get much traffic, you'll only see lab results (Lighthouse) — a single, controlled measurement. Missing real-user data doesn't mean the site is slow — it just means there isn't enough traffic yet to have statistics.
Core Web Vitals — three numbers worth remembering
- LCP (Largest Contentful Paint) — how quickly the page's main, most important content appears;
- INP (Interaction to Next Paint) — how quickly the page responds to a click or tap;
- CLS (Cumulative Layout Shift) — whether the page layout “jumps” while it loads.
Each one gets a label: good, needs improvement, or poor — based on the same thresholds Google uses to evaluate pages.
What this test can't see
The external test checks what's visible from the outside: HTTP headers, cache, compression, redirects, and detected technology (WordPress, WooCommerce, caching plugins). It has no access to the panel, the database, or the server — it doesn't see SQL queries, WP-Cron, Action Scheduler, PHP configuration, or logs. That requires a full technical audit with access to the account.
A sensible order of action
- Read the “What to fix first” section — issues are assigned a priority (critical, high, medium, low).
- Start with items marked critical or high — these usually give the biggest, fastest-to-see improvement.
- Check the “What's already working well” section — nothing needs to change there.
- After making fixes, run the test again on the same address and compare the results.