Website review, no card needed

geckoengage.com logo

geckoengage.com website review

Visit site (opens in a new tab)Reviewed 22 October 202625 issues · 74 checks

This review found 25 issues worth fixing on geckoengage.com, 13 of them high impact, across 74 checks. The most urgent: reduce unused JavaScript. 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
5.3 s1.8 sMay 2Oct 174.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.2 s
May 9, 20263.1 s
May 16, 20263.1 s
May 23, 20263.1 s
May 30, 20263.1 s
Jun 6, 20262.9 s
Jun 13, 20262.7 s
Jun 20, 20262.5 s
Jun 27, 20262.4 s
Jul 4, 20262.3 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.2 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.3 s
Sep 12, 20262.5 s
Sep 19, 20263.1 s
Sep 26, 20263.8 s
Oct 3, 20264.7 s
Oct 10, 20264.9 s
Oct 17, 20264.9 s
Real-visitor tap response (INP)75th percentile, phones
349 ms261 msMay 2Oct 17323 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026302 ms
May 9, 2026316 ms
May 16, 2026304 ms
May 23, 2026334 ms
May 30, 2026339 ms
Jun 6, 2026321 ms
Jun 13, 2026334 ms
Jun 20, 2026273 ms
Jun 27, 2026271 ms
Jul 4, 2026271 ms
Jul 11, 2026271 ms
Jul 18, 2026284 ms
Jul 25, 2026271 ms
Aug 1, 2026297 ms
Aug 8, 2026309 ms
Aug 15, 2026309 ms
Aug 22, 2026323 ms
Aug 29, 2026311 ms
Sep 5, 2026274 ms
Sep 12, 2026278 ms
Sep 19, 2026286 ms
Sep 26, 2026273 ms
Oct 3, 2026311 ms
Oct 10, 2026326 ms
Oct 17, 2026323 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 geckoengage.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix54
  • Reduce unused JavaScript

    4.3 s · 836 KiB

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

  • Improve image delivery

    1.9 s · 790 KiB

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

  • Use efficient cache lifetimes

    950 ms · 249 KiB

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

  • Mobile performance score: 54

    54/100

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

  • Google Tag Manager adds 219 ms

    219 ms

    Google Tag Manager costs a phone 219 ms of main-thread work and 337 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Cookiebot and others), adding 656 KiB and 466 ms of main-thread time.

  • Render-blocking requests

    200 ms

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

  • Reduce unused CSS

    150 ms · 28 KiB

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

  • 7 long tasks on the main thread

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

  • Legacy JavaScript

    100 ms · 26 KiB

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

  • 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: 1.9 s

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

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

12 to fix33
  • 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 LCP: 5.2 s

    5.2 s

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

  • Real-user FCP: 3.0 s

    3.0 s

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

  • Real-user TTFB: 1.9 s

    1.9 s

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

  • Largest Contentful Paint: 19.1 s

    19.1 s

    Your largest element takes 19.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Gecko CRM: contacts, conversations, events and in-app calli…”.

  • Time to Interactive: 19.3 s

    19.3 s

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

  • First Contentful Paint: 4.8 s

    4.8 s

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

  • Speed Index: 9.3 s

    9.3 s

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

  • Real-user INP: 390 ms

    390 ms

    Real visitors wait 390 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Largest content (LCP) got 57% slower for real visitors

    +57%

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

  • 16 images without width and height

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

  • Total Blocking Time: 212 ms

    212 ms

    Scripts block taps and scrolling for 212 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-17, real Chrome visitors' tap response (inp) went from 302 ms to 323 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

2 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 22.8 MB in 92 requests

    22.8 MB

    Your homepage downloads 22.8 MB in 92 requests on a phone: images 15.0 MB (42), media 5.9 MB (1) and scripts 1.8 MB (24). Under 2 MB keeps phones on slow connections fast.

  • 8 images over 500 KB

    8 images weigh 13.0 MB together. On a phone connection a single image that size takes seconds.

  • 12 images far larger than shown

    12.3 MB

    12 images are downloaded at several times the size a phone draws them, for example uel-campus-tours-Pathways-Feature-Image-London-UEL-Homepage- at 2,499 px wide, shown at 315 px. Resized copies would save about 12.3 MB.

  • 19 images below the first screen load straight away

    19 images further down the page (14.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 13 images in older formats

    13 images (13.9 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 6.5 g of CO₂ per visit

    6.47 g

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

Accessibility

Google 100100
2 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

Google 100100
  • 28 internal links, 12 external

    The homepage links to 28 pages on geckoengage.com and 12 external pages.

8 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “Connect with students, automate communications and manage recruitment events with Gecko’s student engagement software f…”.

  • One H1 headline

    Your main headline reads: “CRM built for student engagement”.

  • Title: 53 characters

    Your title is a healthy 53 characters: “CRM built for Student Engagement backed by AI | Gecko”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization.

  • 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://geckoengage.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

  • llms.txt published

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

Other pages

100
  • 5 pages slow to respond

    https://geckoengage.com/case-studies, https://geckoengage.com/webinars, https://geckoengage.com/contact, https://geckoengage.com/request-demo and https://geckoengage.com/platform/student-portal took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • 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

1 to fix90
  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • About 1,387 words of copy

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Request a demo”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact” and “Request a demo”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies (measured from a US location before any click).

  • 14 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) 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 geckoengage.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Tag Manager
Hosting
Vercel

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on geckoengage.com, including 17 speed issues and 1 conversion gap. 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