thinkshiftinc.com website review

4 images could be 533 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.

About 331 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

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

Your mobile performance score is 53 (desktop: 75). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Cookiebot and others), adding 1.0 MB and 894 ms of main-thread time.

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

Google Tag Manager costs a phone 438 ms of main-thread work and 531 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.

Facebook costs a phone 262 ms of main-thread work and 220 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.

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

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

Polyfills for old browsers add 12 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.

Your largest element takes 13.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ABOUT US We are a full-service marketing agency that enable…”.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 10.2 MB in 74 requests on a phone: media 8.3 MB (1), scripts 1.0 MB (18) and images 790 KiB (28). Under 2 MB keeps phones on slow connections fast.

4 images further down the page (661 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images (506 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

3 images are downloaded at several times the size a phone draws them, for example alberta-beef-producers-featured-image.jpg at 1,450 px wide, shown at 350 px. Resized copies would save about 221 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 2.88 g of CO₂e: 345.6 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: 1 element on the page fails this check, rated moderate by axe-core.

Structured data found (BreadcrumbList, Organization and WebPage) but with 2 problems, for example “Organization: missing name”.

The homepage links to 25 pages on thinkshiftinc.com and 3 external pages.

Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/contact, /our-work/pioneer-100, /blog/the-multiplication-effect-when-marketing-math-becomes-magic, /blog/from-campaigns-to-capital-rethinking-how-we-invest-our-marketing-dollars, /subscribe-to-our-newsletter and /privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

/contact and /subscribe-to-our-newsletter have 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.

We fetched 12 pages linked from your homepage and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 48 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 350 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 2 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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