Website review, no card needed

snapraise.com logo

snapraise.com website review

Visit site (opens in a new tab)Reviewed 18 November 202636 issues · 82 checks

This review found 36 issues worth fixing on snapraise.com, 12 of them high impact, across 82 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.3 s1.8 sMay 30Nov 142.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.0 s
Jun 6, 20261.9 s
Jun 13, 20262.0 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.8 s
Jul 11, 20261.9 s
Jul 18, 20262.0 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.0 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Oct 31, 20262.0 s
Nov 7, 20262.0 s
Nov 14, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
127 ms84 msMay 30Nov 14119 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202696 ms
Jun 6, 202689 ms
Jun 13, 2026104 ms
Jun 20, 2026103 ms
Jun 27, 2026104 ms
Jul 4, 2026111 ms
Jul 11, 2026105 ms
Jul 18, 2026117 ms
Jul 25, 2026114 ms
Aug 1, 2026122 ms
Aug 8, 2026113 ms
Aug 15, 2026111 ms
Aug 22, 2026114 ms
Aug 29, 2026106 ms
Sep 5, 2026112 ms
Sep 12, 2026114 ms
Sep 19, 2026108 ms
Sep 26, 2026116 ms
Oct 3, 2026117 ms
Oct 10, 2026114 ms
Oct 17, 2026118 ms
Oct 24, 2026112 ms
Oct 31, 2026111 ms
Nov 7, 2026113 ms
Nov 14, 2026119 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 snapraise.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. snapraise.com at 0.5 s0.5 s
  2. snapraise.com at 1.0 s1.0 s
  3. snapraise.com at 1.5 s1.5 s
  4. snapraise.com at 2.0 s2.0 s
  5. snapraise.com at 2.5 s2.5 s
  6. snapraise.com at 3.0 s3.0 s
  7. snapraise.com at 3.5 s3.5 s
  8. snapraise.com at 4.0 s4.0 s

Speed

7 to fix66
  • Use efficient cache lifetimes

    4.1 s · 20.2 MB

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

  • Render-blocking requests

    3.3 s

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

  • Improve image delivery

    1.5 s · 383 KiB

    8 images could be 383 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.

  • Mobile performance score: 66

    66/100

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

  • Reduce unused JavaScript

    450 ms · 115 KiB

    About 115 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Reduce unused CSS

    450 ms · 61 KiB

    About 61 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.

  • Main-thread work: 2.0 s

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (omappapi.com, Hubspot and Cloudflare CDN and others), adding 393 KiB and 202 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 30 KiB

    Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 6 long tasks on the main thread

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

  • Minify JavaScript

    6 KiB

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 3 ms

    3 ms

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

  • First Contentful Paint: 3.6 s

    3.6 s

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

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

    +25%

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • Time to Interactive: 7.3 s

    7.3 s

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

  • Speed Index: 5.0 s

    5.0 s

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

  • 11 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

5 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user INP: 114 ms

    114 ms

    Real visitors wait 114 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.

  • Total Blocking Time: 101 ms

    101 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix52
  • Page weight: 20.4 MB in 84 requests

    20.4 MB

    Your homepage downloads 20.4 MB in 84 requests on a phone: media 18.7 MB (2), images 977 KiB (17) and scripts 515 KiB (45). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    snap-raise-season-wishlist-1-690x642.jpg 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).

  • 7 images below the first screen load straight away

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

  • 6 images far larger than shown

    143 KiB

    6 images are downloaded at several times the size a phone draws them, for example SM1-Phone.png.webp at 1,172 px wide, shown at 350 px. Resized copies would save about 143 KiB.

  • 1 image in older formats

    1 image (59 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 5.8 g of CO₂ per visit

    5.78 g

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

Accessibility

3 to fixGoogle 9094
  • Links look like plain text

    6 links inside paragraphs rely on colour alone to stand out.

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

  • Orphan list items

    Some list items are not inside a list.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

3 to fixGoogle 9288
  • Title is short (26 characters)

    Your title is only 26 characters: “Snap! Raise | Snap! Mobile”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

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

  • 7 links with vague text

    7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 70 internal links, 24 external

    The homepage links to 70 pages on snapraise.com and 24 external pages.

6 checks passed
  • Meta description: 135 characters

    Your meta description is 135 characters: “Snap! Raise is the best online fundraising platform for schools and sports teams. Join 150,000+ groups who have raised …”.

  • One H1 headline

    Your main headline reads: “What’s on your program’s wishlist?”.

  • Canonical URL set

    The canonical URL is https://www.snapraise.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage 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://www.snapraise.com/sitemap.xml.

AI search readiness

1 to fix83
  • Parts of the site are closed to 4 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

3 checks passed
  • 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,566 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix73
  • 1 page points its canonical at the homepage

    https://snapraise.com/raise declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://snapraise.com/raise all use the title “Snap! Raise | Snap! Mobile”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://snapraise.com/early-access, https://snapraise.com/blog/tag/press-release, https://snapraise.com/blog, https://snapraise.com/partners, https://snapraise.com/connect-with-us and https://snapraise.com/partnerships and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://snapraise.com/connect-with-us has 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 29 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “The report-only Content Security Policy 'script-src 'self' 'unsafe-inline' https://snapraise.com; ' was delivered via a…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: “over 150,000 teams”. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • About 1,350 words of copy

    The homepage carries about 1,350 words of visible text.

6 checks passed
  • 12 calls to action

    The homepage has 12 calls to action, for example “Students! Start Here”, “Get Started” and “Get started with Snap! Raise”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • 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

  • 3 cookies set on arrival

    3

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

  • 7 other companies contacted

    Loading the homepage contacts 7 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 snapraise.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 Tag Manager
Hosting
AWS

Hiring

Hiring
164 open roles
Teams
North Sales (161), South Sales (1), West Sales (1)
Job board
greenhouse

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on snapraise.com, including 16 speed issues, 3 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