Website review, no card needed

goape.co.uk logo

goape.co.uk website review

Visit site (opens in a new tab)Reviewed 20 November 202626 issues · 83 checks

This review found 26 issues worth fixing on goape.co.uk, 7 of them high impact, across 83 checks. The most urgent: 9,774 HTML elements. 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
912 ms807 msMay 30Nov 14890 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 2026899 ms
Jun 6, 2026855 ms
Jun 13, 2026844 ms
Jun 20, 2026847 ms
Jun 27, 2026851 ms
Jul 4, 2026858 ms
Jul 11, 2026855 ms
Jul 18, 2026851 ms
Jul 25, 2026857 ms
Aug 1, 2026859 ms
Aug 8, 2026854 ms
Aug 15, 2026859 ms
Aug 22, 2026853 ms
Aug 29, 2026852 ms
Sep 5, 2026854 ms
Sep 12, 2026851 ms
Sep 19, 2026840 ms
Sep 26, 2026824 ms
Oct 3, 2026819 ms
Oct 10, 2026829 ms
Oct 17, 2026850 ms
Oct 24, 2026877 ms
Oct 31, 2026890 ms
Nov 7, 2026900 ms
Nov 14, 2026890 ms
Real-visitor tap response (INP)75th percentile, phones
141 ms125 msMay 30Nov 14135 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026139 ms
Jun 6, 2026139 ms
Jun 13, 2026138 ms
Jun 20, 2026138 ms
Jun 27, 2026138 ms
Jul 4, 2026138 ms
Jul 11, 2026137 ms
Jul 18, 2026135 ms
Jul 25, 2026133 ms
Aug 1, 2026131 ms
Aug 8, 2026130 ms
Aug 15, 2026129 ms
Aug 22, 2026129 ms
Aug 29, 2026128 ms
Sep 5, 2026129 ms
Sep 12, 2026129 ms
Sep 19, 2026128 ms
Sep 26, 2026128 ms
Oct 3, 2026127 ms
Oct 10, 2026127 ms
Oct 17, 2026128 ms
Oct 24, 2026129 ms
Oct 31, 2026130 ms
Nov 7, 2026133 ms
Nov 14, 2026135 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 goape.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix80
  • 9,774 HTML elements

    The page has 9,774 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Reduce unused JavaScript

    1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page.

  • Mobile performance score: 80

    80/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Maps, Intercom and zeropartyforms.com and others), adding 1.2 MB and 453 ms of main-thread time.

  • 7 long tasks on the main thread

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

  • Main-thread work: 2.4 s

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

  • Google Maps adds 134 ms

    134 ms

    Google Maps costs a phone 134 ms of main-thread work and 358 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.

  • Improve image delivery

    230 KiB

    12 images could be 230 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    122 KiB

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

  • Legacy JavaScript

    18 KiB

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

  • Reduce unused CSS

    15 KiB

    About 15 KiB of CSS is downloaded but never applied on this page.

  • Minify JavaScript

    8 KiB

    8 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: 13 ms

    13 ms

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

Core Web Vitals

4 to fix100
  • Time to Interactive: 21.6 s

    21.6 s

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

  • Speed Index: 7.2 s

    7.2 s

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

  • Total Blocking Time: 428 ms

    428 ms

    Scripts block taps and scrolling for 428 ms in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Tap response (INP) held steady for real visitors

    -4%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

8 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.2 s

    1.2 s

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

  • Real-user INP: 138 ms

    138 ms

    Real visitors wait 138 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: 474 ms

    474 ms

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

  • Largest Contentful Paint: 2.0 s

    2.0 s

    Your largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “SAVE 25% ON GIFT EXPERIENCES”.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix53
  • Page weight: 5.3 MB in 175 requests

    5.3 MB

    Your homepage downloads 5.3 MB in 175 requests on a phone: images 3.1 MB (97), scripts 1.9 MB (57) and fonts 224 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    220 KiB

    2 images are downloaded at several times the size a phone draws them, for example award-top-50-best-companies.D8h7tmwF.png at 2,440 px wide, shown at 127 px. Resized copies would save about 220 KiB.

  • 6 images below the first screen load straight away

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

  • 5 images in older formats

    5 images (376 KiB) 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.50 g

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

Accessibility

8 to fixGoogle 8590
  • Unlabelled dropdowns

    1 dropdown has no label.

  • 14 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (23 elements)

    All page content should be contained by landmarks: 23 elements on the page fail this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 form fields without a label

    5 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Elements use prohibited ARIA attributes

    Elements use prohibited ARIA attributes (1 element).

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 157 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

Google 100100
  • 178 internal links, 8 external

    The homepage links to 178 pages on goape.co.uk and 8 external pages.

8 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Discover epic outdoor adventures with Go Ape. Treetop courses, zip lines, and unforgettable days out across 35 UK fores…”.

  • One H1 headline

    Your main headline reads: “Save 25% on Gift Experiences”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Go Ape | Outdoor Adventures, High Ropes & Forest Adventures”.

  • Canonical URL set

    The canonical URL is https://goape.co.uk/.

  • Structured data in place

    Structured data found: Organization 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://goape.co.uk/sitemap-index.xml.

AI search readiness

100
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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,088 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://goape.co.uk/llms.txt (195 KiB, 1 link, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 94 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

2 to fixGoogle 8191
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

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

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

    The homepage carries about 1,769 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: “Book Now” and “Shop experiences”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Book Now”, “Shop experiences” and “Subscribe”.

  • 3 short forms

    3 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies, 2 of them by other companies (measured from a US location before any click).

  • 19 other companies contacted

    Loading the homepage contacts 19 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 goape.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Astro
Analytics
Google Tag Manager
Hosting
Cloudflare

Company

Founded
2001

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 goape.co.uk, including 11 speed 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