Website review, no card needed

frankwebb.com logo

frankwebb.com website review

Visit site (opens in a new tab)Reviewed 9 November 202638 issues · 89 checks

This review found 38 issues worth fixing on frankwebb.com, 10 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. 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
1.7 s1.5 sMay 23Nov 71.5 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.7 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.5 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Oct 24, 20261.5 s
Oct 31, 20261.5 s
Nov 7, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
107 ms94 msMay 23Nov 796 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202695 ms
May 30, 202695 ms
Jun 6, 202695 ms
Jun 13, 202696 ms
Jun 20, 2026100 ms
Jun 27, 2026101 ms
Jul 4, 2026102 ms
Jul 11, 2026105 ms
Jul 18, 2026102 ms
Jul 25, 2026103 ms
Aug 1, 2026102 ms
Aug 8, 202696 ms
Aug 15, 202696 ms
Aug 22, 202696 ms
Aug 29, 202698 ms
Sep 5, 2026102 ms
Sep 12, 2026104 ms
Sep 19, 2026105 ms
Sep 26, 2026102 ms
Oct 3, 2026104 ms
Oct 10, 2026101 ms
Oct 17, 202697 ms
Oct 24, 2026100 ms
Oct 31, 202696 ms
Nov 7, 202696 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 frankwebb.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. frankwebb.com at 1.0 s1.0 s
  2. frankwebb.com at 2.0 s2.0 s
  3. frankwebb.com at 3.0 s3.0 s
  4. frankwebb.com at 4.0 s4.0 s
  5. frankwebb.com at 5.0 s5.0 s
  6. frankwebb.com at 6.0 s6.0 s
  7. frankwebb.com at 7.0 s7.0 s
  8. frankwebb.com at 8.0 s8.0 s

Speed

9 to fix60
  • Reduce unused JavaScript

    1.2 s · 949 KiB

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

  • Use efficient cache lifetimes

    350 ms · 863 KiB

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

  • Mobile performance score: 60

    60/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google Maps and Klaviyo and others), adding 1.9 MB and 775 ms of main-thread time.

  • Render-blocking requests

    500 ms

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

  • Google Tag Manager adds 284 ms

    284 ms

    Google Tag Manager costs a phone 284 ms of main-thread work and 375 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.

  • Main-thread work: 2.9 s

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

  • Google Maps adds 158 ms

    158 ms

    Google Maps costs a phone 158 ms of main-thread work and 394 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.

  • Hawk Search adds 23 ms

    23 ms

    Hawk Search costs a phone 23 ms of main-thread work and 405 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.

  • 7 long tasks on the main thread

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

  • Minify JavaScript

    128 KiB

    128 KiB could be saved by minifying JavaScript.

  • Improve image delivery

    105 KiB

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

  • Legacy JavaScript

    65 KiB

    Polyfills for old browsers add 65 KiB JavaScript that modern phones do not need.

  • Reduce unused CSS

    62 KiB

    About 62 KiB of CSS is downloaded but never applied on this page.

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

  • Forced reflow

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

  • Duplicated JavaScript

    2 KiB

    2 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

8 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Time to Interactive: 20.6 s

    20.6 s

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

  • Speed Index: 8.3 s

    8.3 s

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

  • First Contentful Paint: 4.0 s

    4.0 s

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

  • Largest Contentful Paint: 4.0 s

    4.0 s

    Your largest element takes 4.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “At Frank Webb Home, we offer a large selection of the lates…”. Most of its time is element render delay (2.4 s).

  • Real-user CLS: 0.21

    0.21

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

  • Total Blocking Time: 464 ms

    464 ms

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

5 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user INP: 91 ms

    91 ms

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 689 ms

    689 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix81
  • Page weight: 3.4 MB in 208 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 208 requests on a phone: scripts 2.1 MB (70), other files 879 KiB (107) and images 271 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    FWW_Website_Middlebury-banner_500x125_01-26_400x.webp 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).

  • 2 images in older formats

    2 images (269 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 1.0 g of CO₂ per visit

    0.96 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

8 to fixGoogle 8890
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Hidden but focusable

    5 elements hidden from screen readers can still receive keyboard focus.

  • 5 text elements with low contrast

    5 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 (11 elements)

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

  • No main landmark

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • 9 form fields without a label

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

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

    Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.

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

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

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

4 to fixGoogle 8587
  • 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 long (176 characters)

    Your meta description is 176 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 7 links crawlers can't follow

    7 links have no real href, so search engines can't follow them.

  • 6 links with vague text

    6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 283 internal links, 4 external

    The homepage links to 283 pages on frankwebb.com and 4 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Start Your Project Off Right with Frank Webb Home”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Luxury Kitchen, Bath & Lighting Showrooms | Frank Webb Home”.

  • Canonical URL set

    The canonical URL is https://frankwebb.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://frankwebb.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,191 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://frankwebb.com/hearth, whose canonical is https://frankwebb.com/collections/category-heating-cooling-and-air-quality-fireplace-and-hearth-c3022. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://frankwebb.com/pages/contact-us has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8591
  • 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 ()”.

  • Pasting is blocked

    A form field blocks pasting, which frustrates password managers and people on phones.

2 checks passed
  • Tap targets are thumb-sized

    35 of 43 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

  • About 417 words of copy

    The homepage carries about 417 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “LEARN MORE” and “Contact”.

  • 19 calls to action

    The homepage has 19 calls to action, for example “schedule showroom consultation”, “Contact” and “Schedule aFree Consultation”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Klaviyo (measured from a US location before any click). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies (measured from a US location before any click).

  • 21 other companies contacted

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

1 checks passed
  • Consent tool: Termly

    A consent management tool (Termly) loads with the page.

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

1clickpopup · Advanced Wishlist · My Wishlist Share Remind · klaviyo.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

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Company

Founded
1999

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on frankwebb.com, including 17 speed issues, 4 SEO issues and 2 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