Website review, no card needed
giveandgo.com website review
Visit site (opens in a new tab)Reviewed 1 November 202638 issues · 79 checks
This review found 38 issues worth fixing on giveandgo.com, 15 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.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.4 s |
| May 16, 2026 | 4.3 s |
| May 23, 2026 | 4.4 s |
| May 30, 2026 | 4.2 s |
| Jun 6, 2026 | 4.0 s |
| Jun 13, 2026 | 4.1 s |
| Jun 20, 2026 | 4.1 s |
| Jun 27, 2026 | 4.2 s |
| Jul 4, 2026 | 4.3 s |
| Jul 11, 2026 | 4.4 s |
| Jul 18, 2026 | 4.4 s |
| Jul 25, 2026 | 4.3 s |
| Aug 1, 2026 | 4.0 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.5 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.3 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.6 s |
| Sep 26, 2026 | 3.8 s |
| Oct 3, 2026 | 3.7 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 3.5 s |
| Oct 24, 2026 | 3.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 112 ms |
| May 16, 2026 | 112 ms |
| May 23, 2026 | 111 ms |
| May 30, 2026 | 111 ms |
| Jun 6, 2026 | 110 ms |
| Jun 13, 2026 | 109 ms |
| Jun 20, 2026 | 112 ms |
| Jun 27, 2026 | 116 ms |
| Jul 4, 2026 | 118 ms |
| Jul 11, 2026 | 121 ms |
| Jul 18, 2026 | 120 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 112 ms |
| Aug 8, 2026 | 112 ms |
| Aug 15, 2026 | 111 ms |
| Aug 22, 2026 | 109 ms |
| Aug 29, 2026 | 108 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 105 ms |
| Sep 19, 2026 | 110 ms |
| Sep 26, 2026 | 117 ms |
| Oct 3, 2026 | 114 ms |
| Oct 10, 2026 | 112 ms |
| Oct 17, 2026 | 109 ms |
| Oct 24, 2026 | 104 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
Speed
Use efficient cache lifetimes
1.3 s · 3.7 MB133 files are served with short cache lifetimes, so returning visitors download them again (3.7 MB).
Reduce unused JavaScript
4.3 s · 537 KiBAbout 537 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.3 s faster on a phone.
Render-blocking requests
4.6 s43 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.6 s.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
800 ms · 130 KiBAbout 130 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 800 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and Clarity and others), adding 1.3 MB and 795 ms of main-thread time.
Improve image delivery
579 KiB9 images could be 579 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google CDN adds 345 ms
345 msGoogle CDN costs a phone 345 ms of main-thread work and 734 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.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,634 HTML elements
The page has 1,634 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify JavaScript
150 ms · 8 KiB8 KiB could be saved by minifying JavaScript.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 120 ms. During a long task the page ignores taps.
Legacy JavaScript
16 KiBPolyfills for old browsers add 16 KiB JavaScript that modern phones do not need.
Minify CSS
12 KiB12 KiB could be saved by minifying CSS.
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: 271 ms
271 msYour server sent the HTML in 271 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user FCP: 3.3 s
3.3 sReal visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.2 s
2.2 sReal visitors wait 2.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 21.5 s
21.5 sYour largest element takes 21.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We and our partners use cookies on this website for differe…”.
Time to Interactive: 22.5 s
22.5 sThe page becomes fully interactive after 22.5 s. Good is under 3.8 s.
Speed Index: 12.3 s
12.3 sVisually, the page fills in at 12.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.6 s
3.6 sReal visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Total Blocking Time: 266 ms
266 msScripts block taps and scrolling for 266 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 112 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 98 ms
98 msReal visitors wait 98 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Largest content (LCP) got 22% faster for real visitors
-22%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.4 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.4 MB in 190 requests
5.4 MBYour homepage downloads 5.4 MB in 190 requests on a phone: images 3.4 MB (99), scripts 1.3 MB (36) and other files 357 KiB (13). Under 2 MB keeps phones on slow connections fast.
7 images in older formats
7 images (1.0 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.5 g of CO₂ per visit
1.54 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.54 g of CO₂e: 184.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
16 images without alt text
16 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4, h3 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 2 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (20 characters)
Your title is only 20 characters: “Homepage - Give & Go”. Between 30 and 65 characters leaves room to say what you do and for whom.
6 H1 headlines
There are 6 <h1> headlines (“Baked with love to makeyou go wow!”, “Give & Go is excited to be joining the” and “Mondelez International Family”). One clear main headline is easier for people and search engines.
Meta description is long (302 characters)
Your meta description is 302 characters; Google truncates after about 160, so the end of your pitch is cut.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
25 internal links, 4 external
The homepage links to 25 pages on giveandgo.com and 4 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://giveandgo.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
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://giveandgo.com/sitemap.xml.
AI search readiness
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 description; sameAs (social profiles) and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (7,891 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://giveandgo.com/llms.txt (45 KiB, 123 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://giveandgo.com/project-truehue and https://giveandgo.com/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages without an H1
https://giveandgo.com/careers, https://giveandgo.com/project-truehue, https://giveandgo.com/privacy-policy, https://giveandgo.com/accessibility, https://giveandgo.com/privacy-officer and https://giveandgo.com/candidate-data-privacy and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
14 internal pages checked
We fetched 14 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 14 pages we checked loaded without an error.
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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
10 broken images
10 images failed to load on a phone, for example https://unclewallys.giveandgolabs.com/wp-content/uploads/2015/07/BANANA-NUT.jpg.
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.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Uncaught ReferenceError: Popper is not defined”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 213 words
The homepage has only about 213 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: “Learn More”.
5 calls to action
The homepage has 5 calls to action, for example “Contact Us”, “Learn More” and “Join Our Team”.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Microsoft Clarity (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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
15 other companies contacted
Loading the homepage contacts 15 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 giveandgo.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
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Microsoft Clarity
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on giveandgo.com, including 19 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.