Mobile speed report · June 15, 2026
How thinkd2.com loads on a phone
We loaded 6 of your pages on a typical phone over a normal cellular connection and recorded each one frame by frame - 141 frames in all. On a fast desktop these pages feel fine, which is exactly why what is below is easy to miss.
Captured June 15, 2026 - a snapshot of the live site that day. If the site has changed since, this report may no longer reflect it.
In plain terms, a visitor on a phone waits about 8.1s before the typical page here is usable, and 3 of your pages visibly jump around under their thumb while loading.
How to read this. Each strip is one of your pages loading on a phone, left to right in real time. We pulled the moments that matter out of every frame we captured. Tap any frame to enlarge it.
Homepage
/The biggest piece of the page takes 10.0s to appear
Most of the page paints early, so the wait is easy to miss - but the biggest piece of the page only lands then.
▶ Press play - this is the 10.0s a phone visitor waits, in real time.
Frame-by-frame breakdown 16 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
Blue = the first content lands. Orange = the moment the biggest piece of the page lands. Red boxes = parts of the page that move after a visitor is already reading. A near-blank frame is a phone still showing an empty screen.
The page takes nearly 10 seconds to show you the content, which is slow; it has to download 1.5MB of images and fonts first, but once it loads, it works smoothly and doesn't jump around.
Blog post - how D2 uses AI
/post/how-d2-uses-aiThe page jumps around as it loads
The page scores 1.29 on Google's layout-shift scale, where anything above 0.25 is poor - so things move under your visitor's thumb.
▶ Press play and watch the page jump around as it loads.
Frame-by-frame breakdown 18 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
The page loads its main content fast, but things annoyingly shift around while loading, and it's a bit slow to respond to clicks.
Sector - tech
/sector/techThe page jumps around as it loads
The page scores 1.16 on Google's layout-shift scale, where anything above 0.25 is poor - so things move under your visitor's thumb.
▶ Press play and watch the page jump around as it loads.
Frame-by-frame breakdown 22 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
This page is quite slow to load, taking over 11 seconds to show its main content, and things jump around while it's loading.
Work index
/workThe biggest piece of the page takes 13.2s to appear
Most of the page paints early, so the wait is easy to miss - but the biggest piece of the page only lands then.
▶ Press play - this is the 13.2s a phone visitor waits, in real time.
Frame-by-frame breakdown 35 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
This page takes over 13 seconds to show its main content, which is way too slow for any visitor to enjoy.
Service
/serviceThe biggest piece of the page takes 10.1s to appear
Most of the page paints early, so the wait is easy to miss - but the biggest piece of the page only lands then.
▶ Press play - this is the 10.1s a phone visitor waits, in real time.
Frame-by-frame breakdown 42 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
The main content takes over 10 seconds to appear, which is quite slow, but the page feels stable and responsive once everything loads.
The rest of your pages, same pattern
- About /about Loads cleanly in 2.5s
That is the full read on your live site, captured frame by frame. Any questions on it, just reply to the email it came with.
Measured on June 15, 2026 on an emulated mid-range phone over the Slow-4G throttling profile Google PageSpeed uses - the conditions a real mobile visitor faces, not a developer's fast laptop. "Speed score" is the same 0-100 scale Google PageSpeed uses for mobile (90 and up is fast, under 50 is slow); "layout-shift score" is Google's CLS, where anything above 0.25 is poor.
Put together by ShakaCode.