Website review, no card needed

socialdiscoverygroup.com logo

socialdiscoverygroup.com website review

Visit site (opens in a new tab)Reviewed 1 November 202631 issues · 75 checks

This review found 31 issues worth fixing on socialdiscoverygroup.com, 8 of them high impact, across 75 checks. The most urgent: render-blocking 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

Real-visitor load time (LCP)75th percentile, phones
5.8 s3.2 sMay 9Oct 245.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.4 s
May 16, 20264.7 s
May 23, 20264.8 s
May 30, 20264.8 s
Jun 6, 20264.8 s
Jun 13, 20264.6 s
Jun 20, 20264.7 s
Jun 27, 20265.0 s
Jul 4, 20265.0 s
Jul 11, 20265.0 s
Jul 18, 20264.7 s
Jul 25, 20264.2 s
Aug 1, 20263.8 s
Aug 8, 20263.5 s
Aug 15, 20263.8 s
Aug 22, 20264.4 s
Aug 29, 20264.5 s
Sep 5, 20264.7 s
Sep 12, 20264.6 s
Sep 19, 20264.6 s
Sep 26, 20265.1 s
Oct 3, 20265.2 s
Oct 10, 20265.5 s
Oct 17, 20265.4 s
Oct 24, 20265.0 s
Real-visitor tap response (INP)75th percentile, phones
214 ms101 msMay 9Oct 24175 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026138 ms
May 16, 2026150 ms
May 23, 2026151 ms
May 30, 2026155 ms
Jun 6, 2026153 ms
Jun 13, 2026138 ms
Jun 20, 2026143 ms
Jun 27, 2026147 ms
Jul 4, 2026144 ms
Jul 11, 2026144 ms
Jul 18, 2026139 ms
Jul 25, 2026127 ms
Aug 1, 2026117 ms
Aug 8, 2026114 ms
Aug 15, 2026130 ms
Aug 22, 2026155 ms
Aug 29, 2026169 ms
Sep 5, 2026173 ms
Sep 12, 2026172 ms
Sep 19, 2026174 ms
Sep 26, 2026193 ms
Oct 3, 2026201 ms
Oct 10, 2026201 ms
Oct 17, 2026199 ms
Oct 24, 2026175 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 socialdiscoverygroup.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. socialdiscoverygroup.com at 0.6 s0.6 s
  2. socialdiscoverygroup.com at 1.1 s1.1 s
  3. socialdiscoverygroup.com at 1.7 s1.7 s
  4. socialdiscoverygroup.com at 2.2 s2.2 s
  5. socialdiscoverygroup.com at 2.8 s2.8 s
  6. socialdiscoverygroup.com at 3.3 s3.3 s
  7. socialdiscoverygroup.com at 3.9 s3.9 s
  8. socialdiscoverygroup.com at 4.4 s4.4 s

Speed

7 to fix89
  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 89

    89/100

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

  • Use efficient cache lifetimes

    150 ms · 601 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and LinkedIn Ads and others), adding 638 KiB and 637 ms of main-thread time.

  • Google Tag Manager adds 304 ms

    304 ms

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

  • Facebook adds 270 ms

    270 ms

    Facebook costs a phone 270 ms of main-thread work and 230 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 JavaScript

    283 KiB

    About 283 KiB of JavaScript is downloaded but never used on this page.

  • 4 long tasks on the main thread

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

  • Reduce unused CSS

    140 ms · 43 KiB

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

  • Legacy JavaScript

    100 ms · 51 KiB

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

  • Improve image delivery

    70 KiB

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

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

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

  • Server response: 12 ms

    12 ms

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

Core Web Vitals

10 to fix67
  • 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: 4.2 s

    4.2 s

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

  • Real-user FCP: 4.7 s

    4.7 s

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

  • Time to Interactive: 8.8 s

    8.8 s

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

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

    +30%

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Speed Index: 5.1 s

    5.1 s

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

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

  • Total Blocking Time: 239 ms

    239 ms

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

  • 2 images without width and height

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

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

    +16%

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

4 checks passed
  • Real-user INP: 137 ms

    137 ms

    Real visitors wait 137 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.

  • 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 “CAREERS”.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • 2 images in older formats

    2 images (100 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 0.3 g of CO₂ per visit

    0.34 g

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

3 checks passed
  • Page weight: 1.2 MB in 37 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 37 requests on a phone: scripts 715 KiB (13), images 413 KiB (11) and stylesheets 48 KiB (3). That is a lean page.

  • 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

3 to fixGoogle 8889
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

2 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

  • 14 automated accessibility rules passed

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

SEO

2 to fixGoogle 10091
  • No structured data

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

  • 3 H1 headlines

    There are 3 <h1> headlines (“SDG solves the problem of loneliness, isolation, …”, “Vacancies for those seeking opportunities and amb…” and “Our events bring together a global SDGang communi…”). One clear main headline is easier for people and search engines.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 15 internal links, 7 external

    The homepage links to 15 pages on socialdiscoverygroup.com and 7 external pages.

6 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Social Discovery Group is the world's largest group of social discovery companies. It unites more than 40 brands, an in…”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “SDG: Social Discovery Group - Global Tech Company”.

  • Canonical URL set

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

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

AI search readiness

1 to fix83
  • 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://socialdiscoverygroup.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.

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

Other pages

2 to fix83
  • 1 page points its canonical at the homepage

    https://socialdiscoverygroup.com/contact declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://socialdiscoverygroup.com/contact all use the title “SDG: Social Discovery Group - Global Tech Company”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages with very little text

    https://socialdiscoverygroup.com/vacancies, https://socialdiscoverygroup.com/sdgang and https://socialdiscoverygroup.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.

  • 7 internal pages checked

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

5 checks passed
  • Linked pages load

    All 7 pages we checked loaded without an error.

  • Every page has a meta description

    All 7 pages that loaded have a meta description.

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

Best practices

1 to fixGoogle 10092
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://assets.mailerlite.com/css/universal.css' from origin 'https://socialdiscoverygroup…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix58
  • 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.

  • Thin social proof

    Social proof on the homepage: 2 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.

  • Only about 70 words

    The homepage has only about 70 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 2 calls to action

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 4 cookies set on arrival

    4

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

  • 12 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on socialdiscoverygroup.com, including 17 speed issues, 2 SEO issues and 4 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