Website review, no card needed

proofsyrup.com logo

proofsyrup.com website review

Visit site (opens in a new tab)Reviewed 11 November 202633 issues · 87 checks

This review found 33 issues worth fixing on proofsyrup.com, 6 of them high impact, across 87 checks. The most urgent: page weight: 4.9 MB in 301 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

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

How it loaded on a phone

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

Speed

9 to fix67
  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Clarity and loox.io and others), adding 1.5 MB and 1.0 s of main-thread time.

  • Improve image delivery

    1.1 MB

    16 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 67

    67/100

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

  • Reduce unused JavaScript

    663 KiB

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

  • Google Tag Manager adds 536 ms

    536 ms

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

  • Render-blocking requests

    450 ms

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

  • Main-thread work: 3.8 s

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

  • 2,784 HTML elements

    The page has 2,784 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • rechargecdn.com adds 89 ms

    89 ms

    rechargecdn.com costs a phone 89 ms of main-thread work and 297 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.

  • 9 long tasks on the main thread

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

  • Use efficient cache lifetimes

    202 KiB

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

  • Legacy JavaScript

    36 KiB

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

  • Minify JavaScript

    36 KiB

    36 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    16 KiB

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

    4 KiB

    4 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 13 ms

    13 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 22.4 s

    22.4 s

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

  • Largest Contentful Paint: 6.5 s

    6.5 s

    Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Friends gathered around a home bar at night listening to a …”.

  • Total Blocking Time: 371 ms

    371 ms

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

  • Speed Index: 3.6 s

    3.6 s

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

  • 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 130 ms to 131 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

    1.5 s

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

  • Real-user INP: 136 ms

    136 ms

    Real visitors wait 136 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 FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 631 ms

    631 ms

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

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

    -11%

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 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 fix70
  • Page weight: 4.9 MB in 301 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 301 requests on a phone: images 2.3 MB (72), scripts 1.6 MB (82) and other files 826 KiB (131). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.39 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.39 g of CO₂e: 167.4 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

7 to fixGoogle 8289
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

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

  • 61 images without alt text

    61 images have no alt text, which hurts accessibility and image search.

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

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

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

  • 2 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

1 checks passed
  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 7 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 9280
  • Title is long (74 characters)

    Your title is 74 characters, so Google will cut it off around 60: “All Natural Old Fashioned & Cocktail Bar Syrup | Proof Syrup · Proof Syrup”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Seconds away from a bar-quality Old Fashioned.” and “Seconds away from a bar-quality Old Fashioned.”). One clear main headline is easier for people and search engines.

  • Meta description is long (233 characters)

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

  • No social preview image

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

  • 133 internal links, 3 external

    The homepage links to 133 pages on proofsyrup.com and 3 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://proofsyrup.com/.

  • Structured data in place

    Structured data found: Organization, Store and WebSite.

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

AI search readiness

100
4 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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

3 to fix86
  • 5 pages share a title

    https://proofsyrup.com/blogs/recipes, https://proofsyrup.com/blogs/recipes/tagged/mood-style-smoky, https://proofsyrup.com/blogs/recipes/tagged/mood-style-spicy, https://proofsyrup.com/blogs/recipes/tagged/mood-style-sweet and https://proofsyrup.com/blogs/recipes/tagged/syrup-traditional all use the title “Cocktail Recipes - Proof Syrup · Proof Syrup”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 10 pages share a meta description

    https://proofsyrup.com/products/subscription-box, https://proofsyrup.com/a/store-locator/list, https://proofsyrup.com/products/subscription-box-pre-pay-every-3-months, https://proofsyrup.com/products/subscription-box-pre-pay-every-2-months and https://proofsyrup.com/products/subscription-box-per-year use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://proofsyrup.com/products/subscription-box, https://proofsyrup.com/products/subscription-box-pre-pay-every-3-months, https://proofsyrup.com/products/subscription-box-pre-pay-every-2-months and https://proofsyrup.com/products/subscription-box-per-year have 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 38 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.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 9687
  • 5 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • A 237-field form

    Your longest form asks for 237 fields (0 required). Every extra field lowers completion.

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

  • About 475 words of copy

    The homepage carries about 475 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 Traditional” and “Subscribe & Save on Syrups”.

  • 29 calls to action

    The homepage has 29 calls to action, for example “Subscribe now”, “WHERE TO BUY & TRY” and “Shop Syrups”.

  • Social proof on the page

    Social proof on the homepage: 2 testimonial or review blocks, a star rating and “6,700+ reviews”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

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

  • 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
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and LinkedIn Insight and 4 mores (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.

  • 25 cookies set on arrival

    25

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

  • 46 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on proofsyrup.com, including 13 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