Website review, no card needed

greenbooks.com logo

greenbooks.com website review

Visit site (opens in a new tab)Reviewed 16 November 202642 issues · 79 checks

This review found 42 issues worth fixing on greenbooks.com, 18 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. 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.9 s1.4 sMay 30Nov 141.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.3 s
Jun 27, 20262.5 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20262.8 s
Jul 25, 20262.4 s
Aug 1, 20262.1 s
Aug 8, 20262.0 s
Aug 15, 20262.1 s
Aug 22, 20262.0 s
Aug 29, 20262.3 s
Sep 5, 20262.2 s
Sep 12, 20262.0 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 31, 20261.8 s
Nov 7, 20261.9 s
Nov 14, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
162 ms97 msMay 30Oct 10144 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026110 ms
Jun 6, 2026113 ms
Jun 13, 2026113 ms
Jun 20, 2026113 ms
Jun 27, 2026107 ms
Jul 4, 2026104 ms
Jul 11, 2026104 ms
Jul 18, 2026112 ms
Jul 25, 2026115 ms
Aug 1, 2026129 ms
Aug 8, 2026138 ms
Aug 15, 2026138 ms
Aug 22, 2026138 ms
Aug 29, 2026144 ms
Sep 5, 2026146 ms
Sep 12, 2026144 ms
Sep 19, 2026144 ms
Sep 26, 2026154 ms
Oct 3, 2026144 ms
Oct 10, 2026144 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 greenbooks.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. greenbooks.com at 0.7 s0.7 s
  2. greenbooks.com at 1.3 s1.3 s
  3. greenbooks.com at 2.0 s2.0 s
  4. greenbooks.com at 2.7 s2.7 s
  5. greenbooks.com at 3.3 s3.3 s
  6. greenbooks.com at 4.0 s4.0 s
  7. greenbooks.com at 4.6 s4.6 s
  8. greenbooks.com at 5.3 s5.3 s

Speed

14 to fix25
  • Use efficient cache lifetimes

    3.0 s · 1.1 MB

    38 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

  • Reduce unused JavaScript

    2.4 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 2.4 s faster on a phone.

  • Render-blocking requests

    2.5 s

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

  • amaicdn.com adds 1.9 s

    1.9 s

    amaicdn.com costs a phone 1.9 s of main-thread work and 531 KiB 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.

  • Google Tag Manager adds 1.3 s

    1.3 s

    Google Tag Manager costs a phone 1.3 s of main-thread work and 1.1 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: 25

    25/100

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

  • Main-thread work: 9.7 s

    A phone's processor spends 9.7 s on main-thread work while loading, 6.2 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 (amaicdn.com, Google Tag Manager and Heroku and others), adding 12.3 MB and 4.6 s of main-thread time.

  • 20 long tasks on the main thread

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

  • Improve image delivery

    900 ms · 470 KiB

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

  • Reduce unused CSS

    640 ms · 115 KiB

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

  • Heroku adds 393 ms

    393 ms

    Heroku costs a phone 393 ms of main-thread work and 59 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.

  • Facebook adds 263 ms

    263 ms

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

  • Hotjar adds 250 ms

    250 ms

    Hotjar costs a phone 250 ms of main-thread work and 72 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.

  • Legacy JavaScript

    117 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Minify JavaScript

    10 KiB

    10 KiB could be saved by minifying JavaScript.

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

  • Duplicated JavaScript

    3 KiB

    3 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 6 ms

    6 ms

    Your server sent the HTML in 6 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.

  • Largest Contentful Paint: 16.9 s

    16.9 s

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

  • Total Blocking Time: 4.6 s

    4.6 s

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

  • Time to Interactive: 37.2 s

    37.2 s

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

  • First Contentful Paint: 6.5 s

    6.5 s

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

  • Speed Index: 13.3 s

    13.3 s

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

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

    +29%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 110 ms to 144 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.

  • 9 images without width and height

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

5 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • 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 TTFB: 447 ms

    447 ms

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

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

    -20%

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

  • 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: 23.3 MB in 348 requests

    23.3 MB

    Your homepage downloads 23.3 MB in 348 requests on a phone: media 17.2 MB (1), scripts 3.5 MB (123) and other files 845 KiB (141). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (218 KiB) is 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.

  • 2 images below the first screen load straight away

    2 images further down the page (248 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 6.6 g of CO₂ per visit

    6.62 g

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

6 to fixGoogle 9093
  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 form fields without a label

    5 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
  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 5 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 10079
  • Title is short (25 characters)

    Your title is only 25 characters: “Bushnell Golf Green Books”. 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.

  • 11 H1 headlines

    There are 11 <h1> headlines (“”, “Sign In” and “Insert your Account Information”). One clear main headline is easier for people and search engines.

  • Meta description is long (208 characters)

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

  • 19 internal links, 12 external

    The homepage links to 19 pages on greenbooks.com and 12 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://greenbooks.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://greenbooks.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 (527 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

100
  • 4 internal pages checked

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

1 checks passed
  • Linked pages load

    All 4 pages we checked loaded without an error.

Best practices

4 to fixGoogle 7770
  • 3 broken images

    3 images failed to load on a phone, for example https://greenbooks.com/#.

  • 3 small tap targets

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

  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs 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 “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 34 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 315 words of copy

    The homepage carries about 315 words of visible text.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Register Here” and “CONTACT US”.

  • 4 short forms

    4 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Hotjar and LinkedIn Insight.

Privacy and tracking

  • 10 trackers load before any consent

    10

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

  • 34 cookies set on arrival

    34

    Opening the homepage sets 34 cookies, 5 of them by other companies (measured from a US location before any click).

  • 51 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 greenbooks.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 11 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Eg Auto Add To Cart · Pagefly Ai Page Builder · Klaviyo Email Marketing Sms · Product Upsell · Stack Discounts Pro · Freegifts · rise-ai.com · carecart.io · boldapps.net · bogos.io · nice-team.net

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
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Hotjar
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on greenbooks.com, including 23 speed issues, 4 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