Website review, no card needed

destinyglobal.com logo

destinyglobal.com website review

Visit site (opens in a new tab)Reviewed 6 November 202641 issues · 83 checks

This review found 41 issues worth fixing on destinyglobal.com, 14 of them high impact, across 83 checks. The most urgent: page weight: 51.5 MB in 341 requests. 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 destinyglobal.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. destinyglobal.com at 0.5 s0.5 s
  2. destinyglobal.com at 0.9 s0.9 s
  3. destinyglobal.com at 1.4 s1.4 s
  4. destinyglobal.com at 1.8 s1.8 s
  5. destinyglobal.com at 2.3 s2.3 s
  6. destinyglobal.com at 2.7 s2.7 s
  7. destinyglobal.com at 3.2 s3.2 s
  8. destinyglobal.com at 3.6 s3.6 s

Speed

9 to fix46
  • Improve image delivery

    1.4 s · 3.6 MB

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

  • Render-blocking requests

    1.5 s

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

  • Mobile performance score: 46

    46/100

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

  • Main-thread work: 5.1 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Vimeo and Clarity and others), adding 36.9 MB and 976 ms of main-thread time.

  • Vimeo adds 230 ms

    230 ms

    Vimeo costs a phone 230 ms of main-thread work and 35.7 MB 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.

  • Use efficient cache lifetimes

    700 ms · 1.6 MB

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

  • Reduce unused JavaScript

    930 ms · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 930 ms faster on a phone.

  • Google Tag Manager adds 553 ms

    553 ms

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

  • 16 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 24 KiB

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

  • Legacy JavaScript

    150 ms · 22 KiB

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

  • Font display

    50 ms

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

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 51 ms

    51 ms

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

Core Web Vitals

7 to fix47
  • Largest Contentful Paint: 10.0 s

    10.0 s

    Your largest element takes 10.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WHAT ARE YOU LOOKING TO FLY TO FREEDOM IN?”.

  • Time to Interactive: 34.2 s

    34.2 s

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

  • Speed Index: 15.2 s

    15.2 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Cumulative Layout Shift: 0.17

    0.17

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

  • Total Blocking Time: 366 ms

    366 ms

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

  • 13 images without width and height

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

  • 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

4 to fix38
  • Page weight: 51.5 MB in 341 requests

    51.5 MB

    Your homepage downloads 51.5 MB in 341 requests on a phone: other files 33.8 MB (65), images 14.4 MB (92) and scripts 2.6 MB (103). Under 2 MB keeps phones on slow connections fast.

  • 6 images over 500 KB

    6 images weigh 4.1 MB together. On a phone connection a single image that size takes seconds.

  • 17 images in older formats

    17 images (6.0 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.

  • 7 images below the first screen load straight away

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

  • About 14.6 g of CO₂ per visit

    14.61 g

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

1 checks passed
  • 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 7387
  • 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.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

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

    All page content should be contained by landmarks: 16 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.

  • 2 links without text

    2 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 28 automated accessibility rules passed

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

SEO

6 to fixGoogle 8570
  • No meta description

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

  • Title is short (14 characters)

    Your title is only 14 characters: “Destiny Global”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 13 H1 headlines

    There are 13 <h1> headlines (“What Are You Looking To Fly To Freedom IN?”, “Now Boarding” and “Registration Ends In 112 Days”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 4 links crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 31 internal links, 53 external

    The homepage links to 31 pages on destinyglobal.com and 53 external pages.

3 checks passed
  • Canonical URL set

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

  • 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.destinyglobal.com/wp-sitemap.xml.

AI search readiness

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

  • No llms.txt

    There is no https://www.destinyglobal.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.

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

Other pages

2 to fix70
  • 1 linked page is broken

    Your homepage links to https://www.destinyglobal.com/member-center, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 6 pages without a meta description

    https://www.destinyglobal.com/index.php/how-it-works, https://www.destinyglobal.com/index.php/events-now-boarding, https://www.destinyglobal.com/index.php/shop-freedom-tools, https://www.destinyglobal.com/index.php/global-personal-experience, https://www.destinyglobal.com/index.php/global-rewards and https://www.destinyglobal.com/index.php/next-gen have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages slow to respond

    https://www.destinyglobal.com/index.php/events-now-boarding and https://www.destinyglobal.com/index.php/global-personal-experience took over 3 s to send their HTML from our server.

  • 8 internal pages checked

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

5 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 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 6 pages that loaded have a <title>.

Best practices

4 to fixGoogle 5483
  • 3 third-party cookies

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

  • 2 small tap targets

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

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot access 'interval' before initialization”.

  • 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

1 to fix92
  • Thin social proof

    Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 319 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CALL: 866.760.8255”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Call: 866.760.8255”, “Shop Freedom Tools” and “Start Here”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics, Microsoft Clarity and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 0 email links.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 16 cookies set on arrival

    16

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

  • 20 other companies contacted

    Loading the homepage contacts 20 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 destinyglobal.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 Analytics | Microsoft Clarity
Hosting
Cloudflare

Company

Headquarters
Kerrville

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on destinyglobal.com, including 16 speed issues, 6 SEO 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