tempositions.com website review

28 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.

30 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.2 s.

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

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

7 third-party services load with your homepage (Google Tag Manager, Vimeo and datagrail.io and others), adding 13.1 MB and 415 ms of main-thread time.

Vimeo costs a phone 110 ms of main-thread work and 12.5 MB 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 files are served with short cache lifetimes, so returning visitors download them again (134 KiB).

About 70 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

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

7 KiB could be saved by minifying JavaScript.

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.

5 KiB could be saved by minifying CSS.

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.76 (75th percentile). Good is under 0.1.

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

Your largest element takes 21.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “OUR BRANDS LEARN MORE CONTACT US LOGIN TOP 1% OF U.S. STAFF…”.

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

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

The layout shifts by 0.517 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

Your homepage downloads 16.3 MB in 126 requests on a phone: other files 12.0 MB (13), images 2.8 MB (43) and scripts 1.2 MB (38). Under 2 MB keeps phones on slow connections fast.

16 images are downloaded at several times the size a phone draws them, for example talent-10.png at 1,377 px wide, shown at 37 px. Resized copies would save about 1.7 MB.

22 images further down the page (2.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

The homepage links to 77 pages on tempositions.com and 54 external pages.

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.

/our-locations and /privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Cookie”).

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

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

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

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 8 cookies, 2 of them by other companies (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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.