Website review, no card needed

squirrelforum.com logo

squirrelforum.com website review

Visit site (opens in a new tab)Reviewed 12 November 202626 issues · 65 checks

This review found 26 issues worth fixing on squirrelforum.com, 4 of them high impact, across 65 checks. The most urgent: fails Core Web Vitals for real visitors. 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.8 s2.0 sMay 23Nov 72.2 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.4 s
May 30, 20262.1 s
Jun 6, 20262.2 s
Jun 13, 20262.5 s
Jun 20, 20262.6 s
Jun 27, 20262.7 s
Jul 4, 20262.7 s
Jul 11, 20262.6 s
Jul 18, 20262.5 s
Jul 25, 20262.4 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.1 s
Aug 22, 20262.3 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.4 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Oct 24, 20262.6 s
Oct 31, 20262.4 s
Nov 7, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
102 ms68 msMay 23Nov 798 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202679 ms
May 30, 202679 ms
Jun 6, 202682 ms
Jun 13, 202679 ms
Jun 20, 202677 ms
Jun 27, 202675 ms
Jul 4, 202677 ms
Jul 11, 202675 ms
Jul 18, 202672 ms
Jul 25, 202675 ms
Aug 1, 202675 ms
Aug 8, 202678 ms
Aug 15, 202681 ms
Aug 22, 202681 ms
Aug 29, 202682 ms
Sep 5, 202688 ms
Sep 12, 202679 ms
Sep 19, 202689 ms
Sep 26, 202685 ms
Oct 3, 202690 ms
Oct 10, 202690 ms
Oct 17, 202679 ms
Oct 24, 202680 ms
Oct 31, 202691 ms
Nov 7, 202698 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 squirrelforum.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. squirrelforum.com at 0.6 s0.6 s
  2. squirrelforum.com at 1.2 s1.2 s
  3. squirrelforum.com at 1.8 s1.8 s
  4. squirrelforum.com at 2.4 s2.4 s
  5. squirrelforum.com at 3.0 s3.0 s
  6. squirrelforum.com at 3.6 s3.6 s
  7. squirrelforum.com at 4.2 s4.2 s
  8. squirrelforum.com at 4.8 s4.8 s

Speed

6 to fix82
  • Mobile performance score: 82

    82/100

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

  • Reduce unused JavaScript

    150 ms · 547 KiB

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

  • Use efficient cache lifetimes

    150 ms · 325 KiB

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

  • Render-blocking requests

    450 ms

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (YouTube, Other Google APIs/SDKs and WordPress Site Stats and others), adding 1.2 MB and 290 ms of main-thread time.

  • YouTube adds 282 ms

    282 ms

    YouTube costs a phone 282 ms of main-thread work and 992 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.

  • Reduce unused CSS

    150 ms · 142 KiB

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

  • Minify CSS

    150 ms · 7 KiB

    7 KiB could be saved by minifying CSS.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 101 ms. During a long task the page ignores taps.

  • Font display

    100 ms

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

  • Improve image delivery

    76 KiB

    1 image could be 76 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    16 KiB

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

  • Minify JavaScript

    9 KiB

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

2 checks passed
  • Main-thread work: 0.8 s

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

  • Server response: 501 ms

    501 ms

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

Core Web Vitals

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

  • Speed Index: 9.8 s

    9.8 s

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

  • Time to Interactive: 9.0 s

    9.0 s

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

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

    +20%

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Largest Contentful Paint: 2.6 s

    2.6 s

    Your largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Squirrel Forum is the worlds largest squirrel emergency…”. Most of its time is element render delay (4.1 s).

  • Cumulative Layout Shift: 0.103

    0.103

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

  • 1 image without width and height

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

  • Largest content (LCP) held steady for real visitors

    0%

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

4 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user INP: 98 ms

    98 ms

    Real 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.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Total Blocking Time: 26 ms

    26 ms

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

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.43 g

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

1 checks passed
  • Page weight: 1.5 MB in 49 requests

    1.5 MB

    Your homepage downloads 1.5 MB in 49 requests on a phone: scripts 990 KiB (21), fonts 235 KiB (5) and images 122 KiB (5). That is a lean page.

Accessibility

1 to fix95
  • 3 text elements with low contrast

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

  • Headings skip levels

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

1 checks passed
  • Every image has alt text

    All 3 images in the HTML carry an alt attribute.

SEO

4 to fixGoogle 8575
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (24 characters)

    Your title is only 24 characters: “Welcome - SQUIRREL FORUM”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No XML sitemap

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

  • No robots.txt

    There is no robots.txt at squirrelforum.com/robots.txt, the first file search crawlers ask for.

  • 45 internal links, 11 external

    The homepage links to 45 pages on squirrelforum.com and 11 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Welcome”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

1 to fix69
  • 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.

Other pages

1 to fix95
  • 3 pages without a meta description

    https://squirrelforum.com/donate, https://squirrelforum.com/videos and https://squirrelforum.com/educational-programs have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages slow to respond

    https://squirrelforum.com/donate, https://squirrelforum.com/videos and https://squirrelforum.com/educational-programs took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 21 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    3 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • Every page has a title

    All 3 pages that loaded have a <title>.

Best practices

1 to fixGoogle 7793
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 1,926 words of copy

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

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact”.

  • 1 short form

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

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 2 trust badges.

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

Upkeep, stack and company

Stack

Hosting
Oracle Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on squirrelforum.com, including 16 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