Website review, no card needed

ronherman.com logo

ronherman.com website review

Visit site (opens in a new tab)Reviewed 10 November 202626 issues · 55 checks

This review found 26 issues worth fixing on ronherman.com, 5 of them high impact, across 55 checks. The most urgent: no call to action on the first screen. 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

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

How it loaded on a phone

  1. ronherman.com at 0.5 s0.5 s
  2. ronherman.com at 1.0 s1.0 s
  3. ronherman.com at 1.4 s1.4 s
  4. ronherman.com at 1.9 s1.9 s
  5. ronherman.com at 2.4 s2.4 s
  6. ronherman.com at 2.9 s2.9 s
  7. ronherman.com at 3.4 s3.4 s
  8. ronherman.com at 3.9 s3.9 s

Speed

2 to fix77
  • Mobile performance score: 77

    77/100

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

  • Reduce unused JavaScript

    450 ms · 72 KiB

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

  • Use efficient cache lifetimes

    216 KiB

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

  • Render-blocking requests

    150 ms

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Cloudflare CDN and Google Fonts and others), adding 218 KiB and 119 ms of main-thread time.

  • Improve image delivery

    120 KiB

    1 image could be 120 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 2 long tasks on the main thread

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

  • 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.

1 checks passed
  • Main-thread work: 0.2 s

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

Core Web Vitals

4 to fix82
  • Speed Index: 6.1 s

    6.1 s

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

  • Largest Contentful Paint: 4.1 s

    4.1 s

    Your largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Ron Herman”.

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Time to Interactive: 4.1 s

    4.1 s

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

  • Not enough real-visitor data yet

    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.

2 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 37 ms

    37 ms

    Scripts block the page for only 37 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix90
  • 1 image far larger than shown

    82 KiB

    1 image is downloaded at several times the size a phone draws it, for example waikiki_main.webp at 1,500 px wide, shown at 390 px. Resized copies would save about 82 KiB.

  • About 0.1 g of CO₂ per visit

    0.12 g

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

3 checks passed
  • Page weight: 436 KiB in 11 requests

    436 KiB

    Your homepage downloads 436 KiB in 11 requests on a phone: images 213 KiB (2), scripts 180 KiB (2) and fonts 34 KiB (1). That is a lean page.

  • 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.

Accessibility

Google 100100
2 checks passed
  • Every image has alt text

    All 2 images in the HTML carry an alt attribute.

  • 26 automated accessibility rules passed

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

SEO

10 to fixGoogle 10060
  • Title is short (23 characters)

    Your title is only 23 characters: “Ron Herman | Since 1976”. 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 (49 characters)

    Your meta description is only 49 characters: “Shop LA's Iconic California Lifestyle Boutique...”. 70 to 160 characters is enough to sell the click.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

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

  • No XML sitemap

    No XML sitemap at https://ronherman.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at ronherman.com/robots.txt, the first file search crawlers ask for.

  • Only 2 internal links

    The homepage links to only 2 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • One H1 headline

    Your <h1> is empty.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

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.

  • No llms.txt

    There is no https://ronherman.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

1 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Best practices

2 to fixGoogle 10087
  • 3 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • No call to action on the first screen

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

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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.

  • Only about 52 words

    The homepage has only about 52 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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.

3 checks passed
  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    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.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies (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.

  • 6 other companies contacted

    Loading the homepage contacts 6 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 ronherman.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Plus;Tabarnapp
Analytics
Google Analytics
Hosting
KDDI Web Communications Inc.

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 26 issues on ronherman.com, including 6 speed issues, 10 SEO issues and 5 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