timberdoodle.com website review

A phone's processor spends 22.5 s on main-thread work while loading, 11.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Google Tag Manager costs a phone 1.2 s of main-thread work and 331 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Shopify and others), adding 845 KiB and 2.9 s of main-thread time.

About 408 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

20 long tasks block the main thread while loading, the longest for 890 ms. During a long task the page ignores taps.

Facebook costs a phone 842 ms of main-thread work and 225 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Shopify costs a phone 277 ms of main-thread work and 40 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

The page has 1,805 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

7 files are served with short cache lifetimes, so returning visitors download them again (240 KiB).

4 images could be 63 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 26 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

For real visitors the layout shifts by 0.30 (75th percentile). Good is under 0.1.

Scripts block taps and scrolling for 8.7 s in total while the page loads. Good is under 200 ms.

The page becomes fully interactive after 20.3 s. Good is under 3.8 s.

Visually, the page fills in at 12.0 s (Speed Index). Good is under 3.4 s.

Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “We Do the Research. You Do the Teaching.”.

Real visitors wait 205 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.

Real visitors wait 901 ms for your server to start answering (75th percentile). Good is under 800 ms.

The first text or image appears after 2.0 s on a phone. Good is under 1.8 s.

10 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 183 ms to 179 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.7 MB in 241 requests on a phone: scripts 1.5 MB (158), images 717 KiB (42) and other files 327 KiB (32). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.77 g of CO₂e: 91.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Your meta description is 162 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 95 pages on timberdoodle.com and 8 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

https://timberdoodle.com/gift-guide, https://timberdoodle.com/wishlist and https://timberdoodle.com/schedule have no <h1> headline, so visitors and search engines get no clear main topic.

https://timberdoodle.com/wishlist has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://timberdoodle.com/free-shipping and https://timberdoodle.com/wishlist took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 59 found) and read each the way a search engine does.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 images are served at too low a resolution for sharp phone screens.

Large scripts ship without source maps.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,245 words of visible text.

Opening the homepage sets 3 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.