Website review, no card needed

hattieb.com logo

hattieb.com website review

Visit site (opens in a new tab)Reviewed 23 October 202640 issues · 90 checks

This review found 40 issues worth fixing on hattieb.com, 12 of them high impact, across 90 checks. The most urgent: render-blocking requests. 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.8 s1.4 sJun 13Oct 171.5 s
Show as table
DateReal-visitor load time (LCP)
Jun 13, 20261.8 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.4 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
111 ms95 msJun 13Oct 17109 ms
Show as table
DateReal-visitor tap response (INP)
Jun 13, 2026101 ms
Jun 20, 202697 ms
Jun 27, 202697 ms
Jul 4, 202697 ms
Jul 11, 202697 ms
Jul 18, 202698 ms
Jul 25, 202697 ms
Aug 1, 202697 ms
Aug 8, 202698 ms
Aug 15, 202699 ms
Aug 22, 2026103 ms
Aug 29, 2026104 ms
Sep 5, 2026104 ms
Sep 12, 2026105 ms
Sep 19, 2026105 ms
Sep 26, 2026106 ms
Oct 3, 2026106 ms
Oct 10, 2026108 ms
Oct 17, 2026109 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 hattieb.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hattieb.com at 1.0 s1.0 s
  2. hattieb.com at 1.9 s1.9 s
  3. hattieb.com at 2.9 s2.9 s
  4. hattieb.com at 3.8 s3.8 s
  5. hattieb.com at 4.8 s4.8 s
  6. hattieb.com at 5.7 s5.7 s
  7. hattieb.com at 6.7 s6.7 s
  8. hattieb.com at 7.7 s7.7 s

Speed

12 to fix34
  • Render-blocking requests

    2.4 s

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.

  • typeform.com adds 1.7 s

    1.7 s

    typeform.com costs a phone 1.7 s of main-thread work and 1.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 34

    34/100

    Your mobile performance score is 34 (desktop: 60). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 6.5 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (typeform.com, Google Tag Manager and Facebook and others), adding 4.5 MB and 3.4 s of main-thread time.

  • Improve image delivery

    965 KiB

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

  • Reduce unused JavaScript

    880 KiB

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

  • Google Tag Manager adds 614 ms

    614 ms

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

  • 20 long tasks on the main thread

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

  • Use efficient cache lifetimes

    469 KiB

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

  • Facebook adds 425 ms

    425 ms

    Facebook costs a phone 425 ms of main-thread work and 310 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.

  • website-files.com adds 127 ms

    127 ms

    website-files.com costs a phone 127 ms of main-thread work and 1.9 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.

  • Reduce unused CSS

    150 ms · 26 KiB

    About 26 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

    12 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 60 but mobile only 34. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 22.5 s

    22.5 s

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

  • Total Blocking Time: 2.9 s

    2.9 s

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

  • Cumulative Layout Shift: 0.406

    0.406

    The layout shifts by 0.406 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Largest Contentful Paint: 3.8 s

    3.8 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Speed Index: 4.1 s

    4.1 s

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

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

    +10%

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

7 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: 1.4 s

    1.4 s

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

  • Real-user INP: 105 ms

    105 ms

    Real visitors wait 105 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.8 s

    0.8 s

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

  • Real-user TTFB: 425 ms

    425 ms

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

  • Largest content (LCP) got 16% faster for real visitors

    -16%

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

Images and page weight

3 to fix40
  • Page weight: 4.5 MB in 84 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 84 requests on a phone: scripts 2.4 MB (25), images 1.7 MB (28) and fonts 256 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    565 KiB

    2 images are downloaded at several times the size a phone draws them, for example 661808a2a413fb8af940d699_HBS-Web-Home-MerchHero.jpg at 4,330 px wide, shown at 390 px. Resized copies would save about 565 KiB.

  • 9 images in older formats

    9 images (1.1 MB) 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.3 g of CO₂ per visit

    1.29 g

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

1 checks passed
  • Images load when needed

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

Accessibility

8 to fixGoogle 8688
  • Frames without titles

    5 frames have no title, so screen-reader users cannot tell what they contain.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (61 elements)

    All page content should be contained by landmarks: 61 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.

  • 24 links without text

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

  • 10 form fields without a label

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

2 checks passed
  • Every image has alt text

    All 117 images in the HTML carry an alt attribute.

  • 32 automated accessibility rules passed

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

SEO

3 to fixGoogle 10085
  • Title is short (29 characters)

    Your title is only 29 characters: “Home | Hattie B's Hot Chicken”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 12 H1 headlines

    There are 12 <h1> headlines (“Slide 1”, “Slide 1” and “Slide 1”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 95 internal links, 330 external

    The homepage links to 95 pages on hattieb.com and 330 external pages.

5 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Nashville born, nationally loved. Hattie B's Hot Chicken serves authentic Nashville hot chicken across Tennessee, Georg…”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Restaurant.

  • 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://hattieb.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://hattieb.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.

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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

Other pages

100
  • 8 internal pages checked

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

7 checks passed
  • Linked pages load

    All 8 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 8 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

4 to fixGoogle 3583
  • 32 small tap targets

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

  • 3 third-party cookies

    3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://hattieb.com/' was loaded over HTTPS, but requested an insecure prefetch resource 'h…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix78
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

  • About 355 words of copy

    The homepage carries about 355 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP MERCH” and “CONTACT”.

  • 58 calls to action

    The homepage has 58 calls to action, for example “Contact”, “PR COntact” and “Shop Merch”.

  • 10 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

  • Opening hours shown

    Your opening hours are on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta 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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 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.

  • 16 other companies contacted

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

Upkeep, stack and company

Stack

CMS
Webflow
Analytics
Google Analytics

Company

Headquarters
Nashville

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on hattieb.com, including 18 speed issues, 3 SEO issues and 3 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