Website review, no card needed

hopdoddy.com logo

hopdoddy.com website review

Visit site (opens in a new tab)Reviewed 29 October 202634 issues · 77 checks

This review found 34 issues worth fixing on hopdoddy.com, 13 of them high impact, across 77 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
2.6 s2.1 sMay 9Oct 242.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.2 s
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.3 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.6 s
Jul 25, 20262.5 s
Aug 1, 20262.5 s
Aug 8, 20262.4 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Oct 24, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
135 ms98 msMay 9Oct 24130 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026102 ms
May 16, 2026103 ms
May 23, 2026104 ms
May 30, 2026103 ms
Jun 6, 2026103 ms
Jun 13, 2026104 ms
Jun 20, 2026103 ms
Jun 27, 2026104 ms
Jul 4, 2026104 ms
Jul 11, 2026104 ms
Jul 18, 2026104 ms
Jul 25, 2026105 ms
Aug 1, 2026105 ms
Aug 8, 2026106 ms
Aug 15, 2026112 ms
Aug 22, 2026118 ms
Aug 29, 2026123 ms
Sep 5, 2026129 ms
Sep 12, 2026130 ms
Sep 19, 2026129 ms
Sep 26, 2026129 ms
Oct 3, 2026130 ms
Oct 10, 2026130 ms
Oct 17, 2026131 ms
Oct 24, 2026130 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 hopdoddy.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hopdoddy.com at 1.4 s1.4 s
  2. hopdoddy.com at 2.8 s2.8 s
  3. hopdoddy.com at 4.2 s4.2 s
  4. hopdoddy.com at 5.5 s5.5 s
  5. hopdoddy.com at 6.9 s6.9 s
  6. hopdoddy.com at 8.3 s8.3 s
  7. hopdoddy.com at 9.7 s9.7 s
  8. hopdoddy.com at 11.1 s11.1 s

Speed

13 to fix31
  • Reduce unused JavaScript

    5.2 s · 1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.2 s faster on a phone.

  • Render-blocking requests

    5.5 s

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

  • Use efficient cache lifetimes

    2.9 s · 789 KiB

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

  • Mobile performance score: 31

    31/100

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

  • Main-thread work: 5.1 s

    A phone's processor spends 5.1 s on main-thread work while loading, 2.7 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 (Google Tag Manager, YouTube and cloudflarestream.com and others), adding 3.4 MB and 2.5 s of main-thread time.

  • Google Tag Manager adds 927 ms

    927 ms

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

  • YouTube adds 565 ms

    565 ms

    YouTube costs a phone 565 ms of main-thread work and 984 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.

  • Reduce unused CSS

    450 ms · 131 KiB

    About 131 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • cloudflarestream.com adds 380 ms

    380 ms

    cloudflarestream.com costs a phone 380 ms of main-thread work and 422 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 308 ms

    308 ms

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

  • 17 long tasks on the main thread

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

  • Google Maps adds 196 ms

    196 ms

    Google Maps costs a phone 196 ms of main-thread work and 393 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

    200 ms · 75 KiB

    3 images could be 75 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

  • 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
  • Server response: 1 ms

    1 ms

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

Core Web Vitals

9 to fix100
  • 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.

  • First Contentful Paint: 11.8 s

    11.8 s

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

  • Largest Contentful Paint: 19.6 s

    19.6 s

    Your largest element takes 19.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Close-up of cheeseburger with bacon, lettuce, onion, tomato…”.

  • Speed Index: 21.7 s

    21.7 s

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

  • Time to Interactive: 22.4 s

    22.4 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

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

    +27%

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • 12 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

5 checks passed
  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 120 ms

    120 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user TTFB: 744 ms

    744 ms

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

  • Cumulative Layout Shift: 0.008

    0.008

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

Images and page weight

2 to fix81
  • Page weight: 3.6 MB in 73 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 73 requests on a phone: scripts 2.7 MB (21), fonts 549 KiB (6) and images 179 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    69973fe53667d90310fbd39b_64d259c4aa5557cf5163a1290a54c2a1_ar 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).

  • About 1.0 g of CO₂ per visit

    1.01 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

1 to fixGoogle 9497
  • 1 text element with low contrast

    1 text element doesn'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.

2 checks passed
  • Every image has alt text

    All 20 images 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 31 WCAG 2.2 A/AA and best-practice rules on the phone render: 30 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10091
  • No structured data

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“what makes aBurgerworth it?” and “What HappensBeforeIt Hits Your Tray?”). One clear main headline is easier for people and search engines.

  • 22 internal links, 15 external

    The homepage links to 22 pages on hopdoddy.com and 15 external pages.

6 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Our kitchen runs on flavor and our craft is in the details. Better ingredients, precise temps, deep sears and a stack t…”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Hopdoddy Burger Bar | Fresh, Handmade Burgers”.

  • Canonical URL set

    The canonical URL is https://www.hopdoddy.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.hopdoddy.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.

  • No llms.txt

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

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

Other pages

100
  • 13 internal pages checked

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

7 checks passed
  • Linked pages load

    All 13 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 13 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 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 5 small tap targets

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

  • 5 third-party cookies

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

  • Browser-reported issues

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

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

3 to fix67
  • 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.

  • Only about 72 words

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

  • 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
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “START ORDER”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “START ORDER”, “Start Order” and “Contact”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 4 cookies set on arrival

    4

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

  • 25 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2023.

Stack

CMS
Webflow
Analytics
Google Tag Manager
Hosting
Webflow

Company

Founded
2010
Headquarters
Austin

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on hopdoddy.com, including 22 speed issues, 2 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