lamose.com website review

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

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

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

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

1 long task block the main thread while loading, the longest for 67 ms. During a long task the page ignores taps.

4 third-party services load with your homepage (Cloudflare, Google Tag Manager and supabase.co and others), adding 303 KiB and 11 ms of main-thread time.

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

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.

Real visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.

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

Real visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

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

12 images are downloaded at several times the size a phone draws them, for example lamose-fun-name-tag-human-firewall-funny-engraved-name-tag.a at 1,200 px wide, shown at 144 px. Resized copies would save about 649 KiB.

Your homepage downloads 2.4 MB in 135 requests on a phone: images 1.7 MB (90), scripts 454 KiB (19) and fonts 119 KiB (3). Under 2 MB keeps phones on slow connections fast.

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

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

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

All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

Elements with visible text labels do not have matching accessible names. (8 elements).

The homepage links to 142 pages on lamose.com and 0 external pages.

Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

robots.txt blocks GPTBot, ClaudeBot and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

/ and https://lamose.com/collections/sport-gift-sets all use the title “LAMOSE — Engraved Tumblers & Name Badges from Calgary, Canada”. Search engines can't tell which page to show for a search, so each competes with the others.

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

Chrome logged issues while loading the page (“Content security policy”).

Large scripts ship without source maps.

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 1,171 words of visible text.

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