timebeing.store website review

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

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

About 134 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.

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

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

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

51 KiB could be saved by minifying JavaScript.

5 third-party services load with your homepage (Shopify, Cloudflare CDN and shop.app and others), adding 305 KiB and 458 ms of main-thread time.

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

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.

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

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 8.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Slide image”.

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

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

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

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

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

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

mobile-banner.png weighs 543 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 2.2 MB in 183 requests on a phone: images 881 KiB (15), other files 703 KiB (85) and scripts 433 KiB (50). Under 2 MB keeps phones on slow connections fast.

mobile-banner.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example mobile-banner.png at 1,440 px wide, shown at 390 px. Resized copies would save about 185 KiB.

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

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

Your title is only 24 characters: “TIME BEING™ – Time Being”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 60 characters: “TIME BEING™ by Jenn McAllister | Los Angeles, CA - Shop Now!”. 70 to 160 characters is enough to sell the click.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Your <h1> is empty.

The homepage links to 30 pages on timebeing.store and 10 external pages.

https://www.timebeing.shop/collections/all, https://www.timebeing.shop/pages/contact, https://www.timebeing.shop/policies/privacy-policy, https://www.timebeing.shop/policies/shipping-policy, https://www.timebeing.shop/policies/terms-of-service and https://www.timebeing.shop/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.timebeing.shop/pages/contact has no <h1> headline, so visitors and search engines get no clear main topic.

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

4 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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 has only about 101 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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