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.

6
pages checked
8.1s
average wait for main content
3
pages that jump around

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

/
Needs work

The main content takes 10.0s to show up

Most of the page paints early, so the wait is easy to miss - but the biggest piece of the screen 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.

Homepage at 0.0s
Blank0.0s
Homepage at 2.7s
First content2.7s
Homepage at 4.5s
Loading4.5s
Homepage at 6.1s
Loading6.1s
Homepage at 6.4s
Layout jump6.4s
Homepage at 6.4s
Loading6.4s
Homepage at 8.1s
Loading8.1s
Homepage at 10.0s
Main content10.0s

Blue = the first content lands. Orange = the moment your main content appears. 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.

1.4 MB downloaded first 66/100 speed score

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-ai
Poor

The 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.

Blog post - how D2 uses AI at 0.0s
Blank0.0s
Blog post - how D2 uses AI at 1.5s
Blank1.5s
Blog post - how D2 uses AI at 1.5s
Main content1.5s
Blog post - how D2 uses AI at 1.8s
Loaded1.8s
Blog post - how D2 uses AI at 3.0s
Loaded3.0s
Blog post - how D2 uses AI at 3.4s
Loaded3.4s
Blog post - how D2 uses AI at 3.8s
Loaded3.8s
Blog post - how D2 uses AI at 6.2s
Layout jump6.2s
Blog post - how D2 uses AI at 6.3s
Layout jump6.3s
Blog post - how D2 uses AI at 6.3s
Layout jump6.3s
Blog post - how D2 uses AI at 7.1s
Loaded7.1s
819 KB downloaded first 70/100 speed score 1.29 layout-shift score

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/tech
Poor

The 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.

also main content at 11.1s

▶ 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.

Sector - tech at 0.0s
Blank0.0s
Sector - tech at 1.7s
First content1.7s
Sector - tech at 3.2s
Loading3.2s
Sector - tech at 3.9s
Loading3.9s
Sector - tech at 4.7s
Loading4.7s
Sector - tech at 6.1s
Loading6.1s
Sector - tech at 6.8s
Layout jump6.8s
Sector - tech at 6.9s
Layout jump6.9s
Sector - tech at 6.9s
Layout jump6.9s
Sector - tech at 7.0s
Loading7.0s
Sector - tech at 7.4s
Loading7.4s
Sector - tech at 9.7s
Loading9.7s
Sector - tech at 11.1s
Main content11.1s
Sector - tech at 11.2s
Loaded11.2s
1.9 MB downloaded first 42/100 speed score 1.16 layout-shift score

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

/work
Poor

The main content takes 13.2s to show up

Most of the page paints early, so the wait is easy to miss - but the biggest piece of the screen only lands then.

also layout jumps (0.23)

▶ 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.

Work index at 0.0s
Blank0.0s
Work index at 1.7s
First content1.7s
Work index at 2.4s
Loading2.4s
Work index at 3.7s
Loading3.7s
Work index at 4.5s
Loading4.5s
Work index at 6.1s
Loading6.1s
Work index at 6.7s
Layout jump6.7s
Work index at 7.2s
Loading7.2s
Work index at 8.4s
Loading8.4s
Work index at 9.5s
Loading9.5s
Work index at 10.5s
Loading10.5s
Work index at 12.5s
Loading12.5s
Work index at 13.2s
Main content13.2s
2.0 MB downloaded first 55/100 speed score 0.23 layout-shift score

This page takes over 13 seconds to show its main content, which is way too slow for any visitor to enjoy.

Service

/service
Poor

The main content takes 10.1s to show up

Most of the page paints early, so the wait is easy to miss - but the biggest piece of the screen 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.

Service at 0.0s
Blank0.0s
Service at 1.6s
First content1.6s
Service at 3.5s
Loading3.5s
Service at 4.1s
Loading4.1s
Service at 6.1s
Layout jump6.1s
Service at 7.3s
Loading7.3s
Service at 9.0s
Loading9.0s
Service at 10.1s
Main content10.1s
1.5 MB downloaded first 66/100 speed score

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

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.