ten2midnightstudios.com website review

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

8 third-party services load with your homepage (Google CDN, Shopify and Klaviyo and others), adding 2.1 MB and 873 ms of main-thread time.

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

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

Google CDN costs a phone 412 ms of main-thread work and 743 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.

Shopify costs a phone 309 ms of main-thread work and 619 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 images could be 346 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

getgreenspark.com costs a phone 16 ms of main-thread work and 479 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 long tasks block the main thread while loading, the longest for 133 ms. During a long task the page ignores taps.

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

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

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

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

Visually, the page fills in at 4.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 15.3 MB in 378 requests on a phone: media 10.2 MB (1), images 1.6 MB (23) and scripts 1.6 MB (175). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Rainbow_Ornament_Grouping_4-min.jpg at 1,280 px wide, shown at 350 px. Resized copies would save about 42 KiB.

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

2 images (461 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.

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

Certain ARIA roles must be contained by particular parents: 3 elements on the page fail this check, rated critical by axe-core.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

1 image has 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.

7 visible links have no text or label, so screen readers cannot say where they go.

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your title is 90 characters, so Google will cut it off around 60: “Ten2Midnight Studios | Handcrafted Home Decor from Portland, OR – Ten2Midnight Studios LLC”.

There are 2 <h1> headlines (“Ten2Midnight Studios LLC” and “GIFTS THAT DELIGHT”). One clear main headline is easier for people and search engines.

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

1 link has no real href, so search engines can't follow it.

The homepage links to 220 pages on ten2midnightstudios.com and 6 external pages.

Your Organization JSON-LD is missing 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.

https://www.ten2midnightstudios.com/collections/light-keepers-votives, https://www.ten2midnightstudios.com/pages/gift-guide, https://www.ten2midnightstudios.com/pages/corporate-gifting, https://www.ten2midnightstudios.com/pages/bespoke-gifts, https://www.ten2midnightstudios.com/pages/custom-wedding-favors-and-decor and https://www.ten2midnightstudios.com/blogs/news and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.ten2midnightstudios.com/collections/suncatchers-window-hangings, https://www.ten2midnightstudios.com/collections/light-keepers-votives, https://www.ten2midnightstudios.com/pages/gift-guide, https://www.ten2midnightstudios.com/pages/corporate-gifting, https://www.ten2midnightstudios.com/pages/bespoke-gifts and https://www.ten2midnightstudios.com/blogs/news and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.ten2midnightstudios.com/products/ten2midnight-gift-card and https://www.ten2midnightstudios.com/pages/stockists took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 86 found) 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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 11 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Klaviyo, Meta Pixel and Pinterest Tag (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 13 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 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.