Website review, no card needed

getting-goods.com logo

getting-goods.com website review

Visit site (opens in a new tab)Reviewed 11 October 202623 issues · 69 checks

This review found 23 issues worth fixing on getting-goods.com, 10 of them high impact, across 69 checks. The most urgent: improve image delivery. 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.3 s1.2 sAug 1Oct 31.2 s
Show as table
DateReal-visitor load time (LCP)
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
96 ms77 msAug 1Oct 379 ms
Show as table
DateReal-visitor tap response (INP)
Aug 1, 202694 ms
Aug 8, 202692 ms
Aug 15, 202691 ms
Aug 22, 202690 ms
Aug 29, 202689 ms
Sep 5, 202688 ms
Sep 12, 202686 ms
Sep 19, 202684 ms
Sep 26, 202682 ms
Oct 3, 202679 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 getting-goods.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix67
  • Improve image delivery

    2.3 s · 446 KiB

    1 image could be 446 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.3 s faster on a phone.

  • Use efficient cache lifetimes

    1.9 s · 396 KiB

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

  • Mobile performance score: 67

    67/100

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

  • noodledit.com adds 0 ms

    0 ms

    noodledit.com costs a phone 0 ms of main-thread work and 582 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.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Fonts and noodledit.com), adding 607 KiB and 0 ms of main-thread time.

  • Document request latency

    10 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

2 checks passed
  • Main-thread work: 0.1 s

    A phone's processor spends 0.1 s on main-thread work while loading, 4 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 4.7 s

    4.7 s

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

  • Cumulative Layout Shift: 0.305

    0.305

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

  • Time to Interactive: 4.7 s

    4.7 s

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • 2 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -7%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.2 s 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.1 s

    1.1 s

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

  • Real-user INP: 78 ms

    78 ms

    Real visitors wait 78 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.9 s

    0.9 s

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

  • Real-user TTFB: 466 ms

    466 ms

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

  • Tap response (INP) got 13% faster for real visitors

    -13%

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

  • Speed Index: 1.8 s

    1.8 s

    Visually, the page fills in at 1.8 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix75
  • 1 image over 500 KB

    mob_lp_gg.jpg weighs 531 KiB. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (531 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.

  • About 0.2 g of CO₂ per visit

    0.17 g

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

3 checks passed
  • Page weight: 622 KiB in 9 requests

    622 KiB

    Your homepage downloads 622 KiB in 9 requests on a phone: images 582 KiB (5), fonts 25 KiB (3) and HTML 15 KiB (1). That is a lean page.

  • 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

1 to fixGoogle 9597
  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

2 checks passed
  • Every image has alt text

    All 2 images in the HTML carry an alt attribute.

  • 33 automated accessibility rules passed

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

SEO

2 to fixGoogle 10092
  • No structured data

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

  • No XML sitemap

    No XML sitemap at https://getting-goods.com/sitemap.xml, so Google discovers your pages only by following links.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 18 internal links, 2 external

    The homepage links to 18 pages on getting-goods.com and 2 external pages.

5 checks passed
  • Meta description: 86 characters

    Your meta description is 86 characters: “A free reader resource about earning digital rewards, gift cards, and cashback online.”.

  • One H1 headline

    Your main headline reads: “Try Something New. Earn Something Real.”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “GetnGoods — Honest Ways People Earn Rewards Online”.

  • Canonical URL set

    The canonical URL is https://getting-goods.com/.

  • robots.txt in place

    robots.txt is in place.

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 (370 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://getting-goods.com/llms.txt (1 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix55
  • 1 linked page is broken

    Your homepage links to https://getting-goods.com/unsubscribe, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 page without a title

    https://getting-goods.com/p/rewards-program-requirements has no <title>, so Google invents the link text in results.

  • 2 pages without a meta description

    https://getting-goods.com/p/rewards-privacy-policy and https://getting-goods.com/p/rewards-program-requirements have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 internal pages checked

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

4 checks passed
  • Canonical URLs point to themselves

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

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

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • 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.

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 206 words

    The homepage has only about 206 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.

2 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact Us”.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

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

  • 2 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 getting-goods.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 23 issues on getting-goods.com, including 9 speed issues, 2 SEO issues and 5 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