Website review, no card needed

warrenlotas.com logo

warrenlotas.com website review

Visit site (opens in a new tab)Reviewed 6 November 202633 issues · 83 checks

This review found 33 issues worth fixing on warrenlotas.com, 7 of them high impact, across 83 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
852 ms583 msMay 30Oct 31782 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 2026627 ms
Jun 6, 2026614 ms
Jun 13, 2026631 ms
Jun 20, 2026630 ms
Jun 27, 2026635 ms
Jul 4, 2026649 ms
Jul 11, 2026645 ms
Jul 18, 2026649 ms
Jul 25, 2026641 ms
Aug 1, 2026639 ms
Aug 8, 2026625 ms
Aug 15, 2026617 ms
Aug 22, 2026633 ms
Aug 29, 2026636 ms
Sep 5, 2026686 ms
Sep 12, 2026745 ms
Sep 26, 2026821 ms
Oct 3, 2026674 ms
Oct 10, 2026639 ms
Oct 17, 2026662 ms
Oct 24, 2026708 ms
Oct 31, 2026782 ms
Real-visitor tap response (INP)75th percentile, phones
91 ms57 msMay 30Oct 3187 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202662 ms
Jun 6, 202661 ms
Jun 13, 202662 ms
Jun 20, 202662 ms
Jun 27, 202662 ms
Jul 4, 202662 ms
Jul 11, 202662 ms
Jul 18, 202662 ms
Jul 25, 202662 ms
Aug 1, 202663 ms
Aug 8, 202663 ms
Aug 15, 202665 ms
Aug 22, 202665 ms
Aug 29, 202663 ms
Sep 5, 202666 ms
Sep 12, 202670 ms
Sep 26, 202679 ms
Oct 3, 202684 ms
Oct 10, 202687 ms
Oct 17, 202687 ms
Oct 24, 202687 ms
Oct 31, 202687 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of warrenlotas.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. warrenlotas.com at 0.4 s0.4 s
  2. warrenlotas.com at 0.8 s0.8 s
  3. warrenlotas.com at 1.1 s1.1 s
  4. warrenlotas.com at 1.5 s1.5 s
  5. warrenlotas.com at 1.9 s1.9 s
  6. warrenlotas.com at 2.3 s2.3 s
  7. warrenlotas.com at 2.6 s2.6 s
  8. warrenlotas.com at 3.0 s3.0 s

Speed

9 to fix64
  • Use efficient cache lifetimes

    3.9 s · 556 KiB

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

  • Reduce unused JavaScript

    3.1 s · 563 KiB

    About 563 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.

  • Mobile performance score: 64

    64/100

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

  • Avoid multiple page redirects

    901 ms

    The page goes through 1 redirect before it starts loading, costing about 901 ms. Link and advertise the final URL directly.

  • 8 third-party services on the page

    8 third-party services load with your homepage (route.com, rebuyengine.com and Klaviyo and others), adding 1.0 MB and 667 ms of main-thread time.

  • Render-blocking requests

    600 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 600 ms.

  • 2 long tasks on the main thread

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

  • route.com adds 386 ms

    386 ms

    route.com costs a phone 386 ms of main-thread work and 542 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.

  • rebuyengine.com adds 189 ms

    189 ms

    rebuyengine.com costs a phone 189 ms of main-thread work and 298 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.

  • Improve image delivery

    204 KiB

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

  • Reduce unused CSS

    150 ms · 47 KiB

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

  • Legacy JavaScript

    150 ms · 44 KiB

    Polyfills for old browsers add 44 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 856 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

    Your server sent the HTML in 4 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 12.1 s

    12.1 s

    Your largest element takes 12.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Stand For Something T-Shirt - White”.

  • Time to Interactive: 12.5 s

    12.5 s

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

  • Tap response (INP) got 41% slower for real visitors

    +41%

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

  • Largest content (LCP) got 20% slower for real visitors

    +20%

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

  • Total Blocking Time: 397 ms

    397 ms

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 0.8 s

    0.8 s

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

  • Real-user INP: 79 ms

    79 ms

    Real visitors wait 79 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.4 s

    0.4 s

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

  • Real-user TTFB: 376 ms

    376 ms

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

  • First Contentful Paint: 1.8 s

    1.8 s

    The first text or image appears after 1.8 s, inside the 1.8 s “good” threshold.

  • Speed Index: 3.3 s

    3.3 s

    Visually, the page fills in at 3.3 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 2.4 MB in 203 requests

    2.4 MB

    Your homepage downloads 2.4 MB in 203 requests on a phone: scripts 1.1 MB (76), other files 741 KiB (93) and images 413 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.69 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9392
  • 10 text elements with low contrast

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 30 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 30 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10074
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (12 characters)

    Your title is only 12 characters: “Warren Lotas”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is short (21 characters)

    Your meta description is only 21 characters: “BOSS COLLECTIONS ONLY”. 70 to 160 characters is enough to sell the click.

  • 13 internal links, 1 external

    The homepage links to 13 pages on warrenlotas.com and 1 external page.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.warrenlotas.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.warrenlotas.com/sitemap.xml.

AI search readiness

1 to fix83
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • llms.txt published

    The site publishes https://www.warrenlotas.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 5 pages without a meta description

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

  • 2 pages without an H1

    https://www.warrenlotas.com/collections/trophy-room and https://www.warrenlotas.com/collections/all have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 internal pages checked

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

5 checks passed
  • Linked pages load

    All 6 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 6 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 29 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix72
  • No social proof

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

  • Local business without LocalBusiness data

    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 detected

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

  • Only about 88 words

    The homepage has only about 88 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

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

  • No map or directions link

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

  • No risk reducer

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Sign up” and “GIFT SHOP”.

  • 1 call to action

    The homepage has 1 call to action, for example “Shop”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage, asking for an email.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Amplitude, Klaviyo, Meta Pixel and TikTok Pixel (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.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies, 1 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 22 other companies contacted

    Loading the homepage contacts 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at warrenlotas.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

chimpstatic.com · klaviyo.com · route.com · rebuyengine.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Los Angeles

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on warrenlotas.com, including 14 speed issues, 4 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25