timetospa.com website review

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

Your mobile performance score is 81. Pages that score under 90 lose visitors before the first paint.

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

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

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

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

Shopify costs a phone 78 ms of main-thread work and 474 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.

8 third-party services load with your homepage (Cookiebot, bc0a.com and Shopify and others), adding 994 KiB and 471 ms of main-thread time.

About 197 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

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.

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

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

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

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

Your homepage downloads 3.3 MB in 283 requests on a phone: images 1.2 MB (41), scripts 1.0 MB (104) and other files 781 KiB (99). Under 2 MB keeps phones on slow connections fast.

1 image (127 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.94 g of CO₂e: 113.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

6 images have no alt text, which hurts accessibility and image search.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Alternative text of images should not be repeated as text: 16 elements on the page fail this check, rated minor by axe-core.

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

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

There are 2 <h1> headlines (“” and “Friends & Family Sale”). One clear main headline is easier for people and search engines.

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

The homepage links to 290 pages on timetospa.com and 12 external pages.

https://timetospa.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://timetospa.com/customer_authentication/redirect and https://timetospa.com/pages/good-feet-arch-support-insert are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://timetospa.com/collections/all, https://timetospa.com/customer_authentication/redirect and https://timetospa.com/pages/holiday-gift-shop have no meta description, so Google writes the search snippet from whatever text it finds.

https://timetospa.com/pages/elemis and https://timetospa.com/pages/jane-iredale-skincare-makeup use the same meta description. A description written for each page earns more clicks.

https://timetospa.com/customer_authentication/redirect and https://timetospa.com/pages/elemis have no <h1> headline, so visitors and search engines get no clear main topic.

https://timetospa.com/pages/kerastase, https://timetospa.com/pages/california-sun-glow, https://timetospa.com/pages/grown-alchemist-skincare, https://timetospa.com/pages/good-feet-arch-support-insert, https://timetospa.com/pages/holiday-gift-shop and https://timetospa.com/collections/skincare-cleansers and 2 others took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

Before a visitor clicks anything, the page loads Klaviyo (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 5 cookies, 1 of them by other companies (measured from a US location before any click).

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