Site health
Speed as real users experience it, the lab scores of four representative pages, and what the index looks like. The score is read on mobile, where the site is slower and most of the traffic is; switch to desktop to see the other half.
Site health
Half the share of real users who get all three speed measures 'good', half the Lighthouse average of the representative pages. Mobile. Target: over 90.
Speed · Core Web Vitals (mobile)
Real users, 75th percentile. The mark should sit in the green band.
Loading (LCP)
2.9 s
When the main content is visible · target under 2.5 s
Response (INP)
406 ms
How fast the page reacts to a tap · target under 200 ms
Shift (CLS)
0.10
How much the layout jumps while loading · target under 0.1
Speed threshold (mobile)
PageSpeed · CrUXNot passing
All three measures ‘good’ at the 75th percentile. A Google ranking signal.
LCP 'good' share
PageSpeed · CrUX58.0%
Mobile users seeing LCP under 2.5 s
INP 'good' share
PageSpeed · CrUX53.0%
Mobile users seeing INP under 200 ms
CLS 'good' share
PageSpeed · CrUX75.0%
Mobile users seeing CLS under 0.1
Lighthouse average
PageSpeed · CrUX44
Four representative pages · mobile · 0–100
Desktop LCP
PageSpeed · CrUX2.2 s
Real users, 75th percentile
Loading time (LCP) · weekly
Real users, 75th percentile · target under 2.5 s
Response (INP) · weekly
Real users, 75th percentile · target under 200 ms
Layout shift (CLS) · weekly
Real users, 75th percentile · target under 0.1
Representative pages (mobile)
Lighthouse lab scores, one page per template: the four the score averages. Vitals here are lab measurements of that page, not real-user data.
| Page | Template | Performance | Accessibility | Best practices | SEO | LCP | INP | CLS |
|---|---|---|---|---|---|---|---|---|
| / | Home | 52 | 91 | 83 | 92 | 2.4 s | 210 ms | 0.05 |
| /coffee | Category | 41 | 88 | 79 | 90 | 3.1 s | 380 ms | 0.12 |
| /coffee/ethiopia-yirgacheffe | Product | 29 | 86 | 75 | 89 | 3.9 s | 640 ms | 0.14 |
| /blog/how-to-brew-filter-coffee | Blog post | 34 | 93 | 83 | 96 | 3.6 s | 290 ms | 0.09 |
Score bands: 90 and over good, 50 to 89 needs work, under 50 poor. Vital bands follow Google’s thresholds for each measure.
Lighthouse opportunities
What the lab run says would save the most time, across the four pages.
| Opportunity | Saving | Pages | Detail |
|---|---|---|---|
| Properly size images | 1.2 s | 3 | Product hero images are served at 2400 px for a 390 px viewport. |
| Reduce unused JavaScript | 0.9 s | 4 | The reviews widget and a chat script load on every page, used on two. |
| Eliminate render-blocking resources | 0.5 s | 4 | Two font stylesheets and the theme CSS block the first paint. |
| Preload the largest contentful paint image | 0.4 s | 2 | Category and product templates; the home page already does. |
| Serve images in next-gen formats | 0.4 s | 4 | JPEG on the product gallery; WebP or AVIF halves the bytes. |
Index coverage
What Google has indexed, what it has not, and why.
- Indexed pages
- 214
- Not indexed
- 37
- URLs in the sitemap
- 226
- Sitemap last read
- 13 Sep
- Last inspection
- 14 Sep
- Indexed of sitemap
- 94.7%
Redirect chains (two hops)
Old /yazilar/ URLs → /blog/ → trailing-slash variant
38warningCrawled, currently not indexed
Mostly tag pages
21infoDuplicate without user-selected canonical
Colour variants of equipment
9warningNot found (404)
Deleted product pages still linked from three posts
7error
Open issues
Everything on this tab that needs a person, in one list. The same items sit on the Actions tab with an owner.
Mobile does not pass Core Web Vitals
LCP 3.3 s (target 2.5) and INP 521 ms (target 200); CLS passes.
1 itemerrorThird-party reviews script blocks input
About 300 ms of input delay on product pages since the 30 Jun switch.
4 itemswarningPages returning 404 with internal links
Deleted products still linked from three posts.
7 itemserrorRedirect chains
Two hops on the old blog URLs since the August move.
38 itemswarningImages without explicit dimensions
Blog post images cause the small layout shifts on mobile.
12 itemsinfo
CrUX needs enough traffic per page to report, so page-level vitals are the four representative pages and the site-level figures are the origin’s.