Website review, no card needed

gdstour.com logo

gdstour.com website review

Visit site (opens in a new tab)Reviewed 6 November 202633 issues · 82 checks

This review found 33 issues worth fixing on gdstour.com, 13 of them high impact, across 82 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

Full-page screenshot of gdstour.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix44
  • Reduce unused JavaScript

    2.3 s · 319 KiB

    About 319 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

  • Render-blocking requests

    1.0 s

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

  • Mobile performance score: 44

    44/100

    Your mobile performance score is 44. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and adtrafficquality.google and others), adding 590 KiB and 709 ms of main-thread time.

  • Use efficient cache lifetimes

    550 ms · 150 KiB

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

  • Google Tag Manager adds 358 ms

    358 ms

    Google Tag Manager costs a phone 358 ms of main-thread work and 177 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: 3.5 s

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

  • Google/Doubleclick Ads adds 282 ms

    282 ms

    Google/Doubleclick Ads costs a phone 282 ms of main-thread work and 255 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.

  • 13 long tasks on the main thread

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

  • Improve image delivery

    108 KiB

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

  • Font display

    50 ms

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

  • Reduce unused CSS

    21 KiB

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

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 30 ms

    30 ms

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

Core Web Vitals

6 to fix47
  • Largest Contentful Paint: 9.5 s

    9.5 s

    Your largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • First Contentful Paint: 4.7 s

    4.7 s

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

  • Time to Interactive: 9.5 s

    9.5 s

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

  • Speed Index: 6.2 s

    6.2 s

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

  • Total Blocking Time: 525 ms

    525 ms

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

  • Cumulative Layout Shift: 0.115

    0.115

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Images and page weight

100
  • About 0.3 g of CO₂ per visit

    0.32 g

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

4 checks passed
  • Page weight: 1.1 MB in 51 requests

    1.1 MB

    Your homepage downloads 1.1 MB in 51 requests on a phone: scripts 637 KiB (19), images 214 KiB (8) and fonts 213 KiB (6). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 to fixGoogle 7390
  • 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.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 53 images in the HTML carry an alt attribute.

  • 29 automated accessibility rules passed

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

SEO

5 to fixGoogle 8568
  • No meta description

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

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 50 links crawlers can't follow

    50 links have no real href, so search engines can't follow them.

  • Title is short (26 characters)

    Your title is only 26 characters: “Team - Gateway Disc Sports”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 3 problems

    Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 3 problems, for example “WebSite: url is not an absolute URL ("/")”.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 14 internal links, 70 external

    The homepage links to 14 pages on gdstour.com and 70 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is http://gatewayunderground.com/team/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://gatewayunderground.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://gatewayunderground.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

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

Other pages

4 to fix58
  • 1 linked page is broken

    Your homepage links to https://gatewayunderground.com/G82024spiral, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 linked page hidden from search

    https://gatewayunderground.com/recommends/click-up-form is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 10 pages without a meta description

    /, https://gatewayunderground.com/about, https://gatewayunderground.com/team-resources, https://gatewayunderground.com/recommends/click-up-form, https://gatewayunderground.com/resources and https://gatewayunderground.com/blog and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    /, https://gatewayunderground.com/recommends/click-up-form, https://gatewayunderground.com/resources, https://gatewayunderground.com/blog and https://gatewayunderground.com/download-logos have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    /, https://gatewayunderground.com/resources, https://gatewayunderground.com/download-logos and https://gatewayunderground.com/contact have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 3 pages slow to respond

    https://gatewayunderground.com/about, https://gatewayunderground.com/team-resources and https://gatewayunderground.com/recommends/click-up-form took over 3 s to send their HTML from our server.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • 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 a title

    All 10 pages that loaded have a <title>.

Best practices

Google 73100
  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 301 words of visible text.

4 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Shop”, “Download Logos” and “Apply Now”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 2 cookies set on arrival

    2

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

  • 10 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2022.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
HostPapa

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on gdstour.com, including 14 speed issues, 5 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