Mobile speed report · June 23, 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 - 136 frames in all. On a fast desktop these pages feel fine, which is exactly why what is below is easy to miss.
Captured June 23, 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 5.6s 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 4.5s to appear
Until then a visitor on a phone is looking at a mostly empty screen.
▶ Press play - this is the 4.5s 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 4.5 seconds to show what you came for, which is slow, but then it works smoothly without jumping 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 19 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
The page shows its main content quickly, but text and buttons shift around as it loads, which is frustrating and distracting.
Work index
/workThe biggest piece of the page takes 13.3s 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.3s a phone visitor waits, in real time.
Frame-by-frame breakdown 38 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
This page loads slowly - you'll wait about 13 seconds to see the main content, and the browser downloads 2 megabytes across 81 files to get there.
Service
/serviceThe 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 43 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
The page responds from the server right away, but takes almost 10 seconds to show its main content, making it feel sluggish and slow.
Sector - tech
/sector/techThe page jumps around as it loads
The page scores 0.21 on Google's layout-shift scale; a page is fully stable only below 0.10, and yours is above that, so things can still move under your visitor's thumb.
▶ Press play and watch the page jump around as it loads.
Frame-by-frame breakdown 12 frames analyzed
The moments that matter, left to right - tap any frame to enlarge it.
The page shows its main content fast and responds smoothly to clicks, but the layout jumps around quite a bit as it finishes loading.
The rest of your pages, same pattern
- About /about Loads cleanly in 2.4s
Measured on June 23, 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.
Accessibility helps your search ranking. Search engines read the same labels, headings, and alt text that visitors with limited vision, color blindness, or keyboard navigation rely on, so these fixes help your SEO too.
A high score means most of each page is fine. But it only takes one blocking issue to turn a real customer away, so the page below is where we'd start.
Most pages score 100 but still have two repeated issues: navigation sections are not labeled distinctly, and two pages are missing a main heading. Fixing those two patterns across all pages - plus making the scrollable section on the About page keyboard-reachable - would cover the most ground.
How to read this. Each card explains what to change in plain language and shows a zoomed-in shot of any problem you can see on the page - red is high-impact, orange is minor. Structure issues like heading order have nothing to point at on screen, so they have no shot and are described in the text. Score is the Google Lighthouse accessibility score (0-100), the same scale Chrome and PageSpeed use.
About
A scrollable content area on this page cannot be reached with a keyboard, so keyboard-only users cannot read what is inside it; navigation sections also lack distinct labels, making screen reader navigation confusing.
What to change
- Make the scrollable panel reachable with the Tab key so keyboard users can scroll through its content.
- Give each navigation and content section its own distinct label so screen readers can tell them apart.
The other 5 pages we checked have no major accessibility barriers.
The high-impact items are the ones quietly costing you customers who cannot get through the page, and they are usually quick to fix once you know where they are. Happy to walk your team through any of this.