tryoutofoffice.com website review

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

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

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

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

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

8 third-party services load with your homepage (Unpkg, upstackified.com and Klaviyo and others), adding 741 KiB and 1.7 s of main-thread time.

Unpkg costs a phone 997 ms of main-thread work and 102 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.

2 images could be 160 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

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

upstackified.com costs a phone 369 ms of main-thread work and 129 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.

Klaviyo costs a phone 237 ms of main-thread work and 314 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,772 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

6 KiB could be saved by minifying CSS.

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.

2 KiB could be saved by minifying JavaScript.

Your largest element takes 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

26 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 105 ms to 120 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 1.2 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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 2.4 MB in 188 requests on a phone: scripts 845 KiB (81), images 714 KiB (18) and other files 590 KiB (53). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example s7-1_1_1920X.jpg at 1,200 px wide, shown at 187 px. Resized copies would save about 299 KiB.

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

1 image (194 KiB) is 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.

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

2 buttons have no accessible name, so screen readers announce just “button”.

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

13 tap targets are too small or too close together to hit reliably with a finger.

Elements must only use permitted ARIA attributes: 6 elements on the page fail this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 13 characters: “Out of Office”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 39 pages on tryoutofoffice.com and 2 external pages.

https://tryoutofoffice.com/policies/shipping-policy and https://tryoutofoffice.com/pages/shipping-policy all use the title “Shipping policy – Out of Office”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://tryoutofoffice.com/policies/shipping-policy, https://tryoutofoffice.com/products/out-of-office-drink, https://tryoutofoffice.com/products/nightcap-gummies, https://tryoutofoffice.com/pages/rewards, https://tryoutofoffice.com/blogs/out-of-office-blog and https://tryoutofoffice.com/pages/contact and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://tryoutofoffice.com/products/out-of-office-gummies and https://tryoutofoffice.com/products/out-of-office-oil-drops use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://tryoutofoffice.com/blogs/thc-education, whose canonical is https://tryoutofoffice.com/blogs/out-of-office-blog. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://tryoutofoffice.com/products/out-of-office-gummies, https://tryoutofoffice.com/products/out-of-office-drink, https://tryoutofoffice.com/pages/rewards and https://tryoutofoffice.com/pages/contact have no <h1> headline, so visitors and search engines get no clear main topic.

https://tryoutofoffice.com/pages/rewards 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.

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

4 errors were logged to the browser console while the page loaded, for example “Syntax error, unrecognized expression: .”.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

The homepage carries about 770 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Klaviyo (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 19 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 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.