Check of ciunkos.com/you-and-przemyslaw
Nov 17, 2026, 13:42 · daily
- Performance
- Accessibility
- Best Practices
- SEO
Lighthouse 13.5 (mobile, simulated throttling), median of three runs. Scores 0–100: 90 and up green, 50–89 orange, below 50 red; a dash means the category was not measured in that check.
TBT is the lab stand-in for INP, which needs real interactions.
- Performance
- 94good−3 vs previous−2 vs 7-day median
- LCP
- 1.3 sgood−512 ms vs previous+8 ms vs 7-day median
- CLS
- 0.01good±0 vs previous±0 vs 7-day median
- TBT
- 294 msneeds improvement+153 ms vs previous+62 ms vs 7-day median
- FCP
- 1.3 sgood−512 ms vs previous+16 ms vs 7-day median
- TTFB
- 18 msgood−4 ms vs previous±0 vs 7-day median
No slowdown against the previous check and the 7-day median.

- LCP element
section#hero > div.wrap > div.hero-text > p.leadI don’t know who you are. I don’t know what you need. But I have a very particu…- Page weight
- 1.1 MB
- Long tasks
- 7
- Conditions
- Lighthouse 13.5.0, mobile (Moto G Power emulation, 412×823), simulated throttling (150 ms RTT, 1.6 Mbps, CPU 4×), median of 3 runs, benchmarkIndex 2424
Loads
| Load | Perf | LCP | FCP | TBT | CLS | TTFB |
|---|---|---|---|---|---|---|
| 1 | 86 | 1.3 s | 1.2 s | 536 ms | 0.01 | 140 ms |
| 2 | 94 | 1.3 s | 1.3 s | 294 ms | 0.01 | 18 ms |
| 3 | 96 | 1.3 s | 1.3 s | 213 ms | 0.01 | 24 ms |
What failed
Performance 94
- Total Blocking Time
total-blocking-time290 ms - Network dependency tree
network-dependency-tree-insightpreconnect hints help the browser establish a connection earlier in the page loAdd preconnect hints to your most important origins, but try to use no more tha - Minimize main-thread work
mainthread-work-breakdown4.6 s - Use efficient cache lifetimes
cache-insightEst savings of 99 KiBhttps://ciunkos.com/hire/riddle/taken.mp4?v=2026-11-13-4b0d481https://ciunkos.com/hire/vendor/special-elite/special-elite-latin.woff2https://ciunkos.com/hire/vendor/permanent-marker/permanent-marker-latin.woff2 - Minify CSS
unminified-cssEst savings of 9 KiBhttps://ciunkos.com/hire/app.css?v=2026-11-13-4b0d481https://ciunkos.com/hire/themes/riddle.css?v=2026-11-13-4b0d481 - Minify JavaScript
unminified-javascriptEst savings of 3 KiBhttps://ciunkos.com/hire/app.mjs?v=2026-11-13-4b0d481 - Reduce unused CSS
unused-css-rulesEst savings of 28 KiBhttps://ciunkos.com/hire/app.css?v=2026-11-13-4b0d481https://ciunkos.com/hire/themes/riddle.css?v=2026-11-13-4b0d481 - Max Potential First Input Delay
max-potential-fid230 ms
Accessibility 100
Nothing failed in this category.
Best Practices 100
Nothing failed in this category.
SEO 100
Nothing failed in this category.
Google PageSpeed Insights: Comparison details
Vitals Desk is the primary measurement. Google adds one mobile lab run from its servers. This comparison does not change our scores, history or slowdown emails.
Substantial differences: LCP, TBT, FCP
The Lighthouse versions differ; scores and checks may not be directly comparable.
Different locations, hardware, Lighthouse versions and a single run versus our three-run median can produce different results. These are comparison notes, not regression alerts.
| Metric | Vitals Desk | Google minus Vitals Desk | |
|---|---|---|---|
| Performance | 94 | 98 | +4 |
| Accessibility | 100 | 100 | ±0 |
| Best Practices | 100 | 92 | −8 |
| SEO | 100 | 100 | ±0 |
| LCP | 1.3 s | 1.8 s | +494 ms |
| CLS | 0.01 | 0.01 | ±0 |
| TBT | 294 ms | 43 ms | −251 ms |
| FCP | 1.3 s | 1.8 s | +494 ms |
| TTFB | 18 ms | 157 ms | +139 ms |
- Lighthouse version
- 13.6.0
- Google checked at
- Nov 17, 2026, 13:42
- Google’s final URL
- https://ciunkos.com/you-and-przemyslaw
Additional failed checks in Google’s sample
These appear in Google’s saved sample but not in our saved list. Each source keeps a limited list.
- First Contentful Paint
first-contentful-paint(Performance) - Forced reflow
forced-reflow-insight(Performance) - Legacy JavaScript
legacy-javascript-insight(Performance) - Reduce unused JavaScript
unused-javascript(Performance) - Browser errors were logged to the console
errors-in-console(Best Practices) - Issues were logged in the `Issues` panel in Chrome Devtools
inspector-issues(Best Practices)