thiscandleislit.com website review

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.3 s faster on a phone.

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

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

8 third-party services load with your homepage (Google CDN, commoninja.com and Shopify and others), adding 3.1 MB and 1.9 s of main-thread time.

11 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).

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

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

commoninja.com costs a phone 403 ms of main-thread work and 1.2 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.

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

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

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

16 long tasks block the main thread while loading, the longest for 196 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).

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 first text or image appears after 9.8 s on a phone. Good is under 1.8 s.

Your largest element takes 18.3 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 31.0 s. Good is under 3.8 s.

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

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

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

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 7.4 MB in 278 requests on a phone: images 2.9 MB (25), scripts 2.6 MB (81) and other files 1.5 MB (131). Under 2 MB keeps phones on slow connections fast.

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

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

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is only 18 characters: “This Candle is Lit”. Between 30 and 65 characters leaves room to say what you do and for whom.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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 33 pages on thiscandleislit.com and 5 external pages.

Your homepage links to https://thiscandleislit.com/products/fire-cracker-copy and https://thiscandleislit.com/pages/candlebar, which answer with an error. Visitors hit a dead end and search engines drop them.

https://thiscandleislit.com/collections/decor, https://thiscandleislit.com/collections/workshop, https://thiscandleislit.com/collections, https://thiscandleislit.com/policies/terms-of-service and https://thiscandleislit.com/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://thiscandleislit.com/products/state-of-mind-cry-baby and https://thiscandleislit.com/products/state-of-mind-cry-baby-copy use the same meta description. A description written for each page earns more clicks.

https://thiscandleislit.com/collections/decor and https://thiscandleislit.com/collections/workshop have no <h1> headline, so visitors and search engines get no clear main topic.

https://thiscandleislit.com/pages/wholesale, https://thiscandleislit.com/pages/contact-us, https://thiscandleislit.com/collections, https://thiscandleislit.com/pages/featured and https://thiscandleislit.com/policies/refund-policy have 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 15 pages linked from your homepage and read each the way a search engine does.

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

2 errors were logged to the browser console while the page loaded, for example “Uncaught ReferenceError: jdgmSettings is not defined”.

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

Social proof on the homepage: 1 testimonial or review block. 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.

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 154 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, 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 12 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 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.