tobaccolocker.com website review

27 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

7 third-party services load with your homepage (Shopify, trustedsite.com and CyberSource (Visa) and others), adding 6.1 MB and 76 ms of main-thread time.

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

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

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

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

About 101 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

3 long tasks block the main thread while loading, the longest for 93 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 22 KiB JavaScript that modern phones do not need.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 77 ms to 69 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.3 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.0 MB in 267 requests on a phone: media 3.6 MB (2), images 2.8 MB (57) and other files 956 KiB (133). Under 2 MB keeps phones on slow connections fast.

Tobacco_Locker.svg weighs 833 KiB. On a phone connection a single image that size takes seconds.

15 images are downloaded at several times the size a phone draws them, for example new-world.jpg at 1,024 px wide, shown at 171 px. Resized copies would save about 1.1 MB.

big_list_of_cigars.jpg 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 further down the page (33 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 2.27 g of CO₂e: 272.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 contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

Headings skip levels (h3 → h6, h3 → h6 and 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).

Your title is only 14 characters: “Tobacco Locker”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“Premium & Limited Edition Cigars Check out our se…” and “Cart”). One clear main headline is easier for people and search engines.

The homepage links to 210 pages on tobaccolocker.com and 3 external pages.

Your Organization JSON-LD is missing logo, 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://tobaccolocker.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://tobaccolocker.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://tobaccolocker.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://tobaccolocker.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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.

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

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